Hello guys/girls,
I'm new to ORACLE and VM world, I buy the famous book from OccupyTheWeb "Linux basics for hackers".
I try to launch my first VM on my windows 10 pc, VM working on Debian Linux (64bit).
Every time I try to do something, I always get the same error code, can someone help me please?
Error code :
Not in a hypervisor partition (HVP=0) (VERR_NEM_NOT_AVAILABLE).
AMD-V is disabled in the BIOS (or by the host OS) (VERR_SVM_DISABLED).
Result Code: E_FAIL (0X80004005)
Component: ConsoleWrap
Interface: IConsole {6ac83d89-6ee7-4e33-8ae6-b257b2e81be8}
Powering VM up...
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Powering VM up...
Either your computer's "virtualization technology" (VT-x / AMD-V / SVM) is not on in the BIOS or Hyper-V is active. Go through everything in:
I have a 64bit host, but can't install 64bit guests
I have a 64bit host, but can't install 64bit guests
-
- Posts: 2
- Joined: 3. Feb 2023, 00:55
Re: Powering VM up...
Here I've got another error message. Its not the same as the old one but the VM almost got up this time!
Help please!!
Help please!!
- Attachments
-
- VM_Error.PNG (14.69 KiB) Viewed 1116 times
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Powering VM up...
That's a warning, not an error. And did you read it? The message seems very clear to me: you can't store an 80GB file on a FAT-formatted drive (FAT has a 4GB file size limit). If the VDI tries to grow beyond 4GB then the VM will be corrupted. Reformat the drive to exFAT or NTFS. I prefer the latter.
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Powering VM up...
RapidCobra, please abide by two things:
1. Acknowledge and report results of the advice you're given for previous questions before going on to new questions.
2. New questions go in new topics. One issue per thread
And, as Mpack says above, when you get a Virtualbox popup, read the message and think on it for a bit. I too find the warning completely understandable.
So I guess that was three things.
1. Acknowledge and report results of the advice you're given for previous questions before going on to new questions.
2. New questions go in new topics. One issue per thread
And, as Mpack says above, when you get a Virtualbox popup, read the message and think on it for a bit. I too find the warning completely understandable.
So I guess that was three things.