[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] dynamic memory extension not working on Debian Squeeze

On 11/14/2012 12:08 PM, Peter Viskup wrote:
On 11/14/2012 11:51 AM, Ian Campbell wrote:
On Wed, 2012-11-14 at 10:46 +0000, Peter Viskup wrote:
On 11/14/2012 11:39 AM, Ian Campbell wrote:
On Wed, 2012-11-14 at 10:35 +0000, Peter Viskup wrote:
server1:~# xenstore-ls -fp | grep target
<this command is hanging>
xenfs is not mounted on dom0 - could it be the reason of this issues?
Could be, I'm surprised you were able to start a domain at all without
it though.

Also if xenstore is hanging then there is something else majorly wrong
too. Probably best to remedy both of those first.

Mounting xenfs might be enough to kick things back to life but otherwise
you may need to reboot the host.

Sorry I was wrong - xenfs mounted on dom0 and also on domU.
Server rebooted last night (6-7 hours before) - no additional
installation tasks were performed.
These are xen-related packages installed:

ii  xen-tools
4.2-1                        Tools to manage Xen virtual servers
ii  xen-utils-4.0
4.0.1-5.4                    XEN administrative tools
ii  xen-utils-common
4.0.0-1                      XEN administrative tools - common files
ii  xen-hypervisor-4.0-amd64
4.0.1-5.4                    The Xen Hypervisor on AMD64
ii  linux-image-2.6.26-2-xen-amd64
2.6.26-27                    Linux 2.6.26 image on AMD64, oldstyle Xen
ii  linux-image-2.6.32-5-xen-amd64
2.6.32-46 Linux 2.6.32 for 64-bit PCs, Xen dom0 support
What version of xenstore-utils do you have installed?

memory  = '256'
memmax  = '4092'

This is good, it *should* mean you can balloon up to 4G.

Command xenstore-ls still hanging.
Are you running this in dom0 or domU? You should run it in dom0.

If the xenstore tools don't work in dom0 then there is a pretty big
problem. You could try strace'ing the client and/or daemon I suppose?

One not uncommon problem with the C xenstored is a corrupted DB, so
removing /var/run/xenstored/tdb and rebooting might help. In general
removing this on boot (before starting the daemon) is a good idea, not
sure if the Debian scripts do this for you.


I ran that xenstore command in dom0.
These are versions of xenstore packages:
ii libxenstore3.0 4.0.1-5.4 Xenstore communications library for Xen ii xenstore-utils 4.0.1-5.4 Xenstore utilities for Xen

Strange is that xenstore tdb file is missing:

server1:~# ls -la /var/run/xenstored/
total 8
drwxr-xr-x  2 root root 4096 Nov 14 01:06 .
drwxr-xr-x 20 root root 4096 Nov 14 01:08 ..
srw-------  1 root root    0 Nov 14 01:06 socket
srw-rw----  1 root root    0 Nov 14 01:06 socket_ro

Debian is not removing that file during the shutdown (checked /etc/init.d/xend). I also checked checksums of all files of all xen-related packages and all is OK.

As this is production box it's hard to strace it during the office hours.
Any way to get the xenstore tdb re-created without rebooting?


I found the tdb file - in Debian it is in /var/lib/xenstored:

server1:~# ls -la /var/lib/xenstored/tdb
-rw-r----- 1 root root 1368064 Nov 14 11:27 /var/lib/xenstored/tdb

I will try to remove it and reboot this server at night. Is there any way to check the xenstore tdb file consistency?


Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.