On Sat, Oct 18, 2014 at 12:03:23AM +0200, Wouter Verhelst wrote:
> Hi all,
>
> (added rjones from nbdkit fame -- hi there)
[I'm happy to implement whatever you come up with, but I've added
Florian Weimer to CC who is part of Red Hat's product security group]
> So I think the following would make
Recently, I tryed to recompile libvirt in a clean build system, but the
process failed when it tryed to compile the test v:iridentitytest. See the
error below:
[...]
CC viridentitytest.o
CCLD viridentitytest
/usr/bin/ld: viridentitytest.o: undefined reference to symbol
On 04/01/2014 07:34 PM, Solly Ross wrote:
I finally took time to look at this patch again. Sorry for the extreme
delay. Overall, this patch looks decent; I'll probably touch up the
findings I make below and apply it if the rest of the series is okay.
> This commit extracts the parsing logic from
Hi all,
(added rjones from nbdkit fame -- hi there)
So I think the following would make sense to allow TLS in NBD.
This would extend the newstyle negotiation by adding two options (i.e.,
client requests), one server reply, and one server error as well as
extend one existing reply, in the followi
The test case adds passthrough hostdevices and interface of
type hostdev. The test case tests the address for multifunction,
multibus, and pci bridges within the spapr-vfio domain.
Signed-off-by: Shivaprasad G Bhat
Signed-off-by: Pradipta Kumar Banerjee
---
docs/schemas/domaincommon.rng
On pseries, the vfio host devices attach to the spapr-pci-vfio domain
instead of the default emulated domain.
So, for a host device belonging to iommu group(say) 3, would need below
host bridge.
-device spapr-pci-vfio-host-bridge,iommu=3,id=vfiohostbridge3,index=1
The vfio device then needs
This patch will get the iommu group for host devices by XML configuration
of the vfio host bridge controller or from the sysfs.
Like other architectures, the devices in the iommu group need to be
detached manually before the guest is created.
On pseries, the iommu group can be shared by multiple h
The mode attribute is required for the source element of vhost-user. Thus
virDomainNetDefFormat should always generate a xml with it, and
not only when the mode is server.
The commit fixes the issue. And it adds a vhostuser interface in 'client' mode
to qemuxml2argv-net-vhostuser.(args|xml) to tes
To support VFIO for PPC, it is needed spapr-vfio-pci-host-bridge in
QEMU. This patch is to add one capability for it.
Signed-off-by: Li Zhang
Signed-off-by: Shivaprasad G Bhat
---
src/qemu/qemu_capabilities.c |2 ++
src/qemu/qemu_capabilities.h |1 +
2 files changed, 3 insertions(+)
di
The following series of patches enable spapr-pci-vfio-host-bridge
controllers on PPC64-pseries machine which is required for supporting
host device passthrough using VFIO.
There were some initial enablement work on the same at
http://www.redhat.com/archives/libvir-list/2013-September/msg00838.ht
VIR_TEST_DEBUG=2 ./qemuxml2argvtest generates the following output:
409) QEMU XML-2-ARGV shmem-invalid-size
... Got expected error: unsupported configuration: ivshmem device is not \
supported with this QEMU binary
OK
410) QEMU XML-2-ARGV shmem-small-size
... Got expected error: unsupport
Hi,
On Fri, 2014-10-17 at 00:42 +0100, xen.org wrote:
> *** Found and reproduced problem changeset ***
>
> Bug is in tree: libvirt git://libvirt.org/libvirt.git
> Bug introduced: 24c160376275b7d31f71fbde83af8183cbf744a7
> Bug not present: 69f7b67d55316ab7b28fb904b346943497b856a1
The Xen
12 matches
Mail list logo
