public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
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 09:38:53 +0200	[thread overview]
Message-ID: <4C59190D.8050007@web.de> (raw)
In-Reply-To: <4C59113E.8020907@redhat.com>

On 04.08.2010 09:05, Avi Kivity wrote:
> On 08/04/2010 09:55 AM, André Weidemann wrote:
>> On 04.08.2010 08:48, Avi Kivity wrote:
>>> On 08/04/2010 08:39 AM, André Weidemann wrote:
>>>> Hi,
>>>> I recently upgraded my machine from Ubuntu 9.10 to 10.4 (x86_64).
>>>> Ever since I upgraded my machine I cannot get qemu-kvm to start again.
>>>>
>>>> I did not install the kvm package provided by Ubuntu. Instead I pulled
>>>> todays git from git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git and
>>>> ran ./configure && make -j6 && make install.
>>>> The configure output can be found here: http://pastebin.org/447003
>>>>
>>>> I am using the following command line to boot qemu-kvm:
>>>>
>>>> qemu-system-x86_64 -vnc :2 -k de -m 1024 -drive
>>>> file=/dev/sda,if=ide,index=0
>
> /dev/sda? is this not the host disk?

It is not the host disk. For some reason the Marvell Controller is found 
before the Intel ICH10. So the additional disk I put in for testing 
becomes sda.

>>>>
>>>> When connecting to the VNC console I only get a black screen.
>>>
>>> Does the monitor work? add -monitor stdio to the command line and type
>>> 'info registers' after you get the bla[nc]k screen.
>>>
>>
>> This is the monitor output:
>>
>> QEMU 0.13.50 monitor - type 'help' for more information
>> (qemu) info registers
>> EAX=00000010 EBX=00000000 ECX=00006e82 EDX=00b81013
>> ESI=f2010000 EDI=000c8c00 EBP=000e8550 ESP=00006e78
>> EIP=0008bc2f EFL=00010086 [--S--P-] CPL=3 II=0 A20=1 SMM=0 HLT=0
>> ES =0000 00000000 0000ffff 0000f300
>> CS =0000 00000000 0000ffff 0000f300
>
> This guest is very confused (what is it?)

This guest is a Windows 7 Pro 64bit. But it does not matter which image 
I try to boot. Even a PXE network boot results in the same behavior.

> 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

Regards
  André

  reply	other threads:[~2010-08-04  7:39 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 [this message]
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

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=4C59190D.8050007@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