-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rockchip64: make rockchip64 bootable in VM #7392
Conversation
I guess it wouldn't hurt anything, although IMHO would be more ideal to have a specific lean kernel for virtualization builds. Amusingly I'm guessing the rockchip64 kernel is probably a fair bit leaner than the uefi ARM64 kernel |
Virtio drivers was already enabled in rockchip64 kernel config, this PR only adds ~512 bytes of code to make them usable. BTW if you are concerned with disk size of the kernel (not RAM size), then probably you can compress it and let uboot uncompress it. I use something like this in my build config/extension: function pre_package_kernel_image__compress_kernel() {
lzop --best "${kernel_image_pre_package_path}"
mv "${kernel_image_pre_package_path}"{.lzo,}
return 0;
} |
@alex3d btw how you booting the image with Apple Virtualization Framework? In the past I've used UTM a few different ways |
a4cccdd
to
5033fe4
Compare
Mmmh, I see no harm in enablng the generic PCI Host driver. Perhaps having the chance to boot the kernel via VM can be useful for some automated image testing later @igorpecovnik About concerns on size of the kernel and modules, currently rockchip64 carries a lot of useless drivers and features that can be slimmed down by several megabytes any time. I will just make a quick check on a live system then, if it works as I suppose it will, approve |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Checked, the board booted fine with current kernel and PCI_HOST on. I approve
Description
Most of stuff needed to boot inside VM was already in place, the one remaining (new?) thing is CONFIG_PCI_HOST_GENERIC. Enable it to allow quick check of new images in QEMU or Apple Virtualization framework.
The kernel size difference is negligible (actually I see no kernel size change at all, apparently growth is fully covered by some kernel image alignment)
How Has This Been Tested?
Checklist: