Guys, this is HUGELY CRITICAL on 16.04 production openstack with windows guests, since the only workaround is to tell the customer to disable the baloon driver inside the windows machine before migrating, but when migration occurs because of a failure and the customer cant disable it, a simple task like a migration volume-backed doesnt work.
Guys, this is HUGELY CRITICAL on 16.04 production openstack with windows guests, since the only workaround is to tell the customer to disable the baloon driver inside the windows machine before migrating, but when migration occurs because of a failure and the customer cant disable it, a simple task like a migration volume-backed doesnt work.
please, if you can fix it asap would be great