search for: on_shutdown

...all running guests are asked to shutdown. 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 Zentr...

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

Hey there, Has anyone tackled the best way to shut down a VM running Win10 running in RedHat's (CentOS 7) KVM/QEMU VM manager? I'm looking at this link to follow:

hi guys I have 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.

...rectory: ''/dev/0'' my config file looks like this: name = "solaris" memory = "400" kernel = "/solaris/platform/i86xen/kernel/amd64/unix" extra = "/platform/i86xen/kernel/amd64/unix" ramdisk = "/solaris/platform/i86pc/boot_archive" on_shutdown = "destroy" on_reboot = "restart" on_crash = "destroy" root = "/dev/dsk/c0d0s0" disk = [''file:/solaris/root.file,0,w''] vif = [''ip=10.12.1.90'']

...nix-81" ramdisk = "/usr/lib/xen-solaris/x86.miniroot-81" extra = "/platform/i86xpv/kernel/amd64/unix - nowin -B install_media=cdrom" disk = [''file:/usr/lib/xen-solaris/snv81.iso,6:cdrom,r'',''phy:/dev/sda8,0,w''] vif = [''''] on_shutdown = "destroy" on_reboot = "destroy" on_crash = "destroy" ********************************** Run time profile (per MRJ) : ********************************** name = "Solaris81PVM" vcpus = 1 memory = "1024" bootloader = "/usr/bin/pygrub" kernel...

...#39;'512'' disk = [''phy:/dev/sdb1,0,w'' ] vif = [ '''' ] kernel = ''/home/oshman/solaris/unix-66-0624-nd'' ramdisk = ''/home/oshman/solaris/x86.miniroot-66-0624-nd'' extra = ''/platform/i86xpv/kernel/unix'' on_shutdown = "destroy" on_reboot = "destroy" on_crash = "preserve" When it boots up I see: Searching for installed OS instances... ROOT/opensolaris was found on rpool. Do you wish to have it mounted read-write on /a? [y,n,?] y mounting rpool on /a cannot mount ''rpool/...

...all running guests are asked to shutdown. 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 # Numb...

...; ramdisk = "/usr/lib/xen-solaris/x86.miniroot-85" extra = "/platform/i86xpv/kernel/amd64/unix - nowin -B install_media=cdrom" disk = [''file:/usr/lib/xen-solaris/snv85.iso,6:cdrom,r'',''phy:/dev/sdb7,0,w''] vif = [''bridge=eth2''] on_shutdown = "destroy" on_reboot = "destroy" on_crash = "destroy" # xm create -c snv85.install Using config file "./snv85.install". Started domain Solaris85pvm v3.2.1-rc1-pre chgset ''Wed Mar 05 16:49:33 2008 +0000 16805:28e0d4a37bb4...

On 06/11/2017 07:00 AM, Larry Fahnoe wrote: > Hi Ben, > > On RHEL/CentOS 7, libvirt-guests (which comes from libvirt-client) on the host controls the suspend vs. shutdown behavior of the guests. By default the guests suspend, but if you want them to shutdown, change the ON_SHUTDOWN setting in /etc/sysconfig/libvirt-guests. I don't have any Windows guests, but the linux guests work nicely with the default suspend. That said, I have only recently begun to see an issue with one of my CentOS7 guests being resumed with incorrect time--haven't gotten to the bottom of that...

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

...;' root = ''/dev/xvda ro'' name = "centos" memory = "512" disk = [ ''phy:/dev/vms/centos_data,xvda,w'', ''phy:/dev/vms/centos_swap,xvdb,w'',] vif = [ ''mac=00:64:18:20:52:07, bridge=xenbr0'', ] vcpus = 1 on_shutdown = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' For vmlinuz I tried a copy of Dom0''s kernel, the kernel copied from inside the DomU as well as the downloaded kernel file from here: http://mirrors.kernel.org/centos/5/os/i38...

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

...lly. After installation, I am using the following syntax from a python file to start up the domU: # cat solhvm.py name = "solhvm" vcpus = 1 memory = "768" root = "/dev/dsk/c0d0s0" disk = [''file:/solhvm/solhvm.img,0,w''] vif = [ '''' ] on_shutdown = ''destroy'' on_reboot = ''restart'' on_crash = ''destroy'' # xm new -f solhvm.py Using config file "./solhvm.py". # virsh start solhvm Domain solhvm started # virsh console solhvm v3.1.2-xvm chgset ''Mon Mar 03 23:05:33 2008 -080...

...#39;file:/Application/xen/images/opensolaris_2008_11.disk,0,w'' ] kernel = ''/boot/osol/kernel.opensolaris'' ramdisk = ''/boot/osol/ramdisk.opensolaris'' extra = ''/platform/i86xpv/kernel/unix -B zfs-bootfs=rpool/54,bootpath=/xpvd/xdf@0:a'' on_shutdown = ''destroy'' on_reboot = ''destroy'' on_crash = ''destroy'' When I do that, I get an error message like this. Unable to find number for device (0) Can someone please help me debug this problem? Thanks, Viswanath This e-mail and any files tran...

Hi -- I''m getting this error even though I have correct DVD ISO image for snv_92. bash-3.2# uname -a SunOS stoakly2 5.11 snv_92 i86pc i386 i86xpv bash-3.2# xm create snv.py Using config file "./snv.py". Error: (2, ''Invalid kernel'', ''elf_xen_note_check: ERROR: Will only load images built for the generic loader or Linux images'') bash-3.2#

Hi Ben, On RHEL/CentOS 7, libvirt-guests (which comes from libvirt-client) on the host controls the suspend vs. shutdown behavior of the guests. By default the guests suspend, but if you want them to shutdown, change the ON_SHUTDOWN setting in /etc/sysconfig/libvirt-guests. I don't have any Windows guests, but the linux guests work nicely with the default suspend. That said, I have only recently begun to see an issue with one of my CentOS7 guests being resumed with incorrect time--haven't gotten to the bottom of that...

hi guys I have 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.

...= 300 name = "src-fc-01" vif = [ ''type=ioemu, mac=00:16:3E:34:BB:51, bridge=virbr0'' ] disk = [''file:/store/xen/images/fedora/fedora.fc8.img,sda1,w'', ''file://store/xen/images/fedora/fedora.swap,sda2,w''] root = "/dev/sda1 ro" on_shutdown = "destroy" on_reboot = "destroy" on_crash = "destroy" vnc=1 vncconsole=0 /boot/vmlinux.2.6.18-xenU_x86 was built from the xen distribution I built for my dom0 using the KERNELS= parameter. Please help! -Asim _______________________________________________ Xen-user...

...tm) the config file for the Solaris DomU is name = "solaris-install" memory = "1024" disk = [ ''file:/ws/public/isos/65-0604-nd.iso,6:cdrom,r'', ''file:/export/root/solaris_domu/disk.img,0,w'' ] vif = [ ''mac=00:0e:0c:3e:18:cd'' ] on_shutdown = ''destroy'' on_reboot = ''destroy'' on_crash = ''destroy'' In this file only the ISO image is configured - not the kernel or ramdisk to use. When I try this config file for a Live CD with Linux it does not work, e.g. bash-3.00# cat test.cfg nam...