-
Notifications
You must be signed in to change notification settings - Fork 8
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
Stuck while booting : switching console to com0 #7
Comments
Hi, Can you share your qemu version and command line? I'll try to reproduce. |
hi, sorry seems like i make mistake, i use this image found it in here https://bsd-cloud-image.org/ i try to build my self using this repo as refrence but still stuck in partition part, it trow DEVICE BUSY |
I don't really know how to help you, the github action works so I'd say it's an issue on your system... You don't give me enough information to reproduce. You can look at the test action, this is the qemu command I use:
|
Hi sorry for that, heres the detail. i use virtfusion for platform to deploy vps, using your image https://github.com/hcartiaux/openbsd-cloud-image/releases/download/v7.5_2024-05-13-15-25/openbsd-min.qcow2 the output from VNC are like above. and then i try build with the builder script, and stuck in this while running i will try with other platform, and update again. thanks for the help |
You need enter serial0 console in qemu window |
update : in virtusion it need to disable cloud init per vm basis. |
It may be an upstream cloud-init bug, you may want to try the OpenBSD 7.6 image with an up-to-date cloud-init: https://github.com/hcartiaux/openbsd-cloud-image/releases/tag/v7.6_2024-10-08-22-40 Otherwise without instructions to reproduce this issue on my system and without a trace (cloud-init logs ?), I cannot do anything more... Virtfusion seems to be a commercial offering so I cannot really help here... |
Hi
thanks for the image, when booting it stuck in this screen
switching console to com0
what to check?
appreciate the help!
The text was updated successfully, but these errors were encountered: