From: Arun Sharma <arun.sharma@intel.com>
To: Mark Williamson <mark.williamson@cl.cam.ac.uk>
Cc: Mike Wray <mike.wray@hp.com>,
xen-devel@lists.xensource.com, takebe_akio@jp.fujitsu.com
Subject: Re: exception looking up device number for hda
Date: Mon, 08 Aug 2005 17:06:54 -0700 [thread overview]
Message-ID: <42F7F39E.3020300@intel.com> (raw)
In-Reply-To: <200508081548.18887.mark.williamson@cl.cam.ac.uk>
Mark Williamson wrote:
>>I was looking for suggestions as to how:
>>
>>a) IDE hard drives for VMX domains should be configured
>>b) VBD based devices for VMX domains should be configured
>
>
> Ah, I guess we have to distinguish the two...
>
> Hope about an optional: vbd:/emu: prefix (or similar) on the second part of
> the triplet for a disk? The default (for non VMX domains) could be "vbd" so
> existing behaviour would remain the same.
Sounds good to me. How about:
hda = VBD hda
vbd://hda = VBD hda
ioemu://hda = IDE hda
The VBD patches are not ready yet - so I'd like to propose that we do:
- self.create_configured_devices()
+ if self.image.ostype != 'vmx':
+ self.create_configured_devices()
and
- self.create_blkif()
+ if self.image.ostype != 'vmx':
+ self.create_blkif()
When our VBD patches are ready, we'll revert this.
-Arun
next prev parent reply other threads:[~2005-08-09 0:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 19:34 exception looking up device number f,or hda Arun Sharma
2005-08-05 20:33 ` Anthony Liguori
2005-08-05 21:20 ` Arun Sharma
2005-08-08 2:21 ` takebe_akio
2005-08-08 5:38 ` exception looking up device number for hda Arun Sharma
2005-08-08 14:48 ` Mark Williamson
2005-08-09 0:06 ` Arun Sharma [this message]
2005-08-09 1:25 ` David Hopwood
2005-08-09 1:49 ` Mark Williamson
2005-08-09 2:58 ` Xiaofeng Ling
2005-08-09 18:19 ` Arun Sharma
[not found] ` <mailman.1123552364.22306@unix-os.sc.intel.com>
2005-08-09 19:06 ` Arun Sharma
2005-08-09 19:18 ` Mark Williamson
2005-08-08 8:08 ` exception looking up device number f,or hda Mike Wray
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=42F7F39E.3020300@intel.com \
--to=arun.sharma@intel.com \
--cc=mark.williamson@cl.cam.ac.uk \
--cc=mike.wray@hp.com \
--cc=takebe_akio@jp.fujitsu.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.