It turned out the dialog for editing virtual machines doesn't operate correctly when editing amd64 (x86_64) machines. It's because of the architecture being listed as amd64 instead of x86_64. That's what happened when I tried to test Windows 7 x64 again.
Expected behaviour: The VM boots up correctly.
Actual behaviour: The VM became an i386 one.
Steps to reproduce:
Create an x86_64 machine or try with an existing one.
Click on "Edit VM".
Edit something and click OK.
See that the VM doesn't work (correctly).
I wanted to demonstrate it for someone on the following configuration:
Host OS: Windows 10 22H2 x64
CPU: Intel Core i7-4770K
RAM: 16 GB DDR3
Graphics: NVIDIA GeForce GTX 960 4 GB
QEMU: 7.2.0
EmuGUI: 1.0.0.5310
Guest OS: Windows 7 SP1 x64
Workaround: Just delete the VM and create a new one for the time being if something went wrong.
Tech-FZ
commented
1 year ago
It turned out the dialog for editing virtual machines doesn't operate correctly when editing amd64 (x86_64) machines. It's because of the architecture being listed as amd64 instead of x86_64. That's what happened when I tried to test Windows 7 x64 again.
Expected behaviour: The VM boots up correctly.
Actual behaviour: The VM became an i386 one.
Steps to reproduce:
I wanted to demonstrate it for someone on the following configuration: Host OS: Windows 10 22H2 x64 CPU: Intel Core i7-4770K RAM: 16 GB DDR3 Graphics: NVIDIA GeForce GTX 960 4 GB QEMU: 7.2.0 EmuGUI: 1.0.0.5310 Guest OS: Windows 7 SP1 x64
Workaround: Just delete the VM and create a new one for the time being if something went wrong.