All of lore.kernel.org
 help / color / mirror / Atom feed
From: "dwight at supercomputer.org" <dwight@supercomputer.org>
To: xen-devel@lists.xensource.com
Subject: XCP: Xen tools problem with RedHat VMs?
Date: Wed, 2 Jun 2010 22:31:50 -0700	[thread overview]
Message-ID: <201006022231.50818.dwight@supercomputer.org> (raw)

I came across an odd problem with adding the packages from the 
xs-tools.iso today. After mounting the ISO in a fresh CentOS 5.4 
VM, and doing the .../Linux/install.sh, I ended up with this in 
the VM's grub.conf:

----- Start of the new grub.conf entry ----------
title CentOS (2.6.18-164.10.1.el5.xs0.1.1.64xen)
        root (hd0,0)
        kernel /xen.gz-2.6.18-164.10.1.el5.xs0.1.1.64
        module /vmlinuz-2.6.18-164.10.1.el5.xs0.1.1.64xen ro
root=/dev/VolGroup00/LogVol00 rhgb quiet
        module /initrd-2.6.18-164.10.1.el5.xs0.1.1.64xen.img
----- End of the new grub.conf entry ----------

Now, having the Xen hypervisor running in a DomU would be exciting, 
but alas, xen.gz doesn't appear to have been installed.

So, I have to conclude that either:
    1. I'm missing this new DomU hypervisor.
    2. The documentation is wrong.
    3. The xs-tools ISO has a bug in it for the 0.1.1 XCP 
        installation with RedHat distros.

Truth to tell, I was given this VM to examine the problem, and 
didn't have time today to doublecheck the xs-tools.iso. I will do 
so tomorrow, but I wanted to get some feedback ASAP.

So I'm wondering if this is indeed a bug somewhere? And has anyone
added these tools to a CentOS/RedHat VM running on XCP 0.1.1?

If it is a bug, it would be really nice to get this fixed before 
the next release of XCP.

Thanks,

   -dwight-

             reply	other threads:[~2010-06-03  5:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-03  5:31 dwight at supercomputer.org [this message]
2010-06-03  8:25 ` XCP: Xen tools problem with RedHat VMs? Ian Campbell
2010-06-04  7:14   ` dwight at supercomputer.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201006022231.50818.dwight@supercomputer.org \
    --to=dwight@supercomputer.org \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.