You are not logged in.
I need to install a virtual machine on Arch to test some software that runs only on windows. Having never used vmware or virrtualbox I would like to know which is better to install in your opinion.
Thank you
Intelligence is not making mistakes, but find out how to profit immediately.
Offline
Both often have trouble with the versions of software (like kernel) archlinux uses , sometimes the best answer is neither and a 3rd is a better solution (often qemu) .
You need to tell more about your hardware, goal and the software you want to run (including the windows versions) .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Thank you for your reply. :-)
That is the hardware:
CPU: AMD Ryzen 5 3400G with Radeon Vega Graphics
RAM: 64 GB
Multiple disk storage space (hdd and ssd) 4TB
I should virtualize windows 10 to test a free 3D modeling software like cad-cam (only for Windows). I don't need to use external devices, but make sure it runs smoothly and then I can install it on a working machine with Windows 10.
Intelligence is not making mistakes, but find out how to profit immediately.
Offline
I never had any issues with virtualbox. It's straightforward to install and super easy to use. It does support 3D but how good I don't know. You also have to install a cd package, called virtualbox-guest-iso. It's the separate package, available in repos too. You need to mount it as a drive inside Win and install the goodies.
Last edited by maboleth (2023-02-18 09:33:10)
Offline
Thank you for the info. :-)
Intelligence is not making mistakes, but find out how to profit immediately.
Offline
3D modeling software tends to depend heavily on gpu capability* it won't run well on the virtual videocard provided by virtualbox, vmware or others .
It sounds like this VM is intended for testing / experimenting , not for heavy use of the software ?
* about 10 years ago I was asked to improve autocad performance on 3 brand new pc systems were autocad ran slower then on the old systems they had replaced.
Investigating showed that the old systems had more memory then the new ones and high end quattro videocards that were much younger then the systems themselves.
After adding those cards (and extra memory) to the new systems they performed well.
Last edited by Lone_Wolf (2023-02-18 13:03:01)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
It sounds like this VM is intended for testing / experimenting , not for heavy use of the software ?
Yes, you just need to test this new software to make sure it doesn't give problems. If ok, it will then be installed on the working machine
Intelligence is not making mistakes, but find out how to profit immediately.
Offline
Then the performance is not an issue.
A downside of virtualbox is that it requires host and guest to run the exact same version of the virtualbox tooling.
Since virtualbox is in the repos, it will be updated often and fast requiring the guest to also be updated.
VMware is in AUR and is available for multiple versions, which is more work initially but gives more control over the version to use and when to upgrade .
Last edited by Lone_Wolf (2023-02-22 11:01:22)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
A downside of virtualbox is that it requires host and guest to run the exact same version of the virtualbox tooling..
Huh... are you sure about this? For me, on Linux host and Windows guest, if I update host VirtualBox and the tooling installed on Windows becomes out date it will just warn me via a tray balloon, but the tooling will continue to function, at least for a Windows guest.
Offline
I have seen / participated in threads about virtualbox where discrepancies between host and guest vbox versions caused problems.
And i'm not talking about major or minor version diferences but differences in the 3rd number.
Atleast in versions 5.x and 6.x this happened, haven't seen any with 7.x sofar.
It is possible vbox developers have improved how they deal with changes that break compatility.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Thank you all very much for the information ;-)
Intelligence is not making mistakes, but find out how to profit immediately.
Offline