> Has anyone else seen this kind of issue? > I'm currently a bit puzzled where to look for the root cause. > Maybe it is related to dbus. Could you share your XML config? Guess it's something with systemd.

Hi Richard, > -----Original Message----- > From: Richard Weinberger [mailto:richard@nod.at] > Sent: Friday, September 26, 2014 4:59 PM > To: Chen, Hanxiao/陈 晗霄; Richard Weinberger; libvir-list(a)redhat.com > Subject: Re: [libvirt] CreateMachine: Input/output error > > Chen, > > Am 26.09.2014 10:23, schrieb Chen, Hanxiao: >>> Has anyone else seen this kind of issue? >>> I'm currently a bit puzzled where to look for the root cause. >>> Maybe it is related to dbus. >> >> Could you share your XML config? >> Guess it's something with systemd. > > There you go: > <domain type='lxc'> > <name>c_secret_name</name> > <memory>524288</memory> > <os> > <type>exe</type> > <init>/sbin/init</init> > </os> > <idmap> > <!-- here be dragons, the mapping is non-linear --> > <uid start='0' target='101000' count='998'/> > <gid start='0' target='101000' count='998'/> > <uid start='65533' target='101998' count='2'/> > <gid start='65533' target='101998' count='2'/> > </idmap> > <devices> > <console type='pty'/> > <filesystem type='mount'> > <source dir='/srv/container0/secret_name/rootfs'/> > <target dir='/'/> > </filesystem> > <interface type='bridge'> > <source bridge='br0'/> > <mac address='4a:19:0a:XX:XX:XX'/> > </interface> > </devices> > </domain> > > Nothing special. My host is openSUSE 13.1. On fedora20 with systemd 208, upstream libvirt, I could reproduce it.

It not happened 100%,

but once it happened, the container could not be started anymore. One workaround is to undefine it and change another name. With a quick look, I did not find out a explanations.

-----Original Message----- From: Richard Weinberger [mailto:richard@nod.at] Sent: Friday, September 26, 2014 6:31 PM To: Chen, Hanxiao/陈 晗霄; libvir-list(a)redhat.com Subject: Re: [libvirt] CreateMachine: Input/output error Chen, Am 26.09.2014 11:54, schrieb Richard Weinberger: >> On fedora20 with systemd 208, upstream libvirt, >> I could reproduce it. > > We're also on systemd 208. I have an idea, maybe we need this commit in our systemd: http://lists.freedesktop.org/archives/systemd-commits/2014-July/006543.html It is on systemd since v215.

Hi! Sometimes libvirt (1.2.7) becomes unable to start any container. Logs show only: error : virDBusCall:1429 : error from service: CreateMachine: Input/output error It looks like dbus_connection_send_with_reply_and_block() returns EIO. Has anyone else seen this kind of issue? I'm currently a bit puzzled where to look for the root cause.

On Fri, Sep 26, 2014 at 10:06:39AM +0200, Richard Weinberger wrote: > Hi! > > Sometimes libvirt (1.2.7) becomes unable to start any container. > Logs show only: > error : virDBusCall:1429 : error from service: CreateMachine: Input/output error > It looks like dbus_connection_send_with_reply_and_block() returns EIO. > > Has anyone else seen this kind of issue? > I'm currently a bit puzzled where to look for the root cause. > Maybe it is related to dbus. I've seen this while cooking up https://www.redhat.com/archives/libvir-list/2014-September/msg01549.html once. The machine didn't get listed anymore with machinectl, there were no cgroups left but using systemctl I could still see a scope named after that machine like machine-qemu\x2<vmname>.scope failed failed I didn't manage to get rid of that one besides booting. Cheers,