From: Michael Tokarev <mjt@tls.msk.ru>
To: Ross Boylan <ross@biostat.ucsf.edu>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: XP blue screen with qemu-kvm-0.11.0
Date: Sat, 31 Oct 2009 15:21:31 +0300 [thread overview]
Message-ID: <4AEC2BCB.1000503@msgid.tls.msk.ru> (raw)
In-Reply-To: <1256957193.21609.50.camel@markov.biostat.ucsf.edu>
Ross Boylan wrote:
> My XP VM was working OK, and then started crashing shortly after it
> logged me in. There were no obvious changes at the time. I built the
> latest qemu-kvm, but the problem persists.
>
> I am running 32 bit XP on Intel(R) Xeon(R) CPU E5420 @ 2.50GHz (8 cores
> total), Debian GNU/Linux mostly Lenny (amd64), but with some more recent
> stuff. In particular, the kernel is 2.6.30-8 and I pulled in the
> kernel-headers package to match before building kvm. However, libc6 and
> libc6-dev are at Lenny's 2.7-18 version.
Libc is basically irrelevant here. What matters are the host kernel
and kvm version.
> $ ./XP.sh
> ++ sudo vdeq bin/qemu-system-x86_64 -net nic,vlan=1,macaddr=52:54:a0:12:01:00 -net vde,vlan=1,sock=/var/run/vde2/tap0.ctl -boot c -vga std -hda /dev/turtle/XP01 -soundhw es1370 -localtime -m 1G -smp 2
> arg ,vlan=1,sock=/var/run/vde2/tap0.ctl
> TUNGETIFF ioctl() failed: Invalid argument
> TUNSETOFFLOAD ioctl() failed: Bad address
> oss: Could not initialize DAC
> oss: Failed to open `/dev/dsp'
> oss: Reason: Device or resource busy
> oss: Could not initialize DAC
> oss: Failed to open `/dev/dsp'
> oss: Reason: Device or resource busy
> audio: Failed to create voice `es1370.dac2'
> # and more sound-related complaints
Switch to alsa to get your audio working.
> The VM starts; I see the initial XP screen with the 4 colors; I see the
> background I get when I log in (it logs me in directly without prompt);
> and then (pretty fast) I get a blue screen. The stop code is 0x8E, and
> the text says to check disk space and BIOS options.
What's the bios files your kvm uses? Are they by a change
from some old qemu install?
Does kvm deb from http://www.corpit.ru/debian/tls/kvm/ expose the same
issue?
> -no-kvm-irqchip and -no-kvm-pit make no difference.
>
> With -no-kvm I get stop code 0x24 and a suggestion to disable
> anti-virus, defragmentation, and backup software. This is the one
> obvious change between the Lenny kvm and the one I just built; with
> lenny kvm (kvm 72+dfsg-5~lenny3) running with -no-kvm simply seemed to
> hang forever (I think I waited at least 15 minutes).
>
> This disk turtle/XP01 is a read-write snapshot on turtle/XP00. The
> snapshot looks healthy, with about 50% allocated to the snapshot. The
> snapshot volume is 10G and the original is 50G.
>
> The VM starts fine if I point it to XP00 instead of XP01.
Well, that's telling, isn't it? If you change disk image and
it works, the problem should be in the disk image...
>
> P.S. What are the different files in my kvm/bin directory?
There's no kvm/bin directory in the source tarball of qemu-kvm-0.11.0.
/mjt
next prev parent reply other threads:[~2009-10-31 12:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-31 2:46 XP blue screen with qemu-kvm-0.11.0 Ross Boylan
2009-10-31 12:21 ` Michael Tokarev [this message]
2009-10-31 17:23 ` Ross Boylan
2009-10-31 17:31 ` Michael Tokarev
2009-11-04 2:06 ` Ross Boylan
2009-11-04 10:20 ` Michael Tokarev
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=4AEC2BCB.1000503@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=kvm@vger.kernel.org \
--cc=ross@biostat.ucsf.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.