Windows Experience Index

[Francisco6x]

This it is VirtualBox, Windows Experience Index.
It is 1,0. The minor possible!
How can I improve it?

[Francisco6x]

Ok.
I will wait 1 day to post the print screen image!

[Perryg]

We don't need the screen shot, just post the guests log file (as an attachment)

[Francisco6x]

VBox.log

(76.5 KiB) Downloaded 108 times

[Perryg]

Your host does not have the resources to achieve any better performance.
atom processor, not enough RAM, and no VT-x

[Francisco6x]

These they are my Windows Experience Index components,
from de guest OS (VirtualBox), not de host OS.
The atom processor has subscore 2,0;
the Memory (RAM) has subscore 4,5.
They are not the problem.

http://comvir.org/big/x/20130812a.png

[stefan.becker]

And what do you want to say with the Screen Shot?

Buy better Hardware and ask again if 1.0 is the best value.

In other words: You cant win a formula one race with a bobby car.

[Francisco6x]

They are my Windows Experience Index components,
from de guest OS (VirtualBox), not de host OS.

[Perryg]

I knew that when I posted. What do you think you need to do make a better score?
Where do you think the guest gets its resources from?

[Martin]

What do you need the Windows Experience Index number for?
It's just a number without any real relevance in a virtualised system.

[Matt USA]

FYI, I just built my first virtual box. Win7 Pro 64 (Same as host)
The host has a windows experience index of 5.9 but had a windows experience index of 1 on the guest VirtualBox.
After I downloaded the VM Virtualbox extension pack I enabled 3D acceleration and use Windows Aero in VirtualBox.
http://www.howtogeek.com/124479/how-to- ... irtualbox/
Now the attempt to re-run the assessment for Windows Experience Index crashes. I have no other known issues. The guest VirtualBox seems to run fine.

Update to this Update:
I downloaded the latest VirtualBox 4.3.8 re-enabled 3D acceleration and use Windows Aero in VirtualBox (Beta). And now have Windows Experience Index 4.9! WOOHOO

[thanar]

This issue has been puzzling me for quite some time on new VMs running win7. What I found is that, even after installing VM additions, including the Aero driver, it would take some time before acceleration would actually start working. It would usually take running windows experience index a couple of times, restart the VM a couple of times, let it run on idle for half an hour or so, but acceleration/Aero would eventually work. Getting an index of 4.9 (7.2-7.3-5.9-4.9-7.9) on my imac11,1 running 10.8.5.

[loukingjr]

I've never had that happen.