On Tue, 3 Jul 2018 13:32:29 +0200 Kevin Wolf <kwolf@xxxxxxxxxx> wrote: > > > > Has serial/gemoetry been fixed meanwhile and will it make it into the > > > > next release? > > > > > > I cannot find an archive that has it, but it is on the libvirt mailing > > > list as " [PATCH v3] qemu: format serial and geometry on frontend disk device". > > > Review seems done, but it has missed libvirt 4.5 which was released today. > > > > Just posted latest version here: > > > > https://www.redhat.com/archives/libvir-list/2018-July/msg00130.html > > > > It will be in the next release on ~ Aug 1st > > It would have been a lot nicer to have it the July release because this > means that we'll have the released libvirt broken during almost the > whole rc phase of QEMU 3.0, but the release is planned for Aug 8th the > earliest, so I guess we're still okay. People using QEMU from git will > just need libvirt from git as well. Speaking as an innocent* bystander: I would usually presume that I can use any recent libvirt to test current QEMU, even bleeding edge. In this case, not even the latest released libvirt version will be fine, I would also need to build libvirt from git (which is probably not something a non-libvirt developer will usually do). If everything goes according to plan, I can only test QEMU with a released libvirt version at the very tail end of hardfreeze, where only release blockers are appropriate. I think it would be really beneficial to general QEMU test coverage to push deleting this option back a release or two. We should make testing QEMU in conjunction with libvirt as uncomplicated as possible. *YMMV -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
