All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Hu Jia Yi <jyhu@asmpt.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Question: PV and HVM device list
Date: Wed, 5 Sep 2007 16:42:39 +0100	[thread overview]
Message-ID: <20070905154239.GF5503@redhat.com> (raw)
In-Reply-To: <87B402DBCFA63342B7E8CDD1D3D0DCDE983D2C@ATSNTS65.atsex.asmpt.com>

On Wed, Sep 05, 2007 at 02:13:58PM +0800, Hu Jia Yi wrote:
> I have two questions about xen. Hope I can find answers/hints in this
> mailing list.
> 
> 1. how PV and HVM know about what physical devices are in the PC? 

They typically don't know anything about physical hardware. Normal practice
is to only assign virtual devices to guests - virtual network / disk or
sound & USB devices are most common (the latter two for HVM only).

> 2. If a USB disk is plugged in, how does xen notify this to PV and HVM
> so that the guest domains can do things as there were no virtualization
> layer.

Xen doesn't do anything when USB disks are plugged in. It is possible use
admin tools to explicitly map a USB disk through to a guest as a virtual
disk, or in HVM case to hand-off the entire USB device to the guest. This
is a manual admin config step though - nothing automatic occurrs.

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

  reply	other threads:[~2007-09-05 15:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-05  6:13 Question: PV and HVM device list Hu Jia Yi
2007-09-05 15:42 ` Daniel P. Berrange [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-09-10  1:54 Hu Jia Yi

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=20070905154239.GF5503@redhat.com \
    --to=berrange@redhat.com \
    --cc=jyhu@asmpt.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.