Opened 8 years ago
Closed 8 years ago
#15868 closed defect (worksforme)
"double free or corruption" error when installing guest additions
| Reported by: | Nils | Owned by: | |
|---|---|---|---|
| Component: | guest additions | Version: | VirtualBox 5.1.4 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Linux |
Description
Windows 7 host (on Lenovo x250 Laptop) Debian guest The issue started with 5.0 or 5.1 (not quite sure, things seem to work), and happened on several VMs (all Debian) with several updates (5.1.2, 5.1.4)
/media/cdrom$ sudo sh VBoxLinuxAdditions.run Verifying archive integrity... All good. Uncompressing VirtualBox 5.1.4 Guest Additions for Linux........... VirtualBox Guest Additions installer Removing installed version 5.1.2 of VirtualBox Guest Additions... vboxadd.sh: Stopping VirtualBox Additions. update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64 update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64 vboxadd-service.sh: Stopping VirtualBox Guest Addition service. *** Error in `systemctl': double free or corruption (fasttop): 0x00007f233d4bd2a0 *** Copying additional installer modules ... Installing additional modules ... vboxadd.sh: Building Guest Additions kernel modules. vboxadd.sh: You should restart your guest to make sure the new modules are actually used. vboxadd.sh: Starting the VirtualBox Guest Additions. You may need to restart the the Window System (or just restart the guest system) to enable the Guest Additions. /media/cdrom$ uname -a Linux dweb642 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02) x86_64 GNU/Linux
Googling "double free or corruption" seems to show it might be a systemd issue...
/media/cdrom/$ cat /var/log/VBoxGuestAdditions.log vboxadd.sh: failed: Cannot unload module vboxguest.
Attachments (1)
Change History (4)
by , 8 years ago
| Attachment: | vboxadd-install.log added |
|---|
comment:1 by , 8 years ago
More research revealed this Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764613
This bug is closed, and indicates the issue is fixed in systemd 220-2, and I'm only at 215-17+deb8u4.
Perhaps the only thing "wrong" in vbox is not catching the return code of something and showing that an error happened?
comment:2 by , 8 years ago
Installing systemd 230 from jessie-backports resolves the issue.
Please close this bug. Thanks.
comment:3 by , 8 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Yes, I will close this ticket. Regarding not catching the return code: This is hard to do as the install contains of several scripts. We will try to improve the error handling further.
vboxadd-install.log