Comment 2 for bug 1240584
Revision history for this message
| Abhishek Kekane (abhishek-kekane) wrote | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
Possible Solution:
A new parameter "force" will be added to the existing live migration api, if it's set to False and user is connected to the VNC console, it won't live migrate that vm.
If "force" parameter is set to True then even if user is connected to VNC console, live migration will be performed.
To detect whether users are connected to the vnc console or not, we can check if the vnc port is opened on the compute node where the vm is running using following command.
sudo netstat -pnt | awk '{print $4}' | egrep '^127.0.0.1:5900$’
127.0.0.1 : vncserver_listen parameter from nova.conf
5900: graphics port either for spice or vnc.