All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Need your help again - regarding KVM node
AlexBarakov
Patron Provider, Veteran
Well, shortly after the Sentris2 node problems, something hit KVM1 as well.
The node was gracefully shutdown for scheduled RAM upgrade. Everything went okey. The node got booted up. SolusVM, however reported 5 out of 25 VMs to be online. They did not respond to pings however. Virsh command hangs. No errors are thrown. From all the virsh attributes, only --version seems to work. Libvirtd was restarted. The node was restarted as well. The extra RAM has been removed. The node was working absolutely fine before the upgrade, though.
I've pretty much did everything I could think of, including kernel upgrading. I am out of ideas. Will be glad if anyone can shoot out something or share experience.
EDIT: Resolved with the help of Fran. Thanks to all that PMed me with suggestions.
Comments
grep kvmnorunning /var/log/libvirtd/libvirtd.log
I'm betting you need to drop the suspend file and it's spitting out UUID erros
Well, the main problem is that virsh just hangs and does not output any data at all. If there was some kind of error that popped out, I might have been able to resolve it.
Hi Alex: Which OS / libvirt version?
Fran seems to be the answer to all problems.
And the creator of all problems >_>
Care to share the fix?
Could it have been due to a improper shutdown since one of my databases did not shutdown cleanly.
Good luck Alex, hope you can find fix soon
Ajit, that is definitely a possibility in that case. I've seem something like this before and it's not fun to fix
Did you shutdown the vm's first or just the node? What was the issue?