Description of problem: running `xm list` throws xmlrpclib.ProtocolError xen-3.0.2-4 yum updated to rawhide-20060601 guest running rawhide-20060601 installer (via xenguest-install.py) kernel 2.6.16-1.2236_FC6xen0 error seen: $)-> xm list Unexpected error: xmlrpclib.ProtocolError Please report to xen-devel.com Traceback (most recent call last): File "/usr/sbin/xm", line 10, in ? main.main(sys.argv) File "/usr/lib/python2.4/site-packages/xen/xm/main.py", line 1124, in main rc = cmd(args) File "/usr/lib/python2.4/site-packages/xen/xm/main.py", line 378, in xm_list doms = getDomains(params) File "/usr/lib/python2.4/site-packages/xen/xm/main.py", line 351, in getDomains return server.xend.domains(1) File "/usr/lib/python2.4/xmlrpclib.py", line 1096, in __call__ return self.__send(self.__name, args) File "/usr/lib/python2.4/site-packages/xen/util/xmlrpclib2.py", line 83, in __request response = xmlrpclib.ServerProxy.__request(self, methodname, params) File "/usr/lib/python2.4/xmlrpclib.py", line 1383, in __request verbose=self.__verbose File "/usr/lib/python2.4/site-packages/xen/util/xmlrpclib2.py", line 54, in request return Transport.request(self, host, '/RPC2', request_body, verbose) File "/usr/lib/python2.4/xmlrpclib.py", line 1137, in request headers xmlrpclib.ProtocolError: <ProtocolError for /RPC2: 500 Internal error> System was running one fully virtualized guest, domain id 7 (had been running several earlier tests without error). Ran `xm list`, which was previously successful, and the traceback was printed. Previous guests were killed (usually) with xm destroy, as evidenced by several installation trees mounted under /var/lib/xen/xenfs.?????? not yet reproduced, I'm giving the guest sufficient time to finish installing and xenguest-install.py to return. xenguest-install.py was launched with ['/usr/sbin/xm', 'create', '-c', 'cdrom=/mnt/tests/xen/xm/install/boot.iso', 'boot=d', '/etc/xen/rawhide-fv'] /etc/xen/rawhide-fv: # Automatically generated xen config file name = "rawhide-fv" builder = "hvm" memory = "400" uuid = "84ef197f-0dc1-714c-b7e0-60ab32217dbb" disk = [ 'file:/root/rawhide.img,ioemu:hda,w' ] vif = [ 'type=ioemu,bridge=xenbr0,mac=00:16:3e:33:9e:8a' ] on_reboot = 'restart' on_crash = 'restart' kernel = '/usr/lib/xen/boot/hvmloader' device_model = '/usr/lib/xen/bin/qemu-dm' sdl = 0 # use SDL for graphics vnc = 0 # use VNC for graphics vncviewer = 0 # spawn vncviewer by default nographic = 1 # don't use graphics serial='pty' # enable serial console
nevermind. EXT3-fs error (device sda2): ext3_add_entry: bad entry in directory #5210118: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0 Aborting journal on device sda2. ext3_abort called. EXT3-fs error (device sda2): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only EXT3-fs error (device sda2) in start_transaction: Journal has aborted EXT3-fs error (device sda2) in ext3_create: IO failure closing as notabug. unless there's a reason that xm should live through that (like to nicely propagate an `xm shutdown`), that error seems reasonable.