[Pkg-xen-devel] Etch: Xen does not want guests: Error: (22, 'Invalid argument')

[Ralph Passgang]

Am Freitag, 8. Dezember 2006 18:35 schrieb Martin Bretschneider:
[...]
> Then I wanted to create the guests using the following
> /etc/xen-tools/xen-tools.conf:
> #################################################################
> lvm = hot
> debootstrap = 1
> size   = 4Gb      # Disk image size.
> memory = 128Mb    # Memory size
> swap   = 128Mb    # Swap size
> fs     = ext3     # use the EXT3 filesystem for the disk image.
> dist   = etch    # Default distribution to install.
> image  = sparse   # Specify sparse vs. full disk images.
> dhcp = 1
> cache = yes
> passwd = 1
> #kernel = /vmlinuz
> #initrd = /initrd.img
> kernel = /boot/initrd.img-2.6.17-2-amd64
> initrd = /boot/vmlinuz-2.6.17-2-xen-amd64
> arch=i386
> mirror = http://debian.tu-bs.de/debian/
> #################################################################

in this config you said that you want to use the same kernel as for your dom0. 
The amd64 kernel (64bit). 32bit userspace and 64bit kernel should be ok, but 
I never used that combination.

@Bastian: 32bit kernels on 64bit hypervisor is not ok, sure. But please 
correct me if I am wrong, 32bit userspace on a 64bit kernel with a 64bit 
hypervisor should be fine, shouldn't it?

[...]

> But then
>
> # xm create xen-test01.cfg -c
>
> gave me
> #########################
> Using config file "/etc/xen/xen-test01.cfg".
> Error: (22, 'Invalid argument')
> #########################
>
>
> # less /etc/xen/xen-test01.cfg
> ######################################
> kernel  = '/vmlinuz'
> ramdisk = '/initrd.img'
> memory  = '128'
> root    = '/dev/sda1 ro'
> disk    = [ 'phy:hot/xen-test01-disk,sda1,w',
> 'phy:hot/xen-test01-swap,sda2,w' ]
> name    = 'xen-test01'
> dhcp = 'dhcp'
> vif  = [ '' ]
> on_poweroff = 'destroy'
> on_reboot   = 'restart'
> on_crash    = 'restart'
> ######################################

take a look at the "kernel" and "ramdisk" line here. they both have the the 
wrong value. You have to edit that file and put in the kernel and ramdisk 
that you already had set in your xen-tools config.

I never used xen-tool, so I don't know if this is a xen-tool bug, but seems 
so. Please report that bug again, but this time for the "xen-tools" package.

> Can you please help me...
>
> TIA  and kind regards from Germany

grüsse zurück ;-P

--Ralph