Re: backup-begin

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


(preferrably don't top-post on technical lists)

On Wed, Apr 05, 2023 at 07:44:21 +0200, André Malm wrote:
> The reason given is shut off (crashed).
> So something virsh backup-begin does is causing he guest to crash?

The backup operation is quite complex so it is possible.

Please have a look into /var/log/libvirt/qemu/$VMNAME.log to see whether
qemu logged something like an assertion failure before crashing.

Additionally you can have a look into 'coredumpctl' whether there are
any recorded crashes of 'qemu-system-x86_64' and also possibly collect
the backtrace.

Also make sure to try updating the qemu package and see whether the bug

If yes, please collect the stack/back-trace, versions of qemu and
libvirt, the contents of the VM log file and also ideally configure
libvirt for debug logging and collect the debug log as well:

> Den 2023-04-04 kl. 16:58, skrev Peter Krempa:
> > On Tue, Apr 04, 2023 at 16:28:18 +0200, André Malm wrote:
> > > Hello,
> > > 
> > > For some vms the virsh backup-begin sometimes shuts off the vm and returns
> > > "error: operation failed: domain is not running" although it was clearly in
> > > state running (or paused).
> > > 
> > > Is the idea that you should guest-fsfreeze-freeze / virsh suspend before
> > > virsh backup-begin? I have tried with both with the same results.
> > Freezing the guest filesystems is a good idea to increase the data
> > consistency of the backup, but is not necessary. Nor it should have any
> > influence on the lifecycle of the VM.
> > 
> > > What could be causing the machine to shut off?
> > The VM most likely crashed, or was turned off in a different way.
> > 
> > Try running
> > 
> >   virsh domstate --reason $VMNAME
> > 
> > to see what the reason for the current state is.
> > 

[Index of Archives]     [Virt Tools]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux