-
-
Notifications
You must be signed in to change notification settings - Fork 97
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
cloud-hypervisor broken on aarch64-linux #105
Comments
I fear I broke your great aarch64-linux work. If you require something useable right now then use tag By now, the bootDisk is only required for the hypervisors that cannot load initrds by themselves. Namely: cloud-hypervisor. Their solution is https://github.com/cloud-hypervisor/rust-hypervisor-firmware which I packaged in time for nixos-23.05. I used the last stable release 0.4.2 which supports only x86_64-linux. I had trouble packaging an unstable version but we shall try again because it brings support for aarch64 and riscv64. Do the other hypervisors work for you? They shouldn't require the bootDisk to be built. |
I have to double check this because looks like with latest versions the builds work again, but I haven't tested the functionality |
My build is only using QEMU at the moment, didn't try other hypervisors yet |
708f09d I guess this commit fixes this issue for other hypervisors than cloud-hypervisor |
Since 4f752ae we no longer require x86_64-only rust-hypervisor-firmware again. |
I have a hydra setup which is building microvms. What I see is in log:
I have waited for days and it never gets past the "Creating EFI partition" step.
With ps ax on the builder machine I can see qemu-kvm that has been running for a long time.
I'd need to add some debug prints or something to see what is the actual command after "Creating EFI partition" that is taking so long.
This only seems to appear on aarch64-linux targets and not x86_64-linux
The text was updated successfully, but these errors were encountered: