Re: [Xen-users] xen and boot problems (with CentOS 4.2)

[Haavard Bjerke <havard.bjerke@xxxxxxx>]

mbjohn@xxxxxxxx wrote:
> Hello --
>
> We're trying to get a Centos 4.2 system working under a Centos 4.2
> operating system using the instructions we found at
> http://mark.foster.cc/wiki/index.php/Centos-4_on_Xen.  The prospect of
> running several virtual servers on one physical box is pretty
> intriguing.  I think we're pretty close, but we've gotten to a place
> that has me stumped.  I'm hoping someone can help.
>
> We've gotten to a place where we can actually boot our VM by running
> 'xm create -c /etc/xen/vm03 vmid=3' (we are using the configuration from
> the Xen documentation).  We see the standard kernel boot
> up messages and things start out well.  Then we get to:
>
>
> EXT2-fs warning (device sdb3): ext2_fill_super: mounting ext3 filesystem
> as ext2
>
> VFS: Mounted root (ext2 filesystem).
> Freeing unused kernel memory: 184k freed
> unix: no version for "struct_module" found: kernel tainted.
> NET: Registered protocol family 1
> INIT: version 2.85 booting
>                Welcome to  CentOS release 4.2 (Final)
>                Press 'I' to enter interactive startup.
> Starting udev:  [  OK  ]
> Initializing hardware...  storage network audio done[  OK  ]
> raidautorun: RAID_AUTORUN failed: 19
> mount: mount point devpts does not exist
> Configuring kernel parameters:  [  OK  ]
> Setting clock : Tue Mar 28 16:01:59 EST 2006 [  OK  ]
> Setting hostname localhost:  [  OK  ]
> Checking root filesystem
> [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sdb3
> /dev/sdb3 is mounted.  e2fsck: Cannot continue, aborting.
>
>
> [FAILED]
>
> *** An error occurred during the file system check.
> *** Dropping you to a shell; the system will reboot
> *** when you leave the shell.
> Press enter for maintenance
> (or type Control-D to continue):
>
>
> I cannot for the life of me figure out what's going wrong.  I've
> dropped into the maintenance shell and done a fsck, but as soon as I
> try to boot it back up again, the same problem.
Try adding "fastboot" to the "extra" parameter in the domU config file. 
It helps for SL, so I suspect it might for Centos aswell.
Havard

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users