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 1275941 - Guest network becomes unreachable with bridge e1000 after hotplug memory
Summary: Guest network becomes unreachable with bridge e1000 after hotplug memory
Keywords:
Status: CLOSED DUPLICATE of bug 1271527
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.2
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Igor Mammedov
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-28 07:09 UTC by Yumei Huang
Modified: 2016-01-20 10:37 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-20 10:37:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Yumei Huang 2015-10-28 07:09:57 UTC
Description of problem:
With bridge e1000, guest network becomes unreachable after hotplug memory 256 times. Virtio-net-pci and rtl8139 works well.


Version-Release number of selected component (if applicable):
kernel: 3.10.0-326.el7.x86_64
qemu-kvm-rhev-2.3.0-31.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. launch a guest with cmd:
/usr/libexec/qemu-kvm -name rhel72-sn5 -m 1G,slots=256,maxmem=40G \

-numa node -smp 4,sockets=4,cores=1,threads=1 \

-no-user-config -nodefaults -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -boot menu=on,strict=on \

-object iothread,id=iothread0 -drive file=/home/guest/rhel72-sn5.img,if=none,id=drive-data-disk,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop  -device virtio-blk-pci,drive=drive-data-disk,id=data-disk,iothread=iothread0,bus=pci.0,addr=0x7 \

-netdev tap,id=hostnet1,vhost=on -device e1000,netdev=hostnet1,id=net2,mac=10:1a:4a:42:0a:0b,bus=pci.0,addr=0xa \

-usb -device usb-tablet,id=input0 -vga qxl \

-spice port=5901,addr=0.0.0.0,disable-ticketing,image-compression=off,seamless-migration=on -monitor unix:/tmp/monitor3,server,nowait

2. Hotplug 128M memory to guest 256 times with script:
#!/bin/bash 
i=0 
while [ $i -lt 256 ] 
do 
echo $i 
sleep 3 
echo "object_add memory-backend-ram,id=mem$i,size=128M"|nc -U /tmp/monitor3 
sleep 2 
echo "device_add pc-dimm,id=dimm$i,memdev=mem$i,slot=$i"|nc -U /tmp/monitor3 
i=$(($i+1)) 
done 

3. Ping host inside guest


Actual results:
Destination Host Unreachable.

Expected results:
Can ping host well.

Additional info:

Comment 2 Yumei Huang 2015-10-30 08:35:20 UTC
I also found after hotplug memory with 512M once, then reboot the guest, the guest network becomes unreachable too.  But with 128M and 256M, the network works well.

Comment 3 Igor Mammedov 2016-01-20 10:37:07 UTC

*** This bug has been marked as a duplicate of bug 1271527 ***


Note You need to log in before you can comment on or make changes to this bug.