Hallo,
Ich habe die virtualbox neu installiert und erhalte nun die folgende Fehlermeldung.
Für die virtuelle Maschine backblaze konnte keine neue Sitzung eröffnet werden.
Failed to load API DLL: WinHvPlatform.dll: VERR_MODULE_NOT_FOUND; vid.dll: VERR_MODULE_NOT_FOUND (VERR_NEM_INIT_FAILED).
AMD-V is not available (VERR_SVM_NO_SVM).
Fehlercode: E_FAIL (0x80004005)
Komponente: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Mfg
Fehlerhafter Start der Virtualbox
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Fehlerhafter Start der Virtualbox
What version were you previously running?
VirtualBox 6.1.x requires VT-x/AMD-v, or NEM (Hyper-v) as a very poor fallback.
The error message says that AMD-v is not available, and neither is NEM. It's hard to understand how this error message could arise if all you did was reinstall a version of VirtualBox that previously worked on this same host.
See FAQ: I have a 64bit host, but can't install 64bit guests.
VirtualBox 6.1.x requires VT-x/AMD-v, or NEM (Hyper-v) as a very poor fallback.
The error message says that AMD-v is not available, and neither is NEM. It's hard to understand how this error message could arise if all you did was reinstall a version of VirtualBox that previously worked on this same host.
See FAQ: I have a 64bit host, but can't install 64bit guests.
Re: Fehlerhafter Start der Virtualbox
das geht wohl nicht beim Windows Server 2019 sondern erst ab Windows Server 2022?
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Fehlerhafter Start der Virtualbox
Sorry, but I have no idea how you drew that conclusion. Windows Server 2019 and 2022 are both based on Windows 10 so both will have similar requirements (*), including AMD-v.
(*) in fact VirtualBox does not currently (6.1.34) have a Win2022 template, so you would use the server 2019 template.
(*) in fact VirtualBox does not currently (6.1.34) have a Win2022 template, so you would use the server 2019 template.
Re: Fehlerhafter Start der Virtualbox
Ich kann das Hyper-v Feature nicht hinzufügen, da der Prozessor dies nicht unterstützt.
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Fehlerhafter Start der Virtualbox
No one has asked you to enable Hyper-v. That is a piece of software made by Microsoft, it interferes with VirtualBox so you definitely should not enable it if you weren't already using that feature.
I would be very surprised if your AMD processor does not support AMD-v (a hardware feature of AMD CPUs, completely unrelated to Microsoft). Is your processor more than 12 years old?
As the FAQ linked above mentions, most AMD BIOSes have a feature called SVM or SVC (Secure Virtual Mode/Computing) which, when enabled, enables AMD-v.
But, if you are correct that your CPU does not support any such feature then you cannot use VirtualBox 6.1.x. Older (6.0.x and earlier) versions can run some VMs without VT-x/AMD-v, the FAQ covered that too.
I would be very surprised if your AMD processor does not support AMD-v (a hardware feature of AMD CPUs, completely unrelated to Microsoft). Is your processor more than 12 years old?
As the FAQ linked above mentions, most AMD BIOSes have a feature called SVM or SVC (Secure Virtual Mode/Computing) which, when enabled, enables AMD-v.
But, if you are correct that your CPU does not support any such feature then you cannot use VirtualBox 6.1.x. Older (6.0.x and earlier) versions can run some VMs without VT-x/AMD-v, the FAQ covered that too.