Xen users - Sep 2007 - Ghost domain ???

Hi,

I''m running Xen 3.0.4 with suse (kernel 2.6.16.46-0.12-xen).
I''ve a
problem with a "ghost" (paravirt) domain that appear in the output of
xm list. As an example:
# xm list
Name                                      ID   Mem VCPUs      State   Time(s)
Domain-0                                   0  1024     4     r-----     29.0
vm-xyz                                            512     1                 0.0

As you can see the domain has no ID and no State. I cannot make any
reference to it (to destroy it for example). I''ve a) removed any
reference to cfg files and disk images for that domain, b) restarted
the physical host ... but I get always the same output from  xm
list!!!

Is there a method to clean up things? Where does xm list get its
data??? Do I have to remove xen packages from the host and reinstall
them? What else?
Any help wellcome.

Here I append a snapshot from the output of xm list -l :

(domain
    (on_crash destroy)
    (memory 512)
    (uuid 0c4bb267-9596-32ef-46af-d70f3d509e7b)
    (bootloader_args
''--entry=xvda1:/boot/vmlinuz-xen,/boot/initrd-xen'')
    (name vm-xyz)
    (maxmem 512)
    (on_reboot restart)
    (on_poweroff destroy)
    (vcpus 1)
    (bootloader /usr/lib/xen/boot/domUloader.py)
    (shadow_memory 0)
    (cpu_weight 256)
    (cpu_cap 0)
    (features )
    (on_xend_start ignore)
    (on_xend_stop ignore)
    (start_time 1189070518.22)
    (online_vcpus 1)
    (image
        (linux
            (kernel /var/lib/xen/tmp/kernel.q0ajL7)
            (ramdisk /var/lib/xen/tmp/ramdisk.fJgvZ8)
            (args ''TERM=xterm xencons=tty '')
        )
    )
    (status 0)
    (memory_dynamic_min 512)
    (memory_dynamic_max 512)
    (device
        (vif
            (bridge vbr_lo)
            (mac 00:16:3e:4c:7d:f7)
            (backend 0)
            (uuid 12bc4f60-2071-18a3-a09f-44c0cdc8f51a)
            (script vif-bridge)
        )
    )
    (device
        (vbd
            (uuid e600f181-cdb0-1ffa-e8dd-b834f94f56ac)
            (driver paravirtualised)
            (dev xvda:disk)
            (uname file:/xenfs/images/vm-sles10snap/bootdisk)
            (mode w)
            (type disk)
            (backend 0)
        )
    )
    (device
        (vbd
            (uuid 95d3a30b-17c4-8ad8-b812-cb298aebb3d1)
            (driver paravirtualised)
            (dev xvdb:disk)
            (uname file:/xenfs/images/vm-sles10snap/rootdisk)
            (mode w)
            (type disk)
            (backend 0)
        )
    )
    (device
        (vbd
            (uuid b6a8f396-4738-708f-a309-e288b63303a8)
            (driver paravirtualised)
            (dev xvdc:disk)
            (uname file:/system/SLES10-AMD64-EM64T-DVD1.iso)
            (mode r)
            (type disk)
            (backend 0)
        )
    )
)


Regards,
-- Marco

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

hi,

Marco Mililotti schrieb:
> Hi,
> 
> I''m running Xen 3.0.4 with suse (kernel 2.6.16.46-0.12-xen).
I''ve a
> problem with a "ghost" (paravirt) domain that appear in the
output of
> xm list. As an example:
> # xm list
> Name                                      ID   Mem VCPUs      State  
Time(s)
> Domain-0                                   0  1024     4     r-----    
29.0
> vm-xyz                                            512     1                
0.0
it''s just normal for SLES. The entry still exist in xenstore.

cu denny

-- 
Stoppt den Überwachungswahn - Stoppt den Schäuble Katalog:
http://www.nopsis.de



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

On Thu, Sep 06, 2007 at 05:12:49PM +0200, Denny Schierz
wrote:
> 
> > xm list. As an example:
> > # xm list
> > Name                                      ID   Mem VCPUs      State  
Time(s)
> > Domain-0                                   0  1024     4     r-----   
29.0
> > vm-xyz                                            512     1           
0.0
> 
> it''s just normal for SLES. The entry still exist in xenstore.
..and can be removed with ''xm delete vm-xyz''.


Christian

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

On Thu September 6 2007 11:30:11 am Christian Horn
wrote:
> On Thu, Sep 06, 2007 at 05:12:49PM +0200, Denny Schierz wrote:
> > > xm list. As an example:
> > > # xm list
> > > Name                                      ID   Mem VCPUs     
State
> > > Time(s) Domain-0                                   0  1024     4
> > > r-----     29.0 vm-xyz                                           
512
> > >   1                 0.0
> >
> > it''s just normal for SLES. The entry still exist in xenstore.
>
> ..and can be removed with ''xm delete vm-xyz''.
Or failing that, look in /var/lib/xend/domains for a directory named after 
your uuid (uuid 0c4bb267-9596-32ef-46af-d70f3d509e7b) and delete it. You 
could check with ''lsof|grep
0c4bb267-9596-32ef-46af-d70f3d509e7b'' to be sure
there are no open files in that directory. If it''s a phantom guest,
there
probably won''t be any open files. ''xm list'' will
still show the phantom until
you reboot.

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

On 9/6/07, Christian Horn <chorn@fluxcoil.net>
wrote:
> On Thu, Sep 06, 2007 at 05:12:49PM +0200, Denny Schierz wrote:
[snip]
> > it''s just normal for SLES. The entry still exist in xenstore.
>
> ..and can be removed with ''xm delete vm-xyz''.
:)
Yep - Thank you all.
Regards,
-- Marco

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