> diff --git a/crash.8 b/crash.8 > index 136ae78..783fdf7 100644 > --- a/crash.8 > +++ b/crash.8 > @@ -116,6 +116,12 @@ or > .I kvmdump > facilities. > > +The > +.B crash > +utility is able to process VMware VM memory dump generated by VM suspend > +or guest core dump. In that case, .vmss or .guest file should be used as > +a MEMORY-IMAGE and .vmem file must be located in the same folder. > + > If a MEMORY-IMAGE argument is not entered, the session will be invoked on > the live system, which typically requires root privileges because of > the device file used to access system RAM. By default, To preserve the original structure, I think the following is better. # git diff diff --git a/crash.8 b/crash.8 index 136ae78..420cd48 100644 --- a/crash.8 +++ b/crash.8 @@ -111,9 +111,10 @@ A kernel core dump file created by the .I diskdump, .I LKCD .I kdump, -.I xendump -or +.I xendump, .I kvmdump +or +.I VMware facilities. If a MEMORY-IMAGE argument is not entered, the session will be invoked on @@ -144,6 +145,13 @@ in /var/tmp, which will only exist during the crash session. If a raw RAM dumpile represents a live memory source, such as that specified by the QEMU mem-path argument of a memory-backend-file object, then "live:" must be prepended to the MEMORY-IMAGE name. + +As VMware facility, the +.B crash +utility is able to process VMware VM memory dump generated by VM suspend +or guest core dump. In that case, .vmss or .guest file should be used as +a MEMORY-IMAGE and .vmem file must be located in the same folder. + .TP .BI mapfile If the NAMELIST file is not the same kernel that is -- Crash-utility mailing list Crash-utility@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/crash-utility
