hi all, I installed v3.2 from source and now dom0 is booting well. But when I tried to start domU it shows the following error message and seems hanging. EXT3-fs: mounted filesystem with ordered data mode. EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended EXT3 FS on hda1, internal journal device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com EXT3-fs error (device hda1): ext3_free_blocks_sb: bit already cleared for block Aborting journal on device hda1. EXT3-fs error (device hda1) in ext3_reserve_inode_write: Journal has aborted EXT3-fs error (device hda1) in ext3_truncate: Journal has aborted EXT3-fs error (device hda1) in ext3_reserve_inode_write: Journal has aborted EXT3-fs error (device hda1) in ext3_orphan_del: Journal has aborted EXT3-fs error (device hda1) in ext3_reserve_inode_write: Journal has aborted EXT3-fs error (device hda1) in ext3_delete_inode: Journal has aborted ext3_abort called. EXT3-fs error (device hda1): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only audit(1204110895.260:2): audit_pid=0 old=0 by auid=4294967295 audit(1204110895.270:3): audit_backlog_limit=256 old=64 by auid=4294967295 NET: Registered protocol family 10 lo: Disabled Privacy Extensions IPv6 over IPv4 tunneling driver the configuration file is, kernel = "/boot/vmlinuz-2.6.18.8-xen" ramdisk = "/boot/initrd-2.6.18.8-xen" memory = 256 name = "VM1" vif = [ ''mac=00:16:3e:00:00:11, bridge=eth2'' ] disk = [ ''file:/home/xen/images/disk1,hda1,w'' ] root = "/dev/hda1" extra = "3" the file image disk1 was worked with the kernel 2.6.18 that is coming with v3.1. Any idea? regards Masroor _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Valter Douglas Lisbôa Jr.
2008-Feb-27 14:11 UTC
Re: [Xen-users] domU on v3.2 is not booting
On Wednesday 27 February 2008 11:00:24 Masroor Vettuparambil wrote:> hi all, > > I installed v3.2 from source and now dom0 is booting well. But when I > tried to start domU it shows the following error message and seems > hanging. > > EXT3-fs: mounted filesystem with ordered data mode. > EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended > EXT3 FS on hda1, internal journal > device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: > dm-devel@redhat.com > EXT3-fs error (device hda1): ext3_free_blocks_sb: bit already cleared > for block > Aborting journal on device hda1. > EXT3-fs error (device hda1) in ext3_reserve_inode_write: Journal has > aborted > EXT3-fs error (device hda1) in ext3_truncate: Journal has aborted > EXT3-fs error (device hda1) in ext3_reserve_inode_write: Journal has > aborted > EXT3-fs error (device hda1) in ext3_orphan_del: Journal has aborted > EXT3-fs error (device hda1) in ext3_reserve_inode_write: Journal has > aborted > EXT3-fs error (device hda1) in ext3_delete_inode: Journal has aborted > ext3_abort called. > EXT3-fs error (device hda1): ext3_journal_start_sb: Detected aborted > journal > Remounting filesystem read-only > audit(1204110895.260:2): audit_pid=0 old=0 by auid=4294967295 > audit(1204110895.270:3): audit_backlog_limit=256 old=64 by > auid=4294967295 > NET: Registered protocol family 10 > lo: Disabled Privacy Extensions > IPv6 over IPv4 tunneling driver >Its appear to be a error on file system, did you try fsck on it?> the configuration file is, > > kernel = "/boot/vmlinuz-2.6.18.8-xen" > ramdisk = "/boot/initrd-2.6.18.8-xen" > memory = 256 > name = "VM1" > vif = [ ''mac=00:16:3e:00:00:11, bridge=eth2'' ] > disk = [ ''file:/home/xen/images/disk1,hda1,w'' ] > root = "/dev/hda1" > extra = "3" > > the file image disk1 was worked with the kernel 2.6.18 that is coming > with v3.1.Did you do a back test? Booting against old 2.6.18 with xen 3.1 and creating the domain after this error occour?> > Any idea? > > regards > Masroor-- Valter Douglas Lisbôa Jr. Sócio-Diretor Trenix - IT Solutions "Nossas Idéias, suas Soluções!" www.trenix.com.br contato@trenix.com.br Tel. +55 19 3402.2957 Cel. +55 19 9183.4244 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Quoting Masroor Vettuparambil <Masroor.Vettuparambil@neterion.com>:> hi all, > > I installed v3.2 from source and now dom0 is booting well. But when I > tried to start domU it shows the following error message and seems > hanging. > > EXT3-fs: mounted filesystem with ordered data mode. > EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended > EXT3 FS on hda1, internal journal > device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: > dm-devel@redhat.com > EXT3-fs error (device hda1): ext3_free_blocks_sb: bit already cleared > for block > Aborting journal on device hda1. > EXT3-fs error (device hda1) in ext3_reserve_inode_write: Journal has > aborted > EXT3-fs error (device hda1) in ext3_truncate: Journal has aborted > EXT3-fs error (device hda1) in ext3_reserve_inode_write: Journal has > aborted > EXT3-fs error (device hda1) in ext3_orphan_del: Journal has aborted > EXT3-fs error (device hda1) in ext3_reserve_inode_write: Journal has > aborted > EXT3-fs error (device hda1) in ext3_delete_inode: Journal has aborted > ext3_abort called. > EXT3-fs error (device hda1): ext3_journal_start_sb: Detected aborted > journal > Remounting filesystem read-only > audit(1204110895.260:2): audit_pid=0 old=0 by auid=4294967295 > audit(1204110895.270:3): audit_backlog_limit=256 old=64 by > auid=4294967295 > NET: Registered protocol family 10 > lo: Disabled Privacy Extensions > IPv6 over IPv4 tunneling driver > > the configuration file is, > > kernel = "/boot/vmlinuz-2.6.18.8-xen" > ramdisk = "/boot/initrd-2.6.18.8-xen" > memory = 256 > name = "VM1" > vif = [ ''mac=00:16:3e:00:00:11, bridge=eth2'' ] > disk = [ ''file:/home/xen/images/disk1,hda1,w'' ] > root = "/dev/hda1" > extra = "3" > > the file image disk1 was worked with the kernel 2.6.18 that is coming > with v3.1. > > Any idea? > > regards > Masroor >Substitute your ''extra'' line with this one: extra = ''xencons=tty0'' Hope that helps, Jon _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
thanks for the reply Jon. But that kernel option didn''t work for me. filesystem seems to be corrupted, so I ran fsck.ext3 disk1. After that the below mentioned EXT3 boot error is disappeared. Still the domU kernel 2.6.18.8 is getting hanged. Then I installed the kernel in v3.1 using make install-kernels. this kernel(2.6.8) is booting well. So I feel I have missed to copy some kernel related stuffs to disk1. I have copied all lib modules of 2.6.18.8 to disk1. Anything else I need to copy to disk image? thanks Masroor. Date: Wed, 27 Feb 2008 10:27:30 -0900 From: jonr@destar.net Subject: Re: [Xen-users] domU on v3.2 is not booting To: xen-users@lists.xensource.com Message-ID: <20080227102730.6n0032b34g4o0gcg@www.destar.net> Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Quoting Masroor Vettuparambil <Masroor.Vettuparambil@neterion.com>:> hi all, > > I installed v3.2 from source and now dom0 is booting well. But when I > tried to start domU it shows the following error message and seems > hanging. > > EXT3-fs: mounted filesystem with ordered data mode. > EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended > EXT3 FS on hda1, internal journal > device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: > dm-devel@redhat.com > EXT3-fs error (device hda1): ext3_free_blocks_sb: bit already cleared > for block Aborting journal on device hda1. > EXT3-fs error (device hda1) in ext3_reserve_inode_write: Journal has > aborted EXT3-fs error (device hda1) in ext3_truncate: Journal has > aborted EXT3-fs error (device hda1) in ext3_reserve_inode_write: > Journal has aborted EXT3-fs error (device hda1) in ext3_orphan_del: > Journal has aborted EXT3-fs error (device hda1) in > ext3_reserve_inode_write: Journal has aborted EXT3-fs error (device > hda1) in ext3_delete_inode: Journal has aborted ext3_abort called. > EXT3-fs error (device hda1): ext3_journal_start_sb: Detected aborted > journal Remounting filesystem read-only > audit(1204110895.260:2): audit_pid=0 old=0 by auid=4294967295 > audit(1204110895.270:3): audit_backlog_limit=256 old=64 by > auid=4294967295 > NET: Registered protocol family 10 > lo: Disabled Privacy Extensions > IPv6 over IPv4 tunneling driver > > the configuration file is, > > kernel = "/boot/vmlinuz-2.6.18.8-xen" > ramdisk = "/boot/initrd-2.6.18.8-xen" > memory = 256 > name = "VM1" > vif = [ ''mac=00:16:3e:00:00:11, bridge=eth2'' ] disk = [ > ''file:/home/xen/images/disk1,hda1,w'' ] root = "/dev/hda1" > extra = "3" > > the file image disk1 was worked with the kernel 2.6.18 that is coming > with v3.1. > > Any idea? > > regards > Masroor >Substitute your ''extra'' line with this one: extra = ''xencons=tty0'' Hope that helps, Jon _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users