From: Ravi Raso
To: Untitled Mail Group (DO NOT USE)
Date: Tuesday, December 3, 2019 12:06 AM
Subject: Issues caused by unprotected memory

Has anyone evaluated the side effects that might be caused by sharing a memory pool between multiple VMs, rather then allocating them separately? I'm looking at some of the files VM1 is generating, and I'm finding some information that *definitely* shouldn't be there. I haven't seen any evidence that this is actually affecting the inside of the VM itself, so I don't think this is a priority, but it's definitely worth noting.

My best guess is that memory being freed from VM2 isn't getting zeroed out, which technically gives VM1 access to it. All the info I have will go into the issue tracker, but I wanted to check if anyone else already noticed something along these lines.

Ravi Raso
System Engineer