Re: virsh undefine --nvram

2024-03-06 Thread Andrea Bolognani
On Tue, Mar 05, 2024 at 04:08:20PM -0500, Chuck Lever wrote: > Hello - > > The virsh(1) man page says: > > > --nvram and --keep-nvram specify accordingly to delete or keep nvram > > (/domain/os/nvram/) file. > > However on my Fedora 39 system with libvirt 9.7.0, using "virsh > undefine --nvram" op

Re: virsh undefine --nvram

2024-03-06 Thread Daniel P . Berrangé
On Wed, Mar 06, 2024 at 02:28:34AM -0800, Andrea Bolognani wrote: > On Tue, Mar 05, 2024 at 04:08:20PM -0500, Chuck Lever wrote: > > Hello - > > > > The virsh(1) man page says: > > > > > --nvram and --keep-nvram specify accordingly to delete or keep nvram > > > (/domain/os/nvram/) file. > > > > Ho

Re: virsh undefine --nvram

2024-03-06 Thread Richard W.M. Jones
On Wed, Mar 06, 2024 at 02:28:34AM -0800, Andrea Bolognani wrote: > On Tue, Mar 05, 2024 at 04:08:20PM -0500, Chuck Lever wrote: > > Hello - > > > > The virsh(1) man page says: > > > > > --nvram and --keep-nvram specify accordingly to delete or keep nvram > > > (/domain/os/nvram/) file. > > > > Ho

Error Cannot acquire state change lock from remoteDispatchDomainMigratePrepare3Params during live migration of domains

2024-03-06 Thread Christian Rohmann via Users
Hallo libvirt-users! we observe lock-ups / timeouts with in prometheus-libvirt-exporter (https://github.com/inovex/prometheus-libvirt-exporter) when libvirt is live-migrating domains: Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainMigratePrep