On 01/18/10 14:05, Martin Warnecke wrote: > Hi, > > I tried to virtualize a server which has 2 physical disks to be integrated > into one virtual disk. > > LDoms 1.2 Administration Guide says about non-automatic mode: > > Non-automatic mode. You must create the virtual disks and restore the file > system data. > This enables you to change the size and number of disks, the partitioning, > and the file system > layout. The preparation phase in this mode only runs the logical domain > creation and the > OS image modification steps on the file system rooted at guest-root > > I created a virtual disk image file > mkfile -20g /ldoms/server.img > attached it to a loopback device (/dev/lofi/1) and created a new file > system > newfs /dev/rlofi/1 > and mounted the the file system > mount /dev/lofi/1 /mnt1 > > Then I restored (ufsrestore) the file systems which were dumped to > /ldoms/p2v/server during the ldmp2v collect step to the file system mounted > at /mnt1. > > When I issue the ldmp2v prepare command > > ldmp2v prepare -R /mnt1 -d /ldoms/p2v/server -v server > > I get an error: > > Determining vdisks ... > Cannot determine vdisk configuration. > > Does anyone have experience with the ldmp2v prepare -R option? How do I > have to prepare the (target) virtual disk, in particular partitions and > file system layout?
Hi Martin, the documentation is a bit terse but the /mnt1 file system should be on a vdisk temporarily added to the primary domain. The error message is pretty uninformative though (CR 6874896 ldmp2v prepare -R needs better diagnostics). What it is trying to tell you is that the file system mounted on /mnt1 is not on a vdisk. So in your case, do something like this: # ldm add-vdsdev /ldoms/server.img server-vol0 at primary-vds0 # ldm add-vdisk disk0 server-vol0 at primary-vds0 primary (lookup the cXdY name of the vdisk just added) # newfs /dev/rdsk/cXdYs0 # mount /dev/dsk/cXdYs0 /mnt1 and restore the ufsdump(s) at the appropriate places (if you have multiple file systems on the original system). You can create any disk and/or file system layout you want. During p2v we rewrite the guest's /etc/vfstab to match what is mounted on (and below) /mnt1. The P2V tool removes the vdisk from the primary domain and adds it to the created guest domain as part of the process. Now for the bad news: the -R option is broken in the version that was delivered with LDoms 1.2 (CR 6874741 ldmp2v prepare -R option is broken). This bug is fixed in the version of the tool that will be delivered with LDoms 1.3 which should be available shortly. Sorry for the inconvenience, Menno -- Menno Lageman - Sun Microsystems - http://blogs.sun.com/menno
