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

[Xen-users] near native performance


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: johnny <linuxweb@xxxxxxxxx>
  • Date: Thu, 02 Aug 2007 13:55:20 -0400
  • Delivery-date: Thu, 02 Aug 2007 10:53:11 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=mZsG71XZnqWrABtFo/i/Xz9K7MEPSUqlwaEt5fPoZZqBUK5nvvVwNn7n3H7bvM4ROgzTyBX8CFwa04Ow9PR32tohSCPyggk43imqCdlQoDPbyPXxUCf+tuDLV6t7kfu0Nshj0oqpcBrNBP55h767BSLe2mJIqVtw1Nh64c4l4ow=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Just wondering if there was a howto or other URL that explains what is needed to achieve "near native" performance on a domU -- for this purpose, I am thinking about a single domU running on a physical server, in comparison to that same physical server running a vanilla kernel (non-Xenified).

For instance, using a physical partition for VBD v. using a file-backed one is one of the more obvious ones. Assigning all the VCPUs. And as much RAM as you can get away with (maybe leaving the dom0 with 512MB).

But are there others? Since I'm doing PV, I assume I don't need to turn on VT in the BIOS? What about 32-bit v. 64-bit OS, for the dom0 and for the domU? (I'll be using CentOS-5.) Anything else?

johnny

_______________________________________________
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®.