* Guido Günther <a...@sigxcpu.org> [15-06-2013 16:26 EEST]: > It would be awesome if you guys would provide some information to > reproduce like: > > * which version you were upgrading from
0.9.12-11 -> 1.0.5-3
> * which VMs were running
It happens when trying to create a new vm and also when trying to start an
already existing Wheezy VM.
> * content of /proc/mounts
rootfs / rootfs rw 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,relatime,size=10240k,nr_inodes=2046777,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=1645588k,mode=755 0 0
[snipped hdd and other device mounts]
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
tmpfs /run/shm tmpfs rw,nosuid,nodev,noexec,relatime,size=4267920k 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
cgroup /sys/fs/cgroup cgroup
rw,relatime,perf_event,blkio,net_cls,freezer,devices,cpuacct,cpu,cpuset 0 0
rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0
none /sys/kernel/security securityfs rw,relatime 0 0
nfsd /proc/fs/nfsd nfsd rw,relatime 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc
rw,nosuid,nodev,noexec,relatime 0 0
vmware-vmblock /run/vmblock-fuse fuse.vmware-vmblock
rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other 0 0
> * contents of /sys/fs/cgroup before the upgrade
After the libvirt upgrade I have
blkio.io_merged blkio.io_service_time
blkio.sectors_recursive blkio.time_recursive cpuacct.usage_percpu
cpuset.memory_spread_page devices.list
blkio.io_merged_recursive blkio.io_service_time_recursive
blkio.throttle.io_service_bytes blkio.weight cpuset.cpu_exclusive
cpuset.memory_spread_slab net_cls.classid
blkio.io_queued blkio.io_wait_time
blkio.throttle.io_serviced blkio.weight_device cpuset.cpus
cpuset.mems notify_on_release
blkio.io_queued_recursive blkio.io_wait_time_recursive
blkio.throttle.read_bps_device cgroup.clone_children cpuset.mem_exclusive
cpuset.sched_load_balance release_agent
blkio.io_service_bytes blkio.leaf_weight
blkio.throttle.read_iops_device cgroup.event_control cpuset.mem_hardwall
cpuset.sched_relax_domain_level tasks
blkio.io_service_bytes_recursive blkio.leaf_weight_device
blkio.throttle.write_bps_device cgroup.procs cpuset.memory_migrate
cpu.shares
blkio.io_serviced blkio.reset_stats
blkio.throttle.write_iops_device cpuacct.stat cpuset.memory_pressure
devices.allow
blkio.io_serviced_recursive blkio.sectors blkio.time
cpuacct.usage cpuset.memory_pressure_enabled
devices.deny
I don't have the contents from before the upgrade.
> * libvirtd messages see:
>
> http://wiki.debian.org/libvirt/#Bugreports.2FDebugging
>
Trying to start an existing VM in virt-manager:
2013-06-16 03:34:26,075 (engine:878): Starting vm 'wheezy'
2013-06-16 03:34:26,082 (asyncjob:184): Creating async job for function
cb=<function tmpcb at 0x35ccb18>
2013-06-16 03:34:26,320 (error:80): dialog message: Error starting domain:
Unable to initialize /machine cgroup: Invalid argument: Error starting domain:
Unable to initialize /machine cgroup: Invalid argument
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 96, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 117, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/domain.py", line 1160, in startup
self._backend.create()
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 698, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: Unable to initialize /machine cgroup: Invalid argument
Running libvirt in debug mode doesn't show anything more.
> I do think this is related to libvirtd changing cgroup layout but
> without any detail this is impossible to tell.
I think so too.
signature.asc
Description: Digital signature
