Hello everyone,
I''m having an issue migrating an OLD debian 3.0 linux server (2.4.18
kernel) 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)
5. Mounted /dev/hda1 /mnt/
6. Restored from a full backup my physical server onto /mnt
7. chroot-ed /mnt
8. Edited lilo.conf and fstab to match what I have, ran lilo and
everything looks good.
9. Run lilo and reboot
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
read_super_block: can''t find a reiserfs filesytem on (dev 03:01, block
64, size 1024)
read_super_block: can''t find a reiserfs filesytem on (dev 03:01, block
8, size 1024)
Kernel panic VFS: Unable to mount root fs on 03:01
When I boot the Debian Live-CD it looks like the PIIIX3 IDE controller
is detected and hda is QEMU HARDDSIK.
Again, this doesn''t make any sense, to me, since I''m using
ext2/ext3
fs. But I am wondering if it has anything to do with OLD e2fs tools..
or maybe if there''s a driver bug with a 2.4.18 kernel and the IDE
driver. This old server has everything compiled into the kernel, no
modules.
/etc/lilo.conf for domU:
lba32
install=/boot/boot-menu.b
map=/boot/map
vga=normal
default=Linux
image=/vmlinuz
label=Linux
read-only
image=/vmlinuz.old
label=LinuxOLD
read-only
optional
Modified /etc/fstab file for domU:
/dev/hda1 / ext2 errors=remount-ro 0 1
/dev/hda2 none swap sw 0 0
proc /proc proc defaults
0 0
Config File:
kernel = ''/usr/lib/xen/boot/hvmloader''
builder=''hvm''
boot=''dc''
memory = 3072
name = "newt-test"
vif = [ '' mac=aa:00:ef:49:c1:23 '' ]
device_model = ''/usr/lib/xen/bin/qemu-dm''
# dhcp = "dhcp"
disk = [
''phy:/dev/vg01/newt-test,hda,w'',''file:/etc/xen/binary.iso,hdc:cdrom,r''
]
vcpus = 1
root = "/dev/hda1 ro"
extra = "xencons=tty"
vnc=1
vnclisten=''0.0.0.0''
vncpasswd=''xxxxxxxxxxx''
apic = 1
acpi = 1
vncdisplay=4
vncunused=1
Thanks for any suggestions/pointers.
--Jim
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Thu, Jan 29, 2009 at 3:58 AM, James Miller <jimm@simutronics.com> 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: 256This 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 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha wrote:> On Thu, Jan 29, 2009 at 3:58 AM, James Miller <jimm@simutronics.com> 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@lists.xensource.com http://lists.xensource.com/xen-users