thr3ads.net - Xen users - [Xen-users] Problems creating a Fedora 14 domU using XCP 1.0 and xe [May 2011]

If this information is useful, please help other people find it:
Share via:

Joe Linoff

2011-May-17 03:14 UTC

[Xen-users] 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''
new-name-label=''test'')
## 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 \
 
other-config:install-repository=http://192.168.1.10/mnt/Fedora-14-x86_64

## 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@192.168.1.10

## 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.

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@lists.xensource.com
http://lists.xensource.com/xen-users

Mike McClurg

2011-May-17 10:39 UTC

head link

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

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@192.168.1.10
>
> ## 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@lists.xensource.com
> http://lists.xensource.com/xen-users

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

Joe Linoff

2011-May-17 15:54 UTC

head link

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

Hi Mike:

Thank you! I am going to try both approaches today:

1. update other-config:install-methods to include http
2. nfs mount of the iso

Cheers,

Joe

-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Mike McClurg
Sent: Tuesday, May 17, 2011 3:39 AM
To: Joe Linoff; xen-users@lists.xensource.com
Subject: Re: [Xen-users] Problems creating a Fedora 14 domU using XCP
1.0and xe

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@192.168.1.10
>
> ## 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@lists.xensource.com
> http://lists.xensource.com/xen-users

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

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

Joe Linoff

2011-May-17 16:32 UTC

head link

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

Hi Mike:

Setting "other-config:install-methods=cdrom,http" didn''t seem
to work.
It may be that I didn''t do it correctly so ran "xe vm-param-list
uuid=$uuid" to verify. The output is shown below. Apparently I am still
missing something. Do you have any ideas that might help.

+ xe vm-param-list uuid=83e4ea16-480e-bdd4-a765-c733a96e09dc
uuid ( RO)                          :
83e4ea16-480e-bdd4-a765-c733a96e09dc
                    name-label ( RW): heath-2
              name-description ( RW): Installed via xe CLI
                  user-version ( RW): 1
                 is-a-template ( RW): false
                 is-a-snapshot ( RO): false
                   snapshot-of ( RO): <not in database>
                     snapshots ( RO): 
                 snapshot-time ( RO): 19700101T00:00:00Z
                 snapshot-info ( RO): 
                        parent ( RO):
a0b5e3d0-6d5d-1678-71c0-e44a8e9968fc
                      children ( RO): 
             is-control-domain ( RO): false
                   power-state ( RO): running
                 memory-actual ( RO): 0
                 memory-target ( RO): <unknown>
               memory-overhead ( RO): 5242880
             memory-static-max ( RW): 268435456
            memory-dynamic-max ( RW): 268435456
            memory-dynamic-min ( RW): 268435456
             memory-static-min ( RW): 134217728
              suspend-VDI-uuid ( RO): <not in database>
                  VCPUs-params (MRW): 
                     VCPUs-max ( RW): 1
              VCPUs-at-startup ( RW): 1
        actions-after-shutdown ( RW): Destroy
          actions-after-reboot ( RW): Restart
           actions-after-crash ( RW): Restart
                 console-uuids (SRO):
6263f3bf-91fa-f023-0d6c-340fbb67e04b
                      platform (MRW): timeoffset: 0; nx: false; acpi:
true; apic: true; pae: true; viridian: true
            allowed-operations (SRO): changing_dynamic_range;
hard_reboot; hard_shutdown; pause; snapshot
            current-operations (SRO): 
            blocked-operations (MRW): 
           allowed-VBD-devices (SRO): 0; 1; 2; 3
           allowed-VIF-devices (SRO): 0; 1; 2; 3
                possible-hosts ( RO):
6d288164-43e0-4f3b-ae1a-a7302e21aec4
               HVM-boot-policy ( RW): BIOS order
               HVM-boot-params (MRW): order: dc
         HVM-shadow-multiplier ( RW): 1.000
                     PV-kernel ( RW): 
                    PV-ramdisk ( RW): 
                       PV-args ( RW): 
                PV-legacy-args ( RW): 
                 PV-bootloader ( RW): 
            PV-bootloader-args ( RW): 
           last-boot-CPU-flags ( RO): 
              last-boot-record ( RO): ''(''struct''
(''uuid''
''83e4ea16-480e-bdd4-a765-c733a96e09dc'')
(''allowed_operations'' (''array''))
(''current_operations'' (''struct''
(''OpaqueRef:1f1b048b-11dd-65f6-e161-711febdcd183''
''start'')))
(''power_state'' ''Halted'')
(''name_label'' ''heath-2'')
(''name_description''
''Installed via xe CLI'') (''user_version''
''1'') (''is_a_template''
(''boolean''
''0'')) (''suspend_VDI''
''OpaqueRef:NULL'') (''resident_on''
''OpaqueRef:NULL'')
(''affinity'' ''OpaqueRef:NULL'')
(''memory_overhead'' ''5242880'')
(''memory_target'' ''268435456'')
(''memory_static_max'' ''268435456'')
(''memory_dynamic_max'' ''268435456'')
(''memory_dynamic_min'' ''268435456'')
(''memory_static_min'' ''134217728'')
(''VCPUs_params'' (''struct''))
(''VCPUs_max'' ''1'')
(''VCPUs_at_startup'' ''1'')
(''actions_after_shutdown''
''destroy'') (''actions_after_reboot''
''restart'') (''actions_after_crash''
''restart'') (''consoles''
(''array'')) (''VIFs''
(''array'')) (''VBDs''
(''array''))
(''crash_dumps'' (''array''))
(''VTPMs'' (''array''))
(''PV_bootloader'' '''')
(''PV_kernel'' '''')
(''PV_ramdisk'' '''')
(''PV_args'' '''')
(''PV_bootloader_args''
'''') (''PV_legacy_args'' '''')
(''HVM_boot_policy'' ''BIOS order'')
(''HVM_boot_params'' (''struct''
(''order'' ''dc'')))
(''HVM_shadow_multiplier''
(''double'' ''1''))
(''platform'' (''struct''
(''nx'' ''false'') (''acpi''
''true'')
(''apic'' ''true'') (''pae''
''true'') (''viridian''
''true''))) (''PCI_bus'' '''')
(''other_config'' (''struct''
(''install-methods'' ''cdrom,http'')
(''install-repository''
''http://192.168.1.10/mnt/Fedora-14-x86_64'')
(''mac_seed''
''67dc6d71-a880-1830-0cb0-5506920674f3'')))
(''domid'' ''-1'')
(''domarch'' '''')
(''last_boot_CPU_flags'' (''struct''))
(''is_control_domain''
(''boolean'' ''0''))
(''metrics''
''OpaqueRef:2491ff67-ec3b-0072-af1b-a20f7c930943'')
(''guest_metrics''
''OpaqueRef:NULL'') (''last_booted_record''
'''') (''recommendations''
''<restrictions><restriction
field=\"memory-static-max\"
max=\"34359738368\" /><restriction field=\"vcpus-max\"
max=\"8\"
/><restriction property=\"number-of-vbds\" max=\"7\"
/><restriction
property=\"number-of-vifs\" max=\"7\"
/></restrictions>'')
(''xenstore_data'' (''struct''))
(''ha_always_run'' (''boolean''
''0''))
(''ha_restart_priority'' '''')
(''is_a_snapshot'' (''boolean''
''0''))
(''snapshot_of'' ''OpaqueRef:NULL'')
(''snapshots'' (''array''))
(''snapshot_time'' (''dateTime.iso8601''
''19700101T00:00:00Z''))
(''transportable_snapshot_id'' '''')
(''blobs'' (''struct''))
(''tags'' (''array''))
(''blocked_operations'' (''struct''))
(''snapshot_info'' (''struct''))
(''snapshot_metadata'' '''')
(''parent''
''OpaqueRef:d60bcd97-8905-8881-9ac4-9cd2561195ab'')
(''children'' (''array''))
(''bios_strings'' (''struct''))
(''protection_policy'' ''OpaqueRef:NULL'')
(''is_snapshot_from_vmpp'' (''boolean''
''0'')))''
                   resident-on ( RO):
6d288164-43e0-4f3b-ae1a-a7302e21aec4
                      affinity ( RW): <not in database>
                  other-config (MRW): install-methods: cdrom,http;
install-repository: http://192.168.1.10/mnt/Fedora-14-x86_64; mac_seed:
67dc6d71-a880-1830-0cb0-5506920674f3
                        dom-id ( RO): 16
               recommendations ( RO): <restrictions><restriction
field="memory-static-max" max="34359738368"
/><restriction
field="vcpus-max" max="8" /><restriction
property="number-of-vbds"
max="7" /><restriction property="number-of-vifs"
max="7"
/></restrictions>
                 xenstore-data (MRW): 
                 ha-always-run ( RW): false
           ha-restart-priority ( RW): 
                         blobs ( RO): 
                    start-time ( RO): 20110517T16:27:10Z
                  install-time ( RO): 20110517T16:27:09Z
                  VCPUs-number ( RO): 1
             VCPUs-utilisation (MRO): 
                    os-version (MRO): <not in database>
            PV-drivers-version (MRO): <not in database>
         PV-drivers-up-to-date ( RO): <not in database>
                        memory (MRO): <not in database>
                         disks (MRO): <not in database>
                      networks (MRO): <not in database>
                         other (MRO): <not in database>
                          live ( RO): <not in database>
    guest-metrics-last-updated ( RO): <not in database>
                   cooperative ( RO): true
             protection-policy ( RW): <not in database>
         is-snapshot-from-vmpp ( RO): false
                          tags (SRW): 



Thanks,

Joe

-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Mike McClurg
Sent: Tuesday, May 17, 2011 3:39 AM
To: Joe Linoff; xen-users@lists.xensource.com
Subject: Re: [Xen-users] Problems creating a Fedora 14 domU using XCP
1.0and xe

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@192.168.1.10
>
> ## 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@lists.xensource.com
> http://lists.xensource.com/xen-users

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

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

Joe Linoff

2011-May-17 20:40 UTC

head link

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

Hi Mike:

Just a quick follow up. It was trivial to get things working using NFS
-- thank you. But I still can''t get the http boot to work. Could there
be some sort of bug or am I just missing something?

Cheers,

Joe

-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Joe Linoff
Sent: Tuesday, May 17, 2011 9:33 AM
To: Mike McClurg; xen-users@lists.xensource.com
Subject: RE: [Xen-users] Problems creating a Fedora 14 domU using XCP
1.0and xe

Hi Mike:

Setting "other-config:install-methods=cdrom,http" didn''t seem
to work.
It may be that I didn''t do it correctly so ran "xe vm-param-list
uuid=$uuid" to verify. The output is shown below. Apparently I am still
missing something. Do you have any ideas that might help.

+ xe vm-param-list uuid=83e4ea16-480e-bdd4-a765-c733a96e09dc
uuid ( RO)                          :
83e4ea16-480e-bdd4-a765-c733a96e09dc
                    name-label ( RW): heath-2
              name-description ( RW): Installed via xe CLI
                  user-version ( RW): 1
                 is-a-template ( RW): false
                 is-a-snapshot ( RO): false
                   snapshot-of ( RO): <not in database>
                     snapshots ( RO): 
                 snapshot-time ( RO): 19700101T00:00:00Z
                 snapshot-info ( RO): 
                        parent ( RO):
a0b5e3d0-6d5d-1678-71c0-e44a8e9968fc
                      children ( RO): 
             is-control-domain ( RO): false
                   power-state ( RO): running
                 memory-actual ( RO): 0
                 memory-target ( RO): <unknown>
               memory-overhead ( RO): 5242880
             memory-static-max ( RW): 268435456
            memory-dynamic-max ( RW): 268435456
            memory-dynamic-min ( RW): 268435456
             memory-static-min ( RW): 134217728
              suspend-VDI-uuid ( RO): <not in database>
                  VCPUs-params (MRW): 
                     VCPUs-max ( RW): 1
              VCPUs-at-startup ( RW): 1
        actions-after-shutdown ( RW): Destroy
          actions-after-reboot ( RW): Restart
           actions-after-crash ( RW): Restart
                 console-uuids (SRO):
6263f3bf-91fa-f023-0d6c-340fbb67e04b
                      platform (MRW): timeoffset: 0; nx: false; acpi:
true; apic: true; pae: true; viridian: true
            allowed-operations (SRO): changing_dynamic_range;
hard_reboot; hard_shutdown; pause; snapshot
            current-operations (SRO): 
            blocked-operations (MRW): 
           allowed-VBD-devices (SRO): 0; 1; 2; 3
           allowed-VIF-devices (SRO): 0; 1; 2; 3
                possible-hosts ( RO):
6d288164-43e0-4f3b-ae1a-a7302e21aec4
               HVM-boot-policy ( RW): BIOS order
               HVM-boot-params (MRW): order: dc
         HVM-shadow-multiplier ( RW): 1.000
                     PV-kernel ( RW): 
                    PV-ramdisk ( RW): 
                       PV-args ( RW): 
                PV-legacy-args ( RW): 
                 PV-bootloader ( RW): 
            PV-bootloader-args ( RW): 
           last-boot-CPU-flags ( RO): 
              last-boot-record ( RO): ''(''struct''
(''uuid''
''83e4ea16-480e-bdd4-a765-c733a96e09dc'')
(''allowed_operations'' (''array''))
(''current_operations'' (''struct''
(''OpaqueRef:1f1b048b-11dd-65f6-e161-711febdcd183''
''start'')))
(''power_state'' ''Halted'')
(''name_label'' ''heath-2'')
(''name_description''
''Installed via xe CLI'') (''user_version''
''1'') (''is_a_template''
(''boolean''
''0'')) (''suspend_VDI''
''OpaqueRef:NULL'') (''resident_on''
''OpaqueRef:NULL'')
(''affinity'' ''OpaqueRef:NULL'')
(''memory_overhead'' ''5242880'')
(''memory_target'' ''268435456'')
(''memory_static_max'' ''268435456'')
(''memory_dynamic_max'' ''268435456'')
(''memory_dynamic_min'' ''268435456'')
(''memory_static_min'' ''134217728'')
(''VCPUs_params'' (''struct''))
(''VCPUs_max'' ''1'')
(''VCPUs_at_startup'' ''1'')
(''actions_after_shutdown''
''destroy'') (''actions_after_reboot''
''restart'') (''actions_after_crash''
''restart'') (''consoles''
(''array'')) (''VIFs''
(''array'')) (''VBDs''
(''array''))
(''crash_dumps'' (''array''))
(''VTPMs'' (''array''))
(''PV_bootloader'' '''')
(''PV_kernel'' '''')
(''PV_ramdisk'' '''')
(''PV_args'' '''')
(''PV_bootloader_args''
'''') (''PV_legacy_args'' '''')
(''HVM_boot_policy'' ''BIOS order'')
(''HVM_boot_params'' (''struct''
(''order'' ''dc'')))
(''HVM_shadow_multiplier''
(''double'' ''1''))
(''platform'' (''struct''
(''nx'' ''false'') (''acpi''
''true'')
(''apic'' ''true'') (''pae''
''true'') (''viridian''
''true''))) (''PCI_bus'' '''')
(''other_config'' (''struct''
(''install-methods'' ''cdrom,http'')
(''install-repository''
''http://192.168.1.10/mnt/Fedora-14-x86_64'')
(''mac_seed''
''67dc6d71-a880-1830-0cb0-5506920674f3'')))
(''domid'' ''-1'')
(''domarch'' '''')
(''last_boot_CPU_flags'' (''struct''))
(''is_control_domain''
(''boolean'' ''0''))
(''metrics''
''OpaqueRef:2491ff67-ec3b-0072-af1b-a20f7c930943'')
(''guest_metrics''
''OpaqueRef:NULL'') (''last_booted_record''
'''') (''recommendations''
''<restrictions><restriction
field=\"memory-static-max\"
max=\"34359738368\" /><restriction field=\"vcpus-max\"
max=\"8\"
/><restriction property=\"number-of-vbds\" max=\"7\"
/><restriction
property=\"number-of-vifs\" max=\"7\"
/></restrictions>'')
(''xenstore_data'' (''struct''))
(''ha_always_run'' (''boolean''
''0''))
(''ha_restart_priority'' '''')
(''is_a_snapshot'' (''boolean''
''0''))
(''snapshot_of'' ''OpaqueRef:NULL'')
(''snapshots'' (''array''))
(''snapshot_time'' (''dateTime.iso8601''
''19700101T00:00:00Z''))
(''transportable_snapshot_id'' '''')
(''blobs'' (''struct''))
(''tags'' (''array''))
(''blocked_operations'' (''struct''))
(''snapshot_info'' (''struct''))
(''snapshot_metadata'' '''')
(''parent''
''OpaqueRef:d60bcd97-8905-8881-9ac4-9cd2561195ab'')
(''children'' (''array''))
(''bios_strings'' (''struct''))
(''protection_policy'' ''OpaqueRef:NULL'')
(''is_snapshot_from_vmpp'' (''boolean''
''0'')))''
                   resident-on ( RO):
6d288164-43e0-4f3b-ae1a-a7302e21aec4
                      affinity ( RW): <not in database>
                  other-config (MRW): install-methods: cdrom,http;
install-repository: http://192.168.1.10/mnt/Fedora-14-x86_64; mac_seed:
67dc6d71-a880-1830-0cb0-5506920674f3
                        dom-id ( RO): 16
               recommendations ( RO): <restrictions><restriction
field="memory-static-max" max="34359738368"
/><restriction
field="vcpus-max" max="8" /><restriction
property="number-of-vbds"
max="7" /><restriction property="number-of-vifs"
max="7"
/></restrictions>
                 xenstore-data (MRW): 
                 ha-always-run ( RW): false
           ha-restart-priority ( RW): 
                         blobs ( RO): 
                    start-time ( RO): 20110517T16:27:10Z
                  install-time ( RO): 20110517T16:27:09Z
                  VCPUs-number ( RO): 1
             VCPUs-utilisation (MRO): 
                    os-version (MRO): <not in database>
            PV-drivers-version (MRO): <not in database>
         PV-drivers-up-to-date ( RO): <not in database>
                        memory (MRO): <not in database>
                         disks (MRO): <not in database>
                      networks (MRO): <not in database>
                         other (MRO): <not in database>
                          live ( RO): <not in database>
    guest-metrics-last-updated ( RO): <not in database>
                   cooperative ( RO): true
             protection-policy ( RW): <not in database>
         is-snapshot-from-vmpp ( RO): false
                          tags (SRW): 



Thanks,

Joe

-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Mike McClurg
Sent: Tuesday, May 17, 2011 3:39 AM
To: Joe Linoff; xen-users@lists.xensource.com
Subject: Re: [Xen-users] Problems creating a Fedora 14 domU using XCP
1.0and xe

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@192.168.1.10
>
> ## 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@lists.xensource.com
> http://lists.xensource.com/xen-users

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

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

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

Mike McClurg

2011-May-18 10:40 UTC

head link

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

On 17/05/11 21:40, Joe Linoff wrote:> Hi Mike:
>
> Just a quick follow up. It was trivial to get things working using NFS
> -- thank you. But I still can''t get the http boot to work. Could
there
> be some sort of bug or am I just missing something?
>I did some testing this morning and I wasn''t able to get Fedora 14 to 
boot from an HTTP repository. I tried the Other install media, RHEL 6 
and CentOS 5 templates, and each time I got errors from eliloader. 
Unfortunately this isn''t totally unexpected: eliloader does some really
OS-specific things with the repositories, and none of our supported 
templates were made to work with Fedora. I''ve heard that someone here
is
working on making eliloader a little more generic, but I''m not really 
familiar with what''s going on there.

The best way to do what you want to do is definitely to export your ISOs 
on an NFS share and mount them on your pool as an ISO SR. Hope that helps,

Mike

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

Joe Linoff

2011-May-19 16:29 UTC

head link

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

Hi Mike:
> Hope that helps
It really helps. Thank you for taking the time to help me out.

Regards,

Joe

-----Original Message-----
From: Mike McClurg [mailto:mike.mcclurg@citrix.com] 
Sent: Wednesday, May 18, 2011 3:41 AM
To: Joe Linoff
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Problems creating a Fedora 14 domU using XCP
1.0and xe

On 17/05/11 21:40, Joe Linoff wrote:> Hi Mike:
>
> Just a quick follow up. It was trivial to get things working using NFS
> -- thank you. But I still can''t get the http boot to work. Could
there
> be some sort of bug or am I just missing something?
>I did some testing this morning and I wasn''t able to get Fedora 14 to 
boot from an HTTP repository. I tried the Other install media, RHEL 6 
and CentOS 5 templates, and each time I got errors from eliloader. 
Unfortunately this isn''t totally unexpected: eliloader does some really
OS-specific things with the repositories, and none of our supported 
templates were made to work with Fedora. I''ve heard that someone here
is

working on making eliloader a little more generic, but I''m not really 
familiar with what''s going on there.

The best way to do what you want to do is definitely to export your ISOs

on an NFS share and mount them on your pool as an ISO SR. Hope that
helps,

Mike

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

Possibly Parallel Threads

Search for more possibly parallel threads

Xen users - May 2011 - Problems creating a Fedora 14 domU using XCP 1.0 and xe

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

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

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

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

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

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

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

Possibly Parallel Threads