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

[Thorolf Godawa]

Hi Chuck,

thank you very, very much for your answer, its nice to see that I'm not 
just stupid, but that it just don't work yet!

 >The xen in SLES10-beta 1 is known to not work.  It has trouble booting
 >on SMP x86-64, and VMX doesn't work.
OK, I just recognized it ;-)

 >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
Does it fix that the xen0-kernel of SLES 10.0 Beta1 (20.01.2006) even 
can boot?

 >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?

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

Tomorrow (that means for me in at about 10 hours, now we have midnight) 
it should run, but as you can imagine I didn't had only problems with 
the beta-SuSEs but also with the beta-hardware and also XEN 3.0.0 :-(

 >We've got VMX working in the lab.  Have you tried disk images from
 >free.oszoo.org?  That would make a good test corpus, so we can
 >reproduce problems here with the same disk images.
I tried the freedos-image from there, I have a prebuild W2k3 from the 
customer, and my own build WXP and WarpServer!

 >Other known issues to watch out for:
 >* We're testing VMX using SDL; we haven't had time yet to
 >troubleshoot VNC.
With SDL it is running more or less, but very slow and the W2k3-image 
hangs up the server completly, freedos starts but then the SDL-windows 
crashes and my WXP-image also traps, I even can see it in the SDL-window :-)

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

 >* 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?


Thanks a lot again, I think it was a big step forward for me to get in 
contact with you!
-- 

Chau y hasta luego,

Thorolf