| Summary: | migration: generate domain security label before migration actually starts | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | David Jaša <djasa> |
| Component: | libvirt | Assignee: | Jiri Denemark <jdenemar> |
| Status: | CLOSED NOTABUG | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.5 | CC: | acathrow, dallan, djasa, jdenemar |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-10-03 12:23:25 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: | |
|
Description
David Jaša
2013-09-30 13:22:32 UTC
Do you actually see anything bad happening? The logs show that everything went as expected. The security label is generated during the process of starting a new qemu to be listening to incoming migration, that is as soon as a destination host knows a domain is going to be migrated in and before the migration really starts. Yes, I did. The VM fully migrated and then was killed. Since the log ended around the log excerpt aftr the migration, I assumed that this is the error that leads to subsequent "VM shutdown". So except for several failed migrations caused by "unsupported configuration: Unable to find security driver for label selinux", there are only two other cases where wxp33-dj domain was shutdown:
2013-09-27 12:51:41.208+0000: 23657: debug : virDomainDestroyFlags:2238 : dom=0x7f1228000cf0, (VM: name=wxp33-dj, uuid=707f6abe-8bf7-4211-9838-0265d73a8bc0), flags=1
2013-09-27 12:51:41.208+0000: 23657: debug : qemuProcessKill:4142 : vm=wxp33-dj pid=27462 flags=0
2013-09-27 12:51:41.208+0000: 23435: debug : qemuMonitorIOProcess:354 : QEMU_MONITOR_IO_PROCESS: mon=0x7f123c0059c0 buf={"timestamp": {"seconds": 1380286301, "microseconds":
len=85
2013-09-27 12:51:41.208+0000: 23435: debug : qemuMonitorEmitShutdown:988 : mon=0x7f123c0059c0
2013-09-27 12:51:41.208+0000: 23435: debug : qemuProcessHandleShutdown:658 : vm=0x7f123c00d390
2013-09-27 12:51:41.408+0000: 23657: debug : qemuDomainObjBeginJobInternal:808 : Starting job: destroy (async=none)
2013-09-27 12:51:41.429+0000: 23657: debug : qemuProcessStop:4244 : Shutting down VM 'wxp33-dj' pid=27462 flags=0
This was initiated by vdsm calling virDomainDestroyFlags():
Thread-167::DEBUG::2013-09-27 14:51:41,207::BindingXMLRPC::974::vds::(wrapper) client [10.34.73.33]::call vmDestroy with ('707f6abe-8bf7-4211-9838-0265d73a8bc0',) {}
The other case is
2013-09-27 13:36:29.978+0000: 30264: debug : virDomainMigratePerform3:6251 : dom=0x7f27a0011fa0, (VM: name=wxp33-dj, uuid=707f6abe-8bf7-4211-9838-0265d73a8bc0), xmlin=(null) cookiein=(nil), cookieinlen=0, cookieout=0x7f27b47ddaf0, cookieoutlen=0x7f27b47ddafc, dconnuri=qemu+tls://10.34.73.74/system, uri=tcp://10.34.73.74, flags=3, dname=(null), bandwidth=32
...
2013-09-27 13:36:41.541+0000: 30264: debug : qemuProcessStop:4244 : Shutting down VM 'wxp33-dj' pid=770 flags=1
...
2013-09-27 13:36:41.974+0000: 30264: debug : qemuDomainObjEndAsyncJob:955 : Stopping async job: migration out
which is the end of a successful migration.
The first case happened shortly after a successful migration from another host so that's the failure you reported by this bug (confirmed via IRC). However, it was vdsm on behalf of the management layer that killed the domain. That all said, we (David and I) agreed, this is not a bug in libvirt. |