Multiple Instances of VirtualBox
-
tafeteach
- Posts: 6
- Joined: 3. Aug 2010, 11:20
- Primary OS: MS Windows 7
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Linux, Windows XP, Windows Server 2008
- Location: Sydney, Australia
Multiple Instances of VirtualBox
I use VirtualBox 4.2.12 on a Windows 7 Pro 64bit host system. I have noticed that if I start a second instance of VirtualBox running and then start a VM in that second instance that when I shut down the VM, VirtualBox crashes. Has anyone else experienced this? Is there a way to prevent a second instance of VirtualBox starting up? Or, am I barking up the wrong tree here and the crash is unrelated to multiple instances? Any ideas? Thanks
-
noteirak
- Site Moderator
- Posts: 5231
- Joined: 13. Jan 2012, 11:14
- Primary OS: Debian other
- VBox Version: OSE Debian
- Guest OSses: Debian, Win 2k8, Win 7
- Contact:
Re: Multiple Instances of VirtualBox
Are you talking about another Virtualbox Manager instance? or another instance of the VM?
An exact step by step of how you acheive this, aswell as the exact crash details aswell as the VM log would help.
An exact step by step of how you acheive this, aswell as the exact crash details aswell as the VM log would help.
Hyperbox - Virtual Infrastructure Manager - https://apps.kamax.lu/hyperbox/
Manage your VirtualBox infrastructure the free way!
Manage your VirtualBox infrastructure the free way!
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Multiple Instances of VirtualBox
Crash message?
I believe he is talking about when he accidentally creates a second instance of the manager, then launches a VM from the second instance.
However: it would be useful to have it confirmed that the VM being launched from the later instance is not the same VM. Although that shouldn't be possible since there will still only be one instance of the VBoxSVC background process.
Also, a log would be useful to establish that the cause is not lack of memory.
I believe he is talking about when he accidentally creates a second instance of the manager, then launches a VM from the second instance.
However: it would be useful to have it confirmed that the VM being launched from the later instance is not the same VM. Although that shouldn't be possible since there will still only be one instance of the VBoxSVC background process.
Also, a log would be useful to establish that the cause is not lack of memory.