{"id":2062,"date":"2016-03-15T09:00:09","date_gmt":"2016-03-15T16:00:09","guid":{"rendered":"http:\/\/www.coretechnologies.com\/blog\/?p=2062"},"modified":"2022-05-01T22:27:43","modified_gmt":"2022-05-02T05:27:43","slug":"virtualbox-vm-powered-off","status":"publish","type":"post","link":"https:\/\/www.coretechnologies.com\/blog\/alwaysup\/virtualbox-vm-powered-off\/","title":{"rendered":"Why does my VirtualBox VM say “Powered Off” when it’s running as a Service with AlwaysUp?"},"content":{"rendered":"
\"VirtualBox<\/div>\n

We’re big fans of Oracle’s VirtualBox<\/a> software. It’s powerful and free, and it enables our small company to efficiently test and validate our software on various versions of Windows without having to invest in costly, dedicated hardware.<\/p>\n

However, we noticed a strange problem with VirtualBox last week. After following our tutorial to setup a VirtualBox Virtual Machine (VM) as a Windows Service with AlwaysUp<\/a>, we noticed that even though the machine was working normally, the VirtualBox Manager application incorrectly listed the VM as “Powered Off”. But it had been on for more than 10 days!
\n
\n\"VirtualBox<\/a>\n<\/p>\n

And it wasn’t just the VirtualBox Manager. Even the powerful VBoxManage command line utility<\/a> thought that our VM wasn’t running:
\n
\n\"VBoxManage<\/a>\n<\/p>\n

However, when we ran a command prompt in Session 0<\/a>, VBoxManage saw the VM there:
\n
\n\"VBoxManage<\/a>\n<\/p>\n

So it seems that the VirtualBox tools can only see virtual machines running in the same session that they are in.<\/b><\/p>\n

Therefore, we simply can’t rely on the state shown in the VirtualBox Manager application when running our VM in the background (in Session 0) with AlwaysUp.<\/p>\n

Bummer. \ud83d\ude41<\/p>\n