|
xen-users
RE: [Xen-users] Xen 3.0.3 confusion
> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Art Fore
> Sent: 24 October 2006 18:55
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-users] Xen 3.0.3 confusion
>
> 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?
It's normal.
You can run:
xen-3.0-x86_64 - Paravirtual 3.0-compatible 64-bit kernel.
hvm-3.0-x86_32 - fully virtualized 32-bit kernel.
hvm-3.0-x86_64 - fully virtualized 64-bit kernel.
And it's actually only two hvms and one "xen" (but until I started
splitting it up on separate lines, I didn't see the difference either!).
The above .pdf reference I presume was written by someone that didn't do
64-bit builds of Xen at the time of writing. [Although essentially, what
the above text refers to is THERE, right, it's just not alone, which the
text doesn't say it should be (nor does it say that is shouldn't be
alone)].
>
> 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.
What version (according to xm info) are you using? Can you post the full
"xm info" output, please?
--
Mats
>
> Art
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>
>
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
Home