Bug 994882
Summary: | Live block migration results in a zero console log | ||
---|---|---|---|
Product: | [Community] Virtualization Tools | Reporter: | quqi99 |
Component: | libvirt | Assignee: | Libvirt Maintainers <libvirt-maint> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | unspecified | CC: | kchamart, parthipan, pawel.koniszewski, quqi99, rbalakri |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-02-25 14:11:59 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
quqi99
2013-08-08 07:58:40 UTC
Just trying to understand your question, why would you expect the console log (which is related to boot) be updated when live migration is performed? Kashyap, not updated but moved to destination host along with the VM. Please consider situation when operator live migrates VM only for host maintenance. After host maintenance he will live migrate VM back to original host and I think that in such case console.log should still be there (e.g. transferred to destination host with VM and then back to original host). (In reply to Pawel Koniszewski from comment #2) > Kashyap, not updated but moved to destination host along with the VM. > > Please consider situation when operator live migrates VM only for host > maintenance. After host maintenance he will live migrate VM back to original > host and I think that in such case console.log should still be there (e.g. > transferred to destination host with VM and then back to original host). Pawel, seems like there's general agreement from libvirt upstream that this needs to be handled at a higher-layer than libvirt. [Below is a comment from IRC, by Dan Berrangé, on this topic] "This bug is basically asking for the block migration functionality to extend to other qemu devices backed by files. This is pretty tricky in general, because with latest libvirt & qemu, qemu doesn't even get acess to the log files. It just gets given an anonymous pipe file descriptor, so it has no ability to migrate the log file even if it wanted to. libvirt tries to only concern itself with what happens on a single-node so moving stuff between nodes is left to the app using libvirt which knows better what to do". |