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

Re: [Xen-users] Install ubunto domU



On Thu, May 27, 2010 at 09:39:51PM -0700, Boris Derzhavets wrote:
> You can run Ubuntu Lucid PV guest at 3.4.2, but not via "pygrub"
> Gitco.de/repo doesn't contain required 4.0 src.rpm . It's Gunter's policy i 
> guess.
> When he will make 4.0.1 he would probably provide it.
> I would remove CentOS 5.4 as Dom0 base and build system on F13 (F12)
> due to xen-4.0.0.-0.7.f12.src.rpm available at xensource.
> 

Or then use CentOS 5.5 as dom0 and apply the el5 pygrub grub2 patch from:
https://bugzilla.redhat.com/show_bug.cgi?id=577511

-- Pasi

> wget http://pasik.reaktio.net/fedora/xen-4.0.0-0.7.fc12.src.rpm
> 
> Boris.
> 
> 
> --- On Thu, 5/27/10, Donny Brooks <dbrooks@xxxxxxxxxxxxxxxx> wrote:
> 
>   From: Donny Brooks <dbrooks@xxxxxxxxxxxxxxxx>
>   Subject: Re: [Xen-users] Install ubunto domU
>   To: "xen-users" <xen-users@xxxxxxxxxxxxxxxxxxx>
>   Date: Thursday, May 27, 2010, 3:21 PM
> 
>   I read this and I gather I need to be running Xen 4.0 in order to run 
> Ubuntu 10.04 as a pv domu... is that
>   correct? I am currently at 3.4.2 on a centos 5.4 dom0 but need to run some 
> ubuntu domu's very badly. Please
>   advise!
> 
>   --
> 
>   Donny B.
> 
>   On Monday, May 17, 2010 10:39 PM CDT, Boris Derzhavets 
> <[1]bderzhavets@xxxxxxxxx> wrote:
> 
>   > > I tried to follow your steps (installing Lucid x86_64 PV domU on a
>   > CentOS 54 x86_64 dom0, running xen 3.4.2 from gitco) ... but was not
>   > successful. Something is still escaping me.
>   >
>   > Yes , you missing David's patch. Personally , i could back port it only 
> to Xen 4.0,
>   > even Xen 3.4.3 was not enough. Some other CSs from 4.0 are required for 
> consistency and you don't know
>   which ones.
>   >
>   > You are at 3.4.2 !
>   >
>   > I believe gitco did Xen 4.0 rpms. Gitgo's  4.0 src.rpm has to patched per 
> David and rpms rebuilt. That 's
>   in case you want "pygrub" to be bootloader for DomU . It's comfortable, but 
> not required.
>   >
>   > Boris.
>   >
>   > --- On Mon, 5/17/10, David Markey <[2]admin@xxxxxxxxxxx> wrote:
>   >
>   > From: David Markey <[3]admin@xxxxxxxxxxx>
>   > Subject: Re: [Xen-users] Install ubunto domU
>   > To: "Nuno L. Ferreira" <[4]nunolf@xxxxxxxxx>
>   > Cc: "Boris Derzhavets" <[5]bderzhavets@xxxxxxxxx>, "xen-users" 
> <[6]xen-users@xxxxxxxxxxxxxxxxxxx>
>   > Date: Monday, May 17, 2010, 6:54 PM
>   >
>   > You need 
> [7]http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00748.html
>   >
>   >
>   > On 17 May 2010 23:24, Nuno L. Ferreira <[8]nunolf@xxxxxxxxx> wrote:
>   >
>   > Dear *, Boris
>   >
>   >
>   >
>   > I tried to follow your steps (installing Lucid x86_64 PV domU on a CentOS 
> 54 x86_64 dom0, running xen
>   3.4.2 from gitco) ... but was not successful. Something is still escaping 
> me.
>   >
>   > Installation went just fine till the end after a "xm create -c lucid.xen" 
> (see below).
>   >
>   > After installation (without any modifications to what was installed) I 
> edited the xen config file
>   (test.xen, see below) to boot with pygrub instead. But I get the following 
> error:
>   >
>   > Error: Boot loader didn't return any data!
>   >
>   >
>   >
>   > I checked that the new domU does not have /usr/bin/pygrub, and this 
> explains the error.
>   >
>   > So Boris, how did you boot your ubunto based domU after a netboot 
> installation?
>   >
>   > I did not tried yet the debootstrap method also suggested ... first I 
> want to know what I'm doing wrong
>   here.
>   >
>   >
>   >
>   > I'm a bit lost on setting up an ubunto domU, first time getting outside 
> RedHat like OSes. So if there are
>   some good working links to blogs/tutorials on how to install ubunto domU's 
> on RedHat like dom0's I'll
>   appreciate.
>   >
>   >
>   >
>   >
>   > Cheers,
>   >
>   > N.
>   >
>   >
>   >
>   > P.S. Steps taken :
>   >
>   >
>   >
>   > 1 - lvcreate -n domu.ubunto.lucid -L 4G vg1
>   >
>   > 2 - mkfs.ext3 /dev/vg1/domu.ubunto.lucid
>   >
>   > 3 - wget
>   
> [9]http://archive.ubuntu.com/ubuntu/dists/lucid/main/installer-amd64/current/images/netboot/xen/vmlinuz
>   >
>   >
>   > 4 - wget
>   
> [10]http://archive.ubuntu.com/ubuntu/dists/lucid/main/installer-amd64/current/images/netboot/xen/initrd.gz
>   >
>   >
>   > 5 - cat lucid.xen
>   >
>   > name      = "lucid"
>   >
>   > memory    = 1024
>   >
>   > disk      = ['phy:/dev/vg1/domu.ubunto.lucid,xvda,w' ]
>   >
>   > vif       = [ 'bridge=eth0' ]
>   >
>   > kernel    = "/mnt/dom0/data/domu.setup/ubunto/lucid/vmlinuz"
>   >
>   > ramdisk   = "/mnt/dom0/data/domu.setup/ubunto/lucid/initrd.gz"
>   >
>   > vcpus     = 1
>   >
>   > on_reboot = 'destroy'
>   >
>   > on_crash  = 'destroy'
>   >
>   >
>   >
>   > 6 - xm create -c lucid.xen
>   >
>   > ... installation goes just fine ...
>   >
>   > 7 - cat test.xen
>   >
>   > name        = "test"
>   >
>   > memory      = 512
>   >
>   > maxmem      = 1024
>   >
>   > bootloader  = '/usr/bin/pygrub'
>   >
>   > disk        = ['phy:/dev/vg1/domu.spyder.root,xvda,w' ]
>   >
>   > vif         = [ 'bridge=eth0' ]
>   >
>   > vcpus       = 1
>   >
>   > on_poweroff = 'destroy'
>   >
>   > on_reboot   = 'restart'
>   >
>   > on_crash    = 'restart'
>   >
>   >
>   >
>   > 8 - xm create -c test.xen
>   >
>   > Using config file "./test.xen".
>   >
>   > Error: Boot loader didn't return any data!
>   >
>   >
>   >
>   >
>   >
>   >
>   >
>   >
>   >
>   > Boris Derzhavets wrote:
>   >
>   >
>   > I was able to start installer :
>   >
>   >
>   >
>   > root@ServerLnx:/home/boris/ubuntu# wget
>   
> [11]http://archive.ubuntu.com/ubuntu/dists/lucid/main/installer-amd64/current/images/netboot/xen/vmlinuz
>   >
>   >
>   > --2010-05-13 12:36:14--
>    
> [12]http://archive.ubuntu.com/ubuntu/dists/lucid/main/installer-amd64/current/images/netboot/xen/vmlinuz
>   >
>   >
>   > Resolving archive.ubuntu.com... 91.189.92.167, 91.189.88.30, 
> 91.189.88.31, ...
>   >
>   > Connecting to archive.ubuntu.com|91.189.92.167|:80... connected.
>   >
>   > HTTP request sent, awaiting response... 200 OK
>   >
>   > Length: 4037888 (3.9M) [text/plain]
>   >
>   > Saving to: `vmlinuz'
>   >
>   >
>   >
>   > 
> 100%[========================================================================>]
>  4,037,888    101K/s   in
>   27s
>   >
>   > 2010-05-13 12:36:41 (144 KB/s) - `vmlinuz' saved [4037888/4037888]
>   >
>   >
>   >
>   > root@ServerLnx:/home/boris/ubuntu# wget
>   
> [13]http://archive.ubuntu.com/ubuntu/dists/lucid/main/installer-amd64/current/images/netboot/xen/initrd.gz
>   >
>   >
>   > --2010-05-13 12:37:02--
>    
> [14]http://archive.ubuntu.com/ubuntu/dists/lucid/main/installer-amd64/current/images/netboot/xen/initrd.gz
>   >
>   >
>   > Resolving archive.ubuntu.com... 91.189.92.166, 91.189.92.167, 
> 91.189.88.30, ...
>   >
>   > Connecting to archive.ubuntu.com|91.189.92.166|:80... connected.
>   >
>   > HTTP request sent, awaiting response... 200 OK
>   >
>   > Length: 9678415 (9.2M) [application/x-gzip]
>   >
>   > Saving to: `initrd.gz'
>   >
>   >
>   >
>   > 
> 100%[========================================================================>]
>  9,678,415    200K/s   in
>   60s
>   >
>   > 2010-05-13 12:38:03 (156 KB/s) - `initrd.gz' saved [9678415/9678415]
>   >
>   >
>   >
>   > root@ServerLnx:/home/boris/ubuntu# cat ubuntu.cfg
>   >
>   > name="U10PV"
>   >
>   > memory=2048
>   >
>   > disk = ['phy:/dev/sdb5,xvda,w' ]
>   >
>   > vif = [ 'bridge=eth0' ]
>   >
>   > # vfb = [ 'type=vnc,vncunused=1']
>   >
>   > kernel = "/home/boris/ubuntu/vmlinuz"
>   >
>   > ramdisk = "/home/boris/ubuntu/initrd.gz"
>   >
>   > vcpus=2
>   >
>   > on_reboot = 'restart'
>   >
>   > on_crash = 'restart'
>   >
>   >
>   >
>   > # xm create -c ubuntu.cfg
>   >
>   >
>   >
>   > and see several obvious disadvantages (vs HVM convertion) :
>   >
>   >
>   >
>   > 1. VFB doesn't work
>   >
>   > 2. After selecting local mirror "Installing base system" is already 
> running for 15 min
>   >
>   > at 2MB/sec ADSL connection.
>   >
>   >
>   >
>   > Boris.
>   >
>   >
>   >
>   >
>   >
>   > -----Inline Attachment Follows-----
>   >
>   > _______________________________________________
>   > Xen-users mailing list
>   > [15]Xen-users@xxxxxxxxxxxxxxxxxxx
>   > [16]http://lists.xensource.com/xen-users
>   >
>   >
>   >
> 
>   _______________________________________________
>   Xen-users mailing list
>   [17]Xen-users@xxxxxxxxxxxxxxxxxxx
>   [18]http://lists.xensource.com/xen-users
> 
> References
> 
>    Visible links
>    1. file:///mc/compose?to=bderzhavets@xxxxxxxxx
>    2. file:///mc/compose?to=admin@xxxxxxxxxxx
>    3. file:///mc/compose?to=admin@xxxxxxxxxxx
>    4. file:///mc/compose?to=nunolf@xxxxxxxxx
>    5. file:///mc/compose?to=bderzhavets@xxxxxxxxx
>    6. file:///mc/compose?to=xen-users@xxxxxxxxxxxxxxxxxxx
>    7. http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00748.html
>    8. file:///mc/compose?to=nunolf@xxxxxxxxx
>    9. 
> http://archive.ubuntu.com/ubuntu/dists/lucid/main/installer-amd64/current/images/netboot/xen/vmlinuz
>   10. 
> http://archive.ubuntu.com/ubuntu/dists/lucid/main/installer-amd64/current/images/netboot/xen/initrd.gz
>   11. 
> http://archive.ubuntu.com/ubuntu/dists/lucid/main/installer-amd64/current/images/netboot/xen/vmlinuz
>   12. 
> http://archive.ubuntu.com/ubuntu/dists/lucid/main/installer-amd64/current/images/netboot/xen/vmlinuz
>   13. 
> http://archive.ubuntu.com/ubuntu/dists/lucid/main/installer-amd64/current/images/netboot/xen/initrd.gz
>   14. 
> http://archive.ubuntu.com/ubuntu/dists/lucid/main/installer-amd64/current/images/netboot/xen/initrd.gz
>   15. file:///mc/compose?to=Xen-users@xxxxxxxxxxxxxxxxxxx
>   16. http://lists.xensource.com/xen-users
>   17. file:///mc/compose?to=Xen-users@xxxxxxxxxxxxxxxxxxx
>   18. 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


 


Rackspace

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