Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vMotion Issue #21

Closed
CollabSensei opened this issue May 30, 2015 · 4 comments
Closed

vMotion Issue #21

CollabSensei opened this issue May 30, 2015 · 4 comments

Comments

@CollabSensei
Copy link

Running Esxi 5.5. When vmotioning a vm with a serial interface on it, the VMware Client says "An error occurred while saving the state for migration.
The serial port concentrator did not acknowledge the migration within the allowed time limit. ".

From a logging perspective from vSPC, I see the following:
05-30-2015 09:34:06 User.Error 10.255.83.94 May 30 08:34:06 ps-collab-vsc vSPC.py[1027]: Worker exception caught#012Traceback (most recent call last):#12 File "build/bdist.linux-x86_64/egg/vSPC/server.py", line 112, in _queue_run#012 queue.get()()#12 File "build/bdist.linux-x86_64/egg/vSPC/server.py", line 224, in #12 self.task_queue.put(lambda: self.new_vm_data(vt))#12 File "build/bdist.linux-x86_64/egg/vSPC/server.py", line 179, in new_vm_data#012 neg_done = vt.negotiation_done()#12 File "build/bdist.linux-x86_64/egg/vSPC/telnet.py", line 276, in negotiation_done#012 self.process_available()#12 File "build/bdist.linux-x86_64/egg/vSPC/telnet.py", line 273, in process_available#012 self.process_rawq()#12 File "build/bdist.linux-x86_64/egg/vSPC/telnet.py", line 156, in process_rawq#012 self.option_callback(self.sock, c, NOOPT)#12 File "build/bdist.linux-x86_64/egg/vSPC/telnet.py", line 415, in _option_callback#012 getattr(self, meth)(data)#12 File "build/bdist.linux-x86_64/egg/vSPC/telnet.py", line 34...

@xuguanghan
Copy link

xuguanghan commented Aug 16, 2016

function _handle_vmotion_begin has a bug. try change to 👍

def _handle_vmotion_begin(self, data):
    cookie = data + struct.pack("l", hash(self) & 0xFFFFFFFF)
    if self.handler.handle_vmotion_begin(self, cookie):
        logging.debug("vMotion initiated: %s" % hexdump(cookie))
        self._send_vmware(VMOTION_GOAHEAD + cookie)
    else:
        logging.debug("vMotion denied: %s" % hexdump(cookie))
        self._send_vmware(VMOTION_NOTNOW + cookie)

@nicobbg
Copy link

nicobbg commented Oct 11, 2016

I confirm this issue.

Running ESXi 5.5u3, I have a cluster of 2 ESXi and when I try to migrate a VM with a serial port configured for the vSPC server it fails.

This does not happen with other VM with a serial port configured on an Avocent (a commercial virtual serial port concentrator)

Error output:

A general system error occurred: Migration to host <> failed with error Connection closed by remote host, possibly due to timeout (0xbad003f).
Migration to host <> failed with error Connection closed by remote host, possibly due to timeout (195887167).
vMotion migration [-1062076156:1476173590574550] failed to send init message to the remote host <>
vMotion migration [-1062076156:1476173590574550] (0-71743133716968) failed to receive 68/68 bytes from the remote host <>: Connection closed by remote host, possibly due to timeout
The vMotion failed because the destination host did not receive data from the source host on the vMotion network. Please check your vMotion network settings and physical network configuration and ensure they are correct.

@nicobbg
Copy link

nicobbg commented Oct 11, 2016

I confirmed that the patch mentionned by xuguanghan is fixing the issue.
This issue is also a duplicate with issue #17. Can you fix this issue and merge it with master ?

@pbhenson
Copy link
Owner

Fixed in master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants