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

["Petersson, Mats" <Mats.Petersson@xxxxxxx>]

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Thorolf Godawa
> Sent: 02 February 2006 02:30
> To: xen-devel@xxxxxxxxxxxxxxxxxxx
> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
> 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
> 


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users