Bug 1023489
| Summary: | RHEVM 3.3 is19 Migration Fails for Win2008 R2 64 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Vimal Patel <vipatel> | ||||
| Component: | ovirt-engine | Assignee: | Vinzenz Feenstra [evilissimo] <vfeenstr> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Pavel Novotny <pnovotny> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 3.3.0 | CC: | acathrow, bsanford, dblechte, djasa, iheim, istein, lpeer, mavital, michal.skrivanek, Rhev-m-bugs, sherold, vfeenstr, vipatel, yeylon | ||||
| Target Milestone: | --- | Keywords: | Triaged | ||||
| Target Release: | 3.3.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | virt | ||||||
| Fixed In Version: | is26 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 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: | |||||||
| Bug Depends On: | 1037547 | ||||||
| Bug Blocks: | 1044030 | ||||||
| Attachments: |
|
||||||
you observed 2 different results - one failing migration the other succeeding? Please add logs for failing migration (engine, vdsm, libvirt) regarding client freezing this would need to be investigated by SPICE team as it is internal to remote-viewer<->spice-server communication I have a Windows 8.1 client and a W2K8R2 SP1 guest and the migration freezes the guest about 5 seconds into the migration, then for about 30 - 45 seconds nothing is seen and then logs the user out. Once the login screen appears (User is logged out), the migration continues. I then press CAD, login and it was like the guest was never migrated. Bill and Vimal: Which version of the VirtIO Drivers are you using? From what is in http://bob.eng.lab.tlv.redhat.com/builds/is19/, I would believe that we would be using virtio-win-1.6.6-1.el6.noarch.rpm (also at bottom of "is19" list). (In reply to Bill Sanford from comment #4) > From what is in http://bob.eng.lab.tlv.redhat.com/builds/is19/, I would > believe that we would be using virtio-win-1.6.6-1.el6.noarch.rpm (also at > bottom of "is19" list). Please try the latest virtio-win-1.6.7-2 and let me know if this still applies https://brewweb.devel.redhat.com/packageinfo?packageID=12447 Migration works without any problems in is26 Verified in is27.
RHEVM: rhevm-3.3.0-0.40.rc.el6ev.noarch (is27)
virtio-win-1.6.7-3.el6_5.noarch
Guest: Windows 2008 R2 x64
Client / console:
Windows 7 x64 / SPICE over virt-viewer (0.5.7-1.fc19.berrange1375272046), SPICE-HTML5 and noVNC
Win2008R2 guest has been manually migrated several times with console opened on client. All migrations completed successfully.
Closing - RHEV 3.3 Released Closing - RHEV 3.3 Released |
Created attachment 816180 [details] log file from the host where migration failed Description of problem: I tried multiple migrations and all have failed. Doing a simple migration with leaving notepad open and typing left the VM frozen for 7-8 seconds, and then remote-viewer on the client closed out automatically, while the migration was completed. I tried multiple migrations with a video playing on youtube, and I had a failed migration, and the remote-viewer on the client freezing and closing out. Other times it was just freezing on the client for long periods of time, while the migration completed. Client: Windows 7 64 Host: RHEL 6.5 Snap3 Guest: Windows 2008 R2 RHEVM is19 Using native invocation: mingw-virt-viewer 0.5.66.el6_4 Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Migrate the Windows 2008 R2 64 VM from the Admin console of RHEVM 2. 3. Actual results: Frozen on the client for a long period of time, freezing on the client and remote-viewer closing out on the client, freezing on the client, remote-viewer closing out on the client, and migration failing. Expected results: Successful migration with little to no effects seen on the client Additional info: