RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 613867 - qemu-kvm core dumped during live migration with vhost=on
Summary: qemu-kvm core dumped during live migration with vhost=on
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.0
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-13 02:35 UTC by ZhangQian
Modified: 2010-07-13 05:50 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-13 05:50:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description ZhangQian 2010-07-13 02:35:37 UTC 
Description of problem:
qemu-kvm core dumped during live migration with vhost=on

Version-Release number of selected component (if applicable):
# rpm -q qemu-kvm
qemu-kvm-0.12.1.2-2.91.el6.x86_64
# uname -r
2.6.32-44.el6.x86_64


How reproducible:
80%

Steps to Reproduce:
1. start guest by:
#  /usr/libexec/qemu-kvm -m 1G -smp 2 -uuid `uuidgen` -usbdevice tablet -drive file=/home/rhel5.5.z-64-virtio.raw,media=disk,format=raw,if=none,cache=none,werror=stop,rerror=stop,id=virtio0,boot=on -device virtio-blk-pci,drive=virtio0 -netdev tap,id=hostnet0,vhost=on -device virtio-net-pci,netdev=hostnet0,mac=20:20:78:90:12:93 -monitor stdio -vnc :8

2. start listening mode in remote host

3. start migration
  
Actual results:
(qemu) migrate -d tcp:10.66.65.22:5888
(qemu) info migrate
Migration status: active
transferred ram: 819360 kbytes
remaining ram: 264824 kbytes
total ram: 1065344 kbytes
(qemu) info migrate
Migration status: active
transferred ram: 994740 kbytes
remaining ram: 234744 kbytes
total ram: 1065344 kbytes
(qemu) qemu-kvm: /builddir/build/BUILD/qemu-kvm-0.12.1.2/hw/vhost.c:31: vhost_dev_sync_region: Assertion `end / (0x1000 * (8 * sizeof(vhost_log_chunk_t))) < dev->log_size' failed.
Aborted (core dumped)

Expected results:


Additional info:
# gdb /usr/libexec/qemu-kvm -c core.2911
(gdb) bt
#0  0x0000003ce5c329b5 in raise () from /lib64/libc.so.6
#1  0x0000003ce5c34195 in abort () from /lib64/libc.so.6
#2  0x0000003ce5c2b945 in __assert_fail () from /lib64/libc.so.6
#3  0x000000000042283b in vhost_dev_sync_region (dev=<value optimized out>, mfirst=<value optimized out>, mlast=<value optimized out>, 
    rfirst=<value optimized out>, rlast=<value optimized out>) at /usr/src/debug/qemu-kvm-0.12.1.2/hw/vhost.c:31
#4  0x00000000004228c1 in vhost_client_sync_dirty_bitmap (client=0x2bcf970, start_addr=0, end_addr=18446744073709551615)
    at /usr/src/debug/qemu-kvm-0.12.1.2/hw/vhost.c:70
#5  0x00000000004239c5 in vhost_dev_log_resize (client=<value optimized out>, start_addr=4026531840, size=16777216, phys_offset=<value optimized out>)
    at /usr/src/debug/qemu-kvm-0.12.1.2/hw/vhost.c:262
#6  vhost_client_set_memory (client=<value optimized out>, start_addr=4026531840, size=16777216, phys_offset=<value optimized out>)
    at /usr/src/debug/qemu-kvm-0.12.1.2/hw/vhost.c:344
#7  0x00000000004e246e in cpu_notify_set_memory (start_addr=4026531840, size=16777216, phys_offset=1074003968, region_offset=0)
    at /usr/src/debug/qemu-kvm-0.12.1.2/exec.c:1653
#8  cpu_register_physical_memory_offset (start_addr=4026531840, size=16777216, phys_offset=1074003968, region_offset=0)
    at /usr/src/debug/qemu-kvm-0.12.1.2/exec.c:2439
#9  0x0000000000460d92 in cpu_register_physical_memory (s=0x3109a58) at /usr/src/debug/qemu-kvm-0.12.1.2/cpu-common.h:29
#10 map_linear_vram (s=0x3109a58) at /usr/src/debug/qemu-kvm-0.12.1.2/hw/cirrus_vga.c:2560
#11 cirrus_update_memory_access (s=0x3109a58) at /usr/src/debug/qemu-kvm-0.12.1.2/hw/cirrus_vga.c:2627
#12 0x0000000000461157 in pci_cirrus_write_config (d=0x31097c0, address=4, val=4, len=4) at /usr/src/debug/qemu-kvm-0.12.1.2/hw/cirrus_vga.c:3198
#13 0x000000000042a178 in kvm_handle_io (env=0x2bf4010) at /usr/src/debug/qemu-kvm-0.12.1.2/kvm-all.c:541
#14 kvm_run (env=0x2bf4010) at /usr/src/debug/qemu-kvm-0.12.1.2/qemu-kvm.c:975
#15 0x000000000042a239 in kvm_cpu_exec (env=<value optimized out>) at /usr/src/debug/qemu-kvm-0.12.1.2/qemu-kvm.c:1658
#16 0x000000000042ae5f in kvm_main_loop_cpu (_env=0x2bf4010) at /usr/src/debug/qemu-kvm-0.12.1.2/qemu-kvm.c:1900
#17 ap_main_loop (_env=0x2bf4010) at /usr/src/debug/qemu-kvm-0.12.1.2/qemu-kvm.c:1950
#18 0x0000003ce64077e1 in start_thread () from /lib64/libpthread.so.0
#19 0x0000003ce5ce151d in clone () from /lib64/libc.so.6
Comment 2 ZhangQian 2010-07-13 05:50:40 UTC 
close it as my mistake in operation.
Note You need to log in before you can comment on or make changes to this bug.