LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Red Hat (http://www.linuxquestions.org/questions/red-hat-31/)
-   -   RHEL 5: Xen domains unresponsive after login (http://www.linuxquestions.org/questions/red-hat-31/rhel-5-xen-domains-unresponsive-after-login-647168/)

BigRedBall 06-05-2008 06:19 AM

RHEL 5: Xen domains unresponsive after login
 
Hi all,
Having a little experiment with virtualised services. I'm running RHEL5 on a HP Xeon server (a relatively old one, without Vanderpool), and I've created a Xen virtual domain using paravirtualisation and a filesystem created inside a file on disk. I generated it using the GUI virt-manager app, and the install process went smoothly.

I installed Fedora 9, which initially worked fine. However, now once I start up the VM domain, it gets to the login screen, and it crashes if I attempt to log in. The VNC connection goes dead and I can't reconnect to the VM domain.

The odd thing is that I can't then reconnect to the VM domain. The virt-manager app shows CPU utilisation of 99% for the virtualised domain, and the only thing I can think to do is to run 'xm destroy VMNAME' to shut the thing off. 'xm shutdown' is ineffective.

I've also tried restarting xend and libvirtd, to no avail.

I got this error via the local mail system:
Code:

Message 656:
From root@blueridge.gcal.ac.uk  Wed Jun  4 16:42:02 2008
X-Original-To: root
Delivered-To: root@HOST
From: root@ HOST (Cron Daemon)
To: root@ HOST
Subject: Cron <root@ HOST > python /usr/share/rhn/virtualization/poller.py
Content-Type: text/plain; charset=UTF-8
Auto-Submitted: auto-generated
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=root>
X-Cron-Env: <USER=root>
Date: Wed,  4 Jun 2008 16:42:02 +0100 (BST)

libvir: Xen error : Domain not found: xenUnifiedDomainLookupByID
Traceback (most recent call last):
  File "/usr/share/rhn/virtualization/poller.py", line 202, in ?
    domain_list = poll_hypervisor()
  File "/usr/share/rhn/virtualization/poller.py", line 81, in poll_hypervisor
    raise VirtualizationException, \
virtualization.errors.VirtualizationException: Failed to obtain handle to domain 1: <libvirt.libvirtError instance at 0xb7d466cc>

And also this one:
Code:

From root@HOST  Wed Jun  4 16:44:02 2008
X-Original-To: root
Delivered-To: root@HOST
From: root@HOST (Cron Daemon)
To: root@HOST
Subject: Cron <root@HOST> python /usr/share/rhn/virtualization/poller.py
Content-Type: text/plain; charset=UTF-8
Auto-Submitted: auto-generated
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=root>
X-Cron-Env: <USER=root>
Date: Wed,  4 Jun 2008 16:44:02 +0100 (BST)

libvir: Xen error : Domain not found: xenUnifiedDomainLookupByID
Traceback (most recent call last):
  File "/usr/share/rhn/virtualization/poller.py", line 202, in ?
    domain_list = poll_hypervisor()
  File "/usr/share/rhn/virtualization/poller.py", line 81, in poll_hypervisor
    raise VirtualizationException, \
virtualization.errors.VirtualizationException: Failed to obtain handle to domain 1: <libvirt.libvirtError instance at 0xb7d146cc>

Does anyone know what's causing these errors and how I can fix them?

Also, after the VM has crashed, the only way of getting it back seems to be restarting the physical machine. Any other way to do it?

I'm running RHEL with the 2.6.18-92.el5xen kernel and all latest updates.

Thanks.

billymayday 06-05-2008 11:11 PM

Have you tried using any other distros for the virtualisation (RHEL 5 for example since you have it)? Given the cutting edgeness of F9, it may well be a Fedora issue


All times are GMT -5. The time now is 06:17 PM.