EmuGUI v2.1.0.5702_dev "Fatima Nejla" (Dev Release 3)
Pre-release
Pre-release
WARNING
- This is a pre-release, so please don't use this for any productive purposes.
- You now need the latest version of your Linux distribution or at least Windows 10 to get official support for this release.
Changes compared to v2.0.6.5617
- Thanks to Mizuki, we now have more flexible Windows-specific code.
- As per the depreciation policy, the old USB Tablet checkbox has been removed for good.
Foreported
From v2.0.7.5618
- When creating new VMs, you can now choose custom BIOS files again.
From v2.0.8.5619
- The keyboard layout is now set correctly.
From v2.0.9.5620 (kinda)
- ARM machines are now defaulted to "virt" by EmuGUI. (or at least they should be)
Changes compared to v2.1.0.5701_dev
- The VM table on the database can now save information which you would set when starting the VM (excluding TPM information).
- The bootfrom part has been added afterwards.
- The VM dialogs now show UI elements for those settings.
- The time settings can now be enabled and disabled in the VM dialogs using the RTC checkbox.
- The floppy seems to be able to get set on the dialogs.
- The newcomers can now be saved onto the database permanently.
- The CD Browse buttons work now.
- A class for storing VMs is on its way to replace the bad temporary file saving practice with good OOP practice.
- The VHD variable had to be added.
- The addargs also had to be added.
- The edit VM dialog is being adapted to the new OOP-based approach. The following has already been added:
- Name (now fully adapted)
- Architecture
- Machine
- CPU
- RAM
- Basic VHD settings
- VGA
- Network
- BIOS location & files
- Additional arguments
- Sound card
- Linux settings
- Mouse
- CPU cores
- Keyboard type & layout
- USB Controller & Support
- Hardware Acceleration
- HDD Controller
- CD Controllers
- CDs
- Floppy
- "Boot from" option
- Time option
- The Win2k checkbox is to be removed because of the OOP adaption.
- The Edit VM dialog will now turn the Win2k optimisations off regardless of what you really want.
- The Edit VM dialog would now use the new OOP-based initialisation instead of the file-based one.
- A log text had to be adjusted.
- A new Start VM dialog has already been designed.
- The code is in preparation.
- The vmdata can be passed on to the new Start VM dialog.
- The icon would be shown.
- The database connection would be set up.
- The old code for actually starting the VM is used as a base.
- References are changed to the new OOP ones.
- Media
- Date and time
- Architecture selection
- Base command
- HDA Addition
- The following other parameters:
- Machine
- CPU
- VGA
- Network
- USB
- BIOS Directory
- Sound
- Kernel
- Linux initrd
- Linux cmd args
- Mouse
- BIOS file
- Additional args
- Acceleration
- TPM
- Clicking the corresponding button should start it now.
- References are changed to the new OOP ones.
- The main dialog is now opening that instead of the old one.
- The code is in preparation.
- The vmdata converter has been removed again.
- Editing the VM is now implemented.
- Preparations for one-time edits have begun.
- One-time edit functions are prepared.
- One-time edit is implemented.
- One-time edit can be accessed.
- The HDA stuff had to be migrated.
Known issues
- Unfortunately, you might have to run EmuGUI from the terminal on Linux.
- You will not be notified about any more updates for now as update.txt will not be updated.
- As for the TPM functionality, you must run
mkdir (insert-path-here)andswtpm socket --tpm2 --tpmstate dir=(insert-path-here) --ctrl type=unixio,path=(insert-path-here)/swtpm-sock --log level=20in a terminal (You can leave the--tpm2argument away tho if you plan to use TPM 1.2 instead). - The QCOW2 format is prone to not work for some Windows VMs.
- The new settings aren't applied yet. However, as the way to temporarily save VM settings is to be changed anyway, this won't be fixed until then.