The dynamic memory balancer could not add memory to the virtual machine Event ID 10020
Anyone knows how to fix this bug?
This happens on alot of our VM’s running a 2016 Hyper-V Cluster - hardware is HPE BL460c G9.
"This is expected behavior if the virtual machine is booting" - True dat!
Veeam leaves a Recovery Checkpoint after backup job is run?
Hello,
I tend to have a few VM’s with "leftovers" from Veeam Backup Jobs - and the only way to delete them is by doing this :
Remove Lingering Backup Checkpoints from a Hyper-V Virtual Machine
Get-VMSnapshot -ComputerName "MyHyperVHost" -VMName "VMWithLingeringBackupCheckpoint" | Remove-VMSnapshot
Hyper-V is running on Server 2016 Datacenter with Veeam Backup and Replication 9.5 Update 3
https://www.veeam.com/kb2353
So - anyone else experiencing this?
Veeam leaves a Recovery Checkpoint after backup job is run?
Hello,
I tend to have a few VM’s with "leftovers" from Veeam Backup Jobs - and the only way to delete them is by doing this :
Remove Lingering Backup Checkpoints from a Hyper-V Virtual Machine
Get-VMSnapshot -ComputerName "MyHyperVHost" -VMName "VMWithLingeringBackupCheckpoint" | Remove-VMSnapshot
Hyper-V is running on Server 2016 Datacenter with Veeam Backup and Replication 9.5 Update 3
https://www.veeam.com/kb2353
So - anyone else experiencing this?
Move-VM to a Cluster with a Different named Switch not possible through powershell?
Hi guys,
So, we are to move a customers VM’s from one Cluster to another, however the Virtual Switch are named differently on the two Clusters.
I’ve read these articles :
If I chose to move a unclustered VM from Hyper-V Manager - the gui will eventually prompt me to choose the Switch on the destination host/cluster, but if I try to do it from Powershell - the command : Move-VM does not give me the possibility to attach vNIC
to a HA switch on the destination host/cluster with a different name?
Is this by design? Because I cant sit and move hundreds of VM’s from Hyper-V Manager.
Hope you guys have a usefull trick to help me out here 🙂
Server 2016 w. Hyper-V – can’t open Hyper-V Manager after HP SPP 2016.10 is installed
Hello Guys.
I have issues with opening my Hyper-V Manager local after I installed HP SPP 2016.10 bundle on my BL460c G9 blade.
This message pop’s up :
”An error occurred while attempting to connect to server ‘Server1’. Check that the Virtual Machine Management Service is running and that you are authorized to connect to the server. Hyper-V Encountered an error trying to access an object
on computer ‘Server1’ because the object was not found. The object might have been deleted. Verify that the Virtual Machine Management service on the computer is running.”
I suspect WBEM and/or HP Insight Management to be the reason for this not working - any other suggestions or people that have the same issue?
Hyper-V Manager works fine, when HP SPP is not installed - so I am pretty confident that this is related.
Anyone else experiencing the same?
Server 2016 w. Hyper-V – can’t open Hyper-V Manager after HP SPP 2016.10 is installed
Hello Guys.
I have issues with opening my Hyper-V Manager local after I installed HP SPP 2016.10 bundle on my BL460c G9 blade.
This message pop’s up :
”An error occurred while attempting to connect to server ‘Server1’. Check that the Virtual Machine Management Service is running and that you are authorized to connect to the server. Hyper-V Encountered an error trying to access an object
on computer ‘Server1’ because the object was not found. The object might have been deleted. Verify that the Virtual Machine Management service on the computer is running.”
I suspect WBEM and/or HP Insight Management to be the reason for this not working - any other suggestions or people that have the same issue?
Hyper-V Manager works fine, when HP SPP is not installed - so I am pretty confident that this is related.
Anyone else experiencing the same?
- Guest Slow Network Connection with Jumbo Packets December 11, 2019
- New KB articles published for the week ending 8th December,2019 December 10, 2019
- a virtual machine resource was not found in clustered virtual machine December 10, 2019
- hyper v ubuntu vm stuck in restoring December 9, 2019
- Two dhcp servers one virtual switch on Hyper-V December 9, 2019