On Sun, Mar 04, 2018 at 04:47:10PM -0500, taii...@gmx.com wrote:
> I am getting an error.
>
> error: unsupported configuration: IOMMU device: 'intel' is only supported
> with Q35 machines
>
>
> test
> 2
> 2
>
> hvm
Hi, I'm not sure whether this is still relevant, but ^this element i
I am getting an error.
error: unsupported configuration: IOMMU device: 'intel' is only
supported with Q35 machines
test
2
2
hvm
hvm
pc-q35-2.11 is listed as supported in "qemu-system-x86_64 -machine help"
I have also tried many of the other
On Wed, 28 Feb 2018 20:25:11 -0500
"taii...@gmx.com" wrote:
> On 02/26/2018 04:14 PM, Alex Williamson wrote:
>
> > On Mon, 26 Feb 2018 02:12:39 -0500
> > "taii...@gmx.com" wrote:
> >
> >> How would I with libvirt/qemu and AMD-Vi v1.26 restrict device
> >> communication inside a VM as it would
On 02/26/2018 04:14 PM, Alex Williamson wrote:
On Mon, 26 Feb 2018 02:12:39 -0500
"taii...@gmx.com" wrote:
How would I with libvirt/qemu and AMD-Vi v1.26 restrict device
communication inside a VM as it would be on the host?
https://libvirt.org/formatdomain.html#elementsIommu
(Yes, you can u
On Mon, 26 Feb 2018 02:12:39 -0500
"taii...@gmx.com" wrote:
> How would I with libvirt/qemu and AMD-Vi v1.26 restrict device
> communication inside a VM as it would be on the host?
https://libvirt.org/formatdomain.html#elementsIommu
(Yes, you can use Intel IOMMU emulation backed by an AMD IOMM
How would I with libvirt/qemu and AMD-Vi v1.26 restrict device
communication inside a VM as it would be on the host?
I am under the assumption that this doesn't happen and that for instance
with a router/firewall you would have the following dilemma:
Bare metal - IOMMU protects you from netwo