From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 189941] New: rhel7.2 guest will hang after finishing save and restore operation
Date: Fri, 09 Dec 2016 08:18:17 +0000 [thread overview]
Message-ID: <bug-189941-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=189941
Bug ID: 189941
Summary: rhel7.2 guest will hang after finishing save and
restore operation
Product: Virtualization
Version: unspecified
Kernel Version: 4.9.0-rc5
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: Robert.Hu@intel.com
Regression: No
Environment:
------------
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):linux
kvm.git Commit:57d1da871b85c3a79e070d5cfc5ccb554ed839c4
qemu.git Commit:a92f7fe5a82ac9e8d127e92c5dce1a84064126da
Host Kernel Version:4.9.0-rc5
Guest Kernel Version:
Hardware:hsw-ep bdw-ex bdw-ep skl-s knl-d
Bug detailed description:
--------------------------
After saving the rhel7.2 guest,the saved guest will hang occasionally while the
restore operation been done.
Reproduce steps:
------------------------
1. create the guest:
qemu-system-x86_64 -enable-kvm -m 1024 -smp 4 -device
virtio-net-pci,netdev=nic0,mac=00:16:3e:06:4e:13 -netdev
tap,id=nic0,script=/etc/kvm/qemu-ifup -drive
file=/root/ia32e_rhel7u2.qcow,if=none,id=virtio-disk0 -device
virtio-blk-pci,drive=virtio-disk0
2. switch to qemu monitor and save the guest:
(1)press "ctrl+alt+2" to the qemu monitor screen
(2)migrate "exec:dd of=rhel7u2.img"
(3)press "q" to exit
3.restore the guest:
qemu-system-x86_64 -enable-kvm -m 1024 -smp 4 -incoming "exec:dd
if=/root/rhel7u2.img" -device virtio-net-pci,netdev=nic0,mac=00:16:3e:06:4e:13
-netdev tap,id=nic0,script=/etc/kvm/qemu-ifup -drive
file=/root/rhel7u2.qcow,if=none,id=virtio-disk0 -device
virtio-blk-pci,drive=virtio-disk0 -serial file:serial.log
Current result:
--------------------
The guest hanging on the screen where it was saved while restoring it.
Expected result:
----------------
Guest restored successfully and can get IP and run as normal.
Add info:
[root@bdw-ep ~]# qemu-system-x86_64 --enable-kvm -m 1024 -smp 4 -incoming
"exec:dd if=/root/rhel7u2.img" -device
virtio-net-pci,netdev=nic0,mac=00:16:3e:06:4e:13 -netdev
tap,id=nic0,script=/etc/kvm/qemu-ifup -drive
file=/root/rhel7u2.qcow,if=none,id=virtio-disk0 -device
virtio-blk-pci,drive=virtio-disk0 -serial file:serial.log
Receiving block device images
Completed 100 %
Completed 100 %
2662186+0 records in
2662186+0 records out
1363039232 bytes (1.4 GB) copied, 3.33819 s, 408 MB/s
The guest serial log was empty while the guest hang on doing restoring process.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2016-12-09 8:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 8:18 bugzilla-daemon [this message]
2017-09-15 5:56 ` [Bug 189941] rhel7.2 guest will hang after finishing save and restore operation bugzilla-daemon
2017-09-18 2:36 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-189941-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox