Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 633699 - Cannot hot-plug nic in windows VM when the vmem is larger
Cannot hot-plug nic in windows VM when the vmem is larger
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm (Show other bugs)
6.1
All Linux
low Severity high
: rc
: ---
Assigned To: Andrea Arcangeli
Virtualization Bugs
: ZStream
Depends On:
Blocks: 580954 653343 1004197
  Show dependency treegraph
 
Reported: 2010-09-14 05:28 EDT by Golita Yue
Modified: 2013-09-04 03:58 EDT (History)
11 users (show)

See Also:
Fixed In Version: qemu-kvm-0.12.1.2-2.114.el6
Doc Type: Bug Fix
Doc Text:
Previously, when a network interface controller (NIC) was plugged into or unplugged in a running virtual machine with 4 or more gigabytes of virtual memory, a "Device '[device_name]' could not be initialized" error displayed. This is now fixed and plugging or unplugging an NIC in a running virtual machine with 4 or more gigabytes of the virtual memory works as expected.
Story Points: ---
Clone Of:
: 1004197 (view as bug list)
Environment:
Last Closed: 2011-05-19 07:30:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:0534 normal SHIPPED_LIVE Important: qemu-kvm security, bug fix, and enhancement update 2011-05-19 07:20:36 EDT

  None (edit)
Comment 14 Andrea Arcangeli 2010-09-15 11:09:34 EDT
Posted fix in rhvirt-patches with Message-ID: <20100915150855.GF5981@random.random>
Comment 15 Andrea Arcangeli 2010-09-15 12:04:36 EDT
Here a build including the fix: https://brewweb.devel.redhat.com/taskinfo?taskID=2764810
Comment 23 Jaromir Hradilek 2011-01-10 10:40:16 EST
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
When running a virtual machine with 4 or more gigabytes of the virtual memory, an attempt to hot plug a network interface controller (NIC) failed with the following error message:

  Device '[device_name]' could not be initialized

This update resolves this issue, and hot-plugging a NIC in a virtual machine with 4 or more gigabytes of the virtual memory no longer fails.
Comment 24 Misha H. Ali 2011-05-11 21:52:58 EDT
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,5 +1 @@
-When running a virtual machine with 4 or more gigabytes of the virtual memory, an attempt to hot plug a network interface controller (NIC) failed with the following error message:
+Previously, when a network interface controller (NIC) was plugged into or unplugged in a running virtual machine with 4 or more gigabytes of virtual memory, a "Device '[device_name]' could not be initialized" error displayed. This is now fixed and plugging or unplugging an NIC in a running virtual machine with 4 or more gigabytes of the virtual memory works as expected.-
-  Device '[device_name]' could not be initialized
-
-This update resolves this issue, and hot-plugging a NIC in a virtual machine with 4 or more gigabytes of the virtual memory no longer fails.
Comment 25 errata-xmlrpc 2011-05-19 07:30:26 EDT
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
Comment 26 errata-xmlrpc 2011-05-19 08:48:36 EDT
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

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