XEN3 => Image starten klappt nicht

Lord_Icon

Lord_Icon

Member
Hi,

hab einen eigenen Server:

1 x Intel Xeon 5110 mit 1,66 Ghz => also 64 Bit

Hauptsystem = Suse Linux Enterprise Version 10.1


XEN ist eingebunden und läuft auch.

Folgendes wurde bisher gemacht (ausführliche Beschreibung)

Code: 
mkdir /home/xen
cd /home/xen
wget http://buch.eisxen.org/fileadmin/xim/debian.disk.bz2
bunzip debian.disk.bz2 mv debian.disk /home/xen
mount -o loop /home/xen/debian.disk /mnt

Der Download oben ist übrigens ein Image von Debian SPEZIELL für Xen.
Es muß nur noch die Kernel Version in das Image reinkopiert werden und dann sollte es wohl funzen.

ab da wird es aber Interessant.

hier meine Kernel's im Verzeichniss /boot

Code: 
Main-Server:/home/xen # ls /boot
backup_mbr                      vmlinux-2.6.16.13-4-smp.gz
boot                            vmlinux-2.6.16.13-4-xen.gz
config-2.6.16.13-4-smp          vmlinuz
config-2.6.16.13-4-xen          vmlinuz-2.6.16.13-4-smp
grub                            vmlinuz-2.6.16.13-4-xen
initrd                          vmlinuz-xen
initrd-2.6.16.13-4-smp          xen-3.0.2_09656-4.gz
initrd-2.6.16.13-4-xen          xen-3.0.gz
initrd_cutsom                   xen-3.gz
initrd-xen                      xen-dbg-3.0.2_09656-4.gz
message                         xen-dbg-3.0.gz
symsets-2.6.16.13-4-smp.tar.gz  xen-dbg-3.gz
symsets-2.6.16.13-4-xen.tar.gz  xen-dbg.gz
symtypes-2.6.16.13-4-smp.gz     xen.gz
symtypes-2.6.16.13-4-xen.gz     xen-syms
symvers-2.6.16.13-4-smp.gz      xen-syms-3.0.2_09656-4
symvers-2.6.16.13-4-xen.gz      xen-syms-dbg
System.map-2.6.16.13-4-smp      xen-syms-dbg-3.0.2_09656-4
System.map-2.6.16.13-4-xen


ich hab den vmlinux-2.6.16.13-4-xen genommen

also:
Code: 
cp -ax /lib/modules/vmlinux-2.6.16.13-4-xen /mnt/lib/modules
umount /mnt

soo.. und dann noch schnell eine Konfigurationsdatei erstellt

Code: 
kernel = "/boot/vmlinuz-2.6.16.13-4-xen"
ramdisk = "/boot/initrd-2.6.16.13-4-xen"
memory = 256
vif = [ '' ]
disk =[ 'file:/home/xen/debian.disk,sda1,w' ]
root = "/dev/sda1 ro"


Das wars, was ich bis dato vorgenommen habe. Leider erhalte ich immer eine Kernel Panic Meldung. Natürlich hab ich schon mit anderen Kernels versucht.. aber immer das gleiche Lied.

Jm. ein Vorschlag/Idee ??




Code: 
Main-Server:/etc/xen # xm create debian -c

Using config file "debian".
Started domain debian
Bootdata ok (command line is  root=/dev/sda1 ro)
Linux version 2.6.16.13-4-xen (geeko@buildhost) (gcc version 4.1.0 (SUSE Linux)) #1 SMP Wed May 3 04:53:23 UTC 2006
No mptable found.
Built 1 zonelists
Kernel command line:  root=/dev/sda1 ro
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 65536 bytes)
Xen reported: 1599.999 MHz processor.
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Software IO TLB disabled
Memory: 245924k/270336k available (1846k kernel code, 24056k reserved, 780k data, 140k init)
Calibrating delay using timer specific routine.. 4001.43 BogoMIPS (lpj=8002876)
Security Framework v1.0.0 initialized
Mount-cache hash table entries: 256
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
checking if image is initramfs... it is
Freeing initrd memory: 6637k freed
Brought up 1 CPUs
migration_cost=0
DMI not present or invalid.
Grant table initialized
NET: Registered protocol family 16
Brought up 1 CPUs
PCI: setting up Xen PCI frontend stub
ACPI: Subsystem revision 20060127
ACPI: Interpreter disabled.
xen_mem: Initialising balloon driver.
PCI: System does not support PCI
PCI: System does not support PCI
TC classifier action (bugs to netdev@vger.kernel.org cc hadi@cyberus.ca)
IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $
audit: initializing netlink socket (disabled)
audit(1162637193.033:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
i8042.c: No controller found.
isa bounce pool size: 16 pages
RAMDISK driver initialized: 16 RAM disks of 128000K size 1024 blocksize
Xen virtual console successfully installed as tty1
Event-channel device installed.
mice: PS/2 mouse device common for all mice
input: PC Speaker as /class/input/input0
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
TCP established hash table entries: 16384 (order: 6, 262144 bytes)
TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
NET: Registered protocol family 1
XENBUS: Timeout connecting to devices!
Write protecting the kernel read-only data: 328k
Starting udevd
Creating devices
Loading xennet
netfront: Initialising virtual ethernet driver.
Loading xenblk
Registering block device major 8
Loading reiserfs
Waiting for device /dev/sda1 to appear:  ok
rootfs: major=8 minor=1 devn=2049
Mounting root /dev/sda1
[COLOR="Red"][B]mount: unknown filesystem type 'ext3'[/B][/COLOR]
umount: /dev: device is busy
umount: /dev: device is busy
Kernel panic - not syncing: Attempted to kill init!
 
Last edited by a moderator:
Ich habe gerade eine kleine Lösungshilfe bekommen...

Es liegt nicht am Kernel sondern wohl daran, das der Kernel kein ext3 eingebaut hat.


Code: 
Mounting root /dev/sda1
mount: unknown filesystem type 'ext3'
umount: /dev: device is busy
umount: /dev: device is busy
Kernel panic - not syncing: Attempted to kill init!


Die Frage ist jetzt nicht mehr, welcher Kernel, sondern

??? WIE BEKOMME ICH EXT3 IN DEN KERNEL ???
 
You must log in or register to reply here.
Back
Top