Re: [Xen-users] Installing domU from ISO image file

[David Koski <david@xxxxxxxxxxxxxxxx>]

I get the same results.  There is no change.  Now use vncviewer to connect to 
the session and try to do an install.  See if it finds the "CD-ROM".  See if 
it says "No driver found" and prompts for "Select driver" so it can find the 
CD-ROM.

Thanks!
David

On Friday 26 December 2008, Boris Derzhavets wrote:
> Done just now :-
>
> root@boris-desktop:/etc/xen/isos# losetup /dev/loop0
> /etc/xen/isos/rhel52.iso root@boris-desktop:/etc/xen/isos# losetup -a
> /dev/loop0: [081c]:51049 (/etc/xen/isos/rhel52.iso)
>
> root@boris-desktop:/etc/xen/vm# uname -a
> Linux boris-desktop 2.6.24-21-xen #1 SMP Wed Oct 22 01:07:57 UTC 2008
> x86_64 GNU/Linux root@boris-desktop:/etc/xen/vm# xm info
> host                   : boris-desktop
> release                : 2.6.24-21-xen
> version                : #1 SMP Wed Oct 22 01:07:57 UTC 2008
> machine                : x86_64
> nr_cpus                : 2
> nr_nodes               : 1
> cores_per_socket       : 2
> threads_per_core       : 1
> cpu_mhz                : 2400
> hw_caps                :
> bfebfbff:20100800:00000000:00000140:0000e3bd:00000000:00000001:00000000
> virt_caps              : hvm
> total_memory           : 4095
> free_memory            : 128
> node_to_cpu            : node0:0-1
> node_to_memory         : node0:128
> xen_major              : 3
> xen_minor              : 3
> xen_extra              : .0
> xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
> hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler          : credit
> xen_pagesize           : 4096
> platform_params        : virt_start=0xffff800000000000
> xen_changeset          : unavailable
> cc_compiler            : gcc version 4.2.4 (Ubuntu 4.2.4-1ubuntu3)
> cc_compile_by          : buildd
> cc_compile_domain      : buildd
> cc_compile_date        : Wed Oct 29 23:39:07 UTC 2008
> xend_config_format     : 4
> root@boris-desktop:/etc/xen/vm# cat rhel52.cfg
> name="RHEL52PV"
> memory=2048
> disk = ['phy:/dev/loop0,hdc:cdrom,r','phy:/dev/sdb9,xvda,w' ]
> vif = [ 'bridge=eth1' ]
> vfb = [ 'type=vnc,vncunused=1' ]
> bootloader = "/usr/bin/pygrub"
> kernel = "/images/xen/vmlinuz"
> ramdisk = "/images/xen/initrd.img"
> vcpus=1
> on_reboot = 'restart'
> on_crash = 'restart'
> root@boris-desktop:/etc/xen/vm# xm create rhel52.cfg
> Using config file "./rhel52.cfg".
> Started domain rhel52.cfg
> root@boris-desktop:/etc/xen/vm#
> root@boris-desktop:/etc/xen/vm# xm list
> Name                                          ID   Mem VCPUs      State  
> Time(s) Domain-0                                     0  1942     2    
> r-----    447.1 RHEL52PV                                   1  2048    
> 1     -b----      6.0
>
>
> --- On Fri, 12/26/08, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:
> From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
> Subject: Re: [Xen-users] Installing domU from ISO image file
> To: xen-users@xxxxxxxxxxxxxxxxxxx, "David Koski" <david@xxxxxxxxxxxxxxxx>
> Date: Friday, December 26, 2008, 3:28 PM
>
>
>
> --- On Fri, 12/26/08, David Koski <david@xxxxxxxxxxxxxxxx> wrote:
> From: David Koski <david@xxxxxxxxxxxxxxxx>
> Subject: Re: [Xen-users] Installing domU from ISO image file
> To: xen-users@xxxxxxxxxxxxxxxxxxx, bderzhavets@xxxxxxxxx
> Date: Friday, December 26, 2008, 2:12 PM
>
> # uname -a
> Linux northgate 2.6.24-22-xen #1 SMP Mon Nov 24 21:30:37 UTC 2008 i686
> GNU/Linux
>
> # xm info
> host                   : northgate
> release                : 2.6.24-22-xen
> version                : #1 SMP Mon Nov 24 21:30:37 UTC 2008
> machine                : i686
> nr_cpus                : 1
> nr_nodes               : 1
> cores_per_socket       : 1
> threads_per_core       : 1
> cpu_mhz                :
>  3061
> hw_caps                :
> bfebfbff:20000000:00000000:00000180:0000651d:00000000:00000001:00000000
> virt_caps              :
> total_memory           : 503
> free_memory            : 30
> node_to_cpu            : node0:0
> node_to_memory         : node0:30
> xen_major              : 3
> xen_minor              : 3
> xen_extra              : .0
> xen_caps               : xen-3.0-x86_32p
> xen_scheduler          : credit
> xen_pagesize           : 4096
> platform_params        : virt_start=0xf5800000
> xen_changeset          : unavailable
> cc_compiler            : gcc version 4.2.4 (Ubuntu 4.2.4-1ubuntu3)
> cc_compile_by          : buildd
> cc_compile_domain      : buildd
> cc_compile_date        : Wed Oct 29 23:37:58 UTC 2008
> xend_config_format     : 4
>
> # brctl show
> bridge name     bridge id               STP enabled     interfaces
> eth1            8000.005004700f55       no              peth1
>
> # losetup
>  -a
> (no output)
>
> # egrep -v "(^$|^\#)" /etc/xen/cos52.cfg
> name = "cos52"
> memory = 512
>
> Please,run before starting install :-
>
> #losetup /dev/loop0 /etc/xen/iso/COS52.iso
>
> Verify loop device is present:-
>
> # losetup -a
> /dev/loop0: [080b]:1046765 (/etc/xen/iso/COS52.iso)
>
> Cat and paste into profile :-
>
> disk = ['phy:/dev/loop0,hdc:cdrom,r','phy:/dev/vg00/elastix,xvda,w']
> vif = [ 'bridge=eth1' ]
>
>
> #  disk = ['file:/etc/xen/iso/COS52.iso,ioemu:hdc:cdrom,r',
> # 'phy:/dev/vg00/elastix,xvda1,w' ]
>
> Two errors i guess :-
> 1. "ioemu" for paravirtual guest is incorrect
> 2.  xvda not xvda1
>
> # vif = [ '' ]
>
> Bridge not specified
>
>
>
> vfb = ["type=vnc,vncunused=1"]
> bootloader = "/usr/bin/pygrub"
> kernel = '/images/xen/vmlinuz'
> ramdisk = '/images/xen/initrd.img'
> vcpus = 1
> on_reboot = 'restart'
> on_crash = 'restart'
>
> Of course the above is without
>  mounting to loop.  I have tried mounting to loop
> with the same results.
>
> Thank you,
> David
>
> On Friday 26 December 2008 10:59, Boris Derzhavets wrote:
> > Please, submit outputs :-
> >
> > # uname  -a
> >
> > # xm info
> >
> > # brctl show
> >
> > #losetup -a
> >
> > and profile cos52.cfg
> >
> > It should work, if everything is tuned well.
> >
> > --- On Fri, 12/26/08, David Koski <david@xxxxxxxxxxxxxxxx> wrote:
> > From: David Koski <david@xxxxxxxxxxxxxxxx>
> > Subject: Re: [Xen-users] Installing domU from ISO image file
> > To: xen-users@xxxxxxxxxxxxxxxxxxx
> > Date: Friday, December 26, 2008, 1:23 PM
> >
> > I am running 2.6.24-22-xen kernel.  It has been a while since I installed
> > this and I have tried so many things that I can't remember how I
>
> installed
>
> > it but
> > I do have backports in my
>
>  sources.list:
> > deb http://ftp.osuosl.org/pub/ubuntu/ hardy-backports main restricted
> > universe multiverse
> >
> > Anyhow, I did try booting 2.6.24-22 and 3.2 xen but I got:
> >
> > # xm create cos52.cfg -c
> > Using config file "/etc/xen/cos52.cfg".
> > Error: (38, 'Function not implemented')
> >
> > Thank you,
> > David
> >
> > On Friday 26 December 2008 00:36, Boris Derzhavets wrote:
> > > I've got it working on Hardy (native 3.2) Dom0 :-
> > >
> > > http://lxer.com/module/newswire/view/110642/index.html
> > >
> > > Intrepid Xen 3.3 Hypervisor may be back ported to Hardy Dom0 :-
> > >
> > > http://lxer.com/module/newswire/view/112045/index.html
> > >
> > > and i believe http://lxer.com/module/newswire/view/110642/index.html
> > > may be reproduced at Xen 3.3 Hardy Dom0 (2.6.24-22-xen)
> > >
> > > In case
>
>  of Xen 3.3 complete port to Ubuntu Hardy , in general, it
> should
>
> > > (?) work as well, but instead  of native vmlinuz-2.6.24-22-xen your
> >
> > system
> >
> > > is driven by vmlinuz-2.6.18.8-xen. View changes in profile.
> > >
> > > --- On Fri, 12/26/08, David Koski <david@xxxxxxxxxxxxxxxx>
>
> wrote:
> > > From: David Koski <david@xxxxxxxxxxxxxxxx>
> > > Subject: [Xen-users] Installing domU from ISO image file
> > > To: xen-users@xxxxxxxxxxxxxxxxxxx
> > > Date: Friday, December 26, 2008, 12:38 AM
> > >
> > > I am trying to install CentOS from an ISO image file but the
>
> installer
>
> > does
> >
> > > not see a CD-ROM drive.  The VNC viewer works but the CentOS
>
> installer
>
> > > indicates "Unable to find any devices of the type needed for
>
> this
>
> > > installation type."  Then it prompts with "[Select
>
>  driver]
> [Use
>
> > a
> >
> > > driver
> > > disk] [Back]".  I have tried several variations of the
> >
> > "disk"
> >
> > > paramater, all
> > > with the same results.  I also used losetup to attach the imate to
> > > /dev/loop0 and tried the commented out "disk" parameters
>
> with
>
> > the same
> >
> > > results.
> > >
> > > xen is 3.3
> > > OS is Ubuntu 8.04
> > >
> > >   1 name = "cos52"
> > >   2 memory = 128
> > >   3
> > >   4
> > > I've commented out this entries (B.D.)
> > > ************************************************************
> > > #  disk = [ 'file:/etc/xen/iso/COS52.iso,ioemu:hdc:cdrom,r',
> > > 'phy:/dev/vg00/elastix,xvda1,w' ]
> > > #disk = [
> >
> > 'phy:loop0,hdc,r','phy:/dev/vg00/elastix,xvda1,w' ]
>
>  *************************************************************
>
> > > disk = [
>
> 'phy:/dev/loop0,hdc:cdrom,r','phy:/dev/vg00/elastix,xvda1,w' ]
>
> > >   6
> > >   7
> > >   8 vif = [ '' ]
> > >   9 vfb =
>
> ["type=vnc,vncunused=1,vnclisten=0.0.0.0,vncpasswd=kalamoja"]
>
> > >  10
> > >  11 bootloader = "/usr/bin/pygrub"
> > >  12 kernel = '/images/xen/vmlinuz'
> > >  13 ramdisk = '/images/xen/initrd.img'
> > >  14
> > >  15 vcpus = 1
> > >  16 on_reboot = 'restart'
> > >  17 on_crash = 'restart'
> > >  18
> > >
> > > Any suggestions?
> > >
> > > Regards,
> > > David Koski
> > > dkoski@xxxxxxxxxxx
> > >
> > > _______________________________________________
> > > 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
>
>       _______________________________________________
> 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