post, appeared to be a bit more complicated. Pygrub installation profile reading data from HTTP source at Dom0 still worked fine, but Xen 3.2 Ubuntu’s 8.04.1 pygrub failed to read image had been created for OpenSuse 11 PV DomU (/dev/sda11) . Just an ordinary “xm” profile was required to finish configuration and load PV DomU when image was already created on block device, say /dev/sda11. Xenified kernel and ramdisk had to be copied of image device to Dom0 file system. There may be several ways of achieving this goal. I just selected the easiest for myself. Having already CentOS 5.2 PV DomU up and running attached /dev/sda11 via “xm block-attach” to running DomU as “hdb” , mounted /dev/hdb1 inside DomU and scp’ed suse’s xenified kernel and ramdisk to Dom0. Notice, that virtual frame buffer would work fine for OpenSuse 11 PV at Ubuntu Hardy Dom0 (2.6.24-21-xen). Setup Apache at Ubuntu Hardy Dom0.
Manage during initial configuration and installation phase for OpenSuse 11 PV DomU exactly as it was done in  for CentOS 5.2 DomU. Pygrub’s profiles performing this step are similar for both DomUs.
Only paths to distro’s vmlinuz-xen and initrd-xen are different.
What ,actually, provided login to CentOS PV DomU console.
This entry was posted on Tuesday, October 21st, 2008 at 5:04 pm and is filed under Uncategorized.	You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.