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

Re: [Xen-users] xen domU on Centos5 problem


  • To: trilok nuwal <tc.nuwal@xxxxxxxxx>
  • From: Nico Kadel-Garcia <nkadel@xxxxxxxxx>
  • Date: Thu, 10 May 2007 12:12:50 +0100
  • Cc: Georgi Genov <linuxloader@xxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 10 May 2007 04:11:20 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=IjSWKHzZ1lZnxZ+tLL0/ilP1dChj7q85mwEeCU/Xbe5p0nX1H4rqF313hAWmA8z9lpom1Fro4ObYeYzeZRWF4Vy8FjXKbtmGEQxyR/MdPj1f415C1a1wxczXOW98NVoA3uwriJP5GeUrEQDEGoA6Tx7POoZDK6rB6byWzNsuW9o=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

trilok nuwal wrote:
That because..yr initrd doesnot contains the frontend drivers xenblk and xennet so build the initrd image and use that image in yr config file and then restart the domain.

#mkinirtd /boot/initrd.img `uname -r` --with xenblk --with xennet --preload xenblk --preload xennet

Thanks,
Trilok
No.

I'm sorry to be harsh about this, but overwriting initrd.img with random kernels is *BAD*, *BAD*, *BAD*, *BAD* practice. It should be written to /boot/initrd-[kernel version].img, and initrd.img symlinkd to it as necessary. But RedHat's boot loaders are *designed* to use the boot/initrd-[kernel version].img,. Because in many configurations initrd.img is symlinked to the most recently installed or default kernel, doing this can blow your system sky-high and make it impossible to reboot without significant manual work.

Also, since Georgi hasn't been able to boot into this installed system, he obviously can't run the mkinitrd in it sufficiently for "uname -r" to be meaningful, now can he. It would be possible to mount the partitions and do chroots into them to perform these operations.

But guess what? It still doesn't work! The Jailtime images and their configurations do *not* use bootloaders, it specifies the kernels in the Xen config files. It 's a stripped, prebuilt image, and it does not even have modprobe.conf set up for mkinitrd to use for drivers.

The easiest workaround right now is to install the xensource.com kernel-xen kernels and use *those* in the guest domains. It seems to be stable.

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


 


Rackspace

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