On Wed, Dec 22, 2010 at 10:02 AM, Peter Lieven <p...@dlh.net> wrote: > If I start a VM with the following parameters > qemu-kvm-0.13.0 -m 2048 -smp 2 -monitor tcp:0:4014,server,nowait -vnc :14 > -name 'ubuntu.test' -boot order=dc,menu=off -cdrom > ubuntu-10.04.1-desktop-amd64.iso -k de > > and select memtest in the Ubuntu CD Boot Menu, the VM immediately resets. > After this reset there happen several errors including graphic corruption or > the qemu-kvm binary > aborting with error 134. > > Exactly the same scenario on the same machine with qemu-kvm-0.12.5 works > flawlessly. > > Any ideas?
You could track down the commit which broke this using git-bisect(1). The steps are: $ git bisect start v0.13.0 v0.12.5 Then: $ ./configure [...] && make $ x86_64-softmmu/qemu-system-x86_64 -m 2048 -smp 2 -monitor tcp:0:4014,server,nowait -vnc :14 -name 'ubuntu.test' -boot order=dc,menu=off -cdrom ubuntu-10.04.1-desktop-amd64.iso -k de If memtest runs as expected: $ git bisect good otherwise: $ git bisect bad Keep repeating this and you should end up at the commit that introduced the bug. Stefan -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
