similar to: Feature request? Auto start vm upon next shutdown

It is not a destroy. With some hardware changes you require the host to shutdown down and then start. The shutdown down is manually given either via some acpi request or from within the guest. When the guest is down, the 'host' recognizes this guest requires a one time start, and starts it. This should 'solve' that if you change hardware you have to wait for the guest to

On Mon, Jun 22, 2020 at 04:48:32AM -0400, brent s. wrote: > On 6/22/20 03:47, Marc Roos wrote: > > > > > > It is not a destroy. With some hardware changes you require the host to > > shutdown down and then start. The shutdown down is manually given either > > via some acpi request or from within the guest. > > When the guest is down, the 'host'

[Please keed the list CCed] On 01/10/2018 04:43 PM, Raman Gupta wrote: >> Does this command alone succeed? > Yes. I have used this command to migrate VMs successfully, without even > knowing that spelling has changed. > > >> I don't know enough about systemd but maybe it's not waiting for virsh to > finish? > Yes I also think virsh or libvirtd or related

Nut-names.txt states that 1. ups.start.auto controls whether the UPS starts when mains is (re)applied. 2. shutdown.stayoff causes "turn off the load possibly after a delay and remain even if power returns". 3. shutdown.return causes "turn off the load possibly after a delay and return when power is back". 1 seems to conflict with 2 and 3. That is, 2

Hi, > I don't see your service being called. It started when system started, see logs: Jan 12 14:59:42 desktop4 systemd: systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN) Jan 12 14:59:42 desktop4 systemd: Detected architecture x86-64. Jan 12 14:59:42 desktop4

I have 4 hard drives on my system. CentOS is in a logical partition on the first hard drive and there is a swap partition in a logical partition on the first hard drive which I have also told it to use. The other three hard drives contain various partitions, all of which I have hidden from CentOS which are primary partitions. I have as well hidden the primary partitions on the first hard drive

Hi, I have CentOS 7, two node system which allows live VM migration between them. Live migration triggered from virsh is happily happening. I am using GlusterFS for replicating VM disk files. Now I want to automatically do the live migration at the time of reboot/shutdown/halt of the host node and for this I have written a systemd service unit [vPreShutdownHook.service] and placed the live

I have an Ellipse USBS connected via serial cable to a CentOS 3 box. Do I need to turn off the UPS as the final stage of shutdown, or will the UPS power itself off, before the battery reaches a level to low to safely recharge from? I notice there is the option for the UPS to turn itself off (and on again) unattended if power is restored during shutdown, but there doesn't seem to be an option

Here are some thoughts about a possible enhancement to samba. Let me know what yuou think. Whenever I want to re-start samba, for example to upgrade it, there always seem to be people logged in with files open. It occured to me therefore that an auto-restart feature may be useful. To implement this though we need to know when it is safe to re-start samba: 1. When there are no locked

The host server halts upon shutdown of 126000mb domU (64-bit SLES10). It booted fine and was able to run kernbench. However, during shutdown the host crashes. Host is Unisys ES7000 host with 32 processors and 128gb memory using x86_64 SLES10 with xen-unstable c/s 15080. Reducing the memory allocation for the domU to 124000mb works fine. My guess is that specifying 126000 does not leave

Is it possible to have a sieve script reply with a press message to certain emails (and only certain emails) based on sieve matches? I see a lot on vacation replies, but I want something more specific. Something along the lines of procmails formail command? Everything I?ve searched for is about vacation r filing replies into the same folder as the original message.

should have mentioned, apologies, suspend is the graceful shutdown of the guest I was thinking of. Guest is win2k8, why would it not suspend? On 22/10/14 10:58, lejeczek wrote: > hi everybody > > by an assumption I expected VM guests to be shut down/off > gracefully when the host is being powered down or > rebooted, but this does not seem to be the case so I wonder.. > Am I

Hello, I've installed & configured NUT 2.0.4 connected over a serial port to an MGE USBS 750. When the UPS enters the 'critical' state (ie, battery load below the defined battery.charge.low AND power input off), the UPS just shutdown itself instead of notifying NUT. When I say the UPS just shutdown, I mean it autonomously shut down itself within one second after reaching the

Hi, I'm trying to use OVMF to run EFI-partitioned Windows 8.0 virtualized on my laptop. The reason is to reuse the original HDD image intact without re-installation of any kind. I'm running fully updated CentOS 7.1 (1503). Virtualized storage subsystem is VirtIO if it matters. I'm almost OK with the notable exception of inability to reboot the VM. OVMF bootloader doesn't

hi everybody by an assumption I expected VM guests to be shut down/off gracefully when the host is being powered down or rebooted, but this does not seem to be the case so I wonder.. Am I missing some libvirt components/packages ? Or my assumption is incorrect and guests have to be shutdown manually? it's all SL 7 and guest are M$ regards P.

On Wed, Aug 26, 2020 at 10:35:22PM +0200, Milan Zamazal wrote: > Hi, > > we have a problem in oVirt that highly available VMs don't restart after > host poweroff because Vdsm identifies the case as a user initiated > shutdown (https://bugzilla.redhat.com/1800966). > > When poweroff is run on the host, libvirt-guests service takes an > action. If oVirt is initiating a

"Daniel P. Berrange" <dan@berrange.com> writes: > On Wed, Aug 26, 2020 at 10:35:22PM +0200, Milan Zamazal wrote: >> Hi, >> > >> we have a problem in oVirt that highly available VMs don't restart after >> host poweroff because Vdsm identifies the case as a user initiated >> shutdown (https://bugzilla.redhat.com/1800966). >> >>

Hello, I am unable to do a graceful shutdown or reboot of SLES 10 SP4 virtual machines (Kernel version: 2.6.16.60-0.85.1-default) with virsh shutdown or virsh reboot commands. (e.g virsh shutdown "vmname" ). On issuing these commands there is no impact on the VM. Also unable to perform the shutdown or reboot operations from the menu options available on the console when accessing the

My query? Is dovecot not getting this field automatically? -----Original Message----- Subject: Re: Dovecot proxy with ldap, complains about 'host not given' On 23 Nov 2019, at 16:11, Marc Roos <M.Roos at f1-outsourcing.eu> wrote: > It looks like the dovecot proxy can authenticate correctly but fails > then on with this message > > Nov 23 23:33:33 test2 dovecot:

I added this: passdb { driver = passwd skip = authenticated } Which enables indeed local delivery, I also noticed this. Maybe the password field check shoud not be done, when you enable skip authentication? Dec 16 10:26:37 svr1 dovecot: auth-worker(12046): Debug: passwd(test): lookup Dec 16 10:26:37 svr1 dovecot: auth-worker(12046): passwd(test): invalid password field '*'