All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arun Sharma <arun.sharma@intel.com>
To: Xiaofeng Ling <xiaofeng.ling@intel.com>
Cc: takebe_akio@jp.fujitsu.com, Mike Wray <mike.wray@hp.com>,
	xen-devel@lists.xensource.com,
	Mark Williamson <mark.williamson@cl.cam.ac.uk>
Subject: Re: exception looking up device number for hda
Date: Tue, 09 Aug 2005 11:19:29 -0700	[thread overview]
Message-ID: <42F8F3B1.9050308@intel.com> (raw)
In-Reply-To: <42F81BC9.9030008@intel.com>

Xiaofeng Ling wrote:
> I've already made a patch when I doing para-driver debugging.
> see the attach patch.
> Does it fit the requirement?
> It will skip setupping up the loop device for ioemu image files,
> but by xm vbd-list, it can still see the file bind to hda.
> so  this command is still useful.

> -disk = [ 'file:/var/images/min-el3-i386.img,hda,w' ]
> +disk = [ 'ioemu:/var/images/min-el3-i386.img,hda,w' ]

The ioemu: prefix should be on the second element i.e:

+disk = [ 'file:/var/images/min-el3-i386.img,ioemu:hda,w' ]

and it should allow:

+disk = [ 'phy:hdb,ioemu:hda,w' ]

	-Arun

  reply	other threads:[~2005-08-09 18:19 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
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 [this message]
     [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=42F8F3B1.9050308@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 \
    --cc=xiaofeng.ling@intel.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.