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 869206 - Guest cannot start after changing watchdog from i6300esb to ib700
Summary: Guest cannot start after changing watchdog from i6300esb to ib700
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-manager
Version: 6.4
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Martin Kletzander
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-23 09:38 UTC by Geyang Kong
Modified: 2013-11-21 20:38 UTC (History)
12 users (show)

Fixed In Version: virt-manager-0.9.0-19.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-21 20:38:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1646 0 normal SHIPPED_LIVE virt-manager bug fix update 2013-11-20 21:53:27 UTC

Description Geyang Kong 2012-10-23 09:38:45 UTC 
Description of problem:
  Guest cannot start after changing watchdog from i6300esb to ib700.

Version-Release number of selected component (if applicable):
libvirt-0.10.2-4.el6.x86_64
virt-manager-0.9.0-15.el6.x86_64

Reproduce steps:
1. Have a guest with i6300esb device.
2. Change the watchdog from i6300esb to ib700 through virt-manager.
3. Start the guest

Actual results:
1. After step 3, guest cannot be started with following error
[root@localhost ~]# virsh start T2
error: Failed to start domain T2
error: internal error Process exited while reading console log output: char device redirected to /dev/pts/2
qemu-kvm: -device ib700,id=watchdog0,bus=pci.0,addr=0x4: Device 'ib700' can't go on a PCI bus

Expected results:
1. After step 3, guest can be started normally

Additional info:
1. There is an existed bug for this error, but it just covered add ib700 directly, not changing, so if we add ib700 directly, the guest can be started, but not for changing it.
https://bugzilla.redhat.com/show_bug.cgi?id=667091
Comment 2 Jiri Denemark 2012-10-23 10:27:13 UTC 
This is a general problem in virt-manager. Changing a device type/model does not reset the guest address the device should be reachable at and thus you can get meaningless combinations. E.g., changing ide disk to virt-io will tell libvirt to provide the virtio disk at ide bus (or ide disk on pci bus if you're changing from virt-io do ide). Similarly, if you have a watchdog i6300esb device presented on a pci bus and change it to ib700, virt-manager will ask for ib700 on a pci bus, which is wrong.
Comment 4 Martin Kletzander 2013-04-24 13:11:11 UTC 
AFAIK, virt-manager doesn't offer specifying address of devices, so dropping the <address> tag completely should be enough when changing models of devices.
Comment 7 luxin 2013-08-02 07:56:55 UTC 
I can reproduce this bug:

Version:
libvirt-0.10.2-2.el6.x86_64(libvirt-0.10.2-4.el6.x86_64 has been deleted)
virt-manager-0.9.0-15.el6.x86_64

Steps for Reproduce:
1. Built a guest with i6300esb watchdog device.
2. Change the watchdog from i6300esb to ib700 through virt-manager.
3. Start the guest

Result:
After step 3, guest cannot be started with following error
[root@localhost ~]# virsh start test
error: Failed to start domain test
error: internal error Process exited while reading console log output: char device redirected to /dev/pts/2
qemu-kvm: -device ib700,id=watchdog0,bus=pci.0,addr=0x4: Device 'ib700' can't go on a PCI bus

Verify:
libvirt-0.10.2-21.el6.x86_64
virt-manager-0.9.0-19.el6.x86_64

Steps for Verify:
1. Built a guest with i6300esb watchdog device.
2. Change the watchdog from i6300esb to ib700 through virt-manager.
3. Start the guest

Result:
After step 3, guest can be started normally
Comment 9 errata-xmlrpc 2013-11-21 20:38:18 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1646.html
Note You need to log in before you can comment on or make changes to this bug.