Re: [libvirt] [PATCH 0/8] Various KVM PCI device assignment improvements

2009-08-18 Thread Mark McLoughlin
On Tue, 2009-08-18 at 12:23 +0200, Mirko Raasch wrote: > Mark McLoughlin schrieb: > > On Sun, 2009-08-16 at 22:13 +0200, Mirko Raasch wrote: > > > >> ==8823== Invalid read of size 8 > >> ==8823==at 0x420C04: qemuCheckPciHostDevice (qemu_driver.c:1337) > >> ==8823==by 0x4E48CA7: pciResetD

Re: [libvirt] [PATCH 0/8] Various KVM PCI device assignment improvements

2009-08-18 Thread Mirko Raasch
Mark McLoughlin schrieb: On Sun, 2009-08-16 at 22:13 +0200, Mirko Raasch wrote: ==8823== Invalid read of size 8 ==8823==at 0x420C04: qemuCheckPciHostDevice (qemu_driver.c:1337) ==8823==by 0x4E48CA7: pciResetDevice (pci.c:606) ==8823==by 0x4229D5: qemudShutdownVMDaemon (qemu_driver

Re: [libvirt] [PATCH 0/8] Various KVM PCI device assignment improvements

2009-08-17 Thread Mark McLoughlin
On Sun, 2009-08-16 at 22:13 +0200, Mirko Raasch wrote: > ==8823== Invalid read of size 8 > ==8823==at 0x420C04: qemuCheckPciHostDevice (qemu_driver.c:1337) > ==8823==by 0x4E48CA7: pciResetDevice (pci.c:606) > ==8823==by 0x4229D5: qemudShutdownVMDaemon (qemu_driver.c:1479) > ==8823==

Re: [libvirt] [PATCH 0/8] Various KVM PCI device assignment improvements

2009-08-16 Thread Mirko Raasch
Charles Duffy schrieb: Mirko Raasch wrote: How can i use valgrind or some other debugging options with "/etc/init.d/libvirt-bin"? This won't work for valgrind, but the gdb "attach" command will let you connect to (and thus get a stack trace from) a running process. If your libvirtd has PID

Re: [libvirt] [PATCH 0/8] Various KVM PCI device assignment improvements

2009-08-14 Thread Charles Duffy
Mirko Raasch wrote: How can i use valgrind or some other debugging options with "/etc/init.d/libvirt-bin"? This won't work for valgrind, but the gdb "attach" command will let you connect to (and thus get a stack trace from) a running process. If your libvirtd has PID 12054, for instance: $

Re: [libvirt] [PATCH 0/8] Various KVM PCI device assignment improvements

2009-08-14 Thread Mirko Raasch
Daniel P. Berrange schrieb: On Fri, Aug 14, 2009 at 04:09:32PM +0100, Mark McLoughlin wrote: On Fri, 2009-08-14 at 16:41 +0200, Mirko Raasch wrote: Hi, thanks for you improvements. I updated libvirt with git and tried to passthrough two pci devices to a linux guest.

Re: [libvirt] [PATCH 0/8] Various KVM PCI device assignment improvements

2009-08-14 Thread Mark McLoughlin
On Fri, 2009-08-14 at 16:15 +0100, Daniel P. Berrange wrote: > On Fri, Aug 14, 2009 at 04:09:32PM +0100, Mark McLoughlin wrote: > > On Fri, 2009-08-14 at 16:41 +0200, Mirko Raasch wrote: > > > Hi, > > > > > > thanks for you improvements. > > > > > > I updated libvirt with git and tried to passthr

Re: [libvirt] [PATCH 0/8] Various KVM PCI device assignment improvements

2009-08-14 Thread Daniel P. Berrange
On Fri, Aug 14, 2009 at 04:09:32PM +0100, Mark McLoughlin wrote: > On Fri, 2009-08-14 at 16:41 +0200, Mirko Raasch wrote: > > Hi, > > > > thanks for you improvements. > > > > I updated libvirt with git and tried to passthrough two pci devices to a > > linux guest. > > > > > > > >

Re: [libvirt] [PATCH 0/8] Various KVM PCI device assignment improvements

2009-08-14 Thread Mark McLoughlin
On Fri, 2009-08-14 at 16:41 +0200, Mirko Raasch wrote: > Hi, > > thanks for you improvements. > > I updated libvirt with git and tried to passthrough two pci devices to a > linux guest. > > > > > > > > > > > > > In the guest, only

Re: [libvirt] [PATCH 0/8] Various KVM PCI device assignment improvements

2009-08-14 Thread Mirko Raasch
Hi, thanks for you improvements. I updated libvirt with git and tried to passthrough two pci devices to a linux guest. In the guest, only one of them works and after the shutdown of the guest, i got a segfault on the host. libvirtd[1536

[libvirt] [PATCH 0/8] Various KVM PCI device assignment improvements

2009-08-13 Thread Mark McLoughlin
Hi, Here's a fairly mixed set of KVM PCI device assignment improvements: - Add hotplug support - Allow PM reset on multi-function devices - Allow Secondary Bus Reset even if it causes other devices to be reset, so long as those other devices are in use by the same VM or ar