All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Keith Coleman <list.keith@scaltro.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Stub domains broken in 3.4.0-rc3?
Date: Fri, 8 May 2009 15:20:47 +0100	[thread overview]
Message-ID: <4A043FBF.6090105@eu.citrix.com> (raw)
In-Reply-To: <5411dbdc0905041256w1d57cd5fvfa62d1574384851f@mail.gmail.com>

Keith Coleman wrote:

> Is there a known issue that prevents stub domains from working in 3.4.0-rc3?
> 
> I attempted to use a stub domain configuration files that worked in
> xen 3.3.1 but they don't work due to the recent addition of
> automatically generated -dm files. Moving some config lines from the
> old -dm file to the -stub file allows the creation process to go a
> little further but I get the following error:
> 
> # cat /var/log/xen/qemu-dm-win4.log
> Error: Device 768 (vbd) could not be connected.
> Device /dev/mapper/testvg-win4s is mounted in a guest domain,
> and so cannot be mounted now.
> Using config file "/etc/xen/stubdoms/win4-dm".
> Using config file "/etc/xen/stubdoms/win4-dm".
> 
> The stub domain dies immediately.


Could you please post your config file?

After the recent stubdom config file changes you only have one
configuration file, as for normal non-stubdom domains.
As a consequence you need to specify in that config file all the
informations, including vif and disk and graphic frontend type.

Sorry for the late reply,

Stefano

  parent reply	other threads:[~2009-05-08 14:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-04 19:56 Stub domains broken in 3.4.0-rc3? Keith Coleman
2009-05-08  4:47 ` Dulloor
2009-05-08 14:20 ` Stefano Stabellini [this message]
2009-05-08 16:28   ` Keith Coleman
2009-05-08 18:44     ` Stefano Stabellini
2009-05-08 21:35       ` Keith Coleman
2009-05-08 23:41         ` Thiago Camargo Martins Cordeiro
2009-05-09  7:57           ` Keir Fraser

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=4A043FBF.6090105@eu.citrix.com \
    --to=stefano.stabellini@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.