Re: libvirt virsh define {vm_dumpxml.xml} does not work

On Mon, 9 Aug 2021 00:42:08 +0200 Peter Boy wrote: > In the process to migrate from CentOS 8 to Fedora I saved the > definition of various VMs using "virsh dumpxml vm_id > vm_id.xml“ > > According to the manual I can restore using "virsh define vm_id.xml“ > > But I get > Error: Can’t check Q

Re: Kernel Panic with Kernel 5.13.6-200

5.13.9 is now in koji you might give that a shot. 5.13.5 changelog shows commit c3eb534eae09de6cdd3e0ff63897b20e1b079cdb vmxnet3: fix cksum offload issues for tunnels with non-default udp ports 5.13.6 changelog shows several vmware related commits https://cdn.kernel.org/pub/linux/kernel/v5.x

Re: machine suspending

On Mon, Aug 9, 2021 at 10:53 AM George Avrunin wrote: > > Aug 06 17:47:32 ext.math.umass.edu kernel: Lockdown: systemd-logind: > hibernation is restricted; see man kernel_lockdown.7 > Aug 06 17:47:32 ext.math.umass.edu kernel: Lockdown: systemd-logind: > hibernation is restricted; see man kernel_l

machine suspending

My office workstation, a Dell Precision T1700 running Fedora 34 (mostly KDE when I'm at the machine), has been suspending itself after a power outage. This seems to be connected to a networking problem, but I don't really understand what's going on or where to look. It seems that the system tries

Re: module loading problem

Thank you for the hint.  The problem is that the vbox modules are being rebuilt on boot, despite the fact I've already built them. It's interesting that when I run /sbin/vboxconfig to rebuild the modules it tells me that the modules may need to be signed.  After it builds the modules it tries t

Re: module loading problem

On Sun, 8 Aug 2021 09:34:36 -0700 Paolo Galtieri wrote: > I even tried rebuilding both the virtual box and vmware modules from > source, resigned all the modules and rebooted and again only the > vmware modules are loaded.  The virtual box modules no longer show > they are signed. > > Can anybo

Kernel Panic with Kernel 5.13.6-200

Hi,     I am running F34 in a Vmware Player VM and have just done the first boot after installing the update that installed Kernel 5.13.6-200, which fails with a kernel panic saying it can't mount the root volume, but Kernel 5.13.4-200 boots quite happily. Is this a known issue? regards, Ste