Opened 7 years ago
Last modified 7 years ago
#17155 new defect
Running VirtualBox on Ubuntu 17.04 with guest Ubuntu 16.04 crashes VM during apt-get update
| Reported by: | apatrida | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.1.28 |
| Keywords: | crash aborted ubuntu apt-get | Cc: | |
| Guest type: | Linux | Host type: | Linux |
Description
I setup a pretty empty VM of Ubuntu 16.04 inside of a host 17.04 running VirtualBox.
When executing the command sudo apt-get update the VM crashes and goes into "aborted" state. There appears to be no work-around, and nothing in the apt logs of interest.
Seems similar to this StackOverflow post: https://stackoverflow.com/questions/30889170/vagrant-enters-aborted-state-during-apt-get-update
The process to create my VM is using Packer, extending a base image from: https://app.vagrantup.com/box-cutter/boxes/ubuntu1604
and then running a few file copy commands, and then finally "sudo apt-get update" and partway through the update the VM vanishes, and is in "Aborted" state.
The same VM builds fine on Mac OSX as the host, but fails when Ubuntu is the host.
Attachments (1)
Change History (4)
by , 7 years ago
| Attachment: | 2017-10-11-05-32-53.log added |
|---|
comment:1 by , 7 years ago
00:00:01.829530 DMI Product Name: VMware Virtual Platform
Are you running this inside a VM, i.e. nested virtualization?
00:00:01.829570 Host RAM: 971MB total, 610MB available 00:00:02.032855 RamSize <integer> = 0x0000000100000000 (4 294 967 296, 4 096 MB, 4 GB)
You allocated 4 GB to your guest. You only have 610 MB available and 971 MB (!?!) total. Do you see the problem? Plus, 971 MB? I'm asking again; is this nested virtualization? If so, you're out of luck.
May I suggest something? It's usually better and faster, if issues like this one (configuration, question) get first addressed in the VirtualBox forums. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".
comment:2 by , 7 years ago
Yes, this is Ubuntu within VMWare building a VirtualBox VM with packer.
Gotcha, it seemed consistently a bug at the time, will move it to forums.
comment:3 by , 7 years ago
No need to. You'll get the same response; nested virtualization is not supported at the time. If you get this error with a straight installation of Ubuntu on the host that's running VirtualBox directly, then we can talk about it. Plus you started the whole description of the ticket wrong:
I setup a pretty empty VM of Ubuntu 16.04 inside of a host 17.04 running VirtualBox.
You didn't. You setup a pretty empty VM of Ubuntu 16.04 inside of a host running VMWare, running Ubuntu 17.04, running VirtualBox.
This ticket should be closed as "Invalid".
virtualbox log file