similar to: Reboot, halt, poweroff called inside an lxc domain

HI, everyone: My target deal with network hotplug use virDomainDetachDeviceFlags. Because when the API return ,the network maybe doesn’t remove from my vm guest os. So I use virConnectDomainEventRegisterAny to register an event ID: VIR_DOMAIN_EVENT_ID_DEVICE_REMOVED , my process as follow:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 21.08.2013 12:58, Alexandr пишет: > 21.08.2013 12:39, Daniel P. Berrange пишет: >> On Wed, Aug 21, 2013 at 12:36:06PM +0300, Alexandr wrote: >>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >>> >>> 21.08.2013 09:46, Alexandr пишет: >>>> 21.08.2013 09:32, Martin Kletzander пишет: >>>>> On

On Wed, Aug 21, 2013 at 12:36:06PM +0300, Alexandr wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > 21.08.2013 09:46, Alexandr пишет: > > 21.08.2013 09:32, Martin Kletzander пишет: > >> On Wed 21 Aug 2013 01:03:37 AM CEST, Alexandr wrote: > >>> > >>> good day. i trying to make callback function for > >>>

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 21.08.2013 09:32, Martin Kletzander пишет: > On Wed 21 Aug 2013 01:03:37 AM CEST, Alexandr wrote: >> >> good day. i trying to make callback function for >> VIR_DOMAIN_EVENT_ID_LIFECYCLE, i have successfully registering >> callback, but it never called, i need to know when domain >> started, stopped or crashed, i have

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 good day. i trying to make callback function for VIR_DOMAIN_EVENT_ID_LIFECYCLE, i have successfully registering callback, but it never called, i need to know when domain started, stopped or crashed, i have write following code static int domain_event_handler(virConnectPtr conn, virDomainPtr dom, int event, int detail, void * opaque) {

Hi buddy, I wanna to monitor a domain's life cycle event, so i register a event an a virConnectDomainEventCallback, the code segment is as below: ------------------------ int DomainEventCallback(virConnectPtr conn, virDomainPtr dom, int event, int detail, void * opaque){ /*My code */ ....... } int main(){ /* .....*/ virDomainPtr dom =

good day to all. i still have not solved my problem with event handling. currently i have following code void libvirt_eventloop_thr_func() { while(true) //TODO: stop somehow on exit { if(virEventRunDefaultImpl() < 0) { virErrorPtr err = virGetLastError(); fprintf(stderr, "Failed to run event loop: %s\n", err && err->message ? err->message : "Unknown

I just noticed that CentOS (6.2) by default allows any user to reboot/poweroff system without any admin rights, or without any further questions, if using commands 'reboot' or 'poweroff'. But 'shutdown' still requires admin rights. What is the preferred way to restrict any regular user from rebooting / powering off the system (by accident)? IMHO, sudo should be

On Sun, 12 Feb 2023 at 00:43, Chris Clayton <chris2553 at googlemail.com> wrote: > > > > On 10/02/2023 19:33, Linux regression tracking (Thorsten Leemhuis) wrote: > > On 10.02.23 20:01, Karol Herbst wrote: > >> On Fri, Feb 10, 2023 at 7:35 PM Linux regression tracking (Thorsten > >> Leemhuis) <regressions at leemhuis.info> wrote: > >>>

On Tue, 31 Jan 2023 at 09:09, Chris Clayton <chris2553 at googlemail.com> wrote: > > Hi again. > > On 30/01/2023 20:19, Chris Clayton wrote: > > Thanks, Ben. > > <snip> > > >> Hey, > >> > >> This is a complete shot-in-the-dark, as I don't see this behaviour on > >> *any* of my boards. Could you try the attached patch

Michal Privoznik писал 2013-10-14 08:48: > On 14.10.2013 02:42, Alexandr wrote: >> good day to all. >> i still have not solved my problem with event handling. >> currently i have following code >> >> >> void libvirt_eventloop_thr_func() >> { >> while(true) //TODO: stop somehow on exit >> { >>

On Sat, Feb 18, 2023 at 1:22 PM Chris Clayton <chris2553 at googlemail.com> wrote: > > > > On 15/02/2023 11:09, Karol Herbst wrote: > > On Wed, Feb 15, 2023 at 11:36 AM Linux regression tracking #update > > (Thorsten Leemhuis) <regressions at leemhuis.info> wrote: > >> > >> On 13.02.23 10:14, Chris Clayton wrote: > >>> On 13/02/2023

On Sun, 19 Feb 2023 at 04:55, Chris Clayton <chris2553 at googlemail.com> wrote: > > > > On 18/02/2023 15:19, Chris Clayton wrote: > > > > > > On 18/02/2023 12:25, Karol Herbst wrote: > >> On Sat, Feb 18, 2023 at 1:22 PM Chris Clayton <chris2553 at googlemail.com> wrote: > >>> > >>> > >>> > >>> On

Hi, I've been making some tests with libvirt and LXC and found some problems when halting/restarting a LXC container from within. Basically, on a Ubuntu 12.04 system with libvirt installed as package (0.9.8), I've created a basic container image with: lxc-create -t ubuntu -n lxc And started it using the libvirt XML listed below and the following command: virsh -c lxc:// create

[adding various lists and the two other nouveau maintainers to the list of recipients] For the rest of this mail: [TLDR: I'm adding this report to the list of tracked Linux kernel regressions; the text you find below is based on a few templates paragraphs you might have encountered already in similar form. See link in footer if these mails annoy you.] On 18.01.23 21:59, Chris Clayton wrote:

Hi , Is there anyway to get uuid info inside a lxc container which is created by libvirt_lxc? For kvm, we can use dmidecode or lshw to get this info inside vm. Is there any tools to do this thing for libvirt lxc? Thanks for any help~ -- ------------ Jackie Best Regards

On 07/24/2013 10:28 AM, hzguanqiang wrote: > On 2013-07-23 18:14, "Daniel P. Berrange" <berrange@redhat.com> wrote: > >>> On Tue, Jul 23, 2013 at 04:56:30PM +0800, hzguanqiang wrote: >>> Hi Guys, >>> When I created a lxc container by libvirt, I logged into the lxc >>> container and noticed that info under /proc/ dir did not match the

Michal Privoznik писал 2013-10-14 11:39: > On 14.10.2013 10:33, Alexandr wrote: >> Michal Privoznik писал 2013-10-14 08:48: >>> On 14.10.2013 02:42, Alexandr wrote: >>>> good day to all. >>>> i still have not solved my problem with event handling. >>>> currently i have following code >>>> >>>> >>>> void

On Tue, Jul 23, 2013 at 04:56:30PM +0800, hzguanqiang wrote: > Hi Guys, > When I created a lxc container by libvirt, I logged into the lxc > container and noticed that info under /proc/ dir did not match the > lxc container resource. Is the /proc dir in lxc container just > showing the same thing as the lxc host? If I want to monitor the > realtime resource usage inside the lxc

Hi Guys, When I created a lxc container by libvirt, I logged into the lxc container and noticed that info under /proc/ dir did not match the lxc container resource. Is the /proc dir in lxc container just showing the same thing as the lxc host? If I want to monitor the realtime resource usage inside the lxc container, What should I do? -------------- Best regards! GuanQiang 2013-07-23