On Tue, Jun 10, 2008 at 12:40:50PM +0100, Richard W.M. Jones wrote: > I've just had a chat with Daniel about whether it's time for a new > release of libvirt. My own primary focus is getting the > virDomain*Peek APIs into a released version so I can use them from > Fedora. > > libvirt 0.4.2 was released on 8th Apr 2008. > > I just scanned the changelog and there's a pretty long list of new > features: > [snip] > So is it time for a release? Yes, I guess it makes sense :-) I will try to push a new release before the end of the week. Do we have patches pending which should be incorporated before ? I yes please (re)push them,

No, this is not developed enough.

It doesn't support QEMU,

it doesn't support XM,

and there's not test cases.

-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREKAAYFAkhOimMACgkQYH1+F2Rqwn3j4wCgi4NwAd+QnUNMyue65+EOOhDZ yPAAnisPr27LABsSEPJ7DfstzCSQtHuG =/QRT -----END PGP SIGNATURE-----

Daniel Veillard wrote: > On Tue, Jun 10, 2008 at 12:40:50PM +0100, Richard W.M. Jones wrote: >> So is it time for a release? > > Yes, I guess it makes sense :-) > I will try to push a new release before the end of the week. > Do we have patches pending which should be incorporated before ? > I yes please (re)push them, > If the last two patches I posted could be pushed, I'd appreciate it. They are needed for the storage driver (Rich already ACK'd them).

https://www.redhat.com/archives/libvir-list/2008-June/msg00042.html https://www.redhat.com/archives/libvir-list/2008-June/msg00082.html Thanks,

I've just had a chat with Daniel about whether it's time for a new release of libvirt. My own primary focus is getting the virDomain*Peek APIs into a released version so I can use them from Fedora. libvirt 0.4.2 was released on 8th Apr 2008. I just scanned the changelog and there's a pretty long list of new features: - Support for serial and parallel devices in Xend - Network interface model in QEMU network devs - SetVcpus, DomainGetMaxVcpus, VCPU pinning in QEMU - Disk "bus"es - Support for Xenner - Deprecate conn/dom/net fields in virterror - HTML documentation completely restructured - MinGW fixes - Memory leaks plugged - Added HACKING file and lots of work on unifying syntax and methods used in the code base to a single standard - Lots of LXR changes - virDomain*Peek APIs - and of course many bug fixes So is it time for a release? Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top -- Libvir-list mailing list Libvir-list(a)redhat.com https://www.redhat.com/mailman/listinfo/libvir-list

On Tue, Jun 10, 2008 at 09:13:06PM +0900, Atsushi SAKAI wrote: > Would you commit this patch? > https://www.redhat.com/archives/libvir-list/2008-June/msg00031.html I'm not sure that I understand the use of this patch. Is this so that we can specify devices in /etc/xen files like 'phy:' or 'file:' (ie. without any actual device or filename following)? Then according to http://xenbits.xensource.com/xen-unstable.hg?rev/0a8fc1a62796 XenD will give an error? Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into Xen guests. http://et.redhat.com/~rjones/virt-p2v

On Tue, Jun 10, 2008 at 09:36:50PM +0900, Atsushi SAKAI wrote: > When the user forget to add "phy" or "file" in VM image path, > The error handled on libvirt previously without error message now. > > This patch change the VM image path error handling from libvirt to Xend. > For this purpose, libvirt just pass VM image path without check. > Xend reports error with following Xen patch. Yes, I think it looks fine. Any comments Dan?

On Tue, Jun 10, 2008 at 01:17:48PM +0100, Richard W.M. Jones wrote: > On Tue, Jun 10, 2008 at 09:13:06PM +0900, Atsushi SAKAI wrote: > > Would you commit this patch? > > https://www.redhat.com/archives/libvir-list/2008-June/msg00031.html > > I'm not sure that I understand the use of this patch. Yes, I'm not sure why its needed either. It is only touching the xm_internal driver, which is only active for Xen <= 3.0.3. Any new changeset will not impact it, because we'll be using the builtin inactive domain management.