VPS Will Not Reboot

Submitted by brucelet on Wed, 07/07/2010 - 11:00

I am getting this boot message when rebooting a Xen instance. Please advise how to correct this.

PTY PID: 22811 Using config file "/xen/cwtvoip.cfg". Error: VM name 'cwtvoip' already in use by domain 32

Status: 
Closed (fixed)

Comments

Submitted by JamieCameron on Wed, 07/07/2010 - 12:21

Try SSHing into the host system as root and running :

xm list

if you see a VM named cwtvoip or Zombie-cwtvoip already running, kill it manually with the command :

xm destroy cwtvoip

or

xm destroy Zombie-cwtvoip

Submitted by brucelet on Wed, 07/07/2010 - 12:28

xm list returns a message of "bash: xm: command not found"

Submitted by brucelet on Wed, 07/07/2010 - 12:30

However, xm shows up twice on the process list.

Submitted by JamieCameron on Wed, 07/07/2010 - 12:38

Try using /usr/sbin/xm instead

Submitted by brucelet on Wed, 07/07/2010 - 15:28

That did the trick. Thanks.

Submitted by JamieCameron on Wed, 07/07/2010 - 17:29

Cool .. I will improve Virtualmin's detection of those zombie Xen instances in future.

Submitted by brucelet on Mon, 07/19/2010 - 07:31

My server needed rebooted and now the Xen VPS instances are not running. I tried running the xm list command, but it says that xend is not running. I tried to restart it with /etc/init.d/xend start or restart, but it did not restart. Please advise.

Submitted by JamieCameron on Mon, 07/19/2010 - 09:36

Is the xend process actually running? If not, does /etc/init.d/xend start start it?

Submitted by brucelet on Mon, 07/19/2010 - 10:03

xend is not a running process and running the start or restart command just comes back to the command line without an error, but the process does not start.

Submitted by JamieCameron on Mon, 07/19/2010 - 11:07

Are you sure it wasn't rebooted into a non-Xen kernel? Run uname -a and make sure you see xen in the output.

If so, check /boot/grub/menu.lst and make sure the default kernel is the one with Xen.

Submitted by brucelet on Mon, 07/19/2010 - 11:50

That was the problem. It was booting a non-xen kernel.

Thanks.