+++ This bug was initially created as a clone of Bug #211193 +++ Description of problem: When using virt-install and using a non-standard vnc port (2 == 5902 in my case) the installation fails with an error in xend because of a type mismatch: Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 195, in creat e vm.initDomain() File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1355, in init Domain self.createDevices() File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1518, in crea teDevices self.image.createDeviceModel() File "/usr/lib64/python2.4/site-packages/xen/xend/image.py", line 249, in createDeviceMo del args += [ "--vncport", "%d" %(5900 + self.vncdisplay,) ] self.vncdisply is a string. Version-Release number of selected component (if applicable): xen-3.0.2-44.x86_64 How reproducible: always Steps to Reproduce: 1.virt-install -d --p -n name -r 512 -f /dev/sda8 --vnc --vncport 5902 -l nfs:host:/some/path 2. 3. Actual results: libvir: Xen Daemon error : POST operation failed: (xend.err "Error creating domain: unsupported operand type(s) for +: 'int' and 'str'") and the message above in /var/log/xend.log Expected results: no message Additional info: -- Additional comment from berrange on 2006-10-17 16:46 EST -- The string -> int conversion in image.py is only casting the default value to an int, not a user supplied value. -- Additional comment from berrange on 2006-10-17 16:47 EST -- Created an attachment (id=138725) Fix the cast to int
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion.
Dan, I *believe* this is fixed by the following upstream changeset: http://xenbits2.xensource.com/xen-unstable.hg?rev/60e50c65f862 But I could be mis-understanding the issue. When you get a chance can you verify if that changeset will indeed fix this? Thanks, Chris Lalancette
Yes, that upstream fix is same as the attachment I made in bug #211193
*** Bug 243863 has been marked as a duplicate of this bug. ***
*** Bug 217074 has been marked as a duplicate of this bug. ***
Built into dist-5E-qu-candidate as xen-3.0.3-27.el5 * Thu Jun 14 2007 Daniel P. Berrange <berrange> - 3.0.3-27.el5 - Fix allocation of fixed VNC ports (rhbz#211208)
I have seen the exact same thing on HVM with xen-3.0.3-29.el5, when rebooting a Windows XP guest after installation. The xend.log exception was File "/usr/lib64/python2.4/site-packages/xen/xend/image.py", line 369, in configVNC ret += ['-vnc', '%d' % vncdisplay] i.e. at a different place for HVM. Fix was as trivial as casting to int too there I will enclose it, Daniel
Created attachment 158774 [details] patch for the problem but with HVM Trivial fix
The additional required fix from comment #12 is in xen-3.0.3-32.el5 built into dist-5E-qu-candidate
Fujitsu confirmed that this issue is fixed on 5.1 beta. ----------- Hi Matsuya-san, We test this problem with the RHEL5.1 beta and it is fine. Thank you. Nishi This event sent from IssueTracker by mmatsuya issue 111778
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 the 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/RHEA-2007-0635.html