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/
Home Products Support Community News


[Xen-bugs] [Bug 408] New: xm destroy/shutdown doesn't free loop-device

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 408] New: xm destroy/shutdown doesn't free loop-device
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Mon, 14 Nov 2005 14:23:41 +0000
Delivery-date: Mon, 14 Nov 2005 14:23:45 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: xm destroy/shutdown doesn't free loop-device
           Product: Xen
           Version: unstable
          Platform: x86
        OS/Version: Linux-2.6
            Status: NEW
          Severity: major
          Priority: P2
         Component: Unspecified
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: falk@xxxxxxxxxxxx


I'm using xen unstable with xen_changeset Fri Nov 11 19:11:13 2005 +0100 
compiled with gcc 4.0.2 on Debian with kernel 

When I quit a VM with "xm shutdown" or "xm destroy" the loop-device used for 
root-fs of the domain 
isn't freed so after 3 VM restarts all my loopdevices are used up. 

config file for domU: 
kernel = "/boot/vmlinuz-2.6-xenU"
memory = 128
name = "foobar"
disk = [ 

(I have another domU using xen-test2...)

loop device state: 
for i in $(seq  0 7  ) ; do losetup /dev/loop$i ; done 
/dev/loop0: [0301]:3417595 (/systems/xen-test1.swap.fs)
/dev/loop1: [0301]:3417597 (/systems/xen-test2.swap.fs)
/dev/loop2: [0301]:3417594 (/systems/xen-test1.root.fs)
/dev/loop3: [0301]:3417594 (/systems/xen-test1.root.fs)
/dev/loop4: [0301]:3417596 (/systems/xen-test2.root.fs)
/dev/loop5: [0301]:3417597 (/systems/xen-test2.swap.fs)
/dev/loop6: [0301]:3417595 (/systems/xen-test1.swap.fs)
/dev/loop7: [0301]:3417596 (/systems/xen-test2.root.fs)

xm list:
Name                              ID Mem(MiB) VCPUs State  Time(s)
Domain-0                           0      384     1 r-----    41.9

I hope, this is enough info. If needed, I can grant access to the system. 

Have a nice day, 

Falk Stern

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 408] New: xm destroy/shutdown doesn't free loop-device, bugzilla-daemon <=