[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Ghost domain ???

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Marco Mililotti" <foobar.angus@xxxxxxxxx>
  • Date: Thu, 6 Sep 2007 16:53:00 +0200
  • Delivery-date: Thu, 06 Sep 2007 07:53:45 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=jQRPLbW4yGPq3EbSmo9BQdQKVw7889F7pVudR0yKZAGEjPDm0O6825hayd54OjNqeOX1bwMndZHnj/YKSxMzaVs7OrpYalZfKfzOl63FdRswkxvFIXrnPmi26mX/FYRrih5FJ1Vp+aOQQmryDG9pAuoq3XvERf34FW9TTCOX03Q=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>


I'm running Xen 3.0.4 with suse (kernel 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

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 :

    (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)
            (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)
            (bridge vbr_lo)
            (mac 00:16:3e:4c:7d:f7)
            (backend 0)
            (uuid 12bc4f60-2071-18a3-a09f-44c0cdc8f51a)
            (script vif-bridge)
            (uuid e600f181-cdb0-1ffa-e8dd-b834f94f56ac)
            (driver paravirtualised)
            (dev xvda:disk)
            (uname file:/xenfs/images/vm-sles10snap/bootdisk)
            (mode w)
            (type disk)
            (backend 0)
            (uuid 95d3a30b-17c4-8ad8-b812-cb298aebb3d1)
            (driver paravirtualised)
            (dev xvdb:disk)
            (uname file:/xenfs/images/vm-sles10snap/rootdisk)
            (mode w)
            (type disk)
            (backend 0)
            (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)

-- Marco

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.