So... I did a "sudo dnf upgrade" and things seemed to do well.
However, when I rebooted, it hangs on bootup with the statment "Holding
until bootup processes complete" or something like that -- I'm doing
this from memory. I tried with a couple of older kernels, but they also
I assume that this is some transient thing associated with the upgrade.
Over the years, I've had glitches appear on an upgrade and disappear on
the next upgrade. Accordingly, I'd like to boot into rescue mode and
see if I can upgrade again.
However, I've forgotten how to turn on wifi networking from rescue mode.
Can anybody point me to a tutorial?
Ever since Fedora(27) released a 4.17.x kernel, my MacBook Air (7,1)
is no longer able to boot at all. It hangs when trying to use the
NVMe disk controller:
nvme nvme0: controller is down; will reset: CSTS=0x3, PCI_STATUS=0x810
and the entire boot process eventually times out completely. If I
return to using the last 4.16.x kernel (4.16.14-200.fc27.x86_64), then
the problem does *not* reproduce, and everything boots normally.
i opened a bug for this problem:
however, I'm surprised that no one else has run into this issue. Any
ideas or suggestions?
Using Boxes, I installed a Windows 10 guest. I installed the spice drivers from spice-space.org/download (https://www.spice-space.org/download/windows/spice-guest-tools/spice-gues...)
and things look good.
However, when the guest is idle, cpu is 0-4% the host process is significantly higher (28.7% for example below). I'm looking for advice on how to figure out what the problem is. The only thing I did so far is switch the disk bus from ide to virtio, and that didn't help.
I have an XPS 13 with plenty of ram and SSD disk space - i5 processor, running Fedora 28, 4.17.7-200.fc28.x86_64
Here's some output from top:
top - 07:13:02 up 12:49, 1 user, load average: 1.10, 1.84, 1.76
Tasks: 272 total, 1 running, 204 sleeping, 0 stopped, 0 zombie
%Cpu0 : 4.7 us, 2.7 sy, 0.0 ni, 91.6 id, 0.0 wa, 0.7 hi, 0.3 si, 0.0 st
%Cpu1 : 3.0 us, 4.4 sy, 0.0 ni, 92.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu2 : 4.3 us, 4.6 sy, 0.0 ni, 90.4 id, 0.0 wa, 0.3 hi, 0.3 si, 0.0 st
%Cpu3 : 3.3 us, 5.0 sy, 0.0 ni, 91.7 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem : 16144924 total, 272940 free, 5217992 used, 10653992 buff/cache
KiB Swap: 8224764 total, 8087004 free, 137760 used. 10409752 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
27942 ericp 20 0 3886324 2.130g 26340 S 28.7 13.8 27:26.31 qemu-system-x86
Reading other items online I used perf to see what is going on:
$ sudo perf kvm --host stat live
Analyze events for all VMs, all VCPUs:
VM-EXIT Samples Samples% Time% Min Time Max Time Avg time
IO_INSTRUCTION 493 56.93% 67.91% 2.91us 99913.26us 4255.31us ( +- 17.70% )
APIC_ACCESS 237 27.37% 7.71% 0.56us 99775.52us 1004.83us ( +- 51.23% )
HLT 106 12.24% 23.89% 0.59us 99841.70us 6961.72us ( +- 22.82% )
EXTERNAL_INTERRUPT 19 2.19% 0.00% 1.52us 5.56us 2.62us ( +- 9.42% )
EPT_MISCONFIG 6 0.69% 0.49% 28.66us 14837.17us 2506.17us ( +- 98.41% )
PENDING_INTERRUPT 3 0.35% 0.00% 0.74us 4.78us 2.91us ( +- 40.38% )
TPR_BELOW_THRESHOLD 2 0.23% 0.00% 4.21us 4.28us 4.24us ( +- 0.84% )
Total Samples:866, Total events handled time:3089057.95us.
Lots of IO and APIC.
I was hoping the virtio bus change would take care of the high IO_INSTRUCTIONs, but it didn't.
I changed the windows powercfg to be "high performance," but that didn't reduce the APIC calls.
Here's another perf:
$ sudo perf stat -e 'kvm:*' -a -- sleep 1
Performance counter stats for 'system wide':
Lots of fpu ?!?!? Lots of userspace exit. Lots of userspace, and looking at the top, the processors are doing an equal amount of usr and sys. I figure something is constantly doing system calls, causing lots of context switching.
I did "ps -Alf" to get the command line it creates. Hopefully this helps. I can provide the boxes config file if that's easier.
Any suggestions on what to do?
At one point Fedora had something (keyring?) that would allow me to
unlock my SSH private keys and it would keep the unlocked key available
so I could ssh without having to unlock my key every time. I typically
run a simple "terminal" window and then "ssh <hostname>" since my key is
not retained unlocked I'm prompted for a password.
Fast forward to today, the system had been reinstalled (new hardware,
new disks, etc) and I no longer have that ability. I'm currently runn
Fedora 28 and the desktop is "Gnome", I'm sure it is just a matter of
installing/configuring/running the correct application.... but which one?
I get *Failed to start Load Kernel Modules* during the boot.
Everytime Kernel is updated VirtualBox modules fail I have to reboot into
the new Kernel, run the following commands and then it starts working.
$ sudo akmods --force
$ sudo dracut -v -f
$ sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
Then everything starts working again and the boot error goes away. You can
found the background of the issue in the link below.
My question is how can I automate this task.
I have two computers, Fedora 27 and 28 that do not mount the nfs server
at boot. It works from root afterward without any difficulty but that is
a bit of an inconvenience. I put up with that problem with the Samba
server for a long time but two is too much!
This problem was unknown until I built this nfs box which pretty much
says I've done something wrong but I have no idea what ... /etc/exports is:
[bobg@ASRock-J3455M ~]$ cat /etc/exports
The client /etc/fstab is:
192.168.1.86:/home/exports /mnt/testb nfs4 defaults 0 0
Any suggestions appreciated,
Bob Goodwin - Zuni, Virginia, USA
box10 FEDORA-27/64bit LINUX XFCE Fastmail POP3
I've just upgraded my TP X230i from F27 to F28 painless.
But I'm still on my last F27 kernel-4.16.16-200.fc27.i686+PAE.
No newer kernel installed.
During ame upgrade procedure on my TP x121e kernel was updated to
Both systems are 32bit. What could prevent update to a newer kernel?
I have computer which I have upgraded every six month or so from 26
September 2014, starting with Fedora 20. I want to do a fresh
installation of Fedora. I have a 3 Tbyte disk with two partitions, 500
Mbyte for /boot and the rest is one physical volume which is divided in
three logical volume /, /home and /data. I want to reuse the old /boot
for a new one and also reuse / while preserve /home and /data.
Is this doable without lot of work?
I have several large tar balls
-rwxr-xr-x. 1 todd users 6359558528 Jul 12 10:51
I have to deal with. They only extract (t or x) with the
command line "tar" command and crash both file-roller
and xarchive manager.
Anyone have a favorite GUI tar ball reader that will work with