From: Thiemo Seufer <ths@networkno.de>
To: Don Kitchen <don@n2.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] cvs regression - blue screen INACCESSIBLE_BOOT_DEVICE
Date: Fri, 5 Jan 2007 19:20:05 +0000 [thread overview]
Message-ID: <20070105192005.GB15486@networkno.de> (raw)
In-Reply-To: <20070103074830.CC69B1DCC5B@ravel.n2.net>
Don Kitchen wrote:
> I just compiled CVS and have experienced a regression with some windows
> qcow images (2000 pro and server). The images work with cvs I compiled back
> in July, but current cvs produces blue screen with INACCESSIBLE_BOOT_DEVICE.
Could you try to find out which change in qemu triggers this behaviour?
I don't have a windows to test, and given there weren't (yet :-) loud
complaints I figure the problem might be connected to you local setup.
Thiemo
next prev parent reply other threads:[~2007-01-05 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 7:48 [Qemu-devel] cvs regression - blue screen INACCESSIBLE_BOOT_DEVICE Don Kitchen
2007-01-05 19:20 ` Thiemo Seufer [this message]
2007-01-08 7:00 ` Don Kitchen
2007-01-06 0:03 ` maestro
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=20070105192005.GB15486@networkno.de \
--to=ths@networkno.de \
--cc=don@n2.net \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).