WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] How do you add a bootable cdrom ISO?

To: "Per Jensen" <per@xxxxxxxxx>
Subject: RE: [Xen-users] How do you add a bootable cdrom ISO?
From: "James Dingwall" <james.dingwall@xxxxxxxxxx>
Date: Fri, 4 Sep 2009 09:01:14 +0100
Cc: Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 04 Sep 2009 01:03:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4AA0308B.9040109@xxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <7547505.3301251990993806.JavaMail.root@xxxxxxxxxxxxxx><1251999114.17253.17.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <4AA0308B.9040109@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acos2veDBmC/OdP4TPyCTbL0isndtAAWaQFA
Thread-topic: [Xen-users] How do you add a bootable cdrom ISO?
> James Pifer skrev:
> >> James,
> >>
> >> I needed to restore a server from a 'dar' backupset. What I did was
> to "copy" the server .cfg and make it a HVM setup.
> >>
> >> When started, I connected to the vnc server on port 5900 and did the
> usual stuff when working from a rescue cdrom.
> >>
> >> The config went like this (Debian Lenny Xen 3.2.1):
> >>
> >> # boot fra CD-ROM
> >> kernel = '/usr/lib/xen-3.2-1/boot/hvmloader'
> >> builder = 'hvm'
> >> boot = "d"
> >> memory = '512'
> >>
> >> #
> >> #  Disk device(s).
> >> #
> >> root        = '/dev/hda ro'
> >> disk        = [
> >>                    'phy:/dev/vg01/balrog2.net-es.dk-disk,hda,w',
> >>                    'phy:/dev/vg01/balrog2.net-es.dk-swap,hdb,w',
> >>                    'phy:/dev/vg01/balrog-backup,hdc,r',
> >>                    'phy:/usr/local/sysresccd.iso,hdd:cdrom,r'
> >>               ]
> >>
> >> #
> >> #  Hostname
> >> #
> >> name        = 'balrog2-hvm'
> >>
> >> #
> >> #  Networking
> >> #
> >> vif         = [ 'ip=192.168.2.11,mac=00:16:3E:32:38:D9' ]
> >>
> >> #
> >> #  Behaviour
> >> #
> >> on_poweroff = 'destroy'
> >> on_reboot   = 'restart'
> >> on_crash    = 'restart'
> >>
> >>
> >> keymap="da"
> >>
> >> vnc=1
> >> vnclisten="0.0.0.0"
> >> vncconsole=1
> >
> > Sorry, forgot to change "To" to the list....
> >
> > Per,
> >
> > Thanks for the response, but I'm not seeing where this helps me.
> >
> > Thanks,
> > James
> >
> James,
> 
> Perhaps I misunderstood your problem. the problem I had was to boot my
> PV    machine from a rescue cd, which can only be done in a 'hvm'
> config
> (as I understand)
> 
> The problem for me was to  convert the PV config to a 'hvm' type,
> particularly the disk layout. I thought my config could help you along.
> 
> /Per

I have managed to boot Fedora11 and OpenSolaris 09.06 as PV domUs since my 
hardware can't do hvm.  It is usually just a case of giving pygrub the correct 
boot arguments and making sure the .iso is the first line in the disk = [] 
stanza.

e.g.

Fedora 11:
bootloader = "/usr/bin/pygrub"
bootargs = "--kernel=/isolinux/vmlinuz --ramdisk=/isolinux/initrd.img"
disk = [ 'file:/misc/iso/fedora/Fedora-11-x86_64-DVD.iso,xvdc:cdrom,r' ]

OpenSolaris:
bootloader = "/usr/bin/pygrub"
bootargs = "--kernel=/platform/i86xpv/kernel/amd64/unix 
--ramdisk=/boot/amd64/x86.microroot"
disk = [ 'file:/misc/iso/solaris/OpenSolaris/osol-0906-x86.iso,xvdc:cdrom,r' ]

I haven't managed to get the livecd for FC11 to work as it seems the kernel on 
the disk doesn't have domU support.  OpenSolaris doesn't seem to support the PV 
virtual fb yet so only command line mode.

James

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users