XEN: Error about Xend not running when attempting to manage DomU's
This document (7002198) is provided subject to the disclaimer at the end of this document.
SUSE Linux Enterprise Server 10 Service Pack 2
matching the error
The following steps will help you to match the error.
- Check the status of Xendservice xend status
should have a status of "running"
- Check the status of libvirtdservice libvirtd statusshould have a status of "running"
- Check the /var/log/xend-debug.logtail /var/log/xen/xend-debug.logMay have something similiar toself.__target(*self.__args, **self.__kwargs)
File "/usr/lib64/python2.4/site-packages/xen/web/httpserver.py", line 312, in run
(sock, addr) = self.accept()
File "/usr/lib64/python2.4/site-packages/xen/web/httpserver.py", line 331, in accept
File "/usr/lib64/python2.4/socket.py", line 169, in accept
sock, addr = self._sock.accept()
error: (22, 'Invalid argument')
Exception starting xend: not well-formed (invalid token): line 11, column 2
remove the xend database
Managed Xen DomU's store their definitions in /var/lib/xend/domains. The format uses a Python syntax. If the managed database becomes corrupted then you can lose the virtual machine definitions. If you have made any changes using "xm" commands, Virt-Manager or YaST to any virtual machine definition, then it is very likely that the configuration at install time has been altered. Because of this concern, it is strongly recommended that you backup the database before you do anything.
Therefore, it is recommended that you RENAME /var/lib/xend to /var/lib/xend.bk (or something similiar).
- Backup the /var/lib/xend. Renaming the directory will be sufficient.
- Shutdown the xend serviceservice xend stop
- Shutdown the libvirtd serviceservice libvirtd stop
- Make sure that /var/lib/xend does NOT exist. When xend is started again, this directory will be recreated.
- Start up the xend serviceservice xend start
- Start up the libvirtd serviceservice libvirtd start
- Test to make sure a simple "xm" command works. No DomU's will appear in the management database.xm list
If you do not use a managed database, use the DomU's in a clustered environment then there is no further configuration needed. You should now be able to start, stop, create and otherwise manage your virtual machines normally.
Managed domains are DomU's that are manipulated using the "xm" commands such as "block-attach", "network-attach", or are managed through YaST or Virt-Manager. If you use a graphical utility to manage the DomU then the DomU's are most likely managaged. These steps will help you recover the configuration for those DomU's.
- Go to the backup made of the /var/lib/xend.
- Go to the "domain" directory.
- There should directories for each DomU; the directories will be named with a GUID.
- For each of the GUID directories, there is a "config.sxp" that defines the virtual machines.
- Import the .sxp DomU configurationxm new -F config.sxp
- See if the re-imported DomU appears in a DomU listingxm list
- Test whether or not they start normallyxm start DOMU
- Repeat step 5 through 7 for each directory in step 4
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7002198
- Creation Date:16-DEC-08
- Modified Date:27-APR-12
- SUSESUSE Linux Enterprise Server