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.
Description of problem:
Version-Release number of selected component (if applicable):
libvirt-0.9.4-12.el6.x86_64
qemu-kvm-0.12.1.2-2.192.el6.x86_64
kernel-2.6.32-197.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. install guest with tree RHEL5.7-Server-20110622.0
2. start the guest
3. try to attach interface to guest with following two commands
a. # virsh attach-interface rhel57-new network default vnet0 --model e1000
b. # virsh attach-device rhel57-new interface.xml
# cat interface.xml
<interface type='bridge'>
<source bridge='virbr0'/>
<model type='virtio'/>
</interface>
Actual results:
both of the two commands got success to attach the interface to rhel5u7 guest , but without reboot the guest , guest won't recognize the interface automatically
Besides, after shutdown guest, attached device xml won't be removed from guest xml file.
Expected results:
guest can recognize attached interface automatically without reboot .
Additional info:
rhel6 guest won't encounter this problem .
And for rhel5u7 guest, attach virtio disk device doesn't work as well .
Description of problem: Version-Release number of selected component (if applicable): libvirt-0.9.4-12.el6.x86_64 qemu-kvm-0.12.1.2-2.192.el6.x86_64 kernel-2.6.32-197.el6.x86_64 How reproducible: always Steps to Reproduce: 1. install guest with tree RHEL5.7-Server-20110622.0 2. start the guest 3. try to attach interface to guest with following two commands a. # virsh attach-interface rhel57-new network default vnet0 --model e1000 b. # virsh attach-device rhel57-new interface.xml # cat interface.xml <interface type='bridge'> <source bridge='virbr0'/> <model type='virtio'/> </interface> Actual results: both of the two commands got success to attach the interface to rhel5u7 guest , but without reboot the guest , guest won't recognize the interface automatically Besides, after shutdown guest, attached device xml won't be removed from guest xml file. Expected results: guest can recognize attached interface automatically without reboot . Additional info: rhel6 guest won't encounter this problem . And for rhel5u7 guest, attach virtio disk device doesn't work as well .