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 703848 - VDSM - Migrate VM fails when displayNetwork is used
Summary: VDSM - Migrate VM fails when displayNetwork is used
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.1
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Dan Kenigsberg
QA Contact: Kiril Nesenko
URL:
Whiteboard:
Depends On: 703851
Blocks: 753625
TreeView+ depends on / blocked
 
Reported: 2011-05-11 12:54 UTC by Ortal
Modified: 2014-07-11 00:07 UTC (History)
9 users (show)

Fixed In Version: vdsm-4.9-66.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 753625 (view as bug list)
Environment:
Last Closed: 2011-12-06 07:17:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Logs (888.34 KB, application/octet-stream)
2011-05-11 12:54 UTC, Ortal
no flags Details
dumpxml_on_VM (3.95 KB, text/plain)
2011-05-11 13:03 UTC, Ortal
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2011:1782 0 normal SHIPPED_LIVE new packages: vdsm 2011-12-06 11:55:51 UTC

Description Ortal 2011-05-11 12:54:55 UTC
Created attachment 498283 [details]
Logs

VDSM - Migrate VM fails when displayNetwork is used

Prerequisites:

1 DC ver.2.3
2 Hosts in cluster (Intel conroe type)- RHEL 6.1
libvirt-0.8.7-18.el6.x86_64
vdsm-4.9-64.el6.x86_64
qemu-kvm-0.12.1.2-2.160.el6.x86_64


Scenario:

1. Create new VM with Windows OS (such as: Win-XP, Win7)
2. Use the default console for that VM (VNC)
3. Attempt to migrate that VM
4. migration failed, getting an error under libvirtd.log of:

libvirtd.log:

10:23:12.113: 2033: error : remoteIO:10569 : internal error process exited while connecting to monitor: Using CPU model "Conroe"
inet_listen_opts: bind(ipv4,10.35.104.15,5900): Cannot assign requested address
inet_listen_opts: FAILED

VDSM.log

Thread-37701::ERROR::2011-05-09 11:51:50,138::vm::330::vm.Vm::(_recover)
vmId=`a7df874f-e0a4-44cc-924a-5aebed0fca58`::internal error process exited
while connecting to monitor: Using CPU model "Conroe"
inet_listen_opts: bind(ipv4,10.35.104.15,5900): Cannot assign requested address
inet_listen_opts: FAILED

Thread-37704::DEBUG::2011-05-09 11:51:50,138::libvirtvm::197::vm.Vm::(run)
vmId=`a7df874f-e0a4-44cc-924a-5aebed0fca58`::migration downtime thread exiting
Thread-37701::ERROR::2011-05-09 11:51:50,723::vm::456::vm.Vm::(run)
vmId=`a7df874f-e0a4-44cc-924a-5aebed0fca58`::Traceback (most recent call last):
  File "/usr/share/vdsm/vm.py", line 447, in run
    self._startUnderlyingMigration()
  File "/usr/share/vdsm/libvirtvm.py", line 244, in _startUnderlyingMigration
    libvirt.VIR_MIGRATE_PEER2PEER, None, maxBandwidth)
  File "/usr/share/vdsm/libvirtvm.py", line 267, in f
    ret = attr(*args, **kwargs)
  File "/usr/share/vdsm/libvirtconnection.py", line 59, in wrapper
    ret = f(*args, **kwargs)
  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 576, in
migrateToURI
    if ret == -1: raise libvirtError ('virDomainMigrateToURI() failed',
dom=self)
libvirtError: internal error process exited while connecting to monitor: Using
CPU model "Conroe"
inet_listen_opts: bind(ipv4,10.35.104.15,5900): Cannot assign requested address
inet_listen_opts: FAILED

____________

Thread-37701::ERROR::2011-05-09 11:51:50,138::vm::330::vm.Vm::(_recover)
vmId=`a7df874f-e0a4-44cc-924a-5aebed0fca58`::internal error process exited
while connecting to monitor: Using CPU model "Conroe"
inet_listen_opts: bind(ipv4,10.35.104.15,5900): Cannot assign requested address
inet_listen_opts: FAILED


dumpxml on the VM:

<graphics type='vnc' port='5900' autoport='yes' listen='10.35.102.21' keymap='en-us' passwdValidTo='1970-01-01T00:00:01'/>


** Please see attached VDSM.log & RHEVM.log
** Need to specify a simbolic network name, to be evaluated to IP on the destination host, something like

Comment 1 Ortal 2011-05-11 13:03:22 UTC
Created attachment 498287 [details]
dumpxml_on_VM

Comment 3 Dan Kenigsberg 2011-05-12 08:05:32 UTC
Until we have libvirt bug 703851 fixed, we have a tough choice: either ignore displayNetwork altogether, or fail migration when it is set. What is your opinion, Simon?

Comment 5 Dan Kenigsberg 2011-05-14 18:27:09 UTC
ignore displayNetwork until supported by libvirt

http://gerrit.usersys.redhat.com/#change,393

Comment 7 Kiril Nesenko 2011-05-22 10:53:15 UTC
Verified
ic118

Comment 8 errata-xmlrpc 2011-12-06 07:17:55 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/RHEA-2011-1782.html


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