On 2012-12-26 09:49, Osier Yang wrote:
> Generally, this means qemu crashed, can you check the guest log
> to see if there is any useful info?
>
> /var/log/libvirt/qemu/$guest.log
>
> PS: perhaps we should grab the stderr of qemu process and dump it
> to user instead.
There's nothing there about the issue at hand, but the full QEMU command
is there. So I tried executing it (with "fd=41," removed from the
"-net tap,…" option):
# /usr/bin/kvm -S -M pc-0.12 -enable-kvm \
> -m 134217728 -smp 1,sockets=1,cores=1,threads=1 \
> -name test1 -uuid 393fb861-6fbf-67e7-9b98-16511b17ea0c \
> -nographic -nodefaults \
> -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/test1.monitor,server,nowait \
> -mon chardev=monitor,mode=readline \
> -rtc base=utc -no-reboot -boot c \
> -kernel current/images/netboot/debian-installer/amd64/linux \
> -initrd current/images/netboot/debian-installer/amd64/initrd.gz \
> -append 'method=http://http.us.debian.org/debian/dists/squeeze/main/installer-amd64/ auto url=http://10.0.0.128/baldr1.cfg' \
> -drive file=/mnt/data/vms/test1.img,if=none,id=drive-virtio-disk0,boot=on,format=raw \
> -device virtio-blk-pci,bus=pci.0,addr=0x3,drive=drive-virtio-disk0,id=virtio-disk0 \
> -device virtio-net-pci,vlan=0,id=net0,mac=52:54:00:4b:97:f4,bus=pci.0,addr=0x2 \
> -net tap,vlan=0,name=hostnet0 \
> -chardev pty,id=serial0 -device isa-serial,chardev=serial0 \
> -usb -device usb-tablet,id=input0 \
> -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4
char device redirected to /dev/pts/5
# echo ${?}
134
So it looks live I've reproduced the issue outside of libvirtd. But I
don't know what an exit status of 134 from QEMU means. Any ideas?
Thanks,
--
Patrick "P. J." McDermott
http://www.pehjota.net/
http://www.pehjota.net/contact.html
_______________________________________________
libvirt-users mailing list
libvirt-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvirt-users
