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 2144427 - [RHEL8.8 qemu-kvm] Hotplug nic can't get ip after reboot vm
Summary: [RHEL8.8 qemu-kvm] Hotplug nic can't get ip after reboot vm
Keywords:
Status: CLOSED DUPLICATE of bug 1958175
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: qemu-kvm
Version: 8.8
Hardware: aarch64
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Hu Shuai (Fujitsu)
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-21 08:48 UTC by Hu Shuai (Fujitsu)
Modified: 2022-11-22 06:21 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-22 06:21:11 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-139998 0 None None None 2022-11-21 09:05:45 UTC

Description Hu Shuai (Fujitsu) 2022-11-21 08:48:28 UTC 
Description of problem:
Hotplug nic can't get ip after reboot vm

Version-Release number of selected component (if applicable):
qemu-kvm-6.2.0-25.module+el8.8.0+17289+bd3b0bcc.aarch64

How reproducible:
2%

Steps to Reproduce:
1. Prepare a KAR test environment
2. Limit tier1_test_rhel8_aarch64.cfg to `nic_hotplug.vhost_nic.nic_virtio.default` case
3. Run "python3 ConfigTest.py --mem=8192 --vcpu=4 --category=tier1_test_rhel8_aarch64 --hostname=RHEL-8.8.0 --debug"

Actual results:
```
 (1/2) Host_RHEL.m8.u8.v0.product_rhel.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.8.7.0.aarch64.io-github-autotest-qemu.nic_hotplug.vhost_nic.nic_virtio.arm64-pci: STARTED
 (1/2) Host_RHEL.m8.u8.v0.product_rhel.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.8.7.0.aarch64.io-github-autotest-qemu.nic_hotplug.vhost_nic.nic_virtio.arm64-pci:  FAIL: Hotplug nic still can't get ip after reboot vm (1236.08 s)
 (2/2) Host_RHEL.m8.u8.v0.product_rhel.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.8.8.0.aarch64.io-github-autotest-qemu.nic_hotplug.vhost_nic.nic_virtio.arm64-pci: STARTED
 (2/2) Host_RHEL.m8.u8.v0.product_rhel.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.8.8.0.aarch64.io-github-autotest-qemu.nic_hotplug.vhost_nic.nic_virtio.arm64-pci:  PASS (156.84 s)
```

Expected results:
All pass

Additional info:
Comment 1 lijin 2022-11-22 06:03:24 UTC 
Hi Lei,
Could you help to reproduce on x86 as well, it looks like https://bugzilla.redhat.com/show_bug.cgi?id=1762906#c25
Comment 2 Lei Yang 2022-11-22 06:13:03 UTC 
(In reply to lijin from comment #1)
> Hi Lei,
> Could you help to reproduce on x86 as well, it looks like
> https://bugzilla.redhat.com/show_bug.cgi?id=1762906#c25

Hi Li

x86 has always had a product bug tracking this problem, you can refer to:: https://bugzilla.redhat.com/show_bug.cgi?id=1958175. From the feature owner perspective, this issue does not distinguish between different hardware, so the current bug can be closed as a dup.

Thanks
Lei
Comment 3 Hu Shuai (Fujitsu) 2022-11-22 06:21:11 UTC 
Baseed on comment#2, close this bus as dup.

*** This bug has been marked as a duplicate of bug 1958175 ***
Note You need to log in before you can comment on or make changes to this bug.