virtualbox.org

I wanted to add vbox GA to be current with the updated vbox version.

Go easy on me here I am new to linux but have been a sysadmin on windows for many years... First time poster here but I think this might be a bug.

Host:
Windows 7 Pro
32 GB RAM
8 core CPU AMD-V

Guest ubuntu 16.04 desktop

I have snapshots with GA 5.0.24_108108 on them that run fine. Video is good, mouse pointer is fine.. Super snappy. But I did an update of the vbox main sw to r108355 and also added the extension pack r108355 for the USB 3.0 functionality.

runs fine
bigboy@sysbackup:~$ sudo /usr/sbin/VBoxService --version
[sudo] password for bigboy:
5.0.22r108108


I looked closely at what happened in terminal when I "inserted" the vbox guest additions r108355 CD:
Verifying archive integrity... All good.
Uncompressing VirtualBox 5.0.24 Guest Additions for Linux............
VirtualBox Guest Additions installer
Removing installed version 5.0.22 of VirtualBox Guest Additions...
Removing existing VirtualBox non-DKMS kernel modules ...done.
update-initramfs: Generating /boot/initrd.img-/4.4.0-21-generic
update-initramfs: Generating /boot/initrd.img-/4.4.0-28-generic
update-initramfs: Generating /boot/initrd.img-/4.4.0-31-generic
Copying additional installer modules ...
Installing additional modules ...
Removing existing VirtualBox non-DKMS kernel modules ...done.
Building the VirtualBox Guest Additions kernel modules
The headers for the current running kernel were not found. If the following
module compilation fails then this could be the reason.

Building the main Guest Additions module ...done.
Building the shared folder support module ...done.
Building the graphics driver module ...done.
update-initramfs: Generating /boot/initrd.img-4.4.0-28-generic
Doing non-kernel setup of the Guest Additions ...done.
You should restart your guest to make sure the new modules are actually used

Press Return to close this window...

***

well hmm since with 16.04 ubuntu uses systemd .. I would venture a guess that if I reboot after the above.. yup FAIL!
NMI-Watchdog bug soft lockup failed after 22s and then something about jiffies.. Some research showed something about cpu clock cycles being out of sync
The question is for us ubuntu folks running 16.04 which GA install script should we be running?
Is anyone else having these issues?
Cheers.

I also noticed that if I choose to add USB 3.0 under settings to a machine after updating GA r108355. I will get the error

First of all a couple of minor points/corrections:

• You referred to "5.0.24_108108". That was most probably a typo, because it is actually is "5.0.22_108108". You had me going "???" for a moment there...
• You don't have to 'sudo' to get the installed version (sudo /usr/sbin/VBoxService --version). Generally speaking it's best to avoid sudo at all costs, if you can.

You have a clear message that the headers of your current kernel were not found. Make sure that you have installed the kernel headers for the running kernel. It seems that you have at least 3 different kernels (4.4.0-21, -28 and -31). Yet from the "update-initramfs" message, it seems that you've booted with 4.4.0-28, even there is already an update in your system. You might want to clear/purge your system from older kernels.

thinkthoughtsforever wrote:First time poster here but I think this might be a bug.

Way too early to call it a bug.

Clean up your system. Follow the instructions in Chapter 4.2.2. Guest Additions for Linux. If you still have a problem, read the following: Minimum information needed for assistance. For the VM log file ("VBox.log.zip"), here's what you do:

1. Start the VM. Not from a saved or suspended state. Clean start.
2. Take the steps required to generate/observe the error.
3. Record the error message. EXACTLY. Post a screenshot if you have to.
4. Shut down the VM (if it hasn't aborted by itself). Not suspended, not paused. Shut down. If you can't shut it down by normal means, close the VM window and select "Power off".
5. Right-click on the VM in the VirtualBox Manager.
6. Select "Show Log..."
7. Save it (just the first log, VBox.log), ZIP it and attach it in your response (see the "Upload attachment" at the bottom of the form).