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

[Xen-users] Error: (28, 'No space left on device, while writing /vm/ba5f

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Error: (28, 'No space left on device, while writing /vm/ba5fda47-f44a-2f44-b164-d2b1290d0d60/image/ostype : linux')
From: Hans-Christian Armingeon <mog.johnny@xxxxxxx>
Date: Thu, 20 Apr 2006 18:31:08 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 20 Apr 2006 09:31:48 -0700
Envelope-to: www-data@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
User-agent: KMail/1.9.1
Hi,

I am having serious trouble:

# xm create test-xen fails with

Using config file "test-xen".
Error: (28, 'No space left on device, while writing 
/vm/ba5fda47-f44a-2f44-b164-d2b1290d0d60/image/ostype : linux')

There is space free on every disk.

I am using the latest xen unstable and linux hg tree.

Can somebody help me?

Many thanks in advance,

Johnny

xm log

VmError: (28, \047No space left on device, while writing 
/vm/8fa12151-462c-ffc7-d084-2223a7231255/image/ostype : linux\047)
[2006-04-20 18:24:06 xend.XendDomainInfo] DEBUG (XendDomainInfo:1327) 
XendDomainInfo.destroy: domid=27
[2006-04-20 18:24:06 xend.XendDomainInfo] DEBUG (XendDomainInfo:1335) 
XendDomainInfo.destroyDomain(27)
[2006-04-20 18:26:19 xend.XendDomainInfo] DEBUG (XendDomainInfo:178) 
XendDomainInfo.create([\047vm\047, [\047name\047, \047test-xen\047], 
[\047memory\047, 1024], [\047on_powerof
047, \047restart\047], [\047on_crash\047, \047restart\047], [\047vcpus\047, 2], 
[\047image\047, [\047linux\047, [\047kernel\047, 
\047/boot/xen-kernels/vmlinuz-2.6.16-20060420.3-xen0-s
.2.3.4:192.168.5.15:255.255.255.0::eth0:off\047], [\047root\047, \047/dev/sda1 
ro\047]]], [\047device\047, [\047vbd\047, [\047uname\047, 
\047phy:helene500g/test-xenU-root\047],
47, \047w\047]]], [\047device\047, [\047vbd\047, [\047uname\047, 
\047phy:helene74g/test-xenU-swap\047], [\047dev\047, \047sda2\047], 
[\047mode\047, \047w\047]]], [\047device\047
br0\047], [\047mac\047, \04700:0c:8d:00:0a:08\047]]]])
[2006-04-20 18:26:19 xend.XendDomainInfo] DEBUG (XendDomainInfo:284) 
parseConfig: config is [\047vm\047, [\047name\047, \047test-xen\047], 
[\047memory\047, 1024], [\047on_powero
\047, \047restart\047], [\047on_crash\047, \047restart\047], [\047vcpus\047, 
2], [\047image\047, [\047linux\047, [\047kernel\047, 
\047/boot/xen-kernels/vmlinuz-2.6.16-20060420.3-xen0-
1.2.3.4:192.168.5.15:255.255.255.0::eth0:off\047], [\047root\047, \047/dev/sda1 
ro\047]]], [\047device\047, [\047vbd\047, [\047uname\047, 
\047phy:helene500g/test-xenU-root\047],
047, \047w\047]]], [\047device\047, [\047vbd\047, [\047uname\047, 
\047phy:helene74g/test-xenU-swap\047], [\047dev\047, \047sda2\047], 
[\047mode\047, \047w\047]]], [\047device\04
nbr0\047], [\047mac\047, \04700:0c:8d:00:0a:08\047]]]]
[2006-04-20 18:26:19 xend.XendDomainInfo] DEBUG (XendDomainInfo:380) 
parseConfig: result is {\047ssidref\047: None, \047uuid\047: None, 
\047on_crash\047: \047restart\047, \047on_reboo
\047linux\047, [\047kernel\047, 
\047/boot/xen-kernels/vmlinuz-2.6.16-20060420.3-xen0-smp\047], [\047ip\047, 
\047192.168.5.47:1.2.3.4:192.168.5.15:255.255.255.0::eth0:off\047], [\047ro
oweroff\047: \047destroy\047, \047cpus\047: None, \047name\047: 
\047test-xen\047, \047backend\047: [], \047vcpus\047: 2, \047cpu_weight\047: 
None, \047vcpu_avail\047: None, \047
vbd\047, [\047vbd\047, [\047uname\047, \047phy:helene500g/test-xenU-root\047], 
[\047dev\047, \047sda1\047], [\047mode\047, \047w\047]]), (\047vbd\047, 
[\047vbd\047, [\047uname\0
ap\047], [\047dev\047, \047sda2\047], [\047mode\047, \047w\047]]), 
(\047vif\047, [\047vif\047, [\047bridge\047, \047xenbr0\047], [\047mac\047, 
\04700:0c:8d:00:0a:08\047]])], \047bootl
maxmem\047: None}
[2006-04-20 18:26:19 xend.XendDomainInfo] DEBUG (XendDomainInfo:1164) 
XendDomainInfo.construct: None 0
[2006-04-20 18:26:19 xend.XendDomainInfo] DEBUG (XendDomainInfo:1196) 
XendDomainInfo.initDomain: 28 1.0
[2006-04-20 18:26:19 xend.XendDomainInfo] ERROR (XendDomainInfo:190) Domain 
construction failed
Traceback (most recent call last):
  File 
"/usr/src/xen/build/xen-unstable.hg-3.0-20060420.2/debian/xen-unstable.hg-3.0/usr/lib/python/xen/xend/XendDomainInfo.py",
 line 183, in create
    vm.initDomain()
  File 
"/usr/src/xen/build/xen-unstable.hg-3.0-20060420.2/debian/xen-unstable.hg-3.0/usr/lib/python/xen/xend/XendDomainInfo.py",
 line 1241, in initDomain
    raise VmError(str(exn))
VmError: (28, \047No space left on device, while writing 
/vm/b970806c-0815-2792-1fd0-89b95e5496e6/image/ostype : linux\047)
[2006-04-20 18:26:19 xend.XendDomainInfo] DEBUG (XendDomainInfo:1327) 
XendDomainInfo.destroy: domid=28
[2006-04-20 18:26:19 xend.XendDomainInfo] DEBUG (XendDomainInfo:1335) 
XendDomainInfo.destroyDomain(28)

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

<Prev in Thread] Current Thread [Next in Thread>