xm list don't work with python-2.7 Reproducible: Always
Created attachment 257023 [details, diff] app-emulation/xen/files/localpy27fixes.patch
Traceback (most recent call last): File "/usr/sbin/xm", line 7, in <module> main.main(sys.argv) File "/usr/lib64/python2.7/site-packages/xen/xm/main.py", line 3616, in main _, rc = _run_cmd(cmd, cmd_name, args) File "/usr/lib64/python2.7/site-packages/xen/xm/main.py", line 3640, in _run_c md return True, cmd(args) File "/usr/lib64/python2.7/site-packages/xen/xm/main.py", line 969, in xm_list doms = getDomains(params, state, use_long) File "/usr/lib64/python2.7/site-packages/xen/xm/main.py", line 933, in getDoma ins return server.xend.domains_with_state(True, state, full) File "/usr/lib64/python2.7/xmlrpclib.py", line 1224, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.7/site-packages/xen/util/xmlrpcclient.py", line 118, in __request response = xmlrpclib.ServerProxy.__request(self, methodname, params) File "/usr/lib64/python2.7/xmlrpclib.py", line 1570, in __request verbose=self.__verbose File "/usr/lib64/python2.7/site-packages/xen/util/xmlrpcclient.py", line 55, i n request request_body, verbose) File "/usr/lib64/python2.7/xmlrpclib.py", line 1264, in request return self.single_request(host, handler, request_body, verbose) File "/usr/lib64/python2.7/xmlrpclib.py", line 1294, in single_request response = h.getresponse(buffering=True) AttributeError: HTTPUnix instance has no attribute 'getresponse'
Does this bug still occur with dev-lang/python-2.7.1-r1? (It seems to be similar to bug #347465.)
I upgraded to python-2.7.1-r1 today, selected this version as global python version using eselect and then run python-updater. Amongst others xen-tools-4.0.1 was rebuild. Afterwards even after a reboot the error still exists (at least with 'xm list', afair also with 'xm create' but I'm not truly sure anymore - I didn't do any exhaustive tests but directly reverted to python-2.6 as this just works fine). As I don't have the time to test at the moment, I didn't apply the above patch etc. - just want to let you know that the problem is still existent. Regards
Xen 4.1 in tree. Please test with it and reopen if it doesnt work