Just in case, if pygrub fails to read image been created , as it happens for
OpenSuse 11 PV DomU at Xen 3.2 Ubuntu Hardy Dom0. Xenified kernel and ramdisk
may be copied of the image device to Dom0 and DomU may be loaded via profile :-
name='CentOS52PV'
memory='1024'
kernel=/etc/xen/vm/vmlinuz-2.6.18-92.xen
ramdisk=/etc/xen/vm/initrd-2.6.18-92.xen
extra='root=/dev/VolGroup01/LogVol00'
disk=['file:/etc/xen/images/centos.img,xvda,w']
vfb= [ 'type=vnc,vncunused=1' ]
vif =['bridge=eth0']
# xm create CentOS52.cfg
# vncviewer localhost:0
Actually, i mean that pygrub is not required if you were lucky enough to
create image via local Apache instance at Dom0. I never experienced
problems with pygrub access to local http source at Xen 3.3 CentOS 5.2 Dom0
and Xen 3.2 Ubuntu Hardy Dom0.
--- On Fri, 10/24/08, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Subject: [Xen-users] Pygrub & install CentOS 5.2 PV DomU at Xen 3.2 Ubuntu Hardy Dom0 via local HTTP Server (all 64-bit)
To: "James Corteciano" <linux@xxxxxxxxxxxxxxxxx>
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Date: Friday, October 24, 2008, 2:25 AM
The way it works on Ubuntu Hardy Dom0 . Just don't have Debian at Dom0, but
Xen 3.2.1 at Dom0 should be good .
First pygrub installation profile creates image on device via repository at local HTTP Server at Dom0 .
Second pygrub runtime profile loads CentOS 5.2 PV DomU having image already
has been created
http://lxer.com/module/newswire/view/110642/index.html
--- On Thu, 10/9/08, James Corteciano <linux@xxxxxxxxxxxxxxxxx> wrote:
From: James Corteciano <linux@xxxxxxxxxxxxxxxxx>
Subject: [Xen-users] xen 3.2.1 - How to boot ISO image
To:
Date: Thursday, October 9, 2008, 12:49
PM
Hi All, I have working CentOS xen guest (domU) inside in Debian xen
domain (dom0) and here is the domU's config file < http://fpaste.org/paste/7295>.
How could I put the proper syntax inside of domU's config to instruct the domU to boot the /data/CentOS-5.1-i386-bin-DVD.iso during starting of domU? BTW, I am using xen-3.2-1. Thanks,
James
_______________________________________________
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 |
