Dumping Linux Guest Storage

[Stefan Raabe]

to modify my question:

is there more that can be done except VMDUMP?

Regards, Stefan




Stefan Raabe <***@deutsche-boerse.com>
Sent by: VM/ESA and z/VM Discussions <VMESA-***@LISTSERV.UARK.EDU>
31.01.2006 10:08
Please respond to
VM/ESA and z/VM Discussions <VMESA-***@LISTSERV.UARK.EDU>


To
VMESA-***@LISTSERV.UARK.EDU
cc

Subject
Dumping Linux Guest Storage








Hello,

what is the best practise to dump a guest machine (in our case - a linux
guest that seems to be looping) from VM (z/VM 4.4)?

Regards, Stefan

Diese E-Mail enthaelt vertrauliche oder rechtlich geschuetzte
Informationen.
Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte
sofort den Absender und loeschen Sie diese E-Mail. Das unbefugte
Kopieren
dieser E-Mail oder die unbefugte Weitergabe der enthaltenen
Informationen
ist nicht gestattet.

The information contained in this message is confidential or protected
by
law. If you are not the intended recipient, please contact the sender
and
delete this message. Any unauthorised copying of this message or
unauthorised distribution of the information contained herein is
prohibited.

[Rob van der Heij]

On 1/31/06, Stefan Raabe <***@deutsche-boerse.com> wrote:

> is there more that can be done except VMDUMP?

As far as I know the support team can now use the conversion from
vmdump to lcrash to debug your problem. If you are running with NSS
you should include the DSS option on the VMDUMP command to make sure
that portion is dumped as well.
For large virtual machines you will need to prepare a dump volume and
dump onto that.

Personally I would also play a bit with CP TRACE to understand where
the loop is, and if it's around a spinlock try to see who's holding
that.

Rob
--
Rob van der Heij rvdheij @ gmail.com
Velocity Software, Inc

[Rob van der Heij]

On 1/31/06, Kris Buelens <***@be.ibm.com> wrote:

> Sorry Rob, but VMDUMPs are stored in the normal spool area's. Dump
> volumes are only used by CP dumps.

I have not been able to verify for z/VM 5.2, but VMDUMP used to be
limited to 2G virtual storage. The disk to prepare would be a Linux
dump disk, not a CP dump pack.

Rob
--
Rob van der Heij rvdheij @ gmail.com
Velocity Software, Inc

[Rob van der Heij]

On 1/31/06, Rob van der Heij <***@velocitysoftware.com> wrote:

> I have not been able to verify for z/VM 5.2, but VMDUMP used to be
> limited to 2G virtual storage. The disk to prepare would be a Linux
> dump disk, not a CP dump pack.

Should have... with 5.2 we seem to be able to dump a 512G virtual
machine (assuming you want that on your spool space).

--
Rob van der Heij rvdheij @ gmail.com
Velocity Software, Inc