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

[Mike McClurg <mike.mcclurg@xxxxxxxxxx>]

On 17/05/11 04:14, Joe Linoff wrote:
> 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.
 It's probably the documentation's fault, not yours ;)

> 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'
> new-name-label='test')
> ## Note: I also tried CentOS variants
RHEL 6 x86_64 may also work, but 'Other install media' is often your 
best bet.
> ## 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 \
>
> other-config:install-repository=http://192.168.1.10/mnt/Fedora-14-x86_64
At this point, you'll also need to update other-config:install-methods 
to include http. Otherwise, it will just try to boot from the cdrom, 
which is empty.
# xe vm-param-set uuid=$uuid  other-config:install-methods=cdrom,http

> ## Step 4. Verify that the http address is correct using wget to get the
> GPL
> # wget ://192.168.1.10/mnt/Fedora-14-x86_64/GPL
> # 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:127.0.0.1:5901 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.
If you've got an ISO image on your local network, you can also just boot 
from that. You can export the directory containing the ISO as an NFS 
share, and then use `xe-mount-iso-sr host:/ISO-directory`. Once you have 
the ISO directory mounted as an SR, you can then add the Fedora ISO to 
the VM as a CD:
# xe vm-cd-add vm=test device=3 cd-name='Fedora-14-x86_64-Live-Desktop.iso'

While it would work, I wouldn't recommend putting the ISO directly in 
dom0, because we only give that filesystem 4GiB to use, and it'll ruin 
your day if you run out of space on dom0.
> Errata:
>
> ## 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 2.6.32.12-0.7.1.xs1.0.0.311.170586xen #1 SMP
> Tue Feb 1 17:10:20 EST 2011 i686 i686 i386 GNU/Linux
>
> Any hints would be greatly appreciated.
>
> Thanks,
>
> Joe
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

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