Exactly - vdisk is in memory and will be lost if the guest is logged off -- so must be formatted for swap and mounted as swap by Linux when the guest is started..
Scott Rohling On Wed, Apr 20, 2011 at 8:15 AM, RPN01 <[email protected]> wrote: > Since it's a fresh disk every time, you'd have to do the mkswap every time > you log in, so my guess is that's why you'd need the mkswap and subsequent > swapon in the boot.local. The vdisk wouldn't be formatted when you get it > at > each fresh logon. > > -- > Robert P. Nix Mayo Foundation .~. > RO-OC-1-18 200 First Street SW /V\ > 507-284-0844 Rochester, MN 55905 /( )\ > ----- ^^-^^ > "In theory, theory and practice are the same, but > in practice, theory and practice are different." > > > > On 4/20/11 9:06 AM, "Dean, David (I/S)" <[email protected]> wrote: > > > Ok, we have it working. Defined it in User Directory, formatted it for > swap, > > added it to fstab, and added it to boot.local -> mkswap and swapon. > > > > Why did I have to add it boot.local? why does it not act like a normal > DASD > > drive and come on at boot? > > > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
