starting line:
/usr/bin/qemu-x86_64 -chardev
socket,id=qmp,path=/var/run/qemu-server/103.qmp,server,nowait -mon
chardev=qmp,mode=control -pidfile /var/run/qemu-server/103.pid
-daemonize -usbdevice tablet -name kvmcrash -smp sockets=1,cores=8
-nodefaults -boot menu=on -vga cirrus -k de -device
virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5 -drive
file=iscsi://10.0.255.100/iqn.1986-03.com.sun:02:8a9019a4-4aa3-cd8a-f723-f05db9085ef9/0,if=none,id=drive-scsi1,cache=writethrough,aio=native
-device
scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=1,drive=drive-scsi1,id=scsi1
-drive
file=iscsi://10.0.255.100/iqn.1986-03.com.sun:02:8a9019a4-4aa3-cd8a-f723-f05db9085ef9/2,if=none,id=drive-virtio0,cache=writethrough,aio=native
-device virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa
-drive
file=iscsi://10.0.255.100/iqn.1986-03.com.sun:02:8a9019a4-4aa3-cd8a-f723-f05db9085ef9/1,if=none,id=drive-scsi0,cache=writethrough,aio=native
-device
scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=102
-m 4096 -netdev
type=tap,id=net0,ifname=tap103i0,script=/var/lib/qemu-server/pve-bridge,vhost=on
-device
virtio-net-pci,mac=BA:5B:86:AD:14:3A,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300
I've also needed this patch:
https://github.com/stefanha/qemu/commit/d3e3082e6fe63d45cea2d92c41ad148dccf1b63e
otherwise kvm crash while hardware detection of ubuntu / debian.
Greets,
Stefan
Am 09.08.2012 09:19, schrieb Paolo Bonzini:
Il 09/08/2012 09:07, Stefan Priebe ha scritto:
Yes should be possible. guest is Debian or Ubuntu. I couldn't find a
tag for V1.1.1 which I ran from source. So where to start bisect?
You can start from the v1.1.0 tag.
Can you give the command line, perhaps it is enough to reproduce?
Paolo
Stefan
Am 09.08.2012 um 09:01 schrieb Paolo Bonzini <[email protected]>:
Il 09/08/2012 08:13, Stefan Priebe ha scritto:
i really would like to test with actual git. But my VMs run
awfully SLOW with actual git version. Boot process prints one
line every two seconds. So i can't test. Is there a patch or
backport for this problem?
Hmm, no, I haven't seen it reported either... How are you running
the VMs? What guest is in there?
Also, perhaps you could try bisecting the issue? I'm going on
holiday next week, but I'm sure other people could help.
Paolo
