Virtualization is extremely slow on Windows 8

Discussions related to using VirtualBox on Windows hosts.
Post Reply
mkas
Posts: 5
Joined: 6. Oct 2013, 14:32

Virtualization is extremely slow on Windows 8

Post by mkas »

Hi. I haved installed VirtualBox 4.2.18 on my Windows 8 64bit computer.
Host spec: Intel Core i5 3317UM, 12 GB RAM, 500GB HDD

Unfortunately, any Linux Virtual Machine is extremely slow while using.
I have maneged to install Ubuntu 12.04 (32bit), but installation last a few hours. Starting Ubuntu continues for 60-90 minutes, but after it cannot be used because of slowness and freezes.

Yesterday I have downloaded Linux Mint (32bit), but even running it as LiveCD, is very very slow and almost unusable.

I assign 3GB RAM to virtual machines and tried different settings and features enabled but it didn't help. Hoew can I check what causes such slowness?
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Virtualization is extremely slow on Windows 8

Post by Perryg »

Sounds like you need to enable hardware virtualization in the hosts bios.
mkas
Posts: 5
Joined: 6. Oct 2013, 14:32

Re: Virtualization is extremely slow on Windows 8

Post by mkas »

Hi Perryg, thanks for your reply.

But please, have a look at my Bios options:
bios.jpg
bios.jpg (59.32 KiB) Viewed 8059 times
In the first SysInfo tab I can see that VT-x is supported (it is not editable - I cannot change anything here).

In the second Advanced tab I can change only features as seen on the image, there is nothing related to virtualization, I guess.

Third Security Tab allows me to set some passwords. And the last one Boot tab allows to set boot order etc.

I cannot find anything associated with virtualization in my Bios settings.
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Virtualization is extremely slow on Windows 8

Post by Perryg »

Post the guests log file (as an attachment)
See Online Users Manual for the location of the file.
mkas
Posts: 5
Joined: 6. Oct 2013, 14:32

Re: Virtualization is extremely slow on Windows 8

Post by mkas »

I am sending log files as attachments.
Attachments
VBox-mint.log
(70.08 KiB) Downloaded 25 times
VBox-ubuntu.log
(81.56 KiB) Downloaded 25 times
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Virtualization is extremely slow on Windows 8

Post by Perryg »

Code: Select all

00:00:05.971584 HWACCM: No VT-x or AMD-V CPU extension found. Reason VERR_VMX_NO_VMX
Do you have Hyper-V installed in the win8 host?
mkas
Posts: 5
Joined: 6. Oct 2013, 14:32

Re: Virtualization is extremely slow on Windows 8

Post by mkas »

Yes, it is enabled in Windows Features in Programs and Features from Control Panel.
And I have access to the Hyper-V Manager in Win8 host system.
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Virtualization is extremely slow on Windows 8

Post by Perryg »

Then that is your problem. Windows loads the Hyper-V at boot and does not allow anything else to access VMX. AFAIK they are the only ones that do this and you need to make a decision.
1) remove Hyper-V
2) set it to not enable at boot
3) use Hyper-V and nothing else.
mkas
Posts: 5
Joined: 6. Oct 2013, 14:32

Re: Virtualization is extremely slow on Windows 8

Post by mkas »

OK, I see, thanks for your help.
The Hyper-V is required by MS Visual Studio for Windows Phone, as I am developer and I am using this IDE.
There is a Windows Phone emulator run as Virtual Machine, but I didn't know, that it will be causing any problems.

Thanks once again. I have to make decission which one use now.
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Virtualization is extremely slow on Windows 8

Post by Perryg »

Or set Hyper-V to not load at boot. This is usually what those do that require Hyper-V but also want to use a different hypervisor as well.
Post Reply