> On SNV90 HVM DomU at SNV92 Dom0 :
> # xm block-attach file:/export/home/images/disk1.img hdc w (at Dom0)
Is that disk1.img file an empty raw disk image file that
you just created with mkfile (or dd)?
> format>
> fdisk
...
> Partition Status Type Start End Length %
> ========= ====== ============ ===== === ====== ===
> 1 Solaris2 1 2047 2047 100
Did you use format's "partition" menu, do define
slices / a partition table for the disk; and did you
write a SunOS disk label to the new disk using
format's "label" command?
> Attempted newfs ,which worked fine at SNV90 PV DomU
> now at SNV90 HVM DomU reports for any slice :
> bash-3.2# newfs /dev/rdsk/c1d0s0
> /dev/rdsk/c1d0s0: No such device or address
Seems that you skipped the step to partition / label the
new disk. In this case the kernel constructs a default
disk label, which has the "s2" slice that maps the whole
Solaris fdisk partition. All other slices are empty.
You can print the current active partition information with the
prtvtoc command:
# prtvtoc /dev/rdsk/c1d0s2
or
# prtvtoc /dev/rdsk/c1d0p0
This message posted from opensolaris.org
_______________________________________________
xen-discuss mailing list
[email protected]
