Re: KVM segfaults with 3.5 while installing ubuntu 12.04

[Stefan Priebe]

Am 05.08.2012 12:29, schrieb Avi Kivity:
> On 08/05/2012 01:08 PM, Stefan Priebe wrote:
> > Am 01.08.2012 11:53, schrieb Avi Kivity:
> > > On 08/01/2012 12:42 PM, Stefan Priebe - Profihost AG wrote:
> > > > Am 01.08.2012 11:33, schrieb Avi Kivity:
> > > > > > So here are 3 backtraces from booting the rescue system:
> > > > > > http://pastebin.com/raw.php?i=xCy2pEcP
> > > > > >
> > > > > > To me they all look the same.
> > > > >
> > > > > They are.  What version of qemu are you using?
> > > >
> > > > latest stable-1.1 branch (1.1.1) - which works fine with latest RHEL6
> > > > kernel.
> > >
> > > This could be due to a kernel bug, or due to a different code path taken
> > > in qemu because of differing features exposed to kvm.
> > >
> > > Please try qemu-kvm.git master and report.
> >
> > qemu-kvm.git master just hangs after the 2nd screen with using 100% CPU
> > and doing nothing... so i can't test with qemu-kvm.master
>
> Please provide your command line and I will try to reproduce.

ulimit -c unlimited; /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 -drive 
file=/dev/VGiSCSItarget0/vm-103-disk-1,if=none,id=drive-virtio0,aio=native,cache=none 
-device 
virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100 
-drive 
file=/var/lib/vz/template/iso/ubuntu-12.04-server-amd64.iso,if=none,id=drive-ide0,media=cdrom,aio=native 
-device ide-cd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=200 
-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

> Which iso image are you running?
ubuntu-12.04-server-amd64.iso
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/