ikelos

Hmmm, that image seems to work fine for me? You might want to try clearing out your cache (`/path/to/home/.cache/volatility3`), and if that still doesn't work, check that you don't have...

Hmmmm, very strange? Was it just the profile (as in, if you dropped my profile in place of yours, would it work?). Also, are you running the latest git release...

Hmmm, so it appears as though the PDB files that Microsoft offers (even for the earlier PDB of age 1 and name ntkrpamp.pdb) is reduced and contains only symbols and...

For reference, here is the most recent PDB file available from Microsoft: [issue242.zip](https://github.com/volatilityfoundation/volatility3/files/4927822/issue242.zip)

@thall63 It would need to be converted to the appropriate JSON, it's in PDB format at the moment. The file was more for us to debug what was happening. The...

Hi, did you create the appropriate symbol file for the version of Centos 8 you're trying to analyse? Volatility 3 doesn't yet have a library of linux symbol tables, so...

Thanks, it looks like the symbols are present now and it's detecting the right version of linux and using that JSON file, but the intel memory map seems to be...

Thanks, would you be able to attach either of `centos7.3.10.json.xz` or `centos7-3.10.json.xz` so we can take a look at what's going on. That looks like a separate issue, rather than...

Well, it's correctly identifying the symbols, so it could be that the ASLR shift is coming out wrong, but again, I think this is into territory best covered by @atcuno...

@atcuno We now log whether a VMSS/VMSN was present, neither was there with this image: ``` Level 6 volatility3.framework.layers.vmware: Metadata found: VMSS (False) or VMSN (False) ```