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

Re: [libvirt] CreateMachine: Input/output error



Chen,

Am 26.09.2014 11:49, schrieb Chen, Hanxiao:
> 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 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.

We're also on systemd 208.

> It not happened 100%,

Here it happened only twice within months.
Always in production, never on my testbed. :(

> 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.

Hmm, maybe systemd-machined did not cleanup everything upon
container exit.

Thanks,
//richard


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