You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using mkosi qemu, mkosi will always pass things like Timezone and Keymap to the VM using smbios. This is great when developing, but it can be somewhat annoying when trying to validate an image for a production deployment. For example, I built an image that seemed to work as expected in mkosi qemu, but when deployed it got stuck in firstboot because I'd forgotted to set the timezone in the config. It would be useful to either add an option to mkosi qemu or a separate command to boot the image into a "production-like" environment to help with pre-deployment validation.
Used mkosi config
No response
mkosi output
No response
The text was updated successfully, but these errors were encountered:
mkosi commit the issue has been seen with
main
Used host distribution
Fedora Linux 41
Used target distribution
Fedora Linux 41
Linux kernel version used
No response
CPU architectures issue was seen on
None
Unexpected behaviour you saw
When using
mkosi qemu
, mkosi will always pass things like Timezone and Keymap to the VM using smbios. This is great when developing, but it can be somewhat annoying when trying to validate an image for a production deployment. For example, I built an image that seemed to work as expected inmkosi qemu
, but when deployed it got stuck in firstboot because I'd forgotted to set the timezone in the config. It would be useful to either add an option tomkosi qemu
or a separate command to boot the image into a "production-like" environment to help with pre-deployment validation.Used mkosi config
No response
mkosi output
No response
The text was updated successfully, but these errors were encountered: