Tell me more ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.
up vote -1 down vote favorite

I have a Mac Mini on OS X Lion, acting as a server in which an Ubuntu virtual machine is working using VBoxHeadless. The virtual machine has network connected using NAT to the host, and there are two port forwards: 22 on guest gets to 2022 on host (SSH), and 443 on guest goes to 2443 on host (HTTPS).

On the host (mac mini), I propagated these services to the Bonjour service, so that my Time Capsule would wake my mac mini up when I access port 2022 or 2443. There is a problem though: when my mac mini wakes up, VirtualBox has put the guest to pause, but I attempt a connection to the guest, the host wakes up well but VirtualBox doesn't 'unpause' the guest.

So, after I put the host to sleep:

  • If I SSH into my host (port 22), it wakes up beautifully and I get an instant connection.
  • If I SSH into my guest (using port 2022 to host), host wakes up, but the guest remains paused, and I can't connect.

NOTE: This issue really only occurs when using VBoxHeadless, when I'm using the GUI app, it wakes up fine. The problem is the guest is a server that I want to boot up with the host, and I really don't want the UI with it.

share|improve this question
Why was this downvoted? – Pelle ten Cate Nov 10 '11 at 13:29

1 Answer

up vote 0 down vote

Have you tried scripting a:

VBoxManage controlvm "[VM Name]" resume

As part of the Mac's resume (if possible)?

share|improve this answer
I tried doing that using sleepwatcher. Still no success, but it seems that even after waking the machine up, it is not accepting connections beautifully. Is there any possibilities that a linux guest accepting connections doesn't like to be paused? – Pelle ten Cate Sep 2 '11 at 9:19
That is very possible. Another consideration may be to perform a "savestate" prior to the Mac entering sleep and then a "startvm" to restore the VM when it awakes. Not the most agile in responsiveness, but then servers should use power save techniques very sparingly - how about just powering down display along with the hard drive(s) and throttling down the processor? – user48838 Sep 2 '11 at 9:41

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.