Hello there, I might have found some bug in xen-utils-unstable (amd64). When starting some Linux in domU, the ?ramdisk? parameter of my .cfg file is overridden and has the same value as the ?image? parameter. That ends in an unbootable VM (vmlinuz is not a ramdisk ?) ?No filesystem could mount root, tried: cramfs Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(x,y)? [.cfg file] ramdisk = '/boot/initrd.img-2.6.18-6-xen-amd64' kernel = '/boot/vmlinuz-2.6.18-6-xen-amd64' ... [xend.log] [2008-07-26 11:17:23 2890] DEBUG (image:633) domid = 13 [2008-07-26 11:17:23 2890] DEBUG (image:634) memsize = 2048 [2008-07-26 11:17:23 2890] DEBUG (image:635) image = /boot/vmlinuz-2.6.18-6-xen-amd64 [2008-07-26 11:17:23 2890] DEBUG (image:636) store_evtchn = 1 [2008-07-26 11:17:23 2890] DEBUG (image:637) console_evtchn = 2 [2008-07-26 11:17:23 2890] DEBUG (image:638) cmdline = root=/dev/ram0 ip=:127.0.255.255::::eth0:dhcp [2008-07-26 11:17:23 2890] DEBUG (image:639) ramdisk = /boot/vmlinuz-2.6.18-6-xen-amd64 ? weird ? [2008-07-26 11:17:23 2890] DEBUG (image:640) vcpus = 1 [2008-07-26 11:17:23 2890] DEBUG (image:641) features ... [quickfix, hardcoding in /usr/lib/xen-unstable/lib/python/xen/xend/image.py] class LinuxImageHandler(ImageHandler): ... self.ramdisk = "/boot/initrd.img-2.6.18-6-xen-amd64" log.debug("ramdisk = %s (david quickfix)", self.ramdisk) ... Some field must be badly passed to some function somewhere. I?m not used to python Best :) David Denis david at denis.name