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

RE: [Xen-users] Unable to boot a full virtualized guest with two or more processors on a Xeon-VT platform


  • To: "Philippe Berthault" <Philippe.Berthault@xxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
  • Date: Thu, 5 Apr 2007 13:22:15 +0200
  • Delivery-date: Thu, 05 Apr 2007 04:21:34 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: Acd3cowEOkYvAUwJSkGWVborGbJHrAAAV7gg
  • Thread-topic: [Xen-users] Unable to boot a full virtualized guest with two or more processors on a Xeon-VT platform

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Philippe Berthault
> Sent: 05 April 2007 09:35
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-users] Unable to boot a full virtualized guest 
> with two or more processors on a Xeon-VT platform
> 
> On my VT platform (4 dual-core Xeon-VT processors with 16 GB 
> RAM), I am 
> unable to boot a full virtualized guest domain with two or more 
> processors. This problem is independent of the guest type, in 
> example I 
> have this problem with Linux Knoppix, Linux Mandriva, Windows 2003, 
> Windows XP, etc... In all cases, the guest OS recognizes only 
> one processor.

I believe this problem is fixed in 3.0.4 - for certain it's fixed in
unstable which is what I use right now. Unstable will become 3.0.5 in
the next couple of weeks or so. 

The main problem is that the BIOS supplied for 3.0.3 doesn't build the
correct MP-tables when you give it multiple processors. You can
manipulate the BIOS image (from memory, there is a setting for number of
processors in the makefile used to generate the BIOS image), but of
course whatever number you choose will be THE number of processors that
the guest gets [unless you build multiple versions of the BIOS and
hvmloader (hvmloader contains a copy of the BIOS which it copies into
the BIOS location in memory, and then jumps to that location). A lot of
work compared to upgrading to a newer Xen-version... 

I don't know if there were other problems that needed fixing too (there
may have been), but the BIOS not building the correct information is
definitely a hindrance.
--
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®.