From: "G.R." <firemeteor@users.sourceforge.net>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: Any plan to support disk driver domain?
Date: Sat, 22 Jun 2013 20:23:52 +0800 [thread overview]
Message-ID: <CAKhsbWZA1YmSM0bmAEBpUdfLtZccQYMzhLeoTKJLMAzWGJV83w@mail.gmail.com> (raw)
In-Reply-To: <51C54C26.50909@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 628 bytes --]
Thanks so much,Roger. You clarified all my confusions. I think mounting the
disk in dom0 first could serve as an acceptable workaround for HVM.
So anxious to see the new release.
> > While I can imagine why pygrub does not work, I don't understand the
> > reason HVM is affected here. Could you explain a little bit?
> > And what about a HVM with PV driver? (e.g. those windows guests)
>
> If you use HVM, Qemu needs to access the block/file used as disk, so if
> the disk is on another domain Qemu has no way to access it (unless you
> plug the disk to the Dom0 and then pass the created block device
> /dev/xvd* to Qemu).
>
[-- Attachment #1.2: Type: text/html, Size: 725 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-06-22 12:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 10:26 Any plan to support disk driver domain? G.R.
2013-04-04 11:54 ` Roger Pau Monné
2013-04-04 12:08 ` G.R.
2013-04-04 14:23 ` Daniel De Graaf
2013-04-04 15:48 ` G.R.
2013-05-28 10:16 ` Roger Pau Monné
2013-06-21 3:26 ` G.R.
2013-06-21 18:05 ` Konrad Rzeszutek Wilk
2013-06-22 7:03 ` Roger Pau Monné
2013-06-22 12:23 ` G.R. [this message]
2013-07-24 16:17 ` G.R.
2013-07-25 8:31 ` Roger Pau Monné
2013-07-25 15:35 ` G.R.
2013-08-07 10:32 ` G.R.
2013-07-31 15:36 ` George Dunlap
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=CAKhsbWZA1YmSM0bmAEBpUdfLtZccQYMzhLeoTKJLMAzWGJV83w@mail.gmail.com \
--to=firemeteor@users.sourceforge.net \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xen.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).