- #Virtualbox 64 bit problem install#
- #Virtualbox 64 bit problem update#
- #Virtualbox 64 bit problem windows#
#Virtualbox 64 bit problem windows#
If you are using bridged networking and the host can communicate directly with the guest Windows OS, you don’t need to use VRDE. In the case of Windows guests, I say ‘don’t necessarily need’ because it might be required in some cases. You might decide to use VRDE and enable its Remote Desktop server if you want to use RDP to connect to a Linux VM. But if you are connecting to a Windows guest, you don’t necessarily need VRDE and if you are not using VRDE, you don’t need to configure the Remote Display settings in VirtualBox Manager for the guest VM.
#Virtualbox 64 bit problem install#
VirtualBox has a feature called the VirtualBox Remote Desktop Extension (VRDE) and it is only available if you download and install the VirtualBox Extension Pack. And naturally, you might want to access a VirtualBox VM from devices other than on which the guest VM is hosted. Connecting to a VirtualBox VM using Remote Desktop is the easiest way around the problem. There are also some other problems to be aware of like trying to use VMs with a large screen resolution and installing 64-bit OS guests if another hypervisor, such as Hyper-V, is also installed on the system.īut primarily the main reason that I wanted to connect via Remote Desktop initially was because it isn’t possible to use higher display resolutions in VirtualBox VMs when accessing them using VirtualBox Manager. But in addition to some issues with network performance in Windows guests, which I address in a separate article, enabling access to virtual machines (VM) using Remote Desktop isn’t as straight forward as with Hyper-V.
I can’t say that one is necessarily better than the other – it’s swings and roundabouts. I switched from client Hyper-V to VirtualBox earlier this year and it has mainly been a good experience. Since it works now, the bug could be closed again.Oracle VirtualBox is a type-2 hypervisor that is popular on Windows, macOS, Linux, and Solaris. Therefore I could not do exactly the same installation (I selected the Direct3D support during the graphical installation process). I had to use the /S option as well otherwise, a screen poped up with the available command options (as if I tried a badly formated command) (although the restart of the Guest restarted the host as well, I will check if it is a configuration failure or if there is any other bug opened about this point) Well the installation with /I worked without any problem and the fullscreen will resize the guest as expected.
#Virtualbox 64 bit problem update#
I will update with the installation log of the guest additions on the guest soon
0 kommentar(er)
