Skip to content

Instantly share code, notes, and snippets.

[WARNING] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `archiengine`, expected `davincisvessels`. This could be a intended override, but in most cases indicates a broken mod.
[WARNING] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `archianchor`, expected `davincisvessels`. This could be a intended override, but in most cases indicates a broken mod.
[WARNING] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `archisecuredbed`, expected `davincisvessels`. This could be a intended override, but in most cases indicates a broken mod.
[INFO] [org.valkyrienskies.mod.common.ValkyrienSkiesMod]: Valkyrien Skies Initialization:
[INFO] [org.valkyrienskies.mod.common.ValkyrienSkiesMod]: We are running on 3 threads; 4 or more is recommended!
/* Registers:
* r3: kvm_run pointer
* r4: vcpu pointer
*/
_GLOBAL(__kvmppc_vcpu_run)
stwu r1, -HOST_STACK_SIZE(r1)
PPC_STL r1, VCPU_HOST_STACK(r4) /* Save stack pointer to vcpu. */
/* Save host state to stack. */
PPC_STL r3, HOST_RUN(r1)
LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://COPYING;md5=c616d0e7924e9e78ee192d99a3b26fbd"
inherit module
SRC_URI = "file:///homead/QorIQ-SDK-V2.0-20160527-yocto/sources/meta-virtualization/recipes-kernel/kvm-kmodule/kvm-kmod-3.10.21.tar.bz2"
S = "${WORKDIR}/kvm-kmod-3.10.21"
do_configure() {
===On Wed, Nov 6, 2019 at 10:40 AM Wayne Li wrote:
Dear Yocto Developers,
I'm trying to get KVM added and working on a Yocto kernel I built up for a T4240 RDB (has a PowerPC CPU). KVM isn't working and the reason why it isn't working seems to be I'm missing the necessary kernel modules. More specifically, I don't seem to have a kvm.ko file that I can load. Here's how I attempted to add KVM to the kernel.
I went to the SDK install folder and ran ". fsl-setup-env -m t4240rdb-64b" and then "bitbake virtual/kernel -c menuconfig". After the GUI comes up, I went to Virtualization -> KVM support for PowerPC E500MC/E5500/E6500 processors and hit "Save" to save the configuration. I then went and copied the content of the .config file created by this into the kernel configuration file specified by the following path; "build_t4240rdb-64b/virt1.config". This path was specified by the variable KERNEL_DEFCONFIG in sources/meta_freescale/conf/machine/t4240rdb-64b.conf. Here's what I currently have in the kernel c
#!/bin/sh
# Before running this script please ensure that your PATH is
# typical as you use for compilation/istallation. I use
# /bin /sbin /usr/bin /usr/sbin /usr/local/bin, but it may
# differ on your system.
#
echo 'If some fields are empty or look unusual you may have an old version.'
echo 'Compare to the current minimal requirements in Documentation/Changes.'
echo ' '
NOTE: Preparing RunQueue
WARNING: /homead/QorIQ-SDK-V2.0-20160527-yocto/sources/meta-freescale/recipes-kernel/linux/linux-qoriq_4.1.bb.do_compile is tainted from a forced run
NOTE: Checking sstate mirror object availability (for 6 objects)
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Unable to install packages. Command '/homead/QorIQ-SDK-V2.0-20160527-yocto/build_t4240rdb-64b/tmp/sysroots/x86_64-linux/usr/bin/smart --log-level=warning --data-dir=/homead/QorIQ-SDK-V2.0-20160527-yocto/build_t4240rdb-64b/tmp/work/t4240rdb_64b-fsl-linux/fsl-image-full/1.0-r0/rootfs/var/lib/smart install -y lsb@ppc64e6500 packagegroup-core-ssh-openssh@all udev-extraconf@ppc64e6500 packagegroup-fsl-tools-extended@all htop@ppc64e6500 libvirt-virsh@ppc64e6500 libvirt-libvirtd@ppc64e6500 qemu@ppc64e6500 packagegroup-fsl-tools-core@all packagegroup-fsl-tools-audio@all packagegroup-core-eclipse-debug@all packagegroup-fsl-benchmark-core@all openvpn@ppc64e6500 packagegroup-fsl-networking-extended@all udev-rules-qor
#
# Automatically generated file; DO NOT EDIT.
# Linux/powerpc 4.1.8 Kernel Configuration
#
CONFIG_PPC64=y
#
# Processor support
#
# CONFIG_PPC_BOOK3S_64 is not set