From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: Xen-hypervisor 3.2 on HP Proliant DL380 G6 Date: Sun, 18 Jul 2010 23:07:46 +0300 Message-ID: <20100718200746.GD17817@reaktio.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Emanuel dos Reis Rodrigues Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Fri, Jul 16, 2010 at 11:23:38PM -0400, Emanuel dos Reis Rodrigues wrote: > I has beens instaled Debian Lenny 5 and follow packages: > > ii libxenstore3.0 3.2.1-2 > Xenstore communications library for Xen > ii linux-image-2.6.26-2-xen-amd64 2.6.26-24 > Linux 2.6.26 image on AMD64, oldstyle Xen support > ii linux-modules-2.6.26-2-xen-amd64 2.6.26-24 > Linux 2.6.26 modules on AMD64 > ii xen-hypervisor-3.2-1-amd64 3.2.1-2 The > Xen Hypervisor on AMD64 > ii xen-linux-system-2.6.26-2-xen-amd64 2.6.26-24 XEN > system with Linux 2.6.26 image on AMD64 > ii xen-shell 1.8-3 > Console based Xen administration utility > ii xen-tools 3.9-4 > Tools to manage Debian XEN virtual servers > ii xen-utils-3.2-1 3.2.1-2 XEN > administrative tools > ii xen-utils-common 3.2.0-2 XEN > administrative tools - common files > ii xenstore-utils 3.2.1-2 > Xenstore utilities for Xen > ii xenwatch 0.5.2-1 > Virtualization utilities, mostly for Xen > Xen packages in Lenny are getting very old, you should run something more recent.. Especially for Xen HVM guests. > > obviously my hardware has virtualization support for hvm: > > xm dmesg | grep -i hvm > (XEN) HVM: VMX enabled > > and > > xm info | grep xen_caps > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64 > > and > > grep -i vmx /proc/cpuinfo > this nothing return, but this no have problema, because I have other > servers without this output and hvm works fine. > Yeah, because VMX is used by Xen hypervisor (xen.gz), so dom0 Linux doesn't see it. > > Every HVM machine freezing when boot. I tested in the folow scenaries: > > - Boot from iso of Windows install Media 2008/ XP etc ... > > Freeze when boot on image > > - Boot from iso of ubunt > > Freeze after I enter the option in grub, in loading kernel ... > > - Boot from Windows 2008 ready image that run perfectly in another machine > > Freeze during .. loading windows files .... > Update to Xen 3.4.x or 4.0.x. > > > Name ID Mem VCPUs State Time(s) > Domain-0 0 27218 16 r----- 376.5 > win2008-ts 13 2048 1 r----- 123.4 > Also limit your dom0 memory to a fixed/dedicated amount of memory. See: http://wiki.xensource.com/xenwiki/XenBestPractices -- Pasi