Description of problem: OpenSolaris domUs will not start under RHEL5 Version-Release number of selected component (if applicable): RHEL5 xen-3.0.3-25.0.3.el5 How reproducible: Every time Steps to Reproduce: 1. Set up a Solaris domU config file 2. Try to start it with xm create Additional info: The patch here: http://xenbits.xensource.com/xen-unstable.hg?rev/70687bcb82dd needs backporting, and then it will work.
While I'm remembering context, this thread makes it clear why we need the above patch: https://www.redhat.com/archives/libvir-list/2007-September/msg00305.html Solaris uses numbers 0,1,2,3 instead of xvda, xvdb, etc for disk names. The current XenD code doesn't correctly distinguish '0' from 'None', hence the patch above.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Set dev ack for Dan Berrange.
Created attachment 292075 [details] Upstream patch re-diffed for RHEL
Fix built $ brew latest-pkg dist-5E-qu-candidate xen Build Tag Built by ---------------------------------------- -------------------- ---------------- xen-3.0.3-47.el5 dist-5E-qu-candidate berrange * Fri Jan 18 2008 Daniel P. Berrange <berrange> - 3.0.3-47.el5 - Fix blkif check to distinguish 0 and None for Solaris (rhbz #253222)
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/RHBA-2008-0305.html