ubuntu linux-image-4.4.0-31-generic cpu stall vbox 5.1

[taz]

todays update of ubuntu kernel broke boot ...

fwiw 4.4.0-28 still works

[taz]

see pic

[taz]

oh yeah, I can post vbox log internally, ping me on IM or email me, this box which hits the issue is not public

[taz]

more pics

[taz]

it most probably is an ubuntu bug, so I just did spam Kamal from http://packages.ubuntu.com/xenial/linux ... 31-generic ...

[JohnVeness]

I was hit by this too. Choosing the previous kernel (4.4.0-28) from grub boots OK.

Is there an Ubuntu launchpad bug filed for this yet that I can track?

[taz]

no bug yet, I just mailed Kamal, so feel free to open a bug if you know how

[Sagypt]

Me too

[Perryg]

Post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

[Sagypt]

First boot: the VM freezes, I got the log "attachment_01.txt". Then, on the bottom bar I clicked: Machine > Reset, hence second boot: the VM starts, I got the log "attachment_02.txt"

Thanks

[Perryg]

OK so if I understand you can get the guest to boot after resetting the guest. What I have seen in the past is on a warm boot this can happen but very rarely a cold boot. As far as I have been able to isolate it is the OS does not properly clear the initramfs on warm boot and it shows as corrupt. resetting does allow it to boot most of the time. I have not however been able to isolate it to the OS or VBox. Feel free to raise a ticket at bugtracker.

[MichaelW]

Hello,

I have the same problem here so I created a serial device in my Virtualbox-settings and logged the complete startup of the linux-kernel to the file attached.

Because the problem seems to be connected to xhci I disabled USB 3.0 and enabled USB 2.0. With USB 2.0 the kernel boots, with USB 3.0 it does not.

I hope this helps finding the cause of the problem.

Michael.

[Sagypt]

@MichealW

Hi,

interesting. How I can reproduce what you made? You can give me detailed steps?

Thanks



Note: I confirm: into VM settings, switching from USB 3.0 to USB 2.0 bypass the problem.

[MichaelW]

Hi everyone,

I only have the german version of virtualbox installed here, so the options might be called different than my translation.

- Go to the settings of your vm.
- Choose "Serial ports"
- Enable Serial port 1
- Change "Port mode" to "file"
- Enter a filename in path. (maybe you need an absolute path like D:\console.log on windows)

- Now start the vm. Press ESC while booting to get into grub.
- Press "e" to edit the boot coammnd
- Go to the line beginning with "linux"
- Delete the kernel-paramter "quite" in this line
- Add new kernel-parameters "console=ttyS0,115200n8" and "softlockup_panic"
- Press F10 to boot.

You don't get any output on the vm screen now and booting takes longer, because etherything is redirected to the serial port. After some minutes stop the vm and look at the logfile. You see all the messages there. (The file is delted on every new start of the vm)

The kernel parameter "softlockup_panic" is documented in the linux kernel tree in file "Documentation/lockup-watchdogs.txt" (The forum does not allow me to post a link yet)

[taz]

interesting,
works for me as well
I switch from usb 3.0 to usb 2.0 and the 31 kernel works ...