Weblog entry #4 for GhostR
See all weblog entries made by GhostR.
Now the question came up, how could he install a 32Bit domU? we tried arch=i386 in Steve's xen-tools with no luck.
According to xensource (http://wiki.xensource.com/xenwiki/XenFaq#head-5f7176b3909cb0382cece43a6a8fc25a3a114e93) it should run fine. IMHO all new debian 64Bit kernels are PAE/Bigmem right?
Comments on this Entry
How did the xen-tools install fail?
[ Parent | Reply to this comment ]
Is there a tutorial somewhere? How do I install the 32Bit Kernel on dom0? I've heard something about install it by hand in domU and then copy it to dom0 and change it in the xen config. But how do I manage to get the Userland into 32Bit? or how can I check if its 32Bit?
[ Parent | Reply to this comment ]
If you did correctly specify --arch=i386 then what has probably happened is that the guest has been installed as a 32-bit one. But it is booting with the same AMD64 kernel from the host.
To see if that is the case run "file /bin/ls" - that'll tell you whether the guest is really 32-bits, or 64-bits.
If it is genuinely 32 bit just download a 32-bit kernel (xen) package onto the dom0 - and then refer to that in the xen configuration file for the guest.
[ Parent | Reply to this comment ]
wget http://security.debian.org/debian-security/pool/updates/main/l/li nux-2.6/linux-image-2.6.26-1-xen-686_2.6.26-13lenny2_i386.deb
sudo dpkg -X *.deb /sources/i386
xen-create-image --hostname=xen01.mybox.com --size=4Gb --noswap --ip=something --memory=256Mb --arch=i386 --role=udev \
--kernel=/sources/i386/boot/vmlinuz-2.6.26-1-xen-686 --force
what should i do about the initrd image?
[ Parent | Reply to this comment ]
i have the same prob.
[ Parent | Reply to this comment ]
* install the latest xen-kernel on the domU
* copy domU:/boot/*xen to dom0:/boot/
* update dom0:/etc/xen/instance.cfg to reference new kernel and ramdisk
* start the client
- Mike
http://Goodfordogs.org/
[ Parent | Reply to this comment ]