[libvirt] What about next release ?
We are getting quite close to the end of the month, if we want to stick to the 'end of month release' I guess we need to enter the freeze for 1.0.5 at the end of the week say Friday, and then push the release, assuming there is no big problem on Thursday next week (May 2, I could probably do it on May 1 but most civilized people will enjoy the May 1 day off so that should not change that much ;-) Daniel -- Daniel Veillard | Open Source and Standards, Red Hat veillard@redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | virtualization library http://libvirt.org/
On Tue, Apr 23, 2013 at 08:53:00PM +0800, Daniel Veillard wrote:
We are getting quite close to the end of the month, if we want to stick to the 'end of month release' I guess we need to enter the freeze for 1.0.5 at the end of the week say Friday, and then push the release, assuming there is no big problem on Thursday next week (May 2, I could probably do it on May 1 but most civilized people will enjoy the May 1 day off so that should not change that much ;-)
Yep, May 2nd sounds fine to me Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
On 23.04.2013 14:53, Daniel Veillard wrote:
We are getting quite close to the end of the month, if we want to stick to the 'end of month release' I guess we need to enter the freeze for 1.0.5 at the end of the week say Friday, and then push the release, assuming there is no big problem on Thursday next week (May 2, I could probably do it on May 1 but most civilized people will enjoy the May 1 day off so that should not change that much ;-)
Daniel
Yep. works for me. And I think it's the best time to post and review my patchset which moves OOM reporting to VIR_ALLOC, introduces VIR_STRDUP, and so on (of course, I won't push it until after the release). Michal
On 23.04.2013 14:53, Daniel Veillard wrote:
We are getting quite close to the end of the month, if we want to stick to the 'end of month release' I guess we need to enter the freeze for 1.0.5 at the end of the week say Friday, and then push the release, assuming there is no big problem on Thursday next week (May 2, I could probably do it on May 1 but most civilized people will enjoy the May 1 day off so that should not change that much ;-)
Daniel
On the other hand, I just found we are unable to start a guest with virtio-serial, e.g. a guest agent: <domain> ... <devices> ... <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/f17.agent'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> </devices> </domain> Throws me an error: qemu-system-x86_64: -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0: Bus 'virtio-serial0.0' is full qemu-system-x86_64: -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0: Bus 'virtio-serial0.0' not found I am currently chasing the root cause down. Michal
participants (3)
-
Daniel P. Berrange -
Daniel Veillard -
Michal Privoznik