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

Hi,

I want to use Xen on a current Testing using the amd64 architecture. I 
want to use the i386 architecture for the laster Xen guests.

The hardware is a Intel Xeon 5130 (Woodcrest) with the Vanderpool 
support. Two harddisk are used as a Linux software raid 1.

Installing the hypervisor and rebooting worked like a charm since the 
bootmenu of grub has also been updates:)

The hypervisor is running:
# uname -a
Linux mars 2.6.17-2-xen-amd64 #1 SMP Wed Sep 13 18:35:45 CEST 2006 
x86_64 GNU/Linux

# xm list
Name                              ID Mem(MiB) VCPUs State  Time(s)
Domain-0                           0     3879     2 r-----   399.8

That was easy:) 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/
#################################################################

Then I did

# xen-create-image --hostname xen-test01

that also caused no problems:

# less /var/log/xen-tools/xen-test01.log
##########################################
....
Setting up root password
All done
#########################################

The locical volumes are also well done....


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'
######################################

Hm, that was no success:
# less/var/log/xen/xend.log
######################################
[2006-12-08 18:26:52 xend.util.security 9850] INFO (__init__:1072) 
Resource label file not found.
[2006-12-08 18:26:52 xend.util.security 9850] INFO (__init__:1072) 
Resource label file not found.
######################################

and

# less /var/log/xen/xend-debug.log
######################################
ERROR: Unrecognized image format
ERROR: Error constructing guest OS
######################################


I could not find a solutution. Bob Tanner has had the same problem in 
october 
(http://lists.alioth.debian.org/pipermail/pkg-xen-devel/2006-October/000823.html)
but there does not seem to be a solution...


Can you please help me...

TIA  and kind regards from Germany
-- 
Dipl.-Wirtsch.-Ing. Martin Bretschneider

Institut f?r Mess- und Regelungstechnik
Leibniz Universit?t Hannover
Nienburger Stra?e 17
30167 Hannover

Telefon: +49(0)511 762-4279
Fax: +49(0)511 762-3234

On Fri, Dec 08, 2006 at 06:35:05PM +0100, Martin Bretschneider
wrote:
> I want to use Xen on a current Testing using the amd64 architecture. I 
> want to use the i386 architecture for the laster Xen guests.
You can't have 32bit guests with a 64bit dom0 using paravirtualized
xen (i.e. without using HVM/SVM on an intel VT or AMD-V CPU).

You will need to use 32bit dom0 and have 32bit guests, or else have
all 64bit guests.

Cheers,
Andy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url :
http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20061208/d389c028/attachment.pgp

On Fri, Dec 08, 2006 at 06:35:05PM +0100, Martin Bretschneider
wrote:
> I want to use Xen on a current Testing using the amd64 architecture. I 
> want to use the i386 architecture for the laster Xen guests.
This is unsupported, the kernel architecture have to match for now.

Bastian

-- 
Klingon phaser attack from front!!!!!
100% Damage to life support!!!!

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

Andy Smith schrieb:

 > On Fri, Dec 08, 2006 at 06:35:05PM +0100, Martin Bretschneider wrote:
 >> I want to use Xen on a current Testing using the amd64 architecture. 
I want to use the i386 architecture for the laster Xen guests.
 >
 > You can't have 32bit guests with a 64bit dom0 using paravirtualized
 > xen (i.e. without using HVM/SVM on an intel VT or AMD-V CPU).
 >
 > You will need to use 32bit dom0 and have 32bit guests, or else have
 > all 64bit guests.

thanks for all your hints. If I take the 64bit 
vmlinuz-2.6.17-2-xen-amd64 and initrd.img-2.6.17-2-xen-amd64, the domU 
guests do work properly.

But then I tried to take vmlinuz-2.6.17-2-amd64 and 
initrd.img-2.6.17-2-amd64 with no Xen patches I get the same error 22. 
Does that mean that the Intel Virtualization Technology (aka vanderpool) 
does not work properly?

TIA  Martin

-- 
Dipl.-Wirtsch.-Ing. Martin Bretschneider

Institut f?r Mess- und Regelungstechnik
Leibniz Universit?t Hannover
Nienburger Stra?e 17
30167 Hannover

Telefon: +49(0)511 762-4279
Fax: +49(0)511 762-3234