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

[Thorolf Godawa]

Hi Chuck,


well still no luck :-(


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

I installed all RPMs from "SLES10-x86-64-changeset8659.tar.bz2" via 
yast, now the xen0-domain on the Xeon/VT starts!

The Kernel is still an older Version than the one on SL 10.1 Beta2 and 
wouldn't it make sense to use the newer XEN 3.0.1?

But unfortunately I was not a able to start my Linux-xenU-guest, I just 
got the error because of the missing device :-(

There where no loop-devices at all at /dev/loop.., I created them and my 
Linux-guest came up and running :-)


But my freedos.vmx (SDL=1) doesn't start anymore:
   Error: Device 768(?) (vbd) could not be connected. Backend device not 
found.

I don't know what is missing, the packages +python-devel, +SDL-devel, 
and LibVNCServer (BTW: it's not anymore in SLES10b1 included!) are 
installed, but s.th. seems not to be there.

And as expected I also can't use my w2k3-xenU-domain with VNC=1 still 
the same error than before that the VNCServer is not connectable from 
anywhere, I tried this also with the freedos-image!


 >>> 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 just downloaded it und burned it on CDs, but now its too late to try.

 >VMX works in beta 3 (with various caveats...)
Are you sure that the VNC-stuff is included and working in this version?

 > 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
I've done this and it seems to work as expected, so at least one problem 
solved, thanks a lot for your support :-))))
-- 

Chau y hasta luego,

Thorolf