Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Tested on qemu-kvm-0.12.1.2-2.146.el6 & kernel 2.6.32-113.el6.x86_64
How reproducible:
100%
steps:
1.start a VM with 16GB mem on src host.
eg:/usr/libexec/qemu-kvm -enable-kvm -m 16G -smp 4 -name rhel5U6 -uuid ddcbfb49-3411-1701-3c36-6bdbc00bedb9 -rtc base=utc,clock=host,driftfix=slew -boot c -drive file=/mnt/rhel6.raw,if=none,id=drive-ide0-0-0,boot=on,format=raw,cache=none -device virtio-blk-pci,drive=drive-ide0-0-0,id=drive-ide0-0-0 -netdev tap,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:50:a4:c2:c1 -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -device usb-tablet,id=input0 -vnc :2 -device virtio-balloon-pci,id=ballooning -monitor stdio
2.running sress in the guest
eg :#stress --cpu --vm 16 --vm-byte 256M --verbose
3.start listenning port.
4.do live migration .after 1 hour ,stop stress and wait for migration complete.
5.check guest's status
Actual Results:
migration successfully.
network of guest was DOWN after migration.
Additional info :
Tried on the same image with 4G mem ,can not reproduce
Based on above ,re-assign this bug .
This is a different bug, it is related to this two bugzillas (they are for rhel5, but rhel6 has the same problem):
https://bugzilla.redhat.com/show_bug.cgi?id=586643https://bugzilla.redhat.com/show_bug.cgi?id=647189
basically you can't expect to have a 16GB host running a 16GB guest, problems are going to happen sooner or later. Migration has special problems because it needs extra memory for buffers to do the saves. My experience is that you need to leave around 1GB of memory for the host for everything to work smoothely.
Several other things:
a- I can't reproduce, it works for me.
b- nitpik: I guess you mean --cpu 1 (or other number) that command fails for me.
Later, Juan.
(In reply to comment #11)
> This is a different bug, it is related to this two bugzillas (they are for
> rhel5, but rhel6 has the same problem):
> https://bugzilla.redhat.com/show_bug.cgi?id=586643
> https://bugzilla.redhat.com/show_bug.cgi?id=647189
> basically you can't expect to have a 16GB host running a 16GB guest, problems
> are going to happen sooner or later. Migration has special problems because it
> needs extra memory for buffers to do the saves. My experience is that you need
> to leave around 1GB of memory for the host for everything to work smoothely.
I am using 2 hosts and both host's memory is 512G, I will reserve the machine again tormorrow for further testing .
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHSA-2011-0534.html
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHSA-2011-0534.html