For a project I was given a virtualbox image to work on. I don't have virtualbox but opened it in VMware and it works great except that in full screen the vm stays small and in the middle. I tried changing the autosize to stretch but it turns out obviously distorted and hard to work with. How do i get the fullscreen to work properly?
You probably lack VMWare Tools. You can install it with VM > Install VMware Tools.
I had to change the display resolution within the OS, though I thought it should have done that automatically
Related
Everything used to work fine, but I haven't been using Virtual Box for several weeks. Now all of the sudden, I get the following exception when trying to start my Windows 10(32-Bit) VM. Note - Things were working fine several weeks ago. As far as I can tell, I haven't changed anything on my system that would cause this. The exception details are as follow:
VirtualBox - Error In supR3HardenedWinReSpawn (rc=-5640)
Please try reinstalling VirtualBox. where supR3HardenedWinReSpawn
what: 1 VERR_SUP_VP_THREAD_NOT_ALONE (-5640) - Process Verification
Failure: The process has more than one thread
I have been researching this for some time, to avail. Any help would be greatly appreciated.
There is a workaround:
Open VMbox manager
Run your VM with option "Detachable start"
Wait a while and then use "Show" to show the screen
Detachable start option
Show the screen
My setup:
Oracle VM Box 6.0 running on Win10,
VM is Ubuntu 18.04
If you are using vagrant to boot up your Virtual machine, then in most cases the error is due to improper shutdown of the VM. A fix that worked for me is to execute vagrant halt or similar commands multiple times until you have a clean boot.
In case anyone is in the same predicament, I will share what finally fixed my issue. I found a post during my hours and hours of searching that said you have to enable virtualization in BIOS settings. I checked my machine and virtualization was enabled, so I went on searching. At a loss for what to try next, I finally tried turning virtualization off, just to see. No change, but when I went to turn it back on, just as a flook I turned Turbo off, and what do you know - All of the suddent I can start my VM. So the solution, in case it saves someone time:
Uninstall Virtual Box (Latest Version)
Reboot your machine and enter BIOS
Make sure anything with the term 'Virtualization' is turned on
Make sure anything with the term 'Turbo' is turned off
Reboot your machine
Install Virtual Box
Hopefully this saves some poor soul what I had to go through to get this thing working.
METHOD A
If you are using WindHawk, exit it and re-try.
Method B
download previous version from https://www.virtualbox.org/wiki/Download_Old_Builds
install & extensions
Try to re-run your guest OS.
Try to do these steps:
1. Uninstall the VirtualBox program.
2. In your C:\users\\ might have two folders called ".VirtualBox" and "VirtualBox VMs": Delete them
3. Restart your PC
4. Install VirtualBox again
5. Add again your VM
6. It must working fine!
These steps worked for me!
Workaround 1:
Just increase the RAM size from virtual box settings
Right Click on OS image .
Settings->System->MotherBoard
Increase the base memory
Workaround 2:
Change the Paravirtualization Interface from default to none
Right Click on OS image .
Settings->System->Acceleration
Change acceleration from default to none.
The above one's was basically a workaround , which can work in some but not in all.
The best thing would be to reinstall virtual box with latest version which virtual box has tried to rectify the bug and use the same vdi files which was made by Virtual Box .
One of the most common causes that will cause this type of behaviour is a missing driver (VBoxDrv.inf). It’s possible that due to some permission issues, the installation of this crucial driver doesn’t complete during the initial installation. In this case, you can fix the problem by installing the VBoxDrv.inf manually.
1.Fix the directory problem Press Windows key + R to open up a Run dialog box. Inside the text box, type ‘regedit’ and press Enter to open up Registry Editor. When you’re prompted by the User Account Control (UAC), click Yes to grant admin access.
Once you’re inside the Registry Editor, use the left-hand section to navigate to the
following location: HKEY_LOCAL_MACHINE\system\currentcontrolset\services\vboxdrv
After you arrive at the correct location, move over to the right-hand section and
double-click on ImagePath the path associated should be \C:\Program
Files\Oracle\VirtualBox\drivers\vboxdrv\VBoxDrv.sys
if not replace with the above path and click ok.
Install the VBoxDRV.inf OPen location C:\Program Files\Oracle\VirtualBox\drivers\vboxdrv right-click on VBoxDrv.inf and choose Install from the context menu.
Then in cmd run command "sc start vboxdrv"
Restart system. This should work.
I am having a probably trivial issue with the Cloudera Quickstart virtual machine. I tried many things out, but I don't manage to make it work. So, first, I installed the Virtualbox image on a Windows workstation which has a German standard (qwertz) keyboard.
In the virtual machine, which runs a Linux Centos, I set the German keyboard and everything works fine. Now, as the workstation is in my office, I installed TeamViewer, in order to connect from my MacBook from home. And here it comes the issue that struggles me.
The MacBook has a German keyboard and all the keys, which do not require the alt combination works fine. If I need, for example # (alt+L) or \ (alt+shift+7), or anything that requires the alt combination, nothing appears on the Centos (in the Windows workstation it would correctly appear!). Could you imagine to code without \ ~ # ??
I tried also to install a German(Mac) keyboard and also a screen keyboard (florence) in the Centos and they also do not work properly. Is it a TeamViewer issue or a VirtualBox issue? How can I solve it?
Any help is appreciated!
I figure out that is a Virtualbox issue, that takes the keyboard configuration of the host in which is installed, in this case Windows 10. I could not find a simple way changing the keyboard setting in the Centos machine run via the Mac Os in TeamViewer to make it work. So, as workaround, I opted for using Docker Cloudera Quickstart rather than the VM. And everything works fine and can happily type all the #~|\ that I need.
I'm happily using x2go to connect to a remote Ubuntu Server 16.04 with XFCE installed from my local pc with a local resolution of 1920x1080 on a HiDPI screen (13''). If I run the x2go client from a virtualized Linux (Linux Mint 18.03 with XFCE), everything works well and I can see a really sharp image of the remote desktop. Problem is, when I try to connect directly from Windows 10 the image is blurred and the resolution is wrong. I tried to play around with the x2go client settings but no way, the image is always terrible. I also tried to use PyHoca and different X-servers but the result is the same.
Is it a well-known problem? Any suggestion on how to fix it?
Thanks in advance.
I had a very similar problem: A Dell laptop with an Nvidia graphics card, having a resolution of the built-in flat panel of 1280x800. I connected this to an external screen with HDMI with a resolution of 1920x1080. However, X2Go seemed to pick up the resolution of the built-in screen instead of the actual screen, making everything seem blurry (interpolating 1280x800 to 1920x1080).
This is what fixed it for me: Navigate to the C:\Program Files (x86)\X2GoClient\VcXSrv\ directory in Explorer. Select the vcxsrv.exe file and right-click it, choosing Properties from the popup menu. Go to the Compatibility tab, and in the Settings section there, select the option "Override high DPI scaling behavior. Scaling performed by:" and then select "Application" in the combo-box below.
Restart the X2Go Client to have its X server start with this new setting.
This fix also solved X2Go Windows Client crashes in my setup.
I have basically the same scenario: connecting from a high DPI Windows laptop to KDE on Debian, in my case for Desktop Sharing. The client would connect okay, but display only a portion of the remote host's screen.
Keyboard shortcuts would not scroll the client window.
Any attempt to show more (maximize, go full screen, click-and-drag client window border) would seem to work for a second, then crash.
The Compatibility scaling change fixed the instability - no more crashes, yay! - but did lead to slow repaints as noted by Algeboy.
Upgrading to a newer version of VcXsrv also did not resolve the crashes - Compatibility change still required, but screen repaints are quicker.
To upgrade, download and install the latest VcXsrv in its own directory. Using Explorer or whathaveyou, apply the HiDPI setting to vcxsrv,exe.
Start x2go client but don't start a session. Click Options, Settings, then X.Org Server settings tab. Select "use custom x server". Point to the newly installed vcxsrv.exe and click okay. Restart the x2go client.
This apparently takes the version from 1.20.6.0 supplied by x2go to 1.20.14.0 (2022-04).
Screen refreshes are quicker if I minimize all applications on the host, allowing it to repaint the desktop, then restore whatever I want to work on.
I'm running Windows 10 inside VirtualBox 5.1.18 on OS X 10.11.6 and after installing Guest Additions to enable bidirectional c/p the screen resolution has shrank to 800x600 and I managed to increase it to 1024x768. Even though it brings some memories of the times when I was young and restless it won't allow me to do any serious work in Visual Studio.
First time I installed them trough virtual CD-ROM and second time manually by downloading the right version from the official page.
How to fix it?
Thank you in advance.
I've searched every place I could think of, but nobody seems to have had this issue or didn't bother asking about it.
I just installed Ubuntu 11.10 freshly with the gnome fallback shell. Everything works perfectly fine, except for one thing.
My WINE applications start on the wrong screen, this isn't really a big issue, but when I drag the window to my main screen, the mouse doesn't work on the application anymore. The app doesn't freeze, and is fully responsive to keyboard input, I just can't click on anything anymore.
My specs (relevant):
- NVidia Geforce 540M
- 1 laptop screen 1366x768
- 1 Samsung Syncmaster SA550 27" - 1920x1080
Thanks in advance!
Did you create the application on a resolution smaller then the current on your pc?
If so, do the following (I have a laptop with 1366x768 on the internal monitor and 1920x1080 on the external monitor):
Open winecfg
Check the Virtual Desktop checkbox and set the size to the largest resolution you are going to use
Start the app and check if it's working properly now (You can check that with the battlenet launcher :))
Start winecfg again and uncheck the Virtual Desktop box