How do I use device tree overlays on Fedora (since there
is no "cape manager") ?
I assume I have to modify extlinux.conf to boot with a new device tree
file. Is there a way to use "dtc" to merge the am335x-boneblack.dts
file and the overlay file ?
FYI, the reason I ask this question is that I'm interested in CANbus.
I noticed that Fedora has CANbus drivers now. Great. I have a
BeagleBone Black (with Fedora 23 on a SD card) and a "Serial Cape"
from LogicSupply : http://www.logicsupply.com/cbb-serial/ . There are
device tree "overlay" files to enable this :
https://github.com/lgxlogic/CBB-Serial/tree/master/overlay
Hi,
I've got a Wandboard Quad running Fedora 22 (current as of yesterday).
This box is a MythTV backend. It's also running an NFS server to serve
the 2 TB Sata drive connected to store my recordings.
I noticed that the nfs server processes are spinning, even when there
are no clients attached. Here's an output from top:
top - 16:19:30 up 23:36, 1 user, load average: 2.79, 2.75, 2.66
Tasks: 118 total, 5 running, 113 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.3 us, 38.5 sy, 0.0 ni, 40.7 id, 0.0 wa, 0.0 hi, 20.6 si, 0.0 st
KiB Mem : 2064876 total, 62132 free, 73572 used, 1929172 buff/cache
KiB Swap: 249852 total, 249432 free, 420 used. 1935800 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1024 root 20 0 0 0 0 R 77.6 0.0 1154:25 nfsd
1023 root 20 0 0 0 0 R 76.6 0.0 1150:27 nfsd
3 root 20 0 0 0 0 R 47.4 0.0 602:37.59 ksoftirqd/0
60 root 20 0 0 0 0 R 13.8 0.0 36:23.26 kswapd0
981 root 20 0 356948 29000 18440 S 4.6 1.4 158:47.23 mythbackend
13 root 20 0 0 0 0 S 1.0 0.0 10:25.97 ksoftirqd/1
18 root 20 0 0 0 0 S 1.0 0.0 9:19.12 ksoftirqd/2
8556 root 20 0 8908 3556 3060 R 1.0 0.2 0:00.16 top
Any idea why NFS is spinning like this? I haven't noticed this on my
x86-based Fedora servers.
-derek
--
Derek Atkins 617-623-3745
derek(a)ihtfp.com www.ihtfp.com
Computer and Internet Security Consultant
I've been trying to get a 32 bit Fedora/armv7hl guest to boot on a
64 bit Fedora/aarch64 host.
Host: Fedora Rawhide, aarch64 on Mustang
Guest: Fedora 22 disk image from:
$ virt-builder --arch armv7l fedora-22
I should say that:
(1) I can boot this guest using an external <kernel> and <initrd> and
some hand written libvirt XML. However external kernel is not very
flexible, since it means you have to do a dance on the host each time
you update the guest.
(2) I can boot this guest on x86-64 host using external kernel.
(3) It doesn't boot with UEFI in the guest, but that is expected since
the guest doesn't contain a UEFI bootloader, and I'm not even sure if
there is such a thing as UEFI for 32 bit ARM.
Anyway, I attempted to boot this disk image without the external
kernel hack using:
$ virt-install --arch armv7l --import --name test3 --ram 2048 --disk path=/var/tmp/test3.qcow2,format=qcow2 --os-variant fedora22
but it just hangs with a blank console, and with qemu-system-aarch64 [sic]
using 100% CPU. I poked around inside the disk image, and there seems
to be no evidence that it booted, eg. no logs, no updated timestamps.
Should I try a newer guest? I am going to try updating to Fedora 23.
Is it even possible to boot a 32 bit disk image without external
kernel?
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html