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

[Xen-users] Problems creating a Fedora 14 domU using XCP 1.0 and xe

  • To: <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Joe Linoff" <jlinoff@xxxxxxxxxx>
  • Date: Mon, 16 May 2011 20:14:19 -0700
  • Cc: Joe Linoff <jlinoff@xxxxxxxxxx>
  • Delivery-date: Mon, 16 May 2011 20:15:59 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcwUQIMEz6BTxcCcTwK7l6MmvuEBSA==
  • Thread-topic: Problems creating a Fedora 14 domU using XCP 1.0 and xe

Hi Folks:

I am having trouble creating a Fedora 14 domU on a XCP 1.0 dom0
hypervisor and am hoping that someone can help me figure out what I am
doing wrong.

Here is what I did (per the user's guide and reference manual):

## Step 1. Create the VM:
# uuid=$(xe vm-install template='Other install media'
## Note: I also tried CentOS variants

## Step 2. Get the network ID
# netwuuid=$(xe network-list bridge=xenbr0 --minimal)

## Step 3. Create the VIF
# xe vif-create vm-uuid=$uuid \
   network-uuid=$netwuuid \

## Step 4. Verify that the http address is correct using wget to get the
# wget ://
# ls -l GPL

## Step 5. Start the Guest
# xe vm-start uuid=$uuid

## Step 6. Get the VNC port from xenstored, first get the domid
# domid=$(xe vm-list uuid=$uuid params=dom-id --minimal)
# xenstore-ls -f /local/domain/$domid | grep vnc-port
## port is 5901

## Step 7. setup an ssh tunnel for the port on another host
# ssh -L5901: root@xxxxxxxxxxxx

## Step 8. VNC in from the other host (initiator of the ssh tunnel)
# vncviewer localhost:5901

At this point everything works and VNC connects but the boot message is:

    Boot device: CD-Rom - failure: could not read boot disk

    Boot device: Hard Drive - failure: could not read boot disk

    No bootable device.
    Reboot or press any key to retry.

The /mnt/Fedora-14-x86_64 directory was loop mounted directly from the
Fedora CD:

# mount -o loop Fedora-14-x86_64-Live-Desktop.iso /var/www/html/mnt

I verified that the CD was bootable and that everything was readable in
the exploded directory.


## On the XCP server
# lsb_release -a
LSB Version:    :core-3.1-ia32:core-3.1-noarch
Distributor ID: XCP
Description:    XCP release 1.0.0-42052c (xcp)
Release:        1.0.0-42052c
Codename:       xcp

# uname -a
Linux xenserver-tcc-lab-04 #1 SMP
Tue Feb 1 17:10:20 EST 2011 i686 i686 i386 GNU/Linux

Any hints would be greatly appreciated.



Xen-users mailing list



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