From: Paul Durrant <paul.durrant@citrix.com>
To: Keith Coleman <list.keith@scaltro.com>
Cc: Ian Pratt <Ian.Pratt@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: XCP Windows PV Driver Problem
Date: Thu, 5 Nov 2009 09:50:56 +0000 [thread overview]
Message-ID: <4AF2A000.10505@citrix.com> (raw)
In-Reply-To: <5411dbdc0911041137r409d8f99see1d416644d7aecb@mail.gmail.com>
Well, your problem starts with this line from the log:
[ERROR][XENVBD] Failed to set frontend key for data/scsi/target/0
(device/vbd/768, c0000022)
This means that for some reason xenstore did not like our attempt to set
a key data/scsi/0 with our frontend VBD path. The error was EACCES; my
guess is because the data key has not been created under /local/domain/X
by the open source toolstack.
The crash is then:
[NOTICE][XENUTIL] Bugcheck: 7b F8856A98, C0000034, 00000000, 00000000
(which does not match the BSOD, which is an ASSERTion failure)
This indicates, unsurprisingly, that Windows has no boot device.
Could you bring up your Windows and pause the boot (hit F8 or something)
and then go in and create the data key (using xenstore_write and
xenstore_chmod, to give the domain write perms.) from dom0 and then let
Windows continue booting. This should hopefully allow the domain to then
come up.
Paul
--
===============================
Paul Durrant, Software Engineer
Citrix Systems (R&D) Ltd.
First Floor, Building 101
Cambridge Science Park
Milton Road
Cambridge CB4 0FY
United Kingdom
TEL: x35957 (+44 1223 225957)
===============================
next prev parent reply other threads:[~2009-11-05 9:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 18:19 XCP Windows PV Driver Problem Keith Coleman
2009-11-03 19:14 ` Keir Fraser
2009-11-04 9:54 ` Ian Pratt
2009-11-04 19:37 ` Keith Coleman
2009-11-05 9:50 ` Paul Durrant [this message]
2009-11-05 14:53 ` Keith Coleman
2009-11-19 15:50 ` Pasi Kärkkäinen
2009-11-19 16:51 ` Paul Durrant
2009-11-19 18:54 ` Keith Coleman
2009-11-19 18:59 ` Pasi Kärkkäinen
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=4AF2A000.10505@citrix.com \
--to=paul.durrant@citrix.com \
--cc=Ian.Pratt@eu.citrix.com \
--cc=list.keith@scaltro.com \
--cc=xen-devel@lists.xensource.com \
/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.