Hi, i'm Ale from Italy
I've installed virtualbox on ubuntu 15 64 bit
I'm using a Windows 7 64 bit virtualized with virtualbox
When i try to run another vm, after 20/30 secs virtualbox automatically close the windows machine
Why? I would like to use the windows machine and another machine!
On my pc i've 8 gb of ram so i don't think that the problem is low memory
Can anyone help me?
Thanks
Ale
Multi VM crash!!!
-
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: Multi VM crash!!!
Please post a VM log file of the VM that fails. With the VM fully shut down, right click and "Show Log" in the GUI, save "VBox.log" (ONLY) to a zip, and attach the zip here.
Re: Multi VM crash!!!
Hi! here is the zip filempack wrote:Please post a VM log file of the VM that fails. With the VM fully shut down, right click and "Show Log" in the GUI, save "VBox.log" (ONLY) to a zip, and attach the zip here.
Thank you
Ale
- Attachments
-
- log.zip
- (19.36 KiB) Downloaded 7 times
-
socratis
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Multi VM crash!!!
First and foremost, you're using the Ubuntu fork of VirtualBox. I'll give it a shot of replying to you, but if you want to continue this discussion you have to install the official VirtualBox from https://www.virtualbox.org/wiki/Downloads
This the first VM that you launched. If you have configured your 2nd VM with the same settings, yes, it's going to abort. Here is why:
- You assign 3072 MB RAM + 256 MB VRAM + overhead =~ 3.5GB, times 2 VMs =~ 7 GB. You're getting really close to what you have on your host. Your host is going to starve.
- You have 4 CPUs in your host. You assigned 4 vPCUs to the VM. Plus another 4 to the second VM? Well, you see the problem, right? Your host is definitely going to starve.
What you can do is to lower your VM's RAM to a max of 2048 (if not 1536), plus 128 VRAM. Take the number of vCPUs to 1. See if that works... Oh, and BTW, it's always a good idea to keep a system monitor open to watch your system.
This the first VM that you launched. If you have configured your 2nd VM with the same settings, yes, it's going to abort. Here is why:
- You assign 3072 MB RAM + 256 MB VRAM + overhead =~ 3.5GB, times 2 VMs =~ 7 GB. You're getting really close to what you have on your host. Your host is going to starve.
- You have 4 CPUs in your host. You assigned 4 vPCUs to the VM. Plus another 4 to the second VM? Well, you see the problem, right? Your host is definitely going to starve.
What you can do is to lower your VM's RAM to a max of 2048 (if not 1536), plus 128 VRAM. Take the number of vCPUs to 1. See if that works... Oh, and BTW, it's always a good idea to keep a system monitor open to watch your system.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.