Re: [libvirt] make not invoking rpcgen remote_protocol.x

2008-11-11 Thread Kenneth Nagin
>Ben Guthro <[EMAIL PROTECTED]> wrote on 10/11/2008 18:03:07: > from the top level, you could do a > make -C src remote_protocol.c > > This should re-generate both .c and .h files from the .x > make -C src remote_protocol.c does not work. This is the error printout:. [EMAIL PROTECTED] libvirt]$ ma

Re: >>: [libvirt] OpenVZ capabilites in LibVIRT

2008-11-11 Thread Daniel P. Berrange
On Tue, Nov 11, 2008 at 04:15:35PM +0300, Anton Protopopov wrote: > > > > virsh # undefine 3005 > > libvir: OpenVZ error : Domain not found > > Domain 3005 has been undefined > > > > It really removes domain from file system, but why does it throw that error > > message? > > > I think, that it is a

Re: [libvirt] [PATCH]: Implement Qemu/KVM live migration

2008-11-11 Thread Daniel P. Berrange
On Thu, Nov 06, 2008 at 03:10:29PM +0100, Chris Lalancette wrote: > All, > Attached is a patch to implement Qemu/KVM live migration in libvirt. Now > that upstream Qemu has settled on an interface that is friendly to libvirt > (i.e. > one that doesn't block the monitor on -incoming), we can

Re: [libvirt] [PATCH] 0/7 host ("node") device enumeration - completed submission

2008-11-11 Thread Daniel P. Berrange
On Thu, Nov 06, 2008 at 09:32:17PM -0500, David Lively wrote: > Daniel(s) - > In the attached set of patches, I've merged in DanB's reworking of the > headers, etc. and adjusted my code accordingly. I've also renamed > "NodeDriver" to "DeviceMonitor", as discussed with DanV, and added a > --cap

[libvirt] [PATCH] Xen Events Updated

2008-11-11 Thread Ben Guthro
This version of the Xen-Events patch goes a step further than the last version, and now emits the following domain events: STARTED STOPPED ADDED REMOVED This is accomplished by monitoring /etc/xen, and taking advantage of what seemed to be dormant code in the XM driver. By re-enabling the "conf

Re: >>: [libvirt] OpenVZ capabilites in LibVIRT

2008-11-11 Thread Anton Protopopov
Hi - yeah, i've already read that thread and known it was a bug. Just needed a > confirmation that it was going to be fixed in next release. So may be my > question will be a bit indelicate, but is there a hope to see this release > by the end of november? > Yes, I think > > virsh # undefine 300