From: "André Weidemann" <Andre.Weidemann@web.de>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: VM not booting anymore after Ubuntu upgrade
Date: Wed, 04 Aug 2010 13:42:26 +0200 [thread overview]
Message-ID: <4C595222.3060406@web.de> (raw)
In-Reply-To: <4C594F04.5010106@redhat.com>
On 04.08.2010 13:29, Avi Kivity wrote:
> On 08/04/2010 02:22 PM, André Weidemann wrote:
>> On 04.08.2010 12:31, Avi Kivity wrote:
>>> On 08/04/2010 10:38 AM, André Weidemann wrote:
>>>>
>>>>> Please enable ftrace:
>>>>>
>>>>> # mount -t debugfs debugfs /sys/kernel/debug
>>>>> # cd /sys/kernel/debug/tracing
>>>>> # echo 100000 > buffer_size_kb
>>>>> # echo kvm > set_event
>>>>> # echo 1 > tracing on
>>>>>
>>>>> run the guest and kill qemu immediately when you get to the blank
>>>>> screen
>>>>> (use SDL so you can see it immediately). Then post
>>>>> /sys/kernel/debug/trace somewhere.
>>>>
>>>> I ran the trace and put the ouptut here:
>>>> http://ilpss8.dyndns.org/~andrew/qemu-kvm.trace.gz
>>>>
>>>
>>>
>>> <...>-26008 [001] 5175193.046430: kvm_exit: reason exception rip 0xfc842
>>> <...>-26008 [001] 5175193.046430: kvm_page_fault: address fc842
>>> error_code 9
>>> <...>-26008 [001] 5175193.046432: kvm_entry: vcpu 0
>>> <...>-26008 [001] 5175193.046434: kvm_exit: reason cr_access rip 0xfc796
>>> <...>-26008 [001] 5175193.046435: kvm_cr: cr_write 0 = 0x10
>>> <...>-26008 [001] 5175193.046442: kvm_entry: vcpu 0
>>> <...>-26008 [001] 5175193.046444: kvm_exit: reason exception rip 0xfc799
>>> <...>-26008 [001] 5175193.046447: kvm_entry: vcpu 0
>>> <...>-26008 [001] 5175193.046449: kvm_exit: reason exception rip 0xfc799
>>> <...>-26008 [001] 5175193.046449: kvm_page_fault: address feffd066
>>> error_code 9
>>> <...>-26008 [001] 5175193.046453: kvm_inj_virq: irq 13
>>>
>>> #GP at fc799.
>>>
>>> fc78f: 0f 20 c0 mov %cr0,%eax
>>> fc792: 66 83 e0 fe and $0xfffffffe,%eax
>>> fc796: 0f 22 c0 mov %eax,%cr0
>>> fc799: ea 9e c7 00 f0 ljmp $0xf000,$0xc79e
>>>
>>> I think we're in big real mode and your kernel has trouble emulating the
>>> ljmp. Can you try latest seabios[1]? Commit 0f788893a8bba has a
>>> workaround.
>>>
>>>
>>> [1] git://git.linuxtogo.org/home/kevin/seabios.git
>>
>> Thank you very much. Running qemu-kvm with the latest seabios fixed
>> the problem. The VM is running fine again.
>>
>
> Still I'd like to get this fixed. What's your host kernel version?
'uname -a' shows the following:
Linux vm-server 2.6.32-22-generic #35-Ubuntu SMP Tue Jun 1 14:18:25 UTC
2010 x86_64 GNU/Linux
André
prev parent reply other threads:[~2010-08-04 11:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 5:39 VM not booting anymore after Ubuntu upgrade André Weidemann
2010-08-04 6:48 ` Avi Kivity
2010-08-04 6:55 ` André Weidemann
2010-08-04 7:05 ` Avi Kivity
2010-08-04 7:38 ` André Weidemann
2010-08-04 10:31 ` Avi Kivity
2010-08-04 11:22 ` André Weidemann
2010-08-04 11:29 ` Avi Kivity
2010-08-04 11:42 ` André Weidemann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C595222.3060406@web.de \
--to=andre.weidemann@web.de \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox