Xen devel - Feb 2006 - RE: No VMX-guests on Intel Xeon/VT

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

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

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

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