WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] xen 3.1 - domU hangs just after "xm create"

To: "Сергей Лукашевич" <lukash33@xxxxxxxxx>
Subject: RE: [Xen-users] xen 3.1 - domU hangs just after "xm create"
From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
Date: Mon, 25 Jun 2007 18:45:51 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 25 Jun 2007 09:44:22 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1311182788562@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Ace3RSE0GCRYr5ikSOSJeNpxL+dgCQAAMNTg
Thread-topic: [Xen-users] xen 3.1 - domU hangs just after "xm create"
 

> -----Original Message-----
> From: Сергей Лукашевич [mailto:lukash33@xxxxxxxxx] 
> Sent: 25 June 2007 17:23
> To: Petersson, Mats
> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-users] xen 3.1 - domU hangs just after "xm create"
> 
> Thank you, Mats for carefully answering my writings.
> Now I managed to get xend.log by uncommenting it at my 
> /etc/xen/xend-config.sxp.
> And I could reproduce the following case:
> 
> http://lists.xensource.com/archives/html/xen-users/2007-06/msg
> 00766.html
> 
> More precisely:
> 
> [2007-06-25 19:53:23 17224] ERROR (XendDomainInfo:105) Domain 
> construction failed
> Traceback (most recent call last):
>   File "//usr/lib64/python/xen/xend/XendDomainInfo.py", line 
> 103, in create_from_dict
>     vm.start()
>   File "//usr/lib64/python/xen/xend/XendDomainInfo.py", line 
> 420, in start
>     raise XendError('VM already running')
> XendError: VM already running
> [2007-06-25 19:53:23 17224] DEBUG (XendDomainInfo:1660) 
> XendDomainInfo.destroy: domid=26
> [2007-06-25 19:53:23 17224] ERROR (XendDomainInfo:1231) 
> Failed to restart domain 26.
> Traceback (most recent call last):
>   File "//usr/lib64/python/xen/xend/XendDomainInfo.py", line 
> 1216, in _restart
>     new_dom = XendDomain.instance().domain_create_from_dict(
>   File "//usr/lib64/python/xen/xend/XendDomain.py", line 932, 
> in domain_create_from_dict
>     dominfo = XendDomainInfo.create_from_dict(config_dict)
>   File "//usr/lib64/python/xen/xend/XendDomainInfo.py", line 
> 103, in create_from_dict
>     vm.start()
>   File "//usr/lib64/python/xen/xend/XendDomainInfo.py", line 
> 420, in start
>     raise XendError('VM already running')
> XendError: VM already running

So, the kernel crashes, and when it tries to restart, the old one hasn't gone 
yet (maybe it never will??). 


Not sure what to say here. Obviously, the kernel itself should be fine, as Dom0 
works fine. 

Not sure what the "solution" refers to either - I guess it says "change the 
settings for pre-emption model and frequency" to something else - but what I 
don't really know. 

There's nothing that says "this is wrong" in the xend.log as far as I can see 
(but this is just the last few lines, right?)

--
Mats
[snip lots of logs and old comments]



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users