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] Physical to Virtual Migration

To: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Subject: Re: [Xen-users] Physical to Virtual Migration
From: James Miller <jimm@xxxxxxxxxxxxxxx>
Date: Wed, 28 Jan 2009 16:44:25 -0600
Cc: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 28 Jan 2009 14:50:10 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <7207d96f0901281349q26eff06cj42390ea6e6014d52@xxxxxxxxxxxxxx>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: Simutronics Corp
References: <4980C70E.2010209@xxxxxxxxxxxxxxx> <7207d96f0901281349q26eff06cj42390ea6e6014d52@xxxxxxxxxxxxxx>
Reply-to: jimm@xxxxxxxxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.18 (Windows/20081105)

Fajar A. Nugraha wrote:
On Thu, Jan 29, 2009 at 3:58 AM, James Miller <jimm@xxxxxxxxxxxxxxx> wrote:
I'm having an issue migrating an OLD debian 3.0 linux server (2.4.18 kernel)

Ouch!

to an HVM domU.  I'm using Xen 3.3.0 compiled from source.
Here's the process I took:
1. Carve out a chunk of space from an LVM Volume group
2. Create and boot from a Debian live CD ISO
3. Fdisked the LV into 2 partitions /dev/hda1 (OS)  /dev//hda2 (SWAP)
4. Formatted /dev/hda1 as ext3 and /dev/hda2 (swap)

So you're using mkfs.ext from a new Debian live CD?

When I reboot I get the following errors about reisersf -- which makes no
sense considering I'm using ext2/ext3:
EXT3-fs unsupported inod size: 256

This might be problem : inode size

read_super_block: can't find a reiserfs filesytem on (dev 03:01, block 64,
size 1024)

I think this line simply means you have reiserfs built into the
kernel, and the kernel tried to mount root as reiserfs, which
obviously will fail.

 But I am wondering if it has anything to do with OLD e2fs tools..

It should be. From mkfs.ext3 man page :

       -I inode-size
              Specify the size of each inode in bytes.  mke2fs creates
256-byte inodes by default.  In kernels after 2.6.10 and some earlier
vendor kernels it  is
              possible  to  utilize inodes larger than 128 bytes to
store extended attributes for improved performance.  The inode-size
value must be a power of 2
              larger or equal to 128.  The larger the inode-size the
more space the inode table will consume, and this reduces the usable
space in the  filesystem
              and  can  also  negatively  impact performance.
Extended attributes stored in large inodes are not visible with older
kernels, and such filesystems
              will not be mountable with 2.4 kernels at all.  It is
not possible to change this value after the filesystem is created.

you may try reformatting with -I 128, or (a safer choice) use
mkfs.ext3 from your old Debian 3.0 backup

Regards,

Fajar


Thank you for the suggestion Fajar. I used mkfs.ext2 (just bypassed ext3 all together =) from the old, physical, sever and all is good.



--Jim




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

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