Re: [libvirt] [Qemu-devel] [PATCH v7 0/4] Add Mediated device support

On 9/2/2016 10:18 AM, Michal Privoznik wrote: > On 01.09.2016 18:59, Alex Williamson wrote: >> On Thu, 1 Sep 2016 18:47:06 +0200 >> Michal Privoznik wrote: >> >>> On 31.08.2016 08:12, Tian, Kevin wrote: > From: Alex Williamson [mailto:alex.william...@redhat.com] >

Re: [libvirt] [PATCH] conf: Fix initialization value of 'multi' in PCI address

Ping On 8/15/2016 12:22 PM, Xian Han Yu wrote: The 'multi' element in PCI address struct used as 'virTristateSwitch', and its default value is 'VIR_TRISTATE_SWITCH_ABSENT'. Current PCI process use 'false' to initialization 'multi', which is ambiguously for assignment or comparison. This patch

Re: [libvirt] [Qemu-devel] [PATCH v7 0/4] Add Mediated device support

On 01.09.2016 18:59, Alex Williamson wrote: > On Thu, 1 Sep 2016 18:47:06 +0200 > Michal Privoznik wrote: > >> On 31.08.2016 08:12, Tian, Kevin wrote: From: Alex Williamson [mailto:alex.william...@redhat.com] Sent: Wednesday, August 31, 2016 12:17 AM Hi

Re: [libvirt] qapi DEVICE_DELETED event issued *before* instance_finalize?!

On 02.09.2016 01:11, Alex Williamson wrote: > Hey, > > > It appears that DEVICE_DELETED only means the VM is done with the > device but libvirt is interpreting it as QEMU is done with the device. > Which is correct? Do we need a new event or do we need to fix the > ordering of this event? An

[libvirt] qapi DEVICE_DELETED event issued *before* instance_finalize?!

Hey, I'm out of my QOM depth, so I'll just beg for help in advance. I noticed in testing vfio-pci hotunplug that the host seems to be trying to reclaim the device before QEMU is actually done with it, there's a very short race where libvirt has seen the DEVICE_DELETED event and tries to unbind

Re: [libvirt] [PATCH v7 0/4] Add Mediated device support

On Thu, 1 Sep 2016 23:52:02 +0530 Kirti Wankhede wrote: > Alex, > Thanks for summarizing the discussion. > > On 8/31/2016 9:18 PM, Alex Williamson wrote: > > On Wed, 31 Aug 2016 15:04:13 +0800 > > Jike Song wrote: > > > >> On 08/31/2016 02:12 PM,

Re: [libvirt] Querying block device job status and semantics of virDomainBlockJobInfo()

On 09/01/2016 08:57 AM, Kashyap Chamarthy wrote: > So, I'm trying to understand how libvirt reports the "cur" and "end" > values. I've read the virDomainBlockJobInfo() struct, it wasn't crystal > clear. It states: > > /* > * The following fields provide an indication of block job progress.

Re: [libvirt] [PATCH v7 0/4] Add Mediated device support

Alex, Thanks for summarizing the discussion. On 8/31/2016 9:18 PM, Alex Williamson wrote: > On Wed, 31 Aug 2016 15:04:13 +0800 > Jike Song wrote: > >> On 08/31/2016 02:12 PM, Tian, Kevin wrote: From: Alex Williamson [mailto:alex.william...@redhat.com] Sent:

Re: [libvirt] [Qemu-devel] [PATCH v7 0/4] Add Mediated device support

On Thu, 1 Sep 2016 18:47:06 +0200 Michal Privoznik wrote: > On 31.08.2016 08:12, Tian, Kevin wrote: > >> From: Alex Williamson [mailto:alex.william...@redhat.com] > >> Sent: Wednesday, August 31, 2016 12:17 AM > >> > >> Hi folks, > >> > >> At KVM Forum we had a BoF session

Re: [libvirt] [Qemu-devel] [PATCH v7 0/4] Add Mediated device support

On 31.08.2016 08:12, Tian, Kevin wrote: >> From: Alex Williamson [mailto:alex.william...@redhat.com] >> Sent: Wednesday, August 31, 2016 12:17 AM >> >> Hi folks, >> >> At KVM Forum we had a BoF session primarily around the mediated device >> sysfs interface. I'd like to share what I think we

Re: [libvirt]

On 09/01/2016 04:05 AM, Moshe Levi wrote: Hi, In OpenStack we have a port type macvtap. Mavtap port is just a tap device connected to VF. In Libvirt the guest xml look like In the hypervisor we can see that the mac of the VF which is fa:16:3e:f3:9b:e8 - is set

Re: [libvirt] [PATCH v2] virsh: use virConnectGetDomainCapabilities with maxvcpus

On 07/29/2016 09:49 AM, Shivaprasad G Bhat wrote: > virsh maxvcpus --type kvm output is useless on PPC. Also, in > commit e6806d79 we documented not rely on virConnectGetMaxVcpus > output. Fix the maxvcpus to use virConnectGetDomainCapabilities > now to make it useful. The call is made to use

[libvirt] Querying block device job status and semantics of virDomainBlockJobInfo()

In OpenStack Nova, we're trying to analyze a potential race condition[0]. The operation flow is something like: perform a live shallow blockRebase(), check for progress with blockJobInfo(), followed by a blockJobAbort() (QMP 'block-job-cancel') to get a live point-in-time snapshot, then convert

[libvirt] [libvirt-php][PATCH] m4: Check for php modules more wisely

I've got two version of PHP installed on my system, however one of them has imagick the other one doesn't. During configure I've noticed that wrong assumption has been made. Configure script wrongly assumed the plugin missing. This is because for detecting php plugins we use plain 'php -m | grep

Re: [libvirt] [PATCH] qemu: fix state change lock held by remoteDispatchDomainBlockJobAbort forever

On Thu, Sep 01, 2016 at 14:46:01 +0800, Xiubo Li wrote: > When doing the snapshot using the script below: > = > !#/bin/bash > virsh blockjob $instance_name vdX --abort > virsh undefine $instance_name > qemu-img create -f qcow2 -o

[libvirt]

Hi, In OpenStack we have a port type macvtap. Mavtap port is just a tap device connected to VF. In Libvirt the guest xml look like

[libvirt] [PATCH] qemu: fix state change lock held by remoteDispatchDomainBlockJobAbort forever

When doing the snapshot using the script below: = !#/bin/bash virsh blockjob $instance_name vdX --abort virsh undefine $instance_name qemu-img create -f qcow2 -o backing_file=$diskfile,size=$size $path/$uuid.dlta virsh blockcopy --domain $instance_name vdX