I tried to set up an aarch64 vm, and not really wanting to set up boot server and such. I just ran.
--name Fedora_25_AArch64 --ram 2048 --arch aarch64 \
--disk size=8 --os-variant fedora25 \
It almost worked. I already had qemu-kvm set up for a windows partition for my vehicle obdII software probably with group install virtualization, then I installed qemu-system-arm and qemu-system-aarch64 along with edk2-aarch64 libguestfs-tools-c
It bombed out at (I have the full install log including the backtrace but I didn't want to spam the list with it.) It appeared to be going okay for a while. It is using the 4.8.6-300 kernel, is there an SMP bug in it? Or any suggestions?
Downloading 302 RPMs, 194.8 MiB / 194.8 MiB (100%) done.
Preparing transaction from installation source
[ 3151.714055] Internal error: Oops - BUG: 0 [#1] SMP
[ 3151.717402] Modules linked in: vfat fat fcoe libfcoe libfc scsi_transport_fc zram crc32_arm64 ghash_ce mtd chipreg qemu_fw_cfg loop virtio_scsi virtio_console virtio_net gpio_keys virtio_mmio virtio_ring virtio sunrpc xts lrw gf128mul dm_crypt dm_round_robin linear raid10 raid456 async_raid6_recov async_memcpy libcrc32c async_pq async_xor xor async_tx raid6_pq raid1 raid0 scsi_dh_rdac scsi_dh_hp_sw scsi_dh_emc scsi_dh_alua iscsi_tcp libiscsi_tcp libiscsi squashfs cramfs scsi_transport_iscsi dm_multipath
[ 3151.724909] CPU: 0 PID: 1228 Comm: loop0 Tainted: P 4.8.6-300.fc25.aarch64 #1
[ 3151.749929] Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015
On 02/16/2017 10:36 AM, Christopher Covington wrote:
> Hi Peter, Paul, Laura,
> Feel free to drop the QDF2432 system register access erratum workaround
> patch at this point. Thanks for carrying it as long as you have. It has
> enabled additional testing and development that would have been much more
> difficult otherwise.
Thanks :) For everything.
Computer Architect | Sent from my Fedora powered laptop
I'm not going to reply to all the threads so I'll just cover off here.
It looks like (with a few days of testing) that I've managed to fix
the stability issues seen on 4.9 on the Raspberry Pi 3. There is now a
kernel-4.9.8-201.fc25 in updates-testing (maybe still on it's way to
mirrors) that has been stable for me on a RPI3 running Workstation for
a few days without issue.
To test this you need to run:
"dnf upgrade --enablerepo=updates-testing --refresh kernel*"
If it works please provide karma on the update  if your still see
the lock up issue please provide details on the bug . If you have
other issues with the Raspberry Pi please file a new bug or post a new
message to the mailing list.
On Wed, 2017-02-08 at 20:34 +0000, Fedora compose checker wrote:
> Missing expected images:
> Cloud_base qcow2 x86_64
This seems to be running into some kind of size issue:
if you look at screenshot.ppm , it's complaining about "Not enough
space in file systems for the current software selection. An additional
295 MiB is needed."
> Workstation live i386
This is failing due to a dependency issue on librbd1. This is part of
ceph, and needs rebuilding for the Boost soname bump, but build is
> Kde live x86_64
Similarly to Workstation, KDE live compose is failing due to dependency
issues stemming from the Boost soname bump. There's at least hugin that
needs rebuilding, but currently fails to build:
I believe there may be some other packages needing a rebuild too, will
investigate and file those.
> Cloud_base raw-xz x86_64
Same as the other cloud_base.
> Xfce raw-xz armhfp
Seems to be some kind of compose mishap:
"AttributeError: Values instance has no attribute 'optional_arches'"
Will check with releng.
> Minimal raw-xz armhfp
Same as Xfce.
> Workstation live x86_64
> Kde live i386
> Failed openQA tests: 68/85 (x86_64), 16/16 (i386)
Virtually every failure here boils down to one of three bugs:
* The KDE dependency issues
* The GNOME dependency issues
That last one causes like 80% of the failures. It seems a new selinux-
policy is denying agetty from doing something it wants to do. You do
actually get a login prompt, but it's still in the Plymouth color
scheme, so openQA's screenshot match fails. Paul Whalen reports that
this prevents serial console login, as well.
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
I've been running a raspberry pi 3 with Fedora release 25 (Twenty
Five) using kernal 4.9.6-200.fc25.armv7hl, and I have been noticing for the
last 2 weeks that my Pi locks up. I tried hooking it up to an HDMI monitor,
and USB keyboard to see if the system generates any message, but I only get
a blank screen and no reaction from the keyboard. I have looked at the
/var/log/message, and dmesg, and I don't see anything that could be causing
the problem. I was thinking it could be overheating, but Fedara 25 does not
support any of the rasbian commands to run heat sensor checks.