Daniel Veillard wrote: > Thanks everybody for the testing feedback and fixes, in retrospect > I should really had done this in previous releases ! So the third > rc tarball is out, it's likely to be the last one before the release > (within 48 hours): > > ftp://libvirt.org/libvirt/libvirt-0.8.8-rc3.tar.gz > > give it a try ! > Building and passing minimal tests on all supported openSUSE/SLE distros, which in itself is a good exercise of the various configure options. However, I'm trying to run libvirt-tck on openSUSE11.4rc1, qemu0.14rc1, and libvirt 0.8.8rc3 (lots of rc's :)) and getting quite a few failures. The failing qemu invocations look like: 2011-02-15 12:15:05.863: starting up LC_ALL=C PATH=/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/usr/lib64/jvm/jre/bin HOME=/root USER=root LOGNAME=root /usr/bin/qemu-kvm -S -M pc-0.14 -enable-kvm -m 64 -smp 1,sockets=1,cores=1,threads=1 -name tck -uuid 7767756e-9160-41d3-f7a5-0af2aed17d1b -nographic -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/tck.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -boot c -kernel /var/cache/libvirt-tck/os-i686-hvm/vmlinuz -initrd /var/cache/libvirt-tck/os-i686-hvm/initrd -drive file=/var/cache/libvirt-tck/os-i686-hvm/disk.img,if=none,id=drive-virtio-disk0,boot=on,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x2,drive=drive-virtio-disk0,id=virtio-disk0 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 char device redirected to /dev/pts/1 Two devices with same boot index 0 I think qemu0.14 is less tolerable of specifying 2 boot devices, in this case implicitly with -kernel and boot=on for the disk. I'll try to look more later but for now need some sleep. Regards, Jim -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list