A separate migration network wouldn’t help you. I’m trying to figure out why it
would be stuck migrating one vm for 20 hours. Something has to be preventing it.
What is your setup? Have you looked at the engine.log or the vm log in
/var/log/libvirt/qemu/.log?
Eric Evans
Digital Data
Hi Eric, thanks for the reply.
Actually putting the host to activate did stopped the maintenance and aborted
the migration. Thank you for that.
Regarding the segregated motion network, I don’t have additional physical
interfaces, I can only do it on a VLAN. I don’t know if this would help…
It should give you the option to Activate the host to end it's preparing for
maintenance. Once its active if the vm's are shut down it should go strait to
maintenance mode in just a few seconds.
My question is, are you using a migration network separate from ovirtmgmt
network? That would
3 matches
Mail list logo
