[xenpreview-dev] No VMX-guests on Intel Xeon/VT

[Charles Coffing]

>>> On Thu, Feb 2, 2006 at  4:12 PM, in message
<43E291FB.60404 at godawa.de>, Thorolf
Godawa <nospam at godawa.de> wrote: 
>  >Beta 2 or beta 3 (which was released today) are much better.
>  >Updating your beta 1 installation with newer xen- * and kernel- xen
RPMs
>  >may get you started (get them from beta 3 or the Xen Technical
Preview
>  >site).
> Do you mean the following:
> SLES10- i586- changeset8699hvm.src.tar.bz2
> SLES10- i586- changeset8699hvm.tar.bz2

At this point, avoid anything explicitly marked "HVM".  HVM has been
merged into the xen-unstable tree.  So really, the newest files on the
XTP site are:
SLES10-i586-changeset8659.tar.bz2
SLES10-i586-changeset8659.src.tar.bz2

> Does it fix that the xen0- kernel of SLES 10.0 Beta1 (20.01.2006)
even 
> can boot?

yes

>  >Better, of course, is to do a full reinstall with the latest beta.
> Where do I get the x86- 64- version of beta 3, if possible, now?

SUSE Linux 10.1 beta 3 (which is based on the same code as SLES 10 beta
3) is available from http://opensuse.org.

> I'm just downloading the i386 Beta3 but if I understand you correctly
it 
> won't help me with my VMX- guest, or?

VMX works in beta 3 (with various caveats...)

>  >* 32 bit unmodified guest doesn't work on 64 bit hardware with
VMX.
> Never ever or only on SuSE and/or the beta- version?

It's a build problem on our end, I believe.  We're working on it.

>  >* Make your NICs in domain 0 start at boot time; don't use "manual"
or
>  >"ifplugd" in your /etc/sysconfig/network/ifcfg- eth* files, or
domain 0
>  >may lose its IP address when xend starts.  Will be fixed in beta
4.
> Yes I have this quite often and it's hard to get back the IP!
> 
> What do you mean with this: "manual" or "ifplugd" in your 
> /etc/sysconfig/network/ifcfg- eth* ?
> The ifcfg- eth* are created autamaticly by yast, or?

Yes, those are created by yast.  There's a setting in yast regarding
when to bring up the interface.  With yast, make the IP assigned
statically, and bring the interface up at boot.  Don't set the interface
to be manually started, nor should you set it to be started when the
network cable is plugged in.  Set it up this way, and I think beta 3
will not lose the IP address.  This will be fixed better in beta 4.

-Chuck