Bug 1414246
Summary: | Win2016 guest hang after doing migration between two hosts that has a time lag that dst host is 10 minutes backwards than src host | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | xianwang <xianwang> |
Component: | qemu-kvm | Assignee: | Hai Huang <hhuang> |
Status: | CLOSED NOTABUG | QA Contact: | xianwang <xianwang> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.9 | CC: | ailan, chayang, dgilbert, hhuang, jen, michen, mkenneth, qzhang, rbalakri, virt-maint, xianwang, zhengtli |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Windows | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-02-07 11:52:17 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
xianwang
2017-01-18 07:09:14 UTC
Rhel6.9 host arch x86_64 both Intel and AMD machine have this bug. Host(both src and dst): 2.6.32-682.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.500.el6.x86_64 Guest: win2016 virtio-win.iso.el6 Rhel6.9 host arch x86_64 both Intel and AMD machine don't have this bug with rhel69 guest Host(both src and dst): 2.6.32-682.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.500.el6.x86_64 Guest: rhel69-64-virtio.qcow2 2.6.32-671.el6.x86_64 >Do migration between two x86 AMD hosts on win2016 vm, dst host is 10 minutes
>backwards than src host,
I believe this is documented as an invalid scenario; both src and dst hosts must have close-to-identical times. Reassigning for followup.
Yes I think this is documented that the src and dst host must have close times; however, I'm curious, if the dst host is 10 minutes behind, and you migrate the VM, but leave the VM running for 10 minutes, does the VM then unhang at the end of those 10 minutes? Hi, Jeff and David, (1)If this scenario is invalid, why this bug can't be reproduced for rhel69 guest on rhel69 hosts, and can't be reproduced for win2016 guest on rhel73 hosts? Now, this bug is only produced for windows guests on rhel69 hosts. (2)when the dst host is 10 minutes before than src host, windows guest can work well after migration. So, did rhel69 product only support the scenario that dst host is 10 minutes before than src host? and not support the scenario that dst host is 10 minutes backward than src host? (3)For comment 8,I am not sure if I get David's point right."if the dst host is 10 minutes behind, and you migrate the VM, but leave the VM running for 10 minutes", after migration, the VM is hang and can't operate it via vncviewer,10 minutes later, vm can be operated normally. (In reply to xianwang from comment #9) > Hi, Jeff and David, > (1)If this scenario is invalid, why this bug can't be reproduced for rhel69 > guest on rhel69 hosts, and can't be reproduced for win2016 guest on rhel73 > hosts? Now, this bug is only produced for windows guests on rhel69 hosts. The problem here is related to the time as seen by the guest; rhel guests don't worry about that much, but Windows guests get upset by it. However, I can't answer why this doesn't happen for win guests on rhel 73. > (2)when the dst host is 10 minutes before than src host, windows guest can > work well after migration. So, did rhel69 product only support the scenario > that dst host is 10 minutes before than src host? and not support the > scenario that dst host is 10 minutes backward than src host? Your wording is incorrect - when you say 'backward' and 'before' which way around do you mean? Give me an example of the time on both clocks. > (3)For comment 8,I am not sure if I get David's point right."if the dst host > is 10 minutes behind, and you migrate the VM, but leave the VM running for > 10 minutes", after migration, the VM is hang and can't operate it via > vncviewer,10 minutes later, vm can be operated normally. One thing we've seen before is a case like this: a) Src host has clock at 9:00am b) Dst host has clock at 8:50am c) We migrate d) VM appears hung e) Once dst host gets to 9:00am the VM recovers I wanted to know if this is the case you're seeing. Dave (In reply to Dr. David Alan Gilbert from comment #10) > (In reply to xianwang from comment #9) > > Hi, Jeff and David, > > (1)If this scenario is invalid, why this bug can't be reproduced for rhel69 > > guest on rhel69 hosts, and can't be reproduced for win2016 guest on rhel73 > > hosts? Now, this bug is only produced for windows guests on rhel69 hosts. > > The problem here is related to the time as seen by the guest; rhel guests > don't worry about that much, but Windows guests get upset by it. > However, I can't answer why this doesn't happen for win guests on rhel 73. > > > (2)when the dst host is 10 minutes before than src host, windows guest can > > work well after migration. So, did rhel69 product only support the scenario > > that dst host is 10 minutes before than src host? and not support the > > scenario that dst host is 10 minutes backward than src host? > > Your wording is incorrect - when you say 'backward' and 'before' which way > around do you mean? Give me an example of the time on both clocks. > > > (3)For comment 8,I am not sure if I get David's point right."if the dst host > > is 10 minutes behind, and you migrate the VM, but leave the VM running for > > 10 minutes", after migration, the VM is hang and can't operate it via > > vncviewer,10 minutes later, vm can be operated normally. > > One thing we've seen before is a case like this: > a) Src host has clock at 9:00am > b) Dst host has clock at 8:50am > c) We migrate > d) VM appears hung > e) Once dst host gets to 9:00am the VM recovers > > I wanted to know if this is the case you're seeing. > > Dave Hi, David, > > (2)when the dst host is 10 minutes before than src host, windows guest can > > work well after migration. So, did rhel69 product only support the scenario > > that dst host is 10 minutes before than src host? and not support the > > scenario that dst host is 10 minutes backward than src host? > > Your wording is incorrect - when you say 'backward' and 'before' which way > around do you mean? Give me an example of the time on both clocks. > >I am sorry my wording is incorrect. I mean if rhel69 product only support the scenario that dst host is 10 minutes forward than src host for example: a) Src host has clock at 8:50am b) Dst host has clock at 9:00am and don't support the scenario that dst host is 10 minutes backward than src host for example: a) Src host has clock at 9:00am b) Dst host has clock at 8:50am > > > (3)For comment 8,I am not sure if I get David's point right."if the dst host > > is 10 minutes behind, and you migrate the VM, but leave the VM running for > > 10 minutes", after migration, the VM is hang and can't operate it via > > vncviewer,10 minutes later, vm can be operated normally. > > One thing we've seen before is a case like this: > a) Src host has clock at 9:00am > b) Dst host has clock at 8:50am > c) We migrate > d) VM appears hung > e) Once dst host gets to 9:00am the VM recovers > >Yes,test step and result of this bug are as you said a,b,c,d,e. |