dahliaos / fimage Goto Github PK

Thanks for making it easier to run fushcia!

I was puzzled by a variety of confusing kvm permission errors trying to get configured on Ubuntu 18.04. E.g.

$ ./fimage-headless 2048
...
cannot add library /home/usr/fuchsia/fimage-210528/linux-x64/qemu/linux-x86_64/lib64/vulkan/libvulkan.so: failed
added library /home/usr/fuchsia/fimage-210528/linux-x64/lib64/vulkan/libvulkan.so
cannot add library /home/usr/fuchsia/fimage-210528/linux-x64/lib64/vulkan/libvulkan.so.1: full
Could not access KVM kernel module: Permission denied
qemu-system-x86_64-headless: failed to initialize KVM: Permission denied
./fimage-headless: line 2: 27139 User defined signal 1   linux-x64/emulator -feature VirtioInput,GLDirectMem,VirtioMouse,KVM,Vulkan -window-size 1280x800 -gpu swiftshader_indirect -no-location-ui -no-window -no-hidpi-scaling -fuchsia -kernel default/multiboot.bin -initrd init/fuchsia-ssh.zbi -m $1 -serial stdio -vga none -device virtio-keyboard-pci -smp 4 -device virtio-mouse-pci -machine q35 -device isa-debug-exit,iobase=0xf4,iosize=0x04 -enable-kvm -cpu host,migratable=no,+invtsc -netdev type=tap,ifname=qemu,id=net0,script=scripts/start-unsecure-internet.sh,downscript=no -device virtio-net-pci,vectors=8,netdev=net0,mac=52:54:00:63:5e:7a -drive file=init/fvm_raw.blk,format=raw,if=none,id=vdisk -device virtio-blk-pci,drive=vdisk -append 'TERM=xterm-256color zircon.nodename=fuchsia_fimage kernel.serial=legacy kernel.entropy-mixin=ec98e395c5dd4771931a91dfe7e044a651c3b8b0be2828c8bf6544d151f62e2f kernel.halt-on-panic=false '

I had my account properly set up for kvm, since it tells me that the KVM line in /etc/group should end with ":" followed by your username. and that's true...

That file /home/usr/fuchsia/fimage-210528/linux-x64/lib64/vulkan/libvulkan.so.1 exists, but I don't know what full means in that context and don't see good tips on the web.

That problem turned out to be incorrect permissions on /dev/kvm itself. But note you can't just change the permissions with chmod. You need to configure udev, as described concisely in Gerd's answer at Android Studio: /dev/kvm device permission denied.

Since the error is misleading, it would help to have the shell scripts check for that explicitly and give better hints.

Preflight generates the error in fimage-210528:
BUG: An internal command error occurred.
Could not run 'lspci'

Caused by:
No such file or directory (os error 2)

None of the files seemed to land in my linux container in a way they could be executed. Had to chmod -R 1777 * -

Then got this error: emulator: Android emulator version 30.7.2.0 (build_id ) (CL:N/A)
emulator: ERROR: can't find the emulator executable.

I haven't figured out how to exit the VM. When I use Ctrl-Z to suspend it and then kill it, the network ends up busy,

qemu-system-x86_64-headless: could not configure /dev/net/tun (qemu): Device or resource busy

and I resort to:

sudo ip link delete qemu
sudo ip link delete brqemu
./network-config

How can we bring it down cleanly? Perhaps we can modify the network-config script to clean up also?

I'm trying to use fimage to develop fuchsia app but I don't have fuchsia source. So, I don't have ./tools/zbi to put ssh pub key.
Please add a standalone zbi executable in this repo, thanks.

In scripts/start-unsecure-internet.sh there is this statement to allow DNS.

On my Ubuntu 22.04 LTS machine that gives the error

ERROR: Could not find a profile matching 'dns'

and Fuschsia simply does not start.

On my machine I replaced this with this and now Fuschsia does start

sudo ufw allow proto udp from 0.0.0.0 to 255.255.255.255 port 53 comment 'Fuchsia qemu DNS'

I'm unsure if this is a problem with my machine or something else.

I ran the fimage using./fimage-gui 4096 in vm (ubuntu20.04). The color was not correct and the resolution was not correct:

but using the screenshort tool, I did get the right image

./ffx-linux-x64 platform preflight
Running pre-flight checks...

[✓] Found all needed build dependencies: curl, git, unzip

[!] Did not find tested and supported graphics acceleration hardware. Usage of the
graphical Fuchsia emulator (fx vdl start) may fall back to a slow software
renderer. The terminal emulator (fx qemu) is unaffected.
Found the following chipsets: Cirrus Logic GD 5446
Only a small set of chipsets are officially supported:
https://fuchsia.dev/fuchsia-src/get-started/set_up_femu#supported-hardware

[✓] Found tuntap device named 'qemu' for current user

There were some warnings, but you can still carry on. Continue at https://fuchsia.dev/fuchsia-src/get-started

Qemu is a real CPU hog for natural reasons. It would be nice to be able to pause or suspend Fuchsia / Zircon.

My first attempt was simply to use the Linux shell suspend approach (ctrl-z), but if you wait more than a few seconds to put the process back in the foreground, it crashes:

ZIRCON KERNEL OOPS                                                                                           
lockup_detector: no heartbeat from CPU-1 in 42506438 ms, last_heartbeat=520344414253 observed now=43026782921300 name=unknown.

Reported by [CPU-2] (message rate limited)
ZIRCON KERNEL PANIC
timer_ints: 146242, interrupts: 0

        tweight=0.2952270507 nfair=7 ndeadline=0 vtime=180747885048 period=8 tema=12583943 tutil=0.0
UPTIME: 43026795ms

I was happy to see a dm suspend command, but it says:

[00031.044] 21072:21074> [shutdown-shim]: checking power_manager liveness
send_SuspendToRam: Failure with error: ZX_ERR_NOT_SUPPORTED[00031.065]
 21072:21074> [shutdown-shim]: trying to forward command

What would it take to support SuspendToRam in this environment?

Are there other ways to pause the emulation and resume quickly?

i do with this setup https://docs.dahliaos.io/developer/fimage-setup
But cannot find fuchsia_image。whats wrong with me?
Flutter version：
Flutter 2.2.2 • channel stable • https://github.com/flutter/flutter.git
Framework • revision d79295af24 (2 周前) • 2021-06-11 08:56:01 -0700
Engine • revision 91c9fc8fe0
Tools • Dart 2.13.3