Ezio Posted May 1, 2022 Share Posted May 1, 2022 Hello i dont know why i have that on my vm 1 and made a second one to test jusst tell me what infor you need its a 30 gb of ram in the server Quote Link to comment
JorgeB Posted May 2, 2022 Share Posted May 2, 2022 This is normal if "Initial Memory" is less than "Max Memory" for that VM. Quote Link to comment
Ezio Posted May 2, 2022 Author Share Posted May 2, 2022 So Nothing to worry right? Quote Link to comment
JorgeB Posted May 2, 2022 Share Posted May 2, 2022 IIRC someone posted that's just a visual issue, RAM will still be allocated as needed, assuming the memory ballooning driver is installed, though I don't really see much point in thin provisioning RAM, if you set both values to the RAM you want you won't see that. Quote Link to comment
DarthKegRaider Posted May 6, 2022 Share Posted May 6, 2022 I noticed this on my Windows10 test machine too. I did also notice that as soon as I assigned a GPU to the machine that the memory reporting was accurate. Removed the GPU and used the VNC display, the bug returned. I just ignored it thinking that it was working fine. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.