Bug 725368 - VDSM: During failed migration, VM stops responding for ~20 minutes
Summary: VDSM: During failed migration, VM stops responding for ~20 minutes
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kvm
Version: 5.7
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Ronen Hod
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 699402
TreeView+ depends on / blocked
 
Reported: 2011-07-25 10:31 UTC by Daniel Paikov
Modified: 2014-12-15 00:53 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-07 11:37:01 UTC
Target Upstream Version:

Attachments (Terms of Use)
vdsm.log (943.83 KB, application/x-gzip)
2011-07-25 10:31 UTC, Daniel Paikov 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 690189 0 urgent CLOSED 2.2.z - Guest will be left in migrating from status, even if the guest on destination died or inaccessible 2021-02-22 00:41:40 UTC

Internal Links: 690189

Description Daniel Paikov 2011-07-25 10:31:03 UTC 
Created attachment 515007 [details]
vdsm.log

* Create VM with 4GB of RAM.
* Migrate VM to 2nd host.
* During migration, block connection to 2nd host using iptables.
* VM becomes stuck in Not Responding status for ~20 minutes. During this time the VM doesn't respond to ping or any other connection.
Comment 1 Daniel Paikov 2011-07-25 10:53:18 UTC 
Related to bug #690189.
Comment 3 Dan Kenigsberg 2011-07-25 20:14:00 UTC 
Are you saying the the guest is hung for 20 minutes?

If you stop vdsm and contact qemu directly with

nc -U /var/vdsm/<vmId>.monitor.socket

is the qemu monitor responsive? (help, info status). If not, it is a qemu bug.
Comment 4 Dor Laor 2011-07-28 10:40:05 UTC 
You should be able to cancel the migration through the monitor interface.
Comment 5 Daniel Paikov 2011-07-28 13:46:46 UTC 
The monitor interface isn't responding during these 20 minutes.
Comment 8 Ronen Hod 2011-08-07 11:37:01 UTC 
Closing since we only fix urgent bugs in RHEL5.8.
It seems as if we survived this behavior so far. It was not reported by a customer. If I got it right, there is no corruption, and the source vm can be restarted and run properly.
Ronen.
Note You need to log in before you can comment on or make changes to this bug.