-
Notifications
You must be signed in to change notification settings - Fork 112
Nomad Docs: Add new QEMU driver parameters #1416
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
base: nomad/1.11.1
Are you sure you want to change the base?
Conversation
Vercel Previews Deployed
|
Broken Link CheckerNo broken links found! 🎉 |
aimeeu
left a comment
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.
Thanks! I left a few style guide suggestions.
content/nomad/v1.11.x/content/docs/job-declare/task-driver/qemu.mdx
Outdated
Show resolved
Hide resolved
| In Nomad 1.11.1, `emulator` and `machine_type` were added to the task config, | ||
| and `fingerprint_emulator` was added to the driver config. These default to the | ||
| previously used values of `qemu-system-x86_64`, and `pc`. Previously, when using | ||
| the `kvm` accelerator, the machine type `host` was forced. This is no longer true, | ||
| the value for `machine_type` will be used. Additionally, if using resources.cores, | ||
| with the `kvm` accelerator, the `-smp` was hardcoded to that number of cores. This | ||
| is now only done if the user has not specified a custom -smp flag. |
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.
| In Nomad 1.11.1, `emulator` and `machine_type` were added to the task config, | |
| and `fingerprint_emulator` was added to the driver config. These default to the | |
| previously used values of `qemu-system-x86_64`, and `pc`. Previously, when using | |
| the `kvm` accelerator, the machine type `host` was forced. This is no longer true, | |
| the value for `machine_type` will be used. Additionally, if using resources.cores, | |
| with the `kvm` accelerator, the `-smp` was hardcoded to that number of cores. This | |
| is now only done if the user has not specified a custom -smp flag. | |
| In Nomad 1.11.1, we added `emulator` and `machine_type` to the task config and | |
| `fingerprint_emulator` to the driver config. These default to the previously | |
| used values of `qemu-system-x86_64` and `pc`. Previously, when using the `kvm` | |
| accelerator, Nomad forced the machine type `host`. This is no longer true. Nomad | |
| now uses the value for `machine_type` . Additionally, if using `resources.cores` | |
| with the `kvm` accelerator, the `-smp` used that number of cores. Nomad now only | |
| uses the `resources.cores` value when you have not specified a custom `-smp` | |
| flag. |
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.
I had to refactor this paragraph a good bit after refactoring my PR
Description
Links
Code PR: hashicorp/nomad#27179
Contributor checklists
Review urgency:
Pull request:
Content:
Reviewer checklist