search for: shutdown_timeout

...just two guest after which libvirt looks and when I shutdown those guests: $ virsh shutdown $_dom that domain takes little time to power down, as expected one would say(~20sec) But! I reboot the hosts and I have in my: /etc/sysconfig/libvirt-guests : ON_SHUTDOWN=shutdown PARALLEL_SHUTDOWN=1 SHUTDOWN_TIMEOUT=300 I see libvirtd service shut down takes minutes, a few good minutes to deal with guests shutdown(I suppose?) How could I dig into it and troubleshoot? Would you have any idea as why libvirtd shutdown takes that long? many thank, L.

...n. Please be careful with # this settings since there is no way to distinguish between a # guest which is stuck or ignores shutdown requests and a guest # which just needs a long time to shutdown. When setting # ON_SHUTDOWN=shutdown, you must also set SHUTDOWN_TIMEOUT to a # value suitable for your guests. ON_SHUTDOWN=shutdown # If set to non-zero, shutdown will suspend guests concurrently. Number of # guests on shutdown at any time will not exceed number set in this variable. #PARALLEL_SHUTDOWN=0 # Number of seconds we're willing to wait for a...

Hi Folks, been searching around for a while on this and see similar issues reported going back a number of years without solution. The START_DELAY=(number) seems to be completely ignored in /etc/sysconfig/libvirt-guests which is unfortunate as it means everything starts at once without control. This is fine on NVMe based servers however on the older spinning disks the I/O is creating

...Write more information. -V, --version Output version information and exit. -E, --vertical Print output vertically. Is similar to --relative, but prints output vertically. -w, --wait[=#] Wait and retry if connection is down. --connect_timeout=# --shutdown_timeout=# Variables (--variable-name=value) and boolean options {FALSE|TRUE} Value (after reading options) --------------------------------- ----------------------------- count 0 force FALSE compress FALSE character-sets-dir...

...n. Please be careful with # this settings since there is no way to distinguish between a # guest which is stuck or ignores shutdown requests and a guest # which just needs a long time to shutdown. When setting # ON_SHUTDOWN=shutdown, you must also set SHUTDOWN_TIMEOUT to a # value suitable for your guests. ON_SHUTDOWN=shutdown ===================================================== I changed "ON_SHUTDOWN" already from suspend to shutdown. I think this should be the same. Bernd Helmholtz Zentrum München Deutsches Forschungszentrum für Ge...

...just two guest after which libvirt looks and when I shutdown those guests: $ virsh shutdown $_dom that domain takes little time to power down, as expected one would say(~20sec) But! I reboot the hosts and I have in my: /etc/sysconfig/libvirt-guests : ON_SHUTDOWN=shutdown PARALLEL_SHUTDOWN=1 SHUTDOWN_TIMEOUT=300 I see libvirtd service shut down takes minutes, a few good minutes to deal with guests shutdown(I suppose?) How could I dig into it and troubleshoot? Would you have any idea as why libvirtd shutdown takes that long? many thank, L.

...this settings since there is no way to > distinguish between a > # guest which is stuck or ignores shutdown > requests and a guest > # which just needs a long time to shutdown. When setting > # ON_SHUTDOWN=shutdown, you must also set > SHUTDOWN_TIMEOUT to a > # value suitable for your guests. > ON_SHUTDOWN=shutdown > ===================================================== > > I changed "ON_SHUTDOWN" already from suspend to shutdown. I > think this should be the same. > > > Bernd > Hi, for the Ubu...

...ibvirt.org Process: 751 ExecStart=/usr/lib/libvirt/libvirt-guests.sh start (code=exited, status=0/SUCCESS) Main PID: 751 (code=exited, status=0/SUCCESS) ===== $ cat /etc/conf.d/libvirt-guests BYPASS_CACHE=0 CONNECT_RETRIES=10 ON_BOOT=start ON_SHUTDOWN=shutdown PARALLEL_SHUTDOWN=4 RETRIES_SLEEP=1 SHUTDOWN_TIMEOUT=300 START_DELAY=0 URIS=default ===== A virsh # shutdown <vmname> or an in-guest systemctl poweroff takes a few seconds (3-5?) ===== {{{ libvirt-guests.service is: }}} [Unit] Description=Suspend Active Libvirt Guests After=network.target libvirtd.service time-sync.target Documentation=man:libv...

Hi, i have a SLES 11 SP2 64bit host with three guests: - Windows XP 32 - Ubuntu 12.04 LTS 64bit - SLES 11 SP2 64bit The SLES guest shuts down with the host shutdown. The others not. When i shutdown these two guests with the virt-manager, they shutdown fine. ACPI is activated in virt-manager for both of them. Acpid is running in the Ubuntu Client. When the host shuts down, the two guests get a

...if (!strcmp(state, "reset_failed")) > + return MIC_RESET_FAILED; > + mpsslog("%s: BUG invalid state %s\n", mic->name, state); > + /* Invalid state */ > + assert(0); > +}; > + > +static void mic_handle_shutdown(struct mic_info *mic) > +{ > +#define SHUTDOWN_TIMEOUT 60 > + int i = SHUTDOWN_TIMEOUT, ret, stat = 0; > + char *shutdown_status; > + while (i) { > + shutdown_status = readsysfs(mic->name, "shutdown_status"); > + if (!shutdown_status) > + continue; > + mpsslog("%s: %s %d shutdown_status %s\n", > + m...

...if (!strcmp(state, "reset_failed")) > + return MIC_RESET_FAILED; > + mpsslog("%s: BUG invalid state %s\n", mic->name, state); > + /* Invalid state */ > + assert(0); > +}; > + > +static void mic_handle_shutdown(struct mic_info *mic) > +{ > +#define SHUTDOWN_TIMEOUT 60 > + int i = SHUTDOWN_TIMEOUT, ret, stat = 0; > + char *shutdown_status; > + while (i) { > + shutdown_status = readsysfs(mic->name, "shutdown_status"); > + if (!shutdown_status) > + continue; > + mpsslog("%s: %s %d shutdown_status %s\n", > + m...

...g_down")) + return MIC_SHUTTING_DOWN; + if (!strcmp(state, "reset_failed")) + return MIC_RESET_FAILED; + mpsslog("%s: BUG invalid state %s\n", mic->name, state); + /* Invalid state */ + assert(0); +}; + +static void mic_handle_shutdown(struct mic_info *mic) +{ +#define SHUTDOWN_TIMEOUT 60 + int i = SHUTDOWN_TIMEOUT, ret, stat = 0; + char *shutdown_status; + while (i) { + shutdown_status = readsysfs(mic->name, "shutdown_status"); + if (!shutdown_status) + continue; + mpsslog("%s: %s %d shutdown_status %s\n", + mic->name, __func__, __LINE__, shutdow...

ChangeLog: ========= v1 => v2: a) License wording cleanup, sysfs ABI documentation, patch 1 refactoring into 3 smaller patches and function renames, as per feedback from Greg Kroah-Hartman. b) Use VRINGH infrastructure for accessing virtio rings from the host in patch 5, as per feedback from Michael S. Tsirkin. v1: Initial post @ https://lkml.org/lkml/2013/7/24/810 Description:

ChangeLog: ========= v1 => v2: a) License wording cleanup, sysfs ABI documentation, patch 1 refactoring into 3 smaller patches and function renames, as per feedback from Greg Kroah-Hartman. b) Use VRINGH infrastructure for accessing virtio rings from the host in patch 5, as per feedback from Michael S. Tsirkin. v1: Initial post @ https://lkml.org/lkml/2013/7/24/810 Description:

ChangeLog: ========= v2 => v3: a) Patch 1 data structure cleanups, header file include cleanups, IDA interface reuse and switching to device_create_with_groups(..) as per feedback from Greg Kroah-Hartman. b) Patch 7 signal documentation, sleep workaround removal and sysfs access API cleanups as per feedback from Michael S. Tsirkin. v1 => v2: @ http://lwn.net/Articles/563131/ a)

ChangeLog: ========= v2 => v3: a) Patch 1 data structure cleanups, header file include cleanups, IDA interface reuse and switching to device_create_with_groups(..) as per feedback from Greg Kroah-Hartman. b) Patch 7 signal documentation, sleep workaround removal and sysfs access API cleanups as per feedback from Michael S. Tsirkin. v1 => v2: @ http://lwn.net/Articles/563131/ a)

ChangeLog: ========= v2 => v3: a) Patch 1 data structure cleanups, header file include cleanups, IDA interface reuse and switching to device_create_with_groups(..) as per feedback from Greg Kroah-Hartman. b) Patch 7 signal documentation, sleep workaround removal and sysfs access API cleanups as per feedback from Michael S. Tsirkin. v1 => v2: @ http://lwn.net/Articles/563131/ a)

ChangeLog: ========= v2 => v3: a) Patch 1 data structure cleanups, header file include cleanups, IDA interface reuse and switching to device_create_with_groups(..) as per feedback from Greg Kroah-Hartman. b) Patch 7 signal documentation, sleep workaround removal and sysfs access API cleanups as per feedback from Michael S. Tsirkin. v1 => v2: @ http://lwn.net/Articles/563131/ a)

An Intel MIC X100 device is a PCIe form factor add-in coprocessor card based on the Intel Many Integrated Core (MIC) architecture that runs a Linux OS. It is a PCIe endpoint in a platform and therefore implements the three required standard address spaces i.e. configuration, memory and I/O. The host OS loads a device driver as is typical for PCIe devices. The card itself runs a bootstrap after

An Intel MIC X100 device is a PCIe form factor add-in coprocessor card based on the Intel Many Integrated Core (MIC) architecture that runs a Linux OS. It is a PCIe endpoint in a platform and therefore implements the three required standard address spaces i.e. configuration, memory and I/O. The host OS loads a device driver as is typical for PCIe devices. The card itself runs a bootstrap after