[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-users] Xen Not Support multi-cpu??


  • To: "Xin Chen" <xcheney@xxxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
  • Date: Tue, 13 Mar 2007 11:02:03 +0100
  • Delivery-date: Tue, 13 Mar 2007 03:02:09 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcdlEsBpqkpu6UvAS1+SQesYUt2NQQAQ2F/w
  • Thread-topic: [Xen-users] Xen Not Support multi-cpu??

 

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Xin Chen
> Sent: 13 March 2007 01:55
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-users] Xen Not Support multi-cpu??
> 
> OK! I see now. For guest system, they only know virtual cpu 
> which domain 
> 0 made.Domain0 is incharge of real cpus.
> Great. Thanks!

To be VERY PEDANTIC: VCPU's are what ALL domains "know". The REAL CPU's
are handled by the hypervisor only. Whilst it's true that Dom0 gives the
instructions about how many real and virtual CPU's a guest should use,
it still is the hypervisor that enforces, controls and guarantees this. 

Dom0 in the sense of the Hypervisor is another guest - it just so
happens that it's got the "privileged flag" set. Think of Dom0 as a
"root" user in Unix, and DomU as a "regular user", and you get the idea.

--
Mats



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.