[SOLVED] VM negatively affects Linux host with blank screen saver
Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
VM negatively affects Linux host with blank screen saver
I came across an interesting effect with VirtualBox (Version 3.2.6 r63112 running on a CentOS 5.4 host) wherein a VM without Guest Additions can negatively impact the host if a screen saver is set to blank. No other hosts have been tested, and the symptoms are intermittent. I have not gotten this work using an active screen saver.
Here's how it works:
When the VM is running and has the mouse captured, after the screen fades the host will no longer respond to mouse or keyboard input. Pressing the host key to release the mouse has no effect.
At first I recovered by by pressing CTRL-ALT-BKSP to forcibly restart X, but this aborts all other VMs and GUI applications, which is undesirable.
A better work around I've found was to press CTRL-ALT-F1 to log into a separate console. Then, find the VM of interest:
Tiny Core was the VM to have the mouse captured, so:
[roger@localhost ~]$kill 10467
After this you can press CTRL-ALT-F7 to get back to the GUI to unlock the screen. The VM that was killed will show as aborted in the VM Virtual Box Manager.
I didn't like abruptly killing Tiny Core though, so I found an alternative. The best solution in this situation would be to use VirtualBox's own command line, wherein you can do just about anything that you could with VM Virtual Box Manager. Being that we cannot interact with the guest to save any data, the best way to shut the process down is by saving the state using “VBoxManage controlvm <uuid>|<name> savestate”.
Or in my case...
[roger@localhost ~]$VBoxManage controlvm LFS_Tiny savestate
Oracle VM VirtualBox Command Line Management Interface Version 3.2.6
(C) 2005-2010 Oracle Corporation
All rights reserved.