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

Re: [Xen-users] CentOS 4.5 on SLES10SP1 no disk

  • To: Henning Sprang <henning_sprang@xxxxxx>
  • From: Nico Kadel-Garcia <nkadel@xxxxxxxxx>
  • Date: Fri, 13 Jul 2007 12:20:50 +0100
  • Cc: Scott Serr <serrs@xxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 13 Jul 2007 04:14:34 -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=ewHjAF9CqYOEIO+NWjACdqIw8iqq2CycEB0caHWZa/V8/MEtiU7GeU/4h1rXqoKWuooo6pUPtAVPYSR6B9nqKcNMG0j/hfy3C30ZMW6M69qv/JLoKlD2r46R1Fd+2nGeywQ9EipvBpNyojf5J2wCLHYiB43Ss2duAHFCLyaoMYM=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Henning Sprang wrote:
Scott Serr wrote:
I have a server running SLES10SP1 with Xen enabled.  I am able to fire
off SLED10 installs inside Xen VMs just fine.

I need to run (3) CentOS 4.5 VMs on it.

CentOS kernel is not creating block devices for hd or iso image. any ideas?

It doesn't seem to care if there is this line in my config file:

disk = [ 'file:/export/home/CentOS-4.5-x86_64-binDVD.iso,hdc,r' ]

Hmm, you're trying to boot an ISO in paravirtual mode?

AFAIK this isn't so easy as one would assume when having used other
virtualization technologies before.

If at all, you can _maybe_ expect it work halfways nice with HVM.

But you might rather try bootstrapping centos with yum, as described
(this is tested on Debian, it might or might not work on SuSE, I heard
various reports on success and failure on other distributions).

My experience with this approach is that yum hangs doing this on CentOS 4 and CentOS 5, on the "touch" commands run by various "%post" RPM function. You may need to set a lockfile with your build script, and set a little monitor widget to slap such touch processes in the head. Once you have a base minimum OS to your flavor, set it aside in a tarball for starting new configurations.

Or, if you're a complete weasel, you use the "mock" tool from Fedora Core to build full chroot cages, run "mock init", and do your upgrades inside the mock-built chroot.

Or, you might search the web - I used to know where I found this, but
have it not available now - there is a howto on how to start anaconda
inside a domU to make the installation, that should work with SuSE, too.

Take care to give enough(I don't know a number, a good guess is 256 if
on doubt) memory to the VM, otherwise Anaconda will likely hang in an
undefined state without any error message.
For CentOS 5, I find 512 works well. CentOS 4 was quite happy with 256: I haven't looked at the exact difference.

Xen-users mailing list



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