WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] domU on v3.2 is not booting

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] domU on v3.2 is not booting
From: jonr@xxxxxxxxxx
Date: Wed, 27 Feb 2008 10:27:30 -0900
Delivery-date: Wed, 27 Feb 2008 11:28:07 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <78C9135A3D2ECE4B8162EBDCE82CAD7703184517@nekter>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <78C9135A3D2ECE4B8162EBDCE82CAD7703184517@nekter>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Internet Messaging Program (IMP) H3 (4.1.5)
Quoting Masroor Vettuparambil <Masroor.Vettuparambil@xxxxxxxxxxxx>:

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@xxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>