[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] initrd for 32-bit domU on 64-bit dom0

  • To: Xen Users <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: john maclean <jayeola@xxxxxxxxx>
  • Date: Fri, 5 Jun 2009 13:50:09 +0100
  • Delivery-date: Fri, 05 Jun 2009 05:51:02 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=mPLz9dCi2ZbI9MGZ8OIG29h/O17iIKIfIRZT4vVRZT5rnwXBHUuXPc84ANdD+s8DYV tAEUVLUoV9UiXSmqDAHeRtPxpQ8lsE5SqVqvqdxQU70rNuPejNcFXcJMfEH9CjhuFhTz NIbjXD0LubyD3SKYm7Lr2gJGlfevopNg94OEA=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

CentOS dom0 is 64-bit. Xen from the repo.  Created some 32-bit domU
and grabbed one from jailtime.org.

The domUs refuse to boot unless they use an initrd created with
mkinitrd --omit-scsi-modules --with=xennet --with=xenblk
--preload=xenblk initrd-$(uname -r)-no-scsi.img $(uname -r)` but at
least the domUs boot.

The issue is that they all think that they are 64-bit servers.

-bash-3.2# arch
-bash-3.2# uname  -m

Thus whenever I try to update any packages they want to pull in 64-bit
packages. Is there somewhere within /sys or /proc that I can use to
overcome this?
John Maclean
07739 171 531

Timezone: GMT

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.