From: Keir Fraser <keir.fraser@eu.citrix.com>
To: John Weekes <lists.xen@nuclearfallout.net>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Two recent patches that broke my stubdoms
Date: Mon, 18 Jan 2010 10:40:01 +0000 [thread overview]
Message-ID: <C779EB01.67E1%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <B138B2C115654718BF085220A293DC17@JohnPC>
On 13/01/2010 18:14, "John Weekes" <lists.xen@nuclearfallout.net> wrote:
> c/s 20746 :
>
> I tried to start my domain again, and it still wouldn't go. With the original
> image.py, it would just hang and show the main domain as --p--- and the
> stubdom as -b----. This told me that something was probably wrong with the
> stubdom or its configuration, so I took a look at the autogenerated stubdom
> file and found "monitor=null" in the vfb line, which was different than what
> previous versions put in. I simply edited image.py to revert c/s 20746, and
> this got rid of "monitor=null", allowing the domain to start.
I've reverted this changeset now. So hopefully all your issues are dealt
with ahead of 4.0.0-rc2.
-- Keir
prev parent reply other threads:[~2010-01-18 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 18:14 Two recent patches that broke my stubdoms John Weekes
2010-01-14 9:29 ` Keir Fraser
2010-01-14 10:16 ` Keir Fraser
2010-01-18 10:40 ` Keir Fraser [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=C779EB01.67E1%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=lists.xen@nuclearfallout.net \
--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 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).