search for: 2097152l

Displaying 3 results from an estimated 3 matches for "2097152l".

Did you mean: 2097152
2019 Jan 22
0
Re: libvirt 5.0.0 - LXC container still in "virsh list" output after shutdown
...correct domain pointer: (Pdb) self.domain.__dict__ {'_conn': <libvirt.virConnect object at 0x7ff95f881550>, '_o': <capsule object "virDomainPtr" at 0x7ff95f8cca80>} Compare with case just after libvirtd restart and domain stopped: (Pdb) self.domain.info() [5, 2097152L, 2097152L, 2, 0L] Problem reproduced on 2 nodes for lxc. Qemu container on same nodes shutdown correct. b.r. Maxim Kozin
2019 Jan 21
2
libvirt 5.0.0 - LXC container still in "virsh list" output after shutdown
Hello. Centos 7.6 with libvirt build from base "virt" repository: libvirt-daemon-driver-lxc-5.0.0-1.el7.x86_64 libvirt-client-5.0.0-1.el7.x86_64 libvirt-daemon-5.0.0-1.el7.x86_64 libvirt-daemon-driver-network-5.0.0-1.el7.x86_64 libvirt-libs-5.0.0-1.el7.x86_64 + systemd-219-62.el7_6.2.x86_64 Now lxc containers with type='direct' can be started, but can't be stopped :)
2012 Jul 17
1
Bug#681213: Full logs?
Hi Orazio, Is "NoneType object is unsubscriptable" the full and complete error message? I'd have expected some sort of accompanying backtrace, if not on the console then in /var/log/xen/* Is this issue by any chance fixed by installing the xen-qemu-dm-4.0 package? Lastly, does this happen with the packages from Wheezy? Thanks, Ian.