i did the following steps
1. boot the Host Debian 10 VM ( everything works fine in the past )
2. check the Debian 10 phpvirtualbox and virtualbox via "ssh -X vbox@host virtualbox"
3. Result : 32 bit VMs are working, 64 bit does not working, VT-X is shown as activated in the phpvbox interface
=> 2-3 days before the Debian 10 installation works without errors. Debian 10 System was not mounted since the last working boot
==> seems the error is NOT in the OS software or any other runnung software on the OS.
According to this information there is a hardware or hardware config error
4. Disable all features ( even if they wouldn' t have any effekt to the VT-X commands ) of ALL multiuse hardware - including hyperthreading ( just create a minimal error bios config )
5. Start the Debian 10 Installation again and looking for a working virtualbox 6.1.32
=> 32 bit works, 64 does not work, BUT!!! : now there is a message VT-X not available. - Everthing OK
6. Enable the disabled VT-X and other features again
7. Start the Debian 10 Installation again and looking for a working virtualbox 6.1.32
=> 32 and 64 bit VMs works
Now i can ensure correct working hardware.
8. Start the Debian 12 Installation using VBox 7.0.10 and phpVbox 7.0.10
9. check php webinterface => fail
10 check virtualbox GUI via ssh -X vbox@host virtualbox => GUI does not start, no error message anywhere ( GUI/system/VMLog)
11 remove VBox 7.0.10 ( apt purge virtualbox* && updatedb && locate virtual # remove all remaining files and configs ) except phpVB7.0
12 install phpvirtualbox 6.1 including extentions
13 start VBox GUI via ssh -X vbox@host virtualbox
=> everthing works fine 32 and 64 VMs , create, delete, import, export, register etc
14 reboot into D10 installation an backup D12 installation via dd
15 reboot into D12 installation
16 remove virtualbox 6.1.46 completely from system (deinstall via apt and remaining files)
17 install virtualbox-7.0 from virtualbox sources located in sources list
18 start VBox GUI via ssh -X vbox@host virtualbox
=> everthing works
19 check phpvirtualbox-7 webinterface
=> everthing works
20 Final reboot to check if really everthing works
=> mysql server does not start (Aug 14 13:29:33 080-ngNAS-Storage systemd: mariadb.service: Failed with result 'signal'.
21 remove entire mysql server, client and configs from system
22 reinstall mysql/mariadb server cleint and phpmyadmin
23 start mysql server and apache
24 => works
25 Final reboot check again
=> System boot with out any errors, autostarting VMs works, virtualbox GUI and phpVirtualbox works.
very mysterious ... i do this procedure about 20 times and more and it never works correctly. The VT-X flag was always marked as activated in the CPU specs (cat /proc/cpuinfo | grep vmx)
I think the error was caused by the fact, that the VT-X feature was enabled for the OS, so the OS and its components install thee VT-X features. But the Hardware does response the VT-X commands and then thre was the "null-info-error-message".
If i had know this before ...
Now i have some questions:
1. Is it possible that some broken bits in the VT-X config/register shows the OS active VT-X features even if they are disabled ?
2. Is it possible that the VM virtualization options ( default, none, legacy, Hyper-V, KVM ) changes any BIOS configuration or hardware settings ?
I really want to know whats this error causes, because its a very special error found by one over a week try and error.
Debain 12 Vbox 7.0.10 phpVbox 7.0 Install Guide => https://speefak.spdns.de/oss_lifestyle/ ... irtualbox/