Re: [Xen-users] Xen 3.0.3 confusion

[Art Fore <art.fore@xxxxxxxxx>]

On Tue, 2006-10-24 at 17:00 +0200, Ulrich Windl wrote:
> On 24 Oct 2006 at 21:28, Art Fore wrote:
> 
> > I am thoughly confused  with the various Xen 3.0.3 versions for Suse.
> > Firt there is not for suse 10.1, so I gues I woulllt the source tarball
> > and compile. ( I tried the RPM for 10.0 (I am running SuSE 10.1) but it
> > caused a kernel panic)
> > 
> > I have 5 packages listed unter Yast software management (not including
> > documentation,pdf, etc).
> > 
> > Kernel-xen ver      2.6.16.21.25
> > Xen         3.02_09763-0.8
> > xen-libs    3.02_09763-0.8
> > xen-tools   3.02_09763-0.8
> > xen-tools-ioemu     3.02_09763-0.8
> > 
> > I understad allof these have tomach. If I do the compile of the tarball
> > with make distro, does this al create all of the files?
> > 
> > If this does not create all of the files, how do I find the other files?
> 
> rpm -qi <package name> will show the source RPM. There you have the sources. 
> Update the sources, thenrebuild the RPMs.
> 
> [...]
> Ulrich
> 

The more I look into this, the more confused I get.

>From http://www.xensource.com/files/xen_install_windows.pdf
There is a paragraph:
Type /usr/sbin/xm info | grep caps at the command prompt. You will see
“hvm-3.0-x86_32” if Xen can detect the VT or AMD-V technology. If you do
not see this, then your system does not have the appropriate processor
technology, or it has been disabled in the BIOS. You must rectify this
before proceeding.

When I type the command, I get:
linux-p204:~ # /usr/sbin/xm info | grep caps
hw_caps                :
178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f
xen_caps               : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_64

I have 3 hvm listings instead of 1. Could someone kindly explain:
Is this normal of Athlon 64 X2 (Running Suse 10.1 Xen kernel)?
If it is normal, why 3 hvms?
If it isn't, what is happening?

I created 2 full virtualization machines with Yast, but they are both
stopped. The WinXP never completed installation,it hung the computer
about 2/3 of the device installation phase, and the Suse 10 was going so
slow that it was going to take 13 hours to install.

Art

Just had a though after I sent the email. I deleted the Suse virtual machine 
that was stopped in Yast,the ran the /usr/sbin/xm info | grep caps again, but 
came up with same answer!

Just adds to the confusion.

Art


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