[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5033371C.9040703@msgid.tls.msk.ru>
Date: Tue, 21 Aug 2012 11:22:04 +0400
From: Michael Tokarev <mjt@....msk.ru>
To: Tomas Racek <tracek@...hat.com>
CC: Borislav Petkov <borislav.petkov@....com>,
kvm-devel <kvm@...r.kernel.org>,
Marcelo Tosatti <mtosatti@...hat.com>, qemu-devel@...gnu.org,
linux-kernel@...r.kernel.org, Avi Kivity <avi@...hat.com>,
Anthony Liguori <anthony@...emonkey.ws>,
"H. Peter Anvin" <hpa@...ux.intel.com>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Alan Cox <alan@...ux.intel.com>
Subject: Re: [Qemu-devel] x86, nops settings result in kernel crash
On 20.08.2012 21:13, Tomas Racek wrote:
[]
Can we trim the old, large and now not-so-relevant discussion please? ;)
> I can provide you with more different traces if it can help. But I thought that maybe it will be more useful for you to try it on your own. So I've prepared some minimal debian installation which you could download here (apx 163M bzipped):
>
> http://fi.muni.cz/~xracek/debian.img.bz2
>
> Password:
> root/asdfgh
>
> Here is my config for guest kernel:
>
> http://fi.muni.cz/~xracek/config
>
> I use
>
> qemu-kvm -m 1500 -hda debian.img -kernel linux/arch/x86/boot/bzImage -append "root=/dev/sda1"
Um. I'd expect the image to be self-contained, no external kernel.
I wanted to do a quick test to see if it fails on my machine too,
d/loaded debian.img.bz2 but there's no kernel. So.. no quick test
for you ;)
> After logging in just run "sh runtest.sh". This leads to crash in my case (host: Intel Core i5-2540M, kernel 3.5.2-1.fc17.x86_64, qemu 1.0.1).
With all the above, this "runtest.sh" is informationally equal to
your disk image.
/mjt
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists