Comments on Create CentOS 5.2 Domu on Ubuntu Hardy Dom0
Create CentOS 5.2 Domu on Ubuntu Hardy Dom0 This tutorial provides step-by-step instructions on how to install Images of xen on an Ubuntu Hardy Heron (Ubuntu 8.04) server system (i386). Linux distributions that can run as Xen guests out of the box, obviating the need to create your own custom filesystems. The filesystems on jailtime.org have already been tweaked to deal with Xen’s idiosyncracies, and are also designed to be lightweight and minimally divergent from the original distribution.
5 Comment(s)
Comments
http://lxer.com/module/newswire/view/110642/index.html
I'm stuck!
The "mkfs.ext3 diskimage" gives me this error:
"Could not stat diskimage --- No such file or directory
The device apparently does not exist; did you specify it correctly?"
Me too. However I'm looking at this somewhat unrelated how-to:
http://www.watters.ws/wiki/index.php/How_to_Build_a_CentOS_3_Template
...An am inferring that one should replace the give mkfs commands with:
dd if=/dev/zero of=Cent_base.img bs=1024k count=1024
dd if=/dev/zero of=Cent_swap.img bs=1024k count=128
mkfs.ext3 Cent_base.img
mkswap Cent_swap.img
...The mkfs.ext3 then says "Cent_base.img is not a block special device. Proceed anyway? (y,n)" ...to which I say yes.
Hi
i am getting error when I start the vm
xm create -c vm
my config file look like this
kernel= "/xen/xen-3.4.1/dist/install/boot/vmlinuz-2.6.18.8-xenU"
memory = 128
name = "mailserver"
vif = [ 'mac=00:16:3e:00:00:11,bridge=xenbr0' ]
disk = ['file:/lakxen/suselinux/image/centos.5-3.x86.gnome.img,sda1,w']
root = "/dev/sda2 ro xencons=tty"
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI No-Shortcut mode
xen-vbd: registered block device major 8
blkfront: sda1: barriers enabled
XENBUS: Device with no driver: device/console/0
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "sda2" or unknown-block(2,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
[root@testServer]# losetup /dev/loop0 xentest.img
[root@testServer lgh]# e2fsck -f /dev/loop0
e2fsck 1.39 (29-May-2006)
Couldn't find ext2 superblock, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/loop0
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
[root@testServer lgh]# resize2fs /dev/loop0
resize2fs 1.39 (29-May-2006)
resize2fs: Bad magic number in super-block while trying to open /dev/loop0
Couldn't find valid filesystem superblock.