Re: [Xen-users] xen 3.1 and 32bit guests in 64bit dom0

[Martin Goldstone <m.j.goldstone@xxxxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

1st question:  Is the domU kernel actually a Xen kernel?  By the look of
that error, I'd guess that it isn't, especially as normally Xen kernels
have -xen in them somewhere, and yours ends in -smp.  You need to have a
 Xen kernel to do PV, or you have to use HVM.

2nd question:  If it is a Xen kernel, what version of Xen was that 2.4
kernel compiled for?  In my experience, both dom0 and domU have to be
for Xen 3.1 in order to mix 32 bit with 64.

3rd question:  If Danilo Godec's suggestion about the NIC driver doesn't
work, could you give us some more details about your networking setup
(ie NIC make/model, Bonding, VLANs etc)?

Hope this helps.

Martin

Lorin wrote:
> Hello!
> 
> I'm sort of new to Xen but took some time to read around forums, wikis and
> official documentation. I'm experiencing
> some problems with the latest Xen version 3.1. The whole thing I'm
> currently
> working is supposed to support some old OS-es on newer
> hardware, ofc by using virtualization.
> 
> 
> * first ( i think it's related with the bootloader )
> - dom0 is 64bit / k 2.6
> - domU is 32bit/ k 2.4
> 
> I'm creating the image using:
> #xen-create-image --hostname=vm2.bla.com --size=2G --swap=256
> --ide --ip=10.1.27.202 --netmask=255.255.224.0
> --gateway=10.1.0.254--dir=/dat
> a/xen-vms --memory=256Mb --arch=i386
> --kernel=/boot/xen-guests-kernels/vmlinuz-2
> .4.26-1-686-smp --initrd=/boot/xen-guests-kernels/initrd.img-
> 2.4.26-1-686-smp --
> copy=/data/tmp/somesytemimage/ --passwd
> 
> 
> # xm create /etc/xen/vm2.bla.com.cfg
> Using config file "/etc/xen/vm2.bla.cfg".
> Error: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n')
> 
> In xend.log I get:
> 
> [2007-07-25 13:13:42 3152] DEBUG (__init__:1072)
> XendDomainInfo.constructDomain
> [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) Balloon: 557796 KiB free;
> need 2048; done.
> [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) Adding Domain: 18
> [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) XendDomainInfo.initDomain:
> 18 256
> [2007-07-25 13:13:42 3152] DEBUG (__init__:1072)
> _initDomain:shadow_memory=0x0, memory_static_max=0x10000000,
> memory_static_min=0x0.
> [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) Balloon: 557788 KiB free;
> need 262144; done.
> [2007-07-25 13:13:42 3152] INFO (__init__:1072) buildDomain os=linux dom=18
> vcpus=1
> [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) domid = 18
> [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) memsize = 256
> [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) image = /boot/vmlinuz-
> 2.4.26-1-686-smp
> [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) store_evtchn = 1
> [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) console_evtchn = 2
> [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) cmdline =
> root=/dev/hda1 ro
> [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) ramdisk =
> /boot/initrd.img-
> 2.4.26-1-686-smp
> [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) vcpus = 1
> [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) features =
> [2007-07-25 13:13:42 3152] ERROR (__init__:1072) XendDomainInfo.initDomain:
> exception occurred
> Traceback (most recent call last):
> File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 1517, in
> _initDomain channel_details = self.image.createImage()
> File "/usr/lib64/python/xen/xend/image.py", line 112, in createImage return
> self.createDomain()
> File "/usr/lib64/python/xen/xend/image.py", line 131, in createDomain
> result
> = self.buildDomain()
> File "/usr/lib64/python/xen/xend/image.py", line 517, in buildDomain return
> LinuxImageHandler.buildDomain(self)
> File "/usr/lib64/python/xen/xend/image.py", line 215, in buildDomain
> features = self.vm.getFeatures())
> Error: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n')
> [2007-07-25 13:13:42 3152] ERROR (__init__:1072) VM start failed
> Traceback (most recent call last):
> File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 396, in start
> XendTask.log_progress(31, 60, self._initDomain)
> File "/usr/lib64/python/xen/xend/XendTask.py", line 209, in log_progress
> retval = func(*args, **kwds)
> File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 1543, in
> _initDomain raise VmError(str(exn))
> VmError: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n')
> [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) XendDomainInfo.destroy:
> domid=18
> [2007-07-25 13:13:42 3152] DEBUG (__init__:1072)
> XendDomainInfo.destroyDomain(18)
> [2007-07-25 13:13:42 3152] ERROR (__init__:1072) Domain construction failed
> Traceback (most recent call last):
> File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 81, in create
> vm.start()
> File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 396, in start
> XendTask.log_progress(31, 60, self._initDomain)
> File "/usr/lib64/python/xen/xend/XendTask.py", line 209, in log_progress
> retval = func(*args, **kwds)
> File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 1543, in
> _initDomain raise VmError(str(exn))
> VmError: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n')
> [2007-07-25 13:13:42 3152] DEBUG (__init__:1072) XendDomainInfo.destroy:
> domid=None
> [2007-07-25 13:13:42 3152] DEBUG (__init__:1072)
> XendDomainInfo.destroyDomain(None)
> 
> vm2.bla.com cfg is:
> kernel = '/boot/vmlinuz-2.4.26-1-686-smp'
> ramdisk = '/boot/initrd.img-2.4.26-1-686-smp'
> memory = '256'
> root = '/dev/hda1 ro'
> disk = [ 'file:/data/xen-vms/domains/cagemove1-
> vm2.auctionwatch.com/disk.img,hda1,w',
> 'file:/data/xen-vms/domains/cagemove1-vm2.auctionwatch.com/swap.img,hda2,w'
> ]
> name = 'vm2.bla.com'
> 
> vif = [ 'ip=10.1.27.202' ]
> on_poweroff = 'destroy'
> on_reboot = 'restart'
> on_crash = 'restart'
> 
> 
> * second problem is related to networking - each time i start
> network-bridge
> dom0 losses all it's networking. As far as I've managed to track so far
> the peth0 doesn't get setup-ed correctly. I need to dig deeper on this
> one but wondering if someone
> having a similar setup managed to find out a solution.
> 
> I'm using Debian Etch 64bit running on a IBM x3550 machine ( quad xeon,4G
> RAM, VT support ) and the binary 3.1 package from xensource
> 
> 
> Thanks!
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGqFXaRnwIDhcMR9MRAihqAJ0cuqFnsCGuUQvqQty6DyUQ/N7PwgCdFv6K
DXdremp+wkX7EWY5PcARQMM=
=ktUW
-----END PGP SIGNATURE-----

Attachment: m.j.goldstone.vcf
Description: Vcard

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users