The parmfile references mdisks (virtual devices), not real device address. When restoring a volume backed up by OFFLINDR you will typically (but not always) use a different real device address. The constant piece of information here is the VOLSER of the volume. When the VM user machine that will host the Linux instance is started (ie VM logon) the mdisks in the user directory are established based on VOLSER and not real device address. /boot/parmfile specifies DASD=nnn where nnn is the mdisk number, NOT the real device address. I think the mdisk number will remain the same throughout this whole process and therefore the DASD=nnn in parmfile will not need to change.
Does this make sense? Rob ----- Original Message ----- From: "Dave Myers" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 24, 2002 1:05 PM Subject: Re: VM Newbie Question - Cloning an LPAR Linux system to a VM Guest ... > In a message dated 1/24/2002 9:27:29 AM Mountain Standard Time, > [EMAIL PROTECTED] writes: > > > > I just tested OFFLINDR and it works great! No changes necessary. I > > restored the backup to another device (same type) and restarted the Linux > > guest. Since guests use volser to find a mdisk and not dev addr, this > > works fine. Of course the volser of the original volume is the same as the > > volser of the restored volume. > > > > Rob > > > > > > Rob, > It appears that for Redhat 7.2, > I must have (at least) dasd=nnn (where nnn = my Linux root device) > in my boot parmfile...or the system will not IPL. > > So....how would I handle that hardcoded dev addr when > restoring to VM ?? > Must I make the emulated 3390 the same device address ?? > > > Tia > Dave
