Displaying 3 results from an estimated 3 matches for "vir_domain_running_boot".
Did you mean:
vir_domain_running_booted
2011 Nov 17
1
Ruby libvirt gem: state reasons
Does anyone know of a way to use the Ruby bindings to find out
the 'reason' value for the state of the VM? Such as obtaining
VIR_DOMAIN_RUNNING_BOOTED for a running domain?
--
#ken B-)}
Ken Coar, Sanagendamgagwedweinini
IT Engineering Tower, Red Hat/RDU
"Millennium hand and shrimp!"
2013 Jul 15
0
Re: libvrtd-1.1.0 crashes when attempting to start some (but not all) LXC containers
...imized out>
generated = false
__FUNCTION__ = "virSecurityManagerGenLabel"
__func__ = "virSecurityManagerGenLabel"
#2 0x00007fe46aa92979 in virLXCProcessStart (conn=0x7fe460000a80,
driver=0x7fe4640bd340, vm=0x7fe4640c1610, autoDestroy=false,
reason=VIR_DOMAIN_RUNNING_BOOTED) at lxc/lxc_process.c:1144
rc = -1
r = <optimized out>
nttyFDs = 1
ttyFDs = 0x7fe458001790
i = <optimized out>
logfile = 0x7fe458000ad0 "/var/log/libvirt/lxc/dwj-hfax-dev.log"
logfd = -1
nveths = 0
veths...
2013 Jul 15
3
Re: libvrtd-1.1.0 crashes when attempting to start some (but not all) LXC containers
On Mon, Jul 15, 2013 at 3:18 AM, Michal Privoznik <mprivozn@redhat.com>wrote:
>
> Interesting. If you are still able to reproduce the crash, can you try to
> get the line number within virSecurityManagerGenLabel where the crash
> happened? I think it's the STREQ line (440 linenr). Question is whether
> model or name is NULL.
>
>
I'll try.
I'm not sure why