RE: Re: No VMX-guests on Intel Xeon/VT

RE: Re: No VMX-guests on Intel Xeon/VT

[Petersson, Mats]

> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com 
> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of 
> Thorolf Godawa
> Sent: 02 February 2006 02:30
> To: xen-devel@lists.xensource.com
> Cc: xen-users@lists.xensource.com
> Subject: [Xen-users] Re: No VMX-guests on Intel Xeon/VT
> 
> Hi all,
> 
> OK, I've installed possibly all needed packages on SL10.1b2 
> but the VNC-stuff still is not working :-(
> 
> So right now I'm downloading the latest SLES 10-beta-code 
> from the Novell-side and hopefully it is working with that - 
> this is plan A!
> 
> Plan B is compiling XEN by myself, so acording to the docs 
> I've installed the following (or it was already installed):
> python-devel, zlib-devel, LibVNCServer, SDL-devel, 
> bridge-utils, iproute2, udev, dev86-0.16.0-187.i586.rpm
> 
> Then I downloaded and untared xen-3.0.1-src.tgz, to build it 
> I'm doing:
> 
> # make KERNELS=linux-2.6-xen world > make01.log
> 
> The first part seems to run without problems, at least I 
> don't find errors or warnings in the log:
> 
> ------------------------------------------------------
>    ...
>    Install prefix    usr
>    BIOS directory    /usr/share/xen/qemu
>    binary directory  /usr/bin
>    Manual directory  /usr/share/man
>    Source path       /data/xen/2install/xen301/xen-3.0.1/tools/ioemu
>    C compiler        gcc
>    make              make
>    host CPU          amd64
>    host big endian   no
>    target list       target-i386-dm
>    gprof enabled     no
>    static build      no
>    VNC support       yes
>    SDL support       yes
>    SDL static link   yes
>    mingw32 support   no
>    Adlib support     no
>    FMOD support      no
>    ...
>    make[3]: Leaving directory
> `/data/xen/2install/xen301/xen-3.0.1/xen/arch/x86'
>    make[2]: Leaving directory 
> `/data/xen/2install/xen301/xen-3.0.1/xen'
>    make[1]: Leaving directory `/data/xen/2install/xen301/xen-3.0.1'
> ------------------------------------------------------
> 
> It doesn't matter that the "host CPU" is an "amd64" if in 
> truth its a Xeon with EM64T?

AMD64 is funcationality-wise compatible with EM64T (or to be
historically correct, Intel copied AMD64 to make EM64T) - there are some
minor differences, but none that matters to QEMU. 
> 
> And what means "target list       target-i386-dm", does it 
> mean that the 
> compiled binaries are only for i386? I need them for x86-64, 
> if it's not correct where do I change it?

That's fine - works fine on my AMD64-system, and that's straight out of
the Xen-unstable tree - AMD has made no modifications to this, it's all
been in there since Intel first introduced the code into Xen. [I don't
have an Intel system to compare with, but it should make no difference
at all]. 

> 
> Unfortunately only the first part of the compilation runs, then I get:
> 
> ------------------------------------------------------
>    readlink: missing operand
>    Try `readlink --help' for more information.
>     __  __            _____  ___   _
>     \ \/ /___ _ __   |___ / / _ \ / |
>      \  // _ \ '_ \    |_ \| | | || |
>      /  \  __/ | | |  ___) | |_| || |
>     /_/\_\___|_| |_| |____(_)___(_)_|
> 
>    cc1: warnings being treated as errors
>    In file included from
> /data/xen/2install/xen301/xen-3.0.1/xen/include/asm/mpspec.h:5,
>                     from
> /data/xen/2install/xen301/xen-3.0.1/xen/include/asm/smp.h:18,
>                     from
> /data/xen/2install/xen301/xen-3.0.1/xen/include/xen/smp.h:13,
>                     from
> /data/xen/2install/xen301/xen-3.0.1/xen/include/xen/sched.h:8,
>                     from x86_64/asm-offsets.c:9:
>    
> /data/xen/2install/xen301/xen-3.0.1/xen/include/asm/mpspec_def.h:78: 
> warning: ?packed? attribute ignored for field of type 
> ?unsigned char[5u]?
>    make[3]: *** [asm-offsets.s] Error 1
>    make[2]: *** [/data/xen/2install/xen301/xen-3.0.1/xen/xen] Error 2
>    make[1]: *** [install-xen] Error 2
>    make: *** [world] Error 2
> ------------------------------------------------------

What version of gcc are you using? 4.0.2?

You can probably just (at your own peril, of course) remove -Werror from
the CFLAGS line in .../xen/arch/x86/Rules.mk (around line 11). 

However, I'm not sure that you actually need to build Xen itself -
perhaps you can just go down to the .../tools/ioemu and do "make clean;
make" there. As the problem you're seeing appears to be related to
qemu-dm. Then copy target-i386-dm/qemu-dm to /usr/lib64/xen/bin [on your
target system, if you're not compiling and running Xen on the same
system]. 

Note: .../ represents the "Xen root directory", such as
~/xen-unstable.hg or whatever it may be. 

Best of luck. 

--
Mats

> 
> I'm not a c-programmer, so possibly I'm not goinig to fix 
> this in the sources or is there s.th. else wrong in the way 
> I'm going to compile the package for me?
> 
> Again thanks a lot for all the help I got in these news-groups!
> -- 
> 
> Chau y hasta luego,
> 
> Thorolf
> 

Re: No VMX-guests on Intel Xeon/VT

[Thorolf Godawa]

Hi,

 >What version of gcc are you using? 4.0.2?
gcc version 4.1.0 20060109 (prerelease) (SUSE Linux)

I also tried it on the i386-installation with exact the same results :-(

Then I deinstalled all the XEN-stuff that was installed by YaST and what 
was updated by the 3.0.1 bin-package from XenSource.

 >You can probably just (at your own peril, of course) remove -Werror
 >from the CFLAGS line in .../xen/arch/x86/Rules.mk (around line 11).
OK I tried it it continues to compile, downloads the kernel from 
kernel.org and I get a LOT of warnings - finaly errors, so this was not 
the solution :-(

So possibly there is still missing a lib or what ever.

How can I find out what is missing?
-- 

Chau y hasta luego,

Thorolf

RE: No VMX-guests on Intel Xeon/VT

[Petersson, Mats]

 

> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com 
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of 
> Thorolf Godawa
> Sent: 02 February 2006 16:33
> To: Charles Coffing
> Cc: xen-devel@lists.xensource.com
> Subject: Re: [Xen-devel] No VMX-guests on Intel Xeon/VT
> 
> Hi Chuck and all others,
> 
> 
> yeah, its going better and better ...
> 
> 
>  >If you're using the Xen from the SLES 10 betas, VNC and SDL 
> support are  >already compiled in.
> I just installed the latest SLES 10.0 Beta1 x86-64 
> (2006-1-19), during installation there where just a litte 
> thing (ompat-32bit 2006.1.13-2 conflict because 
> libcrypto.so.0.9.7 and libssl.so.0.9.7 are not available, but 
> there is the 0.9.7), the rest was running quite good, even 
> the network-adapter is recognized correct now!
> 
> 
> The standard-kernel ist booting as expected the system, but 
> if I try to install s.th. with YaST it didn't let me select 
> anything and there are no package-descriptions at all.
> 
> But even this could be acceptable because I just want to use XEN!
> 
> 
> So I started the XEN-kernel (2.6.15-git12-6-xen) and what do I get:
> 
> not found -- exiting to /bin/sh
> $
> aaarg ...
> 
> 
> The first thing is:
> 
> Could not allocate 16 bytes percpu data
> WARNING: Error inserting scsi_mod .... : Cannot allocate memory
> sd_mod: Unknown symbol scsi_...
> ...
> ..
> .
> FATAL: Error inserting sd_mod ... : Unknown symbol in modul, 
> or unknown parameter (see dmesg) Loading ata_piix Could not 
> allocate 16 bytes percpu data
> WARNING: Error inserting scsi_mod .... : Cannot allocate memory
> libdata: Unknown symbol scsi_...
> ...
> ..
> .
> WARNING: Error inserting libdata ... : Unknown symbol in 
> modul, or unknown parameter (see dmesg)
> FATAL: Module ahci not found.
> ...
> ata_piix: Unknown symbol ata_...
> ...
> ..
> .
> Waiting for udev to settle: . ok
> not found -- exiting to /bin/bash
> $
> -------------------------

Did you build a new initrd using the "mkinitrd" command? 
Either do that [search the archive if you need to find more details on
how to do this], or you can turn off modules in the kernel [that's what
I do, because I then only need ONE file to copy from the dev machine to
target machine - not that I'm changing the kernel very often...]

I hope this helps. 

--
Mats
> 
> Any ideas?
> -- 
> 
> Chau y hasta luego,
> 
> Thorolf
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 

Re: No VMX-guests on Intel Xeon/VT

[Thorolf Godawa]

Hi Matts,

thanks a lot for your answer!

 >Did you build a new initrd using the "mkinitrd" command?
nothing at all, I only installed the SLES-beta/64 and wanted to start 
the SLES with xen0-kernel.

 >Either do that [search the archive if you need to find more details on
 >how to do this], or you can turn off modules in the kernel [that's what
 >I do, because I then only need ONE file to copy from the dev machine to
 >target machine - not that I'm changing the kernel very often...]
I'll try it later, but if I understand right you are speaking about the 
kernels of the xenU-domains?

Now I install the i386-version of SLES, maybe I've more luck with that - 
it just has to run tomorrow.
-- 

Chau y hasta luego,

Thorolf

RE: Still problems with VNC and Windows on Intel Xeon/VT

[Puthiyaparambil, Aravindh]

> I start my first VM with vnc=1 and vncviewer=1 in the config but no
VNC
> is starting. I get the following message:

Start the domain with vnc=1 and vncviewer=0. Then execute "vncviewer
ipaddress:dom_id" or "vncviewer localhost:dom_id" to connect to the
domain.

Hope this helps.

Aravindh

No VMX-guests on Intel Xeon/VT

[Thorolf Godawa]

Hi all,

first thanks a lot for everybody who is reading my posts and thanks a 
lot for the people who try to help me with my problem.

I know it's hard to work on beta-hardware with beta-technology, with a 
beta-OS, beta-drivers and a software that just is a x.0.0-release - but 
I never give up :-))))


 >Start the domain with vnc=1 and vncviewer=0. Then execute "vncviewer
 >ipaddress:dom_id" or "vncviewer localhost:dom_id" to connect to the
 >domain.
I tried this already before, but I only get "connection refused".


OK, where I am right now:

SuSE Linux 10.1 Beta2 x86-64 with Gnome as desktop on a Dual-Xeon 3,2GHz 
with dualcore/HT/VT, 4GB RAM with Kernel 2.6.16_rc1_git3-4.

I installed SuSE Linux completely new, I updated XEN to 3.0.1 and my 
Linux-guests are still working.

But I even don't get running a very simple freedos as vmx-xenU, with
'qemu -hda /data/xen/images/freedos/freedos.dsk -boot c' it is running 
with Qemu :-((((

I tried all the following on an identical machine with the same results, 
I also tried it SuSE Linux 10.1 Beta2 i386 without success.

Now I will have a look at SuSE Linux 10.0, but with this the 
onboard-NICs are not working, so I have to plug in PCI-card.
BTW: SuSE Linux or SLES is a must!


I always use the "xmexample.vmx" as base for my vmx-xenU-guests, there I 
only adjust the following:

memory = 128
name = "freedos.vmx"
vif = [ 'type=ioemu, bridge=xenbr0' ] # (some times to give a MAC-adr)
disk = [ 'file:/data/xen/images/freedos/freedos.dsk,ioemu:hda,w' ]
boot='c'
sdl=0
vnc=1
vncviewer=1

Now I start the guest with:

# xm create freedos.vmx

And I get:

   Using config file "freedos.vmx".
   VNC= 1
   vncviewer -listen: Listening on port 11001 (flash port 10901)
   vncviewer -listen: Command line errors are not reported until a 
connection comes in.
   Started domain freedos.vmx

But no VNC-viewer is started!


Trying to connect the server from OS/2, Linux (I also tried it from the 
XEN 3.0 Live CD) and even Windows results in a 'connection refused' 
using <xen0-host-ip>:<vm-id> (10.65.0.34:1) or :<5500+vmid> 
(10.65.0.34:5501) and in an error 'ReadFromRFBServer: rd::EndOfStrem' if 
I connect at 10.65.0.34:11001 and on the xen0-host I get also an error:

   vncviewer -listen: invalid command line argument: -log
   TightVNC viewer version 1.2.9

   Usage: vncviewer [<OPTIONS>] [<HOST>][:<DISPLAY#>]
   ...
   ..

'xm list' and 'xm top' telling me the following:

# xm list
   Name                              ID Mem(MiB) VCPUs State  Time(s)
   Domain-0                           0     3873     4 r-----   171.7
   freedos.vmx                        1      128     1 -b----     0.0

# xm top
xentop - 19:54:59   Xen 3.0.1
2 domains: 1 running, 1 blocked, 0 paused, 0 crashed, 0 dying, 0 shutdown
Mem: 4186112k total, 4181288k used, 4824k free    CPUs: 4 @ 3192MHz

NAME  STATE   CPU(sec) CPU(%)     MEM(k) MEM(%)  MAXMEM(k) MAXMEM(%) 
VCPUS NETS NETTX(k) NETRX(k) SSID
   Domain-0 -----r        172    0.0    3965268   94.7   no limit 
n/a     4    8     8712   158371    0
freedos.vmx --b---          0    0.0     131356    3.1     131356 
3.11    0        0        0    0

No I shutdown the xenU.

As suggested I change in the config:

vncviewer=0

and start freedos again, 'netstat -nat' doesn't tell me anything new, 
but anyway I try it, this time with vmid 2 but with the same result as 
before :-(

Next try is changing the config again:

sdl=1
vnc=0
vncviewer=0

Now finaly I get a local window open, it shows some BIOS-info, s.th. 
about booting from harddisk and finally the boot-menu, if I press 1 or 2 
the boot-menu disappears and I get only a cursor in the left upper 
corner (F8) lets me say twice 'Y' the it also stops, and on pressing 3 I 
get a black, then a blank screen and the window closes :-(

But the xenU-domain is still running:

   Name                              ID Mem(MiB) VCPUs State  Time(s)
   Domain-0                           0     3873     4 r-----   499.3
   freedos.vmx                        7      128     1 -b----     1.2

So I shut it down.


I also created images with VirtualPC/2 (Warp Server and WinXP) and 
copied them with dd into an image-file, I can start both images with 
Qemu, well both aren't working really because they are trapping in Qemu, 
but actually they should do something if started as vmx-domU - but there 
is no activity at all, no window opens (sdl=1), 'xm list' and 'xm top' 
say that the OS is running (with status 'b') but CPU is at 0 all the 
time - configurations are the same than the ones for freedos (exept for 
memory=512)!


Today I also tried the XEN 3.0-Demo-CD on the machine and it's running.

Does this version also supports Intel/VT as VMX-guests? I could not find 
the vmxloader in the fs, so probably it isn't integrated?


Thanks very much for your help,
-- 

Chau y hasta luego,

Thorolf

Re: No VMX-guests on Intel Xeon/VT

[Daniel Stekloff]

Sorry if I missed part of this, have you seen:

http://wiki.xensource.com/xenwiki/VmxQuickstartGuide

Have you installed the libvncserver? For sdl, have you installed the
sdl-devel as well as the sdl package?




On Wed, 2006-02-01 at 20:43 +0100, Thorolf Godawa wrote:
> Hi all,
> 
> first thanks a lot for everybody who is reading my posts and thanks a 
> lot for the people who try to help me with my problem.
> 
> I know it's hard to work on beta-hardware with beta-technology, with a 
> beta-OS, beta-drivers and a software that just is a x.0.0-release - but 
> I never give up :-))))
> 
> 
>  >Start the domain with vnc=1 and vncviewer=0. Then execute "vncviewer
>  >ipaddress:dom_id" or "vncviewer localhost:dom_id" to connect to the
>  >domain.
> I tried this already before, but I only get "connection refused".
> 
> 
> OK, where I am right now:
> 
> SuSE Linux 10.1 Beta2 x86-64 with Gnome as desktop on a Dual-Xeon 3,2GHz 
> with dualcore/HT/VT, 4GB RAM with Kernel 2.6.16_rc1_git3-4.
> 
> I installed SuSE Linux completely new, I updated XEN to 3.0.1 and my 
> Linux-guests are still working.
> 
> But I even don't get running a very simple freedos as vmx-xenU, with
> 'qemu -hda /data/xen/images/freedos/freedos.dsk -boot c' it is running 
> with Qemu :-((((
> 
> I tried all the following on an identical machine with the same results, 
> I also tried it SuSE Linux 10.1 Beta2 i386 without success.
> 
> Now I will have a look at SuSE Linux 10.0, but with this the 
> onboard-NICs are not working, so I have to plug in PCI-card.
> BTW: SuSE Linux or SLES is a must!
> 
> 
> I always use the "xmexample.vmx" as base for my vmx-xenU-guests, there I 
> only adjust the following:
> 
> memory = 128
> name = "freedos.vmx"
> vif = [ 'type=ioemu, bridge=xenbr0' ] # (some times to give a MAC-adr)
> disk = [ 'file:/data/xen/images/freedos/freedos.dsk,ioemu:hda,w' ]
> boot='c'
> sdl=0
> vnc=1
> vncviewer=1
> 
> Now I start the guest with:
> 
> # xm create freedos.vmx
> 
> And I get:
> 
>    Using config file "freedos.vmx".
>    VNC= 1
>    vncviewer -listen: Listening on port 11001 (flash port 10901)
>    vncviewer -listen: Command line errors are not reported until a 
> connection comes in.
>    Started domain freedos.vmx
> 
> But no VNC-viewer is started!
> 
> 
> Trying to connect the server from OS/2, Linux (I also tried it from the 
> XEN 3.0 Live CD) and even Windows results in a 'connection refused' 
> using <xen0-host-ip>:<vm-id> (10.65.0.34:1) or :<5500+vmid> 
> (10.65.0.34:5501) and in an error 'ReadFromRFBServer: rd::EndOfStrem' if 
> I connect at 10.65.0.34:11001 and on the xen0-host I get also an error:
> 
>    vncviewer -listen: invalid command line argument: -log
>    TightVNC viewer version 1.2.9
> 
>    Usage: vncviewer [<OPTIONS>] [<HOST>][:<DISPLAY#>]
>    ...
>    ..
> 
> 'xm list' and 'xm top' telling me the following:
> 
> # xm list
>    Name                              ID Mem(MiB) VCPUs State  Time(s)
>    Domain-0                           0     3873     4 r-----   171.7
>    freedos.vmx                        1      128     1 -b----     0.0
> 
> # xm top
> xentop - 19:54:59   Xen 3.0.1
> 2 domains: 1 running, 1 blocked, 0 paused, 0 crashed, 0 dying, 0 shutdown
> Mem: 4186112k total, 4181288k used, 4824k free    CPUs: 4 @ 3192MHz
> 
> NAME  STATE   CPU(sec) CPU(%)     MEM(k) MEM(%)  MAXMEM(k) MAXMEM(%) 
> VCPUS NETS NETTX(k) NETRX(k) SSID
>    Domain-0 -----r        172    0.0    3965268   94.7   no limit 
> n/a     4    8     8712   158371    0
> freedos.vmx --b---          0    0.0     131356    3.1     131356 
> 3.11    0        0        0    0
> 
> No I shutdown the xenU.
> 
> As suggested I change in the config:
> 
> vncviewer=0
> 
> and start freedos again, 'netstat -nat' doesn't tell me anything new, 
> but anyway I try it, this time with vmid 2 but with the same result as 
> before :-(
> 
> Next try is changing the config again:
> 
> sdl=1
> vnc=0
> vncviewer=0
> 
> Now finaly I get a local window open, it shows some BIOS-info, s.th. 
> about booting from harddisk and finally the boot-menu, if I press 1 or 2 
> the boot-menu disappears and I get only a cursor in the left upper 
> corner (F8) lets me say twice 'Y' the it also stops, and on pressing 3 I 
> get a black, then a blank screen and the window closes :-(
> 
> But the xenU-domain is still running:
> 
>    Name                              ID Mem(MiB) VCPUs State  Time(s)
>    Domain-0                           0     3873     4 r-----   499.3
>    freedos.vmx                        7      128     1 -b----     1.2
> 
> So I shut it down.
> 
> 
> I also created images with VirtualPC/2 (Warp Server and WinXP) and 
> copied them with dd into an image-file, I can start both images with 
> Qemu, well both aren't working really because they are trapping in Qemu, 
> but actually they should do something if started as vmx-domU - but there 
> is no activity at all, no window opens (sdl=1), 'xm list' and 'xm top' 
> say that the OS is running (with status 'b') but CPU is at 0 all the 
> time - configurations are the same than the ones for freedos (exept for 
> memory=512)!
> 
> 
> Today I also tried the XEN 3.0-Demo-CD on the machine and it's running.
> 
> Does this version also supports Intel/VT as VMX-guests? I could not find 
> the vmxloader in the fs, so probably it isn't integrated?
> 
> 
> Thanks very much for your help,

Re: No VMX-guests on Intel Xeon/VT

[Thorolf Godawa]

Hi Daniel,

thanks a lot for your answer!

 >Sorry if I missed part of this, have you seen:
 >http://wiki.xensource.com/xenwiki/VmxQuickstartGuide
probably not, I've seen this side but didn't payed much attention to it!

Maybe it's a stupid question, but do I have to build XEN if I want to 
use it with VMX and VNC on the Intel Xeon/VT?


 ># xm create -f /etc/xen/xmexample.vmx
I think there is a small error in the documentation, I didn't found it 
before:
------
Simply follow the usual method of creating the guest, using the -f 
parameter and providing the filename of your VMX configuration file:

# xend start
# xm create /etc/xen/vmxguest.vmx
------

With the parameter '-f' nothing changes with the freedos-images, but the 
warp-server-image seems to do s.th., at least I have CPU(sec) and some 
times CPU(%) but I can't say if it's booting, trapping or even running. 
I installed a PCnet-adapter with fixed ip, VNC-server, telnetd and ftpd 
in the image, so if the OS starts it actually should be connectable!
And winxp also starts, at least it comes to the startmenu where it ask 
what should be started (protected, normal, ...) and a 
windows-trap-screen :-)

 >Have you installed the libvncserver?
No, it's even not in my rpm-list on the SuSE-medias, so I have to 
compile and install it by my self?

 >For sdl, have you installed the sdl-devel as well as the sdl package?
No, it wasn't, I installed it but without any new results!
-- 

Chau y hasta luego,

Thorolf

Re: [Xen-users] Re: No VMX-guests on Intel Xeon/VT

[Daniel Stekloff]

On Wed, 2006-02-01 at 21:51 +0100, Thorolf Godawa wrote:
> Hi Daniel,
> 
> thanks a lot for your answer!
> 
>  >Sorry if I missed part of this, have you seen:
>  >http://wiki.xensource.com/xenwiki/VmxQuickstartGuide
> probably not, I've seen this side but didn't payed much attention to it!
> 
> Maybe it's a stupid question, but do I have to build XEN if I want to 
> use it with VMX and VNC on the Intel Xeon/VT?


I'm not sure I understand this question. If you're going to use VMX
support in Xen, you need to build and use Xen. 



>  ># xm create -f /etc/xen/xmexample.vmx
> I think there is a small error in the documentation, I didn't found it 
> before:
> ------
> Simply follow the usual method of creating the guest, using the -f 
> parameter and providing the filename of your VMX configuration file:
> 
> # xend start
> # xm create /etc/xen/vmxguest.vmx
> ------
> 
> With the parameter '-f' nothing changes with the freedos-images, but the 
> warp-server-image seems to do s.th., at least I have CPU(sec) and some 
> times CPU(%) but I can't say if it's booting, trapping or even running. 
> I installed a PCnet-adapter with fixed ip, VNC-server, telnetd and ftpd 
> in the image, so if the OS starts it actually should be connectable!
> And winxp also starts, at least it comes to the startmenu where it ask 
> what should be started (protected, normal, ...) and a 
> windows-trap-screen :-)
> 
>  >Have you installed the libvncserver?
> No, it's even not in my rpm-list on the SuSE-medias, so I have to 
> compile and install it by my self?


Yep.


>  >For sdl, have you installed the sdl-devel as well as the sdl package?
> No, it wasn't, I installed it but without any new results!

Hmmm... I know that the sdl-devel package isn't listed on what needs to
be installed, but the sdl option won't work without it. 

Re: No VMX-guests on Intel Xeon/VT

[Thorolf Godawa]

Hi all,

OK, I've installed possibly all needed packages on SL10.1b2 but the 
VNC-stuff still is not working :-(

So right now I'm downloading the latest SLES 10-beta-code from the 
Novell-side and hopefully it is working with that - this is plan A!

Plan B is compiling XEN by myself, so acording to the docs I've 
installed the following (or it was already installed):
python-devel, zlib-devel, LibVNCServer, SDL-devel, bridge-utils, 
iproute2, udev, dev86-0.16.0-187.i586.rpm

Then I downloaded and untared xen-3.0.1-src.tgz, to build it I'm doing:

# make KERNELS=linux-2.6-xen world > make01.log

The first part seems to run without problems, at least I don't find 
errors or warnings in the log:

------------------------------------------------------
   ...
   Install prefix    usr
   BIOS directory    /usr/share/xen/qemu
   binary directory  /usr/bin
   Manual directory  /usr/share/man
   Source path       /data/xen/2install/xen301/xen-3.0.1/tools/ioemu
   C compiler        gcc
   make              make
   host CPU          amd64
   host big endian   no
   target list       target-i386-dm
   gprof enabled     no
   static build      no
   VNC support       yes
   SDL support       yes
   SDL static link   yes
   mingw32 support   no
   Adlib support     no
   FMOD support      no
   ...
   make[3]: Leaving directory 
`/data/xen/2install/xen301/xen-3.0.1/xen/arch/x86'
   make[2]: Leaving directory `/data/xen/2install/xen301/xen-3.0.1/xen'
   make[1]: Leaving directory `/data/xen/2install/xen301/xen-3.0.1'
------------------------------------------------------

It doesn't matter that the "host CPU" is an "amd64" if in truth its a 
Xeon with EM64T?

And what means "target list       target-i386-dm", does it mean that the 
compiled binaries are only for i386? I need them for x86-64, if it's not 
correct where do I change it?

Unfortunately only the first part of the compilation runs, then I get:

------------------------------------------------------
   readlink: missing operand
   Try `readlink --help' for more information.
    __  __            _____  ___   _
    \ \/ /___ _ __   |___ / / _ \ / |
     \  // _ \ '_ \    |_ \| | | || |
     /  \  __/ | | |  ___) | |_| || |
    /_/\_\___|_| |_| |____(_)___(_)_|

   cc1: warnings being treated as errors
   In file included from 
/data/xen/2install/xen301/xen-3.0.1/xen/include/asm/mpspec.h:5,
                    from 
/data/xen/2install/xen301/xen-3.0.1/xen/include/asm/smp.h:18,
                    from 
/data/xen/2install/xen301/xen-3.0.1/xen/include/xen/smp.h:13,
                    from 
/data/xen/2install/xen301/xen-3.0.1/xen/include/xen/sched.h:8,
                    from x86_64/asm-offsets.c:9:
   /data/xen/2install/xen301/xen-3.0.1/xen/include/asm/mpspec_def.h:78: 
warning: ?packed? attribute ignored for field of type ?unsigned char[5u]?
   make[3]: *** [asm-offsets.s] Error 1
   make[2]: *** [/data/xen/2install/xen301/xen-3.0.1/xen/xen] Error 2
   make[1]: *** [install-xen] Error 2
   make: *** [world] Error 2
------------------------------------------------------

I'm not a c-programmer, so possibly I'm not goinig to fix this in the 
sources or is there s.th. else wrong in the way I'm going to compile the 
package for me?

Again thanks a lot for all the help I got in these news-groups!
-- 

Chau y hasta luego,

Thorolf

Re: No VMX-guests on Intel Xeon/VT

[Charles Coffing]

Content-Disposition: inline
X-SA-Exim-Connect-IP: 137.65.81.172
X-SA-Exim-Mail-From: ccoffing@novell.com
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on 192.168.0.10
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.1.0
X-SA-Exim-Version: 4.2 (built Thu, 03 Mar 2005 10:44:12 +0100)
X-SA-Exim-Scanned: Yes (on 192.168.0.10)
X-BeenThere: xen-devel@lists.xensource.com
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Xen developer discussion <xen-devel.lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Original-Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
Xref: news.gmane.org gmane.comp.emulators.xen.devel:19860 gmane.comp.emulators.xen.user:7790
Archived-At: <http://permalink.gmane.org/gmane.comp.emulators.xen.devel/19860>

>>> On Wed, Feb 1, 2006 at  1:51 PM, in message
<43E11F43.2000905@godawa.de>,
Thorolf Godawa <nospam@godawa.de> wrote: 
>  ># xm create - f /etc/xen/xmexample.vmx
> I think there is a small error in the documentation, I didn't found
it 
> before:
> ------
> Simply follow the usual method of creating the guest, using the - f 
> parameter and providing the filename of your VMX configuration file:
> 
> # xend start
> # xm create /etc/xen/vmxguest.vmx
> ------

I believe the "-f" is optional.  If it's not specified, xm assumes that
your last argument is a config file.

>  >Have you installed the libvncserver?
> No, it's even not in my rpm- list on the SuSE- medias, so I have to 
> compile and install it by my self?

No.  It's in SUSE, but it's called LibVNCServer.  (I don't know why it
has FunkyCaps.)

If you're using the Xen from the SLES 10 betas, VNC and SDL support are
already compiled in.

One trick you may want to try (especially if using SDL):  Boot your
machine, start X, and then (from within X) restart xend
("/etc/init.d/xend restart").  Then try to start the VMX guest.

Hope that helps,
-Chuck

Re: No VMX-guests on Intel Xeon/VT

[Thorolf Godawa]

Hi Chuck and all others,


yeah, its going better and better ...


 >If you're using the Xen from the SLES 10 betas, VNC and SDL support are
 >already compiled in.
I just installed the latest SLES 10.0 Beta1 x86-64 (2006-1-19), during 
installation there where just a litte thing (ompat-32bit 2006.1.13-2 
conflict because libcrypto.so.0.9.7 and libssl.so.0.9.7 are not 
available, but there is the 0.9.7), the rest was running quite good, 
even the network-adapter is recognized correct now!


The standard-kernel ist booting as expected the system, but if I try to 
install s.th. with YaST it didn't let me select anything and there are 
no package-descriptions at all.

But even this could be acceptable because I just want to use XEN!


So I started the XEN-kernel (2.6.15-git12-6-xen) and what do I get:

not found -- exiting to /bin/sh
$
aaarg ...


The first thing is:

Could not allocate 16 bytes percpu data
WARNING: Error inserting scsi_mod .... : Cannot allocate memory
sd_mod: Unknown symbol scsi_...
...
..
.
FATAL: Error inserting sd_mod ... : Unknown symbol in modul, or unknown 
parameter (see dmesg)
Loading ata_piix
Could not allocate 16 bytes percpu data
WARNING: Error inserting scsi_mod .... : Cannot allocate memory
libdata: Unknown symbol scsi_...
...
..
.
WARNING: Error inserting libdata ... : Unknown symbol in modul, or 
unknown parameter (see dmesg)
FATAL: Module ahci not found.
...
ata_piix: Unknown symbol ata_...
...
..
.
Waiting for udev to settle: . ok
not found -- exiting to /bin/bash
$
-------------------------

Any ideas?
-- 

Chau y hasta luego,

Thorolf