VirtualBox experiencing delays across every operating system version.
VirtualBox experiencing delays across every operating system version.
So, here is my predicament. Regardless of whether I was using Ubuntu, or Antergos, or now Gentoo, VirtualBox was always slow, painfully so. You might say: "You merely do not have hardware that is adequate for your goal.", however I find that to not be true, as VMware Workstation Pro ran all guests smoothly. Considering it's mostly graphical slowness, even though moving through workspaces outside of the virtual machine is still smooth, my assumption is that the fact that VMware WP allows to allocate more than 256MB of video RAM allows for guests to run smoothly. On the other hand, I see many people on YouTube running guests in VIrtualBox smoothly, so I have turned to this forum now, as I have been searching for an answer for nearly two years now without any success. I appreciate any and all help provided! EDIT: The datasheet for my laptop is in the PDF provided below. c05342156.pdf Edited April 21, 2019 by elsandosgrande I've forgotten to mention what the PDF was for.
It seems to be a QEMU front-end configuration, though it runs slowly. The maximum allowed size in the settings is 256MB, which I've set myself. I've installed virtualbox-guest packages on a Ubuntu VM using Disco. The SVM CPU flag is configured in /etc/portage/make.conf and virtualization is turned on in UEFI. Regarding Xen, beyond the VB option, you can use KVM via VirtualBox, though it's more commonly linked with QEMU.
I reviewed the original request... The main idea seems to be about VirtualBox guest drivers. I don’t remember the exact versions but they’re easy to search for online. Using qxl with KVM/qemu might help. Storage performance could also be an issue—check disk usage. It might be useful to compare CPU, storage, and graphics in both environments. Apologies for the confusing message earlier.
What operating system is this guest running? I usually connect via remote desktop, which is more convenient than using the VM console. The console is mainly used during installation and management over the network. Generally, KVM-based setups perform better on Linux.
I added my own note within the quoted text. From the repository(s), amdgpu is available. Given the situation, yes, I’m using Wayland now, though it didn’t change much on Ubuntu where X still works well—especially with Antergos, except after switching to KDE and X has been problematic, particularly with KWin under X, which crashes due to OpenGL issues regardless of version. Wayland handles touchpads and gestures better. As for Linux guests, I can’t remote effectively from the same machine running the VM. QEMU is just as slow, so KVM offers little improvement. I’m not in a position right now to dive deep into QEMU setup because I still have school until mid-June. Haiku’s default configuration runs very slowly, and dragging windows feels laggy; opening the full application list in GNOME takes about three seconds. It’s not the CPU that’s the issue, but the vCPU usage spikes sharply when moving windows, sometimes reaching 100%, unlike in VMware Workstation Pro.
It can be linked through the network similarly to other systems. Use SSH or VNC for connection.
This option isn't suitable for my needs and doesn't clearly show why VMware outperforms VirtualBox and QEMU in most situations. Appreciate the idea!