id summary reporter owner description type status component version resolution keywords cc guest host 443 Some situations make VirtualBox think a session on a powered-off vm is being openned/closed and a full system restart is required gbuonfiglio "I was creating a new vm using the CLI (VBoxManage) instead of the GUI (VirtualBox) and I mistyped the ""ostype"". VBoxManage hanged and I hit CTRL-C to stop it. When I try to issue anything for this new vm I got: [!] FAILED calling virtualBox->OpenSession(session, uuid) at line 3206![[BR]] [!] Primary RC = 0x80070005[[BR]] [!] Full error info present: true , basic error info present: true [[BR]] [!] Result Code = 0x80070005[[BR]] [!] Text = A session for the machine 'w2kad1' is currently open (or being closed)[[BR]] [!] Component = Machine, Interface: IMachine, {0332de0e-ce75-461f-8c6f-0fa42616404a}[[BR]] [!] Callee = IVirtualBox, {d1a2295c-d257-4a4c-a9a6-843d87db6f45}[[BR]] This is really annoying because when this happens I need to shutdown every vm and kill VBoxSVC. If I kill VBoxSVC the vms continue to work but I cannot manage them. " defect closed other VirtualBox 1.4.0 fixed other other