Why is virtualbox such a slow piece of garbage? My windows 10

No your specs really aren't that good to run w10 especially running VS inside it.

>>56978874
>he runs W10 in VM on shitty linux distro to code for windows
what level of irony are we on right now?

File: feelfrog.png (2KB, 90x90px) Image search: [Google]

2KB, 90x90px

>>56978885
You're kidding right? What's the limiting factor here? Is it my RAM? I already give my virtual machine 2gb RAM and both of my cores.

>>56978874
It's not virtualbox' fault anon. Visual Studio is just a bloated piece of shit and you know it. However you can run windows 7 to reduce the resource hog

>>56978874
If you want native performance you gotta passthrough GPU

>>56978874
You should invest in an SSD, because without it windows 10 will keep being this slow.

>>56978874
>My specs are good enough, right
They really aren't anon. You have less than 8GB of RAM, and you have a fucking 5400 RPM HDD. Stop being so poor.

>hating virtualbox

honestly can't believe it

>>56978874
>not to mention it has close to a 100% disk usage.
thats windows fault.

>>56978914
I know anon, it's garbage, but I have to learn C# for a school course. Sadly I cant run windows 7 because a piece of software I have to install only runs on 8.1+. Ironically, when i installed and first used the VM, 10 was the fastest out of all 3 windows distro's i tested out (7,8.1 and 10)

>>56978874
>>56978928 is right. You should probably buy a macbook™ :^)

>>56978874
Also go into your bios and see if VT-x and VT-d are turned on.
>2 core 4 thread
>give it both cores
vbox counts threads as cores.

Also laptop cpus suck compared to desktop cpus. I have laptop i5 that is slower than my 2007 core2.

>>56978946
The irony is that the macbook pro I looked at ships with the same CPU this fucking VAIO has which i bought in 2012.

>>56978928

How is it the RAM's fault? the minimum system requirements say you need 1gb for windows 10.

>>56978923
??

>>56978874
http://cpu.userbenchmark.com/Compare/Intel-Core-i5-3210M-vs-Intel-Core-i5-2500K/2719vs619

Against the ancient i5-2500k, your "i5" mobile shit.

>http://cpu.userbenchmark.com/Compare/Intel-Core-i5-3210M-vs-AMD-Phenom-II-X4-840/2719vsm3302
Even the ancient Phenom II X 840 (2.8 Ghz) is stronger.

TL;DR your CPU garbage

>>56978972
If you were looking at a macbook Pro™ with an ivy-bridge i5, you really are poor :^)

>>56978874
>5400 RPM HDD
>Windows 10

Also install VMware.

>>56978913
>>56978874
Well yeah but your PC is shit, what are you even doing here with a dogshit pc and windows?

>>56978975
The i5-2500K is still relevant precisely because its overclockable, and the Phenom doesnt even support virtualization, so it's stupid that you bring it up.

http://www.cpubenchmark.net/cpu.php?cpu=Intel+Core+i5-3210M+%40+2.50GHz

This is the benchmark I used. Even though I can understand my CPU being garbage, That still doesn't explain why Windows 2012 server works like a charm but windows 10 doesn't.

>>56979012
Not to mention he's running the babby version of Arch

>can't into arch
>install memejaro

Might as well run windows natively at that point

>>56978972
>How is it the RAM's fault? the minimum system requirements say you need 1gb for windows 10.

Plus VS 2013 system requirements
>1 gigabyte (GB) of RAM (1.5 GB if you are running in a virtual machine)

>>56979005
>VMware

i'll consider it but i'm already going to try out virt-manager.

>>56978959

>see if VT-x and VT-d are turned on.

Going to check right, i'll let you know.

>>56979012

I'd argue windows is a lot easier to use than linux, senpai :^)

File: 1243961841738.jpg (37KB, 624x352px) Image search: [Google]

37KB, 624x352px

>>56978874
Less than 4 physical cores
Less than 8 gigs RAM
No VT-d
no SSD
no vPRO
Probably does not have VT-x enabled in BIOS

Don't even bother, you're trying to use software for IT / developers on a facebook machine what the hell did you expect?

>>56979046

Honestly, I think we can zero out RAM, since I give it 2.7 GB already.

>>56979049
>>VMware
VMware does bare metal, near native virtualisation unlike virtualbox

>>56978874
>100% disk usage
Normal for Windows 10. And you having a fucking 5400rpm laptop hdd doesn't help.
Just use 7 or 8.1.

>>56979059
>needing more than 4 cores and more than 8gb ram to run visual studio let alone an ssd

Not that guy but if you're going to give him advice atleast be genuine, you're acting as if Visual Studio is NASA software.

>>56979060
Sure, it will be enough to run it, but not run it well. 6GB is the bare minimum to use virtual machines.

>>56979065
Going to check it out, thanks.
>>56979069
Sadly I cannot use windows 7 (software limitations) and 8.1 is slow as nails too. (I tested out all 3 distros.)

>>56979049
>I'd argue windows is a lot easier to use than linux, senpay :^)
Then why ARE you running linux? A fork of Arch Linux no less.
Just use Ubuntu, it was made for people like you :^)

>>56979081
No, it is much less efficient.

>>56979085
I get what you mean, but all other students run it fine with just 2GB of RAM.

File: carlton-uit-fresh-prince-haalt-vechtersbazen-uit-elkaar-video_667x1000.jpg (69KB, 667x1000px) Image search: [Google]

69KB, 667x1000px

>>56979081
>mfw samefagging this hard

>>56978874
Virtual box is 5-10 years behind pretty much every commercial consumer VM software when it comes to Windows support/performance. Virtual box is only useful for Linux VMs

>>56978874
Disk usage is your bottleneck. Get an SSD.

Also VMs are always sluggish unless you do a GPU passthrough.

>>56979089
>cannot use windows 7 (software limitations)
What?

>>56979081
Not for VS, for virtualization...

>>56979085
thats fucking bullshit.
I ran windows 7 and sometimes 2 windows 7 virtual machines with only 4 gb of ram.
It wasnt pleasant, but if fucking worked (not all the time with both vms but with just one it ran without any problems and no virtualization tech).
You can vm with any amount of ram that is higher than what the host uses and the guest needs to load up.

>>56979110
>GPU passthrough

Alright i'll try it out

>>56979119
The software I have to use cant be used on windows 7

HyperV doesn't completely suck unless you want sound, then it's shit tier.

>>56979109
I use vbox to make an arch vm with kde as a de, it lagged like shit and the mouse didnt show up in fullscreen mode, this is with the vbox guest drivers.

>>56979200
>with kde as a de

There's your problem, you weren't running a tiling WM. Everyone knows that's the only thing you're allowed to use on Arch :^)

>>56979223
rules are meant to be broken
>tfw you dont know the difference

>>56978874
It's W10 that's shit, not your PC or virtualbox

>>56979244
>rules are meant to be broken
"You will immediately cease and not continue to access the site if you are under the age of 18."

>>56979259
Is that what your last ban message said?

windows 10 runs like shit native too

Use VMware. Also you should use at least 4 GB for the VM - Visual Studio doesn't run well on 2 GB even on a native machine.

An SSD wouldn't solve anything in this case - only technology imparted retards think it's a magical solution to all performance problems.

>>56979283
I wouldn't know, I'm not an underage edgelord :^)

>>56979081
Lets just repeat the bigger factors that you conveniently chose to ignore.

No VT-d
no SSD
no vPRO
Probably does not have VT-x enabled in BIOS

File: 1462217327936.jpg (343KB, 1200x1074px) Image search: [Google]

343KB, 1200x1074px

Thanks for all your suggestions. I'm going to try installing windows alongside manjaro now and see if that helps. If it doesn't I'm going to buy a new laptop.

>>56979195
>>Alright i'll try it out
... on your shit tier manjaro laptop?

>>56978874
>HITACHI HTS545050 (5400 RPM

Found your issue.
I put up with this shit for years (even host machine would be a fuck up when VM was in use), now I have been using SSD and never had any such problems since.

>>56979377
sure fooled me

>>56979393
>Vt-d
VT-d is only poses a problem if you virtualize a number of machines
>no SSD
might help, but don't think its the main problem
>no vPRO
Fine, I don't have vPRO
>no vt-x enabled
Virtualization is enabled in BIOS, I check numerous times, it's an umbrella term and i'm 100% sure my cpu has vt-x

>>56979425
I wish I had as much time to waste as you.

>>56979425
>can't into VM
>buy new laptop instead
And that is going to help your incompetence how exactly?

>>56979505
Instead of resorting to ad hominems, try some constructive criticism. As has been pointed out though, the hardware used is not sufficient for virtualization

>Windows VM on Linux to run Visual Studio
>5400RPM HDD
>Borderline marginal CPU & RAM

>Why is virtualbox such a slow piece of garbage?

Nigga whut

>>56979497
You're shitposting on a mongolian badger grooming board, surely you have some time to waste :^)

>>56979425
If you want any chance of having VS not run like shit, then you should just dual boot instead of running a VM

>>56979477
What host os are you using? use kvm and qemu. vbox is hit and miss with things like this.

>>56979570
Manjaro. Installation of windows was slow as fuck in virtualbox so i'm going to opt for a dualboot like >>56979553 proposes

>>56978874
1) Your hardware isn't up to snuff for running a Win10 VM as a client OS.
2) Visual Studio is a fucking resource hog, it shouldn't be but it is fucking Himmler at Dinner.
3) You need to be wary about RAM allocation, because it'll start trashing your HDD in some cases (even if usage is low)
4) Look at allocating additional processor cores to the VM
5) Trim the VMs fat (stop Defender), look at an alternative IDE, MonoDevelop is reasonable (but VS is king for DotNET for Obvi reasons.)

>>56978913
Win 10 should ideally have 4Gb or more.
Dual core or better processor.

>>56979518
>the hardware used is not sufficient for virtualization

But it is, OP just chose to conveniently ignore or at least not get back on
>Use at least 4GB of ram for the VM
>Try GPU passthrough
>Use VMWare, better multi-core support
Instead he chooses to dedicate only a very limited part of his available resources to the VM because "that's what the minimum requirements are"
We're here to provide options and resources, not to spoonfeed OP

>>56978930
>>56978930
No, whats happening is that OP has allocated such a small amount of RAM that it is performing something called disc thrashing where the VM starts using HDD as RAM killing IO.