Re: 1.4.0 memballoon bug?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Quoting Michal Privoznik (mprivozn@xxxxxxxxxx):
> On 05.04.2013 21:22, Serge Hallyn wrote:
> > Hi,
> > 
> > When I run
> > 
> > virsh -c qemu:///system domxml-to-native qemu-argv /tmp/qatest.xml
> > 
> > from 1.4.0 with the qatest.xml below (which has no memballoon
> > device specified), I get an 'unspecified error'.  Some printf
> > debugging shows that virDomainDefParseXML is automatically
> > adding a virtio memballoon device, but that its
> > memballoon->info.type is 0, not the 1 or 8 which is required at
> > qemuBuildMemballoonDevStr().
> > 
> > This didn't happen at 1.2.0, but I'm not sure where the
> > error was introduced, as I don't see any suspicious changes around
> 
> You can run git-bisect to find which commit introduced this 'feature' in
> case it is not obvious from git-log.

Yeah I just needed to first git upstream to reliably compile (with
patch/unpatch around git bisect operations)

git bisect points to:
[608512b24a89d9865e402905b2dbbfd1c8a0e83e] S390: QEMU driver support for CCW addresses

-serge

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list




[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]