[xenpreview-dev] Still no VMX-guests on Intel Xeon/VT, and 'some' problems with SL 10.1b3 x86-64

[Thorolf Godawa]

Hi Chuck,

I downloaded and installed the SL 10.1 Beta3 x86-64 on my systems.

First more general about SuSE:

I'm not able to install it via NFS like I do it with SL10.0 and SL10.1
Beta2 all the time. I copy all CDs into a directory and than I boot with
the Mini-CD, give NFS-IP and directory and the installation starts.
It finished the first part (CD1) completely, reboots, asks me if it
should recognize the network-adapter and continues with the installation
on CD2.

After at about 50% of CD2 it stops installing at the package
"kdebase3-3.5.1-14", no error, it just didn't proceed.

I still can click on <Help> but if I click on <Abord> nothing happens.
I already checked the file, it's there and OK and if I install from CD
the installation works without problem!

Second, the start of Gnome an KDE needs very long, much longer the the
one of the other SuSEs I have. On Gnome some times I only get a grey
background with the mouse in the middle but nothing more!

The LibVNCServer is not in the package of SLES 10 Beta1 and SL 10.1 Beta2/3.


OK, now back to XEN:

I installed SL 10.1 Beta3 x86-64 on both machines, one with my prefered
Gonme-Desktop, the other one with KDE plus "all KDE packages".

The additional selections/packages I use:

+XEN Virtualization, +Kernel Development, +Simple Webserver,
+kdenetwork3-vnc, +python-devel, +python-pygame, +SDL-devel,
+SDL-devel-32bit, +SDL-gfx, +pine, +links, +lynx

I don't install OpenOffice, KOffice, Gimp and XSane.

I accept all automaticly selected packages.

After installation I add the packages LibVNCServer-0.7.1-2.i586.rpm and
dev86-0.16.0-187.i586.rpm via yast -i xxx.rpm!


On the first machine (KDE) I start the XEN-kernel, logon as root and
start KDE by typing 'startx' the first time with the XEN-kernel and I get:

startkde: Starting up...
DCOP aborting call from 'anonymous-5647' to 'kde'
kded: ERROR: Communication problem with kded, it probably crashed.
startkde: Shutting down...

KDE was starting with the normal kernel, but now I get the same error,
I'm not able to start KDE anymore on this machine :-(

Via yast I add the "Gnome system" to my machine, but I get the same
error as on the second machine :-(


On the second machine (Gnome) I also start the XEN-kernel logon as root
and start Gnome with startx, I get the grey background with the mouse in
the middle but nothing else.

I had the same problem with this installation before, I deleted all the
X11/Gnome-stuff, rebooted an reinstalled it and could use it even with
the XEN-kernel until the next reboot.

So I had the possibility to start XEN, my xenU-Linux-domains are always
working (xm create -c sl101b2-64) but my freedos.vmx is not working
anymore, not with sdl=1, not with vnc=1 - I get the wellknown error
"Device xxx (vbd) could not be connected. Backend device not found".

If I start the w2k3-image with vnc=1/vncviewer=1 I have exact the same
results as with all other installations before, I'm not able to connect
via VNC to it!


Can you tell me exactly with which SuSE-Linux, which
selections/packages, which configuration you had success starting
freedos with SDL- and/or VNC-support?

How do yo call your VM, how exactly do you try to connect to it via
VNCviewer?


Is there any possibility that I can call you by phone?


Right now I have no idea anymore what I'm doing wrong - either the
SuSE-packages of XEN/SDL/VNC are not OK or I am just too stupid to get
it running :-(((


Thanks you very much for your help,
-- 

Chau y hasta luego,

Thorolf

------------------------------------------------------------------
e-Mail:   mailto:Thorolf at Godawa.de                      \|/
                                                        /'~'\
Homepage: http://www.godawa.de                        ( o o )
--------------------------------------------------oOOO--(_)--OOOo-