[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-users] prob HVM boot image sco


  • To: "Torsten Lehmann" <tlehmann@xxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
  • Date: Tue, 12 Jun 2007 16:29:59 +0200
  • Delivery-date: Tue, 12 Jun 2007 07:35:01 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: Aces/H1X4IABsD2pQZmuSFnJpP8oXQAAEH+w
  • Thread-topic: [Xen-users] prob HVM boot image sco

 

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Torsten Lehmann
> Sent: 12 June 2007 15:09
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-users] prob HVM boot image sco
> 
> 
> Hallo xenusers!
> 
> 
> I want port a very old sco to to xenU.
> 
> xen (HVM) cannot boot this image.
> This Partition cannot mounted.
> Whats going wrong?
> Is HD-geometry a cause of this problem?

It's possible that the geometry is the problem, particularly if the SCO
image is so old that it's not using LBA-addressing of the sectors. [In
LBA-mode, the sector number is one LARGE number, but in non-LBA mode,
it's a composition of the head, cylinder and sector. If for some reason
the boot-loader has stored the original HCS location for some component,
it's quite likely that it will not find the right place with a different
geometry]. 

Do you have any information in the /var/log/xen/qemu-dm.<pid>.log for
the domain? [using "ls -ltr" to list the "latest" one is a good way to
find which is the one you've just got, as they are "named" based on the
process ID of the qemu-dm, which isn't particularly helpful in knowing
which one is new and old]. 

One other thing that looks a bit weird is the partition info: It seems
like you have moved from partition 1 to partition 4 for some reason...
Maybe this is just a difference between Linux and sco fdisk apps, but it
does look a bit "strange" to me. 

--
Mats
> 
> regards Torsten
> Launoc
> 
> ----------------------------------------------------------------------
> Details:
> 
> sco # uname -a
> SCO_SV n7275sc1 3.2 2 i386
> 
> sco # fdisk
> 
>         1. Display Partition Table
>         2. Use Entire Disk for UNIX
>         3. Use Rest of Disk for UNIX
>         4. Create UNIX Partition
>         5. Activate Partition
>         6. Delete Partition
>         7. Create Partition
> 
> Enter your choice or 'q' to quit: 1
> 
> Current Hard Disk Drive: /dev/rhd00
> 
> 
> +-------------+----------+-----------+---------+---------+---------+
>         | Partition   | Status   | Type      |   Start |     
> End |    Size|
> 
> +-------------+----------+-----------+---------+---------+---------+
>         | 1           | Active   | UNIX      |       1 |  
> 134129 |  134129|
> 
> +-------------+----------+-----------+---------+---------+---------+
> 
> 
> 
> - create img
> 
> sco # dd if=/dev/rhd00 | rcmd $rhost -l admin dd of=$hdimg
> 
> xen # fdisk -l $hdimg
> You must set cylinders.
> You can do this from the extra functions menu.
> 
> Disk sco.dd: 0 MB, 0 bytes
> 255 heads, 63 sectors/track, 0 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> 
>  Device Boot      Start         End      Blocks   Id  System
>  sco.dd4   *           1         526     4225063+  63  GNU 
> HURD or SysV
> 
> 
> 
> ------------------------------------------------------------------
> - test 1 boot_xenu
> 
> 
> xen:~# xm create vm3_sco -c
> Using config file "/etc/xen/vm3_sco".
> Started domain vm3
> 
> 
> Boot from Hard Disk failed: could not read the boot disk
> FATAL: No bootable device
> 
> 
> -------------------------------------------------------------------
> - test 2 mount_partition
> 
> hdimg=sco.dd
> fdisk -l $hdimg
> Cb=1
> seekblk=$((($Cb-1)*63*255)); ## fdisk
> echo "Cb=$Cb Ctmp=$Ctmp seekblk=$seekblk"
> 
> ## lese-test HDimg (s. qemu/060204.test_qemu_img_create)
> devloop=`losetup -f`
> mntdir=/mnt/tmp
> losetup -o $seekblk $devloop $hdimg
> mount $devloop $mntdir
> # or:  lomount -diskimage $hdimg -partition 4 $mntdir
> df  $mntdirdst
> umount  $mntdirdst
> losetup -d $devloop
> 
> -------------
>   - result:
> # lsmod | grep sysv
> sysv                   28804  0
> 
> # lomount -diskimage $hdimg -partition 4 $mntdir
> mount: you must specify the filesystem type
> 
> # mount -t sysv $devloop $mntdir
> mount: wrong fs type, bad option, bad superblock on /dev/loop1,
>        missing codepage or other error
>        In some cases useful info is found in syslog - try
>        dmesg | tail  or so
> 
> 
> -------------------------------------------------------------------
> 
> - geometry of orginal HD:
>   C     H       S
>   526   255     63
> 
> - geometry supported by qemu (man qemu)
>   x     16      63
> 
> -------------------------------------------------------------------
> 
> 
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 
> 
> 



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.