Re: [Xen-users] Unsticking a DomU

[epretorious <epretorious@xxxxxxxxx>]

Florian Heigl wrote
> you could debug that with xenstore-ls maybe; usually I go about
> solving it in two steps.
> 1. xenconsoled restart (if it shows no valid state this will probably not
> help)
> 2. xend restart (plus wait for 20 seconds or so)
> 
> After this the vm should be gone and the xenstore for this domid
> should also be empty.
> 
> Florian

Thanks, Florian:

Neither command had an effect. The DomU test4 still appears in the output of
xm list (but not in the output of xenstore-ls) and will not start; can not
be destroyed, and; can not be deleted.

> xen1:~ # xm list
> Name                                        ID   Mem VCPUs      State  
> Time(s)
> Domain-0                                     0   502     2     r-----   
> 680.4
> test1                                        3   768     1     -b----    
> 15.7
> test3                                            768     1              
> 179.4
> test4                                            768     1                
> 0.0
> 
> xen1:~ # xm list -l | grep '(name'
>     (name Domain-0)
>     (name test1)
>     (name test3)
>     (name test4)
>
> xen1:~ # xenstore-ls | grep 'name = '
>    name = "Domain-0"
>    name = "test1"
>    name = "Pool-0"
>   pool_name = "Pool-0"
>   name = "Domain-0"
>   pool_name = "Pool-0"
>   name = "test1"

The DomU test1 functions correctly, however. (The DomU test3 is experiencing
the same symptoms as test4.)

Ideas? Suggestions?

Eric Pretorious
Truckee, CA



--
View this message in context: 
http://xen.1045712.n5.nabble.com/Unsticking-a-DomU-tp5713191p5713207.html
Sent from the Xen - User mailing list archive at Nabble.com.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users