All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thorolf Godawa <nospam@godawa.de>
To: Charles Coffing <ccoffing@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: No VMX-guests on Intel Xeon/VT
Date: Thu, 02 Feb 2006 17:32:44 +0100	[thread overview]
Message-ID: <43E2342C.8000707@godawa.de> (raw)
In-Reply-To: <43E0C25D.D169.003C.0@novell.com>

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

  parent reply	other threads:[~2006-02-02 16:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-01  2:20 Still problems with VNC and Windows on Intel Xeon/VT Puthiyaparambil, Aravindh
2006-02-01 19:43 ` No VMX-guests " Thorolf Godawa
2006-02-01 19:57   ` Daniel Stekloff
2006-02-01 20:51     ` Thorolf Godawa
2006-02-01 21:03       ` [Xen-users] " Daniel Stekloff
2006-02-01 21:18         ` Re: [Xen-devel] " Thorolf Godawa
     [not found]         ` <200602012221.46090.ralph@debianbase.de>
2006-02-01 22:01           ` Thorolf Godawa
2006-02-02  2:29           ` Thorolf Godawa
2006-02-01 21:14 ` Charles Coffing
2006-02-01 22:35   ` [Xen-devel] " Thorolf Godawa
2006-02-02 16:32   ` Thorolf Godawa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-02 11:51 Petersson, Mats
2006-02-02 20:08 ` Thorolf Godawa
2006-02-02 16:40 Petersson, Mats
2006-02-02 17:01 ` Thorolf Godawa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43E2342C.8000707@godawa.de \
    --to=nospam@godawa.de \
    --cc=ccoffing@novell.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.