Description of problem: After the last update the system is not capable of starting the domains: [2008-06-09 01:37:40 xend 4489] ERROR (xmlrpclib2:184) (22, 'Invalid argument') Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/xen/util/xmlrpclib2.py", line 162, in _marshaled_dispatch response = self._dispatch(method, params) File "/usr/lib64/python2.4/SimpleXMLRPCServer.py", line 406, in _dispatch return func(*params) File "/usr/lib64/python2.4/site-packages/xen/xend/server/XMLRPCServer.py", line 64, in domain_create info = XendDomain.instance().domain_create(config) File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py", line 228, in domain_create dominfo = XendDomainInfo.create(config) File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 194, in create vm.construct() File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1268, in construct handle = uuid.fromString(self.info['uuid'])) Error: (22, 'Invalid argument') I checked the available versions and it looks like there is a version mismatch of xen-libs and xen. The latter seems to be missing from rhn in its latest version. Version-Release number of selected component (if applicable): 3.0.3-64.el5_2.1 How reproducible: always
Please provide your *installed* RPM versions for xen xen-libs kernel-xen And the config file for the guest in question from /etc/xen And the XML config shown by 'virsh dumpxml NAME-OF-GUEST'
My recent license renewal had reset my channel information in rhn, so I was getting only base updates. This is why xen and xen-libs managed to diverge in version. Reactivating vt rectified this. Maybe xen/xen-libs should have a Conflicts: xen < %{version}, xen > %{version} to avoid such a setup? I tried to close as NOTABUG, but bugzilla said: > Bug Change Denied > You are not permitted to make this particular change for this bug. Either because it is a RHEL product and/or you need to be in specific groups to make this change. > Please press Back and try again.
I don't know how you managed to get a mis-matched pair, because we have a fully specified dependancy requirement precisely to avoid this problem Requires: xen-libs = %{version}-%{release}