| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
RE: [Xen-users] Domains do not shut down or reboot cleanly since upgrade
>
> On Sun, Feb 22, 2009 at 6:41 AM, Andy Smith <andy@xxxxxxxxxxxxxx>
wrote:
> >> Have you reboot your system since the upgrade?
> >
> > Yes. Otherwise how would it be running the newer hypervisor?
>
> I had a similar problem with different version of Xen, and it turned
> out it's simply because I forgot to reboot the server, leaving Xen
> userland and hypervisor mismatch :)
>
> Anyway, for your particular situation you could try :
> - making sure hypervisor and userland match. Perhaps something screwed
> up your installation. OR,
> - update to a version of Xen known to work. I'm using Xen 3.3.1 on
> RHEL and it works correctly.
>
There is a bug in 3.3.1 that comes about when you have more than one CPU
and you restrict Dom0 to one CPU by putting "(dom0-cpus 1)" in your
config file. The symptoms are that the domain won't shut down until you
do an 'xm start' again, and even then bits of it hang around in the
hypervisor.
I'm not sure if that bug existed in 3.2 though.
James
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home