← Back to team overview

sslug-teknik team mailing list archive

Xen VM vil ikke starte

 

Jeg har leget lidt med Xen det sidste stykke tid, og er blevet meget glad for det. Til formålet har jeg tilrettet et filsystem med Fedora Core 5 installeret, som nemt kan kopieres hver gang jeg skal bruge en ny virtuel maskine. Det har virket på adskillige forskellige maskiner.

Men når jeg vil starte min Xen VM på vores nye server, gider den ikke.

Den virtuelle maskine dør når den skal mounte sit root-filsystem; antageligvis fordi host-maskinen ikke kan oprette devices (jvf. nedenstående fejlmeddelelser).

I logfilen /var/log/xend.log brokker den sig over "exception looking up device" med samme device-navne som i boot-loggen.

Her er det sidste af boot-loggen. De to første linjer med XENBUS ser mærkelige ud, og de devices henvises der til i Xen debug loggen.

Jeg kunne godt bruge lidt inspiration til hvilke ting jeg skal kigge på... :-)

Host systemet er FC5 med kerne 2.6.17-1.2157_FC5xen0, og gæsten bruger samme kerne (har også prøvet 2.6.18-1.2200.fc5.xen til gæstesystemet).

Mvh
Kenneth


bootlog (kommer efter jeg kører "xm create -c my-xenguest"):

XENBUS: Device with no driver: device/vbd/769
XENBUS: Device with no driver: device/vbd/770
Freeing unused kernel memory: 184k freed
Write protecting the kernel read-only data: 369k
4gb seg fixup, process init (pid 1), cs:ip 73:080f3a06
4gb seg fixup, process init (pid 1), cs:ip 73:08117bae
4gb seg fixup, process init (pid 1), cs:ip 73:080f692d
4gb seg fixup, process init (pid 1), cs:ip 73:080f693b
4gb seg fixup, process init (pid 1), cs:ip 73:080f692d
4gb seg fixup, process init (pid 1), cs:ip 73:080f693b
4gb seg fixup, process init (pid 1), cs:ip 73:08120d22
4gb seg fixup, process init (pid 1), cs:ip 73:080a8501
4gb seg fixup, process init (pid 1), cs:ip 73:080f692d
4gb seg fixup, process init (pid 1), cs:ip 73:080f693b
Red Hat nash version 5.0.32 starting
Mounting proc filesystem
Mounting sysfs filesystem
Creating /dev
Creating initial device nodes
Setting up hotplug.
Creating block device nodes.
Loading scsi_mod.ko module
SCSI subsystem initialized
Loading sd_mod.ko module
Loading megaraid_sas.ko module
megasas: 00.00.03.01 Sun May 14 22:49:52 PDT 2006
Loading jbd.ko module
Loading ext3.ko module
Creating root device.
Mounting root filesystem.
mount: could not find filesystem '/dev/root'
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!


xend.log:

[2006-10-18 12:25:53 xend] DEBUG (blkif:24) exception looking up device number for hda1: [Errno 2] No such file or directory: '/dev/hda1' [2006-10-18 12:25:53 xend] DEBUG (DevController:110) DevController: writing {'virtual-device': '769', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/12/769'} to /local/domain/12/device/vbd/769. [2006-10-18 12:25:53 xend] DEBUG (DevController:112) DevController: writing {'domain': 'snestorm', 'frontend': '/local/domain/12/device/vbd/769', 'dev': 'hda1', 'state': '1', 'params': '/xen/snestorm/rootfs.img', 'mode': 'w', 'frontend-id': '12', 'type': 'file'} to /local/domain/0/backend/vbd/12/769. [2006-10-18 12:25:54 xend] DEBUG (blkif:24) exception looking up device number for hda2: [Errno 2] No such file or directory: '/dev/hda2' [2006-10-18 12:25:54 xend] DEBUG (DevController:110) DevController: writing {'virtual-device': '770', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/12/770'} to /local/domain/12/device/vbd/770. [2006-10-18 12:25:54 xend] DEBUG (DevController:112) DevController: writing {'domain': 'snestorm', 'frontend': '/local/domain/12/device/vbd/770', 'dev': 'hda2', 'state': '1', 'params': '/xen/snestorm/swapfs.img', 'mode': 'w', 'frontend-id': '12', 'type': 'file'} to /local/domain/0/backend/vbd/12/770.



Follow ups