[2025-jun-17] The SlackDocs mailing lists at https://lists.alienbase.nl/mailman/listinfo have been retired. No one has been using these lists for years and it's time to say goodbye. The list archives remain available at https://scalzi.slackware.nl/mailman/listinfo/slackdocs
[2025-jun-17] The SlackDocs Wiki has moved to a new server, in order to make it more performant.
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
howtos:emulators:helper_script_for_managing_qemu_virtual_machines [2016/09/04 20:04 (UTC)] – [Problems] louigi600 | howtos:emulators:helper_script_for_managing_qemu_virtual_machines [2023/12/12 08:13 (UTC)] (current) – [Sources] zeebra | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
+ | <!--I took the liberty to fix this headline, if it should have another name, change it --- // | ||
+ | ===== Preface | ||
Qemu is a popular and powerful open-source emulator often used for running KVM Virtual Machines (VMs). In fact qemu supports emulating so many things that it can be quite challenging, | Qemu is a popular and powerful open-source emulator often used for running KVM Virtual Machines (VMs). In fact qemu supports emulating so many things that it can be quite challenging, | ||
Line 25: | Line 27: | ||
====== Proposed Solution ====== | ====== Proposed Solution ====== | ||
- | It quickly became apparent to me that the VM configuration would need to be generated rather then manually created and that a central configuration repository would much aid the process. Again a text based central configuration file would make the code in inherently complicated (having to deal with an arbitrary number of VMs each with arbitrary number of disks and NICs). | + | It quickly became apparent to me that the VM configuration would need to be generated rather then manually created and that a central configuration repository would much aid the process. Again a text based central configuration file would make, either |
- | Having some experience on database administration made it a little unappealing to use LDAP for central repository and even if I had no DB experience at all I doubt I'd actually want the overhead of running LDAP just for this. Running MariaDB or Postgres | + | Having some experience on database administration made it a little unappealing to use LDAP for central repository and even if I had no DB experience at all I doubt I'd actually want the overhead of running LDAP just for this. Running MariaDB or Postgres was equally |
+ | |||
+ | |||
+ | Another thing that quickly became apparent was the almost repetitive code required to prompt for all the options so I decided to address that in 2 ways: | ||
+ | - have as much of the promoting automatically generated with a clever workaround | ||
+ | - use dialog to further simplify the UI for prompting | ||
- | Another thing quickly became apparent was that a lot of code was required to prompt for all the options on the text console. I find that dialog can be really handy for this along with making a better appealing interface. | ||
===== Basic Configuration ===== | ===== Basic Configuration ===== | ||
- | To get better flexibility | + | To get better flexibility |
* Path to folder that will contain all the VMs | * Path to folder that will contain all the VMs | ||
* Path to where the centralized VM configuration DB is | * Path to where the centralized VM configuration DB is |