Aravind R, this is not the right place to complain about intel-microcode
issues, please use ubuntu-bug and open a new report!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736116
Title:
[SRU] Host
Hello,
This bug is truly anoying
System details
aravind@comp:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.4 LTS
Release:16.04
Codename: xenial
aravind@comp:~$ uname -r
4.13.0-38-generic
Laptop Acer E15 E5-575G-50ZZ
Inter
Lets followup iin bug #1759829 then
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736116
Title:
[SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox
To manage notifications
Filled a bug report for Vagrant to be updated:
https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1759829
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736116
Title:
[SRU] Host with kernel
As stated on comment #100 the current vagrant version on Xenial does not
support the updated Virtualbox version. Is it planned to update
Vagrant?.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736116
This bug was fixed in the package virtualbox-ext-pack -
5.1.34-0ubuntu1.16.04.2
---
virtualbox-ext-pack (5.1.34-0ubuntu1.16.04.2) xenial; urgency=medium
* Really point to 5.1.34 source to download
virtualbox-ext-pack (5.1.34-0ubuntu1.16.04.1) xenial; urgency=medium
* New
This bug was fixed in the package virtualbox-guest-additions-iso -
5.1.34-0ubuntu1.16.04.2
---
virtualbox-guest-additions-iso (5.1.34-0ubuntu1.16.04.2) xenial; urgency=medium
* New upstream version 5.1.34
LP: #1746316 -> security patches for spectre and meltdown
LP:
This bug was fixed in the package virtualbox-guest-additions-iso -
5.1.34-0ubuntu1.17.10.1
---
virtualbox-guest-additions-iso (5.1.34-0ubuntu1.17.10.1) artful; urgency=medium
* New upstream version 5.1.34
LP: #1746316 -> security patches for spectre and meltdown
LP:
This bug was fixed in the package virtualbox - 5.1.34-dfsg-
0ubuntu1.17.10.2
---
virtualbox (5.1.34-dfsg-0ubuntu1.17.10.2) artful; urgency=medium
* New upstream version 5.1.34-dfsg
LP: #1746316 -> security patches for spectre and meltdown
LP: #1736116 -> freeze with kernel
This bug was fixed in the package virtualbox - 5.1.34-dfsg-
0ubuntu1.16.04.2
---
virtualbox (5.1.34-dfsg-0ubuntu1.16.04.2) xenial; urgency=medium
* New upstream version 5.1.34-dfsg
LP: #1746316 -> security patches for spectre and meltdown
LP: #1736116 -> freeze with kernel
This bug was fixed in the package virtualbox-ext-pack -
5.1.34-0ubuntu1.17.10.2
---
virtualbox-ext-pack (5.1.34-0ubuntu1.17.10.2) artful; urgency=medium
* Really point to 5.1.34 source to download
virtualbox-ext-pack (5.1.34-0ubuntu1.17.10.1) artful; urgency=medium
* New
Locutus's xenial-proposed fix works great for me on the stock
4.13.0-37-generic kernel on my amd64 laptop.
Here's how I installed that fix on my 16.04 machine:
Start software-properties-gtk
"Developer Options" tab
Check "Pre-released updates (xenial-proposed)"
sudo apt update
So, at the end we had zero bad reports, and tomorrow will be 10 days
since the package has been accepted in proposed (even more day if we
consider the first upload in ppa and -proposed).
Nobody complained so far, the only bug I got, is unrelated to this
upload, and affecting NVIDIA people (LP:
Hello, kbuild was useful to get virtualbox 5.1 compile, doesn't fix the issue
by itself.
Please wait for the other packages to migrate, or try the proposed pocket
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This version did NOT fix the problem for me; VirtualBox is still hanging
the computer with 4.13-series kernels.
$ dpkg -s kbuild | grep Version
Version: 1:0.1.9998svn2814+dfsg-2~ubuntu16.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug was fixed in the package kbuild -
1:0.1.9998svn2814+dfsg-2~ubuntu16.04.1
---
kbuild (1:0.1.9998svn2814+dfsg-2~ubuntu16.04.1) xenial; urgency=medium
* SRU to xenial, to make virtualbox 5.1 build correctly
* New upstream version 5.1.32-dfsg
LP: #1746316 -> security
This version fixed the crash for me, too. However, the vagrant version
1.8.1 that is shipped with Ubuntu Xenial isn't compatible:
The provider 'virtualbox' that was requested to back the machine
'default' is reporting that it isn't usable on this system. The
reason is shown below:
Vagrant has
To be honest, since this bug is already 3 months old, and the risk of
regressions is high, I would appreciate some additional days even if
nothing bad showed up so far (maybe 10-15 days would be more
appreciated).
People can still use proposed if they want a fix, I don't think few more
days can
There is no shortage of manpower in the ubuntu-sru team. As per the
Stable Release Update policy [1], every update needs to age in -proposed
for a minimum of 7 days before being considered for promotion. Since
these packages have not been driven by the security team we are handling
this update in
Is there currently some shortage of manpower in the release team or am I
overlooking another bug blocking the release?
This bug has a heat of 400+, the new version has been tested quite extensively
and the version to be replaced is also prone to security issues.
--
You received this bug
My previously reported result was on a Core i5-2520M, some deeper
testing was performed on a Celeron J1900:
Running perfectly on a 4.4.0-116 and switching to 4.13.0-37 runs stable
for about a day now. No problems noticed so far.
--
You received this bug notification because you are a member of
Currently running 5.1.34-dfsg-0ubuntu1.16.04.2. This appears to have
solved the host crash for me. I did have to manually update virtualbox-
dkms too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
so far so good!
** Tags removed: verification-needed verification-needed-artful
verification-needed-xenial
** Tags added: verification-done verification-done-artful
verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hello Stephan, or anyone else affected,
Accepted virtualbox-ext-pack into artful-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/virtualbox-ext-pack/5.1.34-0ubuntu1.17.10.2 in a few hours, and then in
the -proposed repository.
Please help us by
BTW I also tested clipboard copy-paste host-guest and vice-versa, and
VBoxClient --check3d && echo yes to see if 3d was correctly enabled
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736116
Title:
Steps performed (only on amd64 hw, no i386 testing performed).
1) Install a clean Ubuntu 16.04.4 LTS amd64 iso.
2) Reboot
3) upgrade and dist-upgrade
4) enable proposed
5) install only virtualbox virtualbox-ext-pack virtualbox-guest-utils-hwe
virtualbox-guest-x11-hwe
6) enable 3d on guest
I'll report test results on #1746316
** Tags removed: verification-needed verification-needed-artful
** Tags added: verification-done verification-done-artful
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can confirm the absence of the previous hang on a 16.04 with 4.13.0-37
kernel with the fix from the Costa's PPA. Just tested with a live cd
start, no more detailed tests.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736116
Title:
[SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox
To manage notifications
"proposed" 5.1.34-dfsg-0ubuntu1.16.04.2 works as smooth as the previous
16.04.1 for me.
** Tags removed: verification-needed-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736116
Title:
I can confirm that
virtualbox 5.1.34-0ubuntu1.16.04.2
virtualbox-guest-additions-iso 5.1.34-0ubuntu1.16.04.2
work as expected.
Host details:
$ lscpu | grep "Model name"
Model name:Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
$ uname -srv
Linux 4.13.0-36-generic #40~16.04.1-Ubuntu SMP
Tested packages:
virtualbox=5.1.34-dfsg-0ubuntu1.16.04.1
virtualbox-dkms=5.1.34-dfsg-0ubuntu1.16.04.1
virtualbox-ext-pack=5.1.34-dfsg-0ubuntu1.16.04.1
virtualbox-qt=5.1.34-dfsg-0ubuntu1.16.04.1
Host longer freezes on guest boot. Performance seems normal. Bug fixed
for me.
Tested with guest OS
I can confirm that virtualbox 5.1.34-dfsg-0ubuntu1.16.04.1 and
virtualbox-ext-pack 5.1.34-0ubuntu1.16.04.1 work on Xenial with the
Linux Kernel 4.13.0-36 without any freeze. I cannot test the other
packages or those on Artful at the moment.
Thanks for the effort to fix this!
--
You received
"proposed" 5.1.34-dfsg-0ubuntu1.16.04.1 has fixed the freezing here too.
I successfully tested it with Windows 10 and Xenial VMs.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs,
"proposed" 5.1.34-dfsg-0ubuntu1.16.04.1 works fine for me as well. It
doesn't freeze the system anymore. Tested with two different VM guests
(Linux and Windows 2000).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
"proposed" 5.1.34-dfsg-0ubuntu1.16.04.1 is working. Not tested
everything but 1. is not hanging and 2. at least one virtual machine is
working ok.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736116
Hello Stephan, or anyone else affected,
Accepted kbuild into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/kbuild/1:0.1.9998svn2814+dfsg-2~ubuntu16.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello Stephan, or anyone else affected,
Accepted virtualbox into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/virtualbox/5.1.34
-dfsg-0ubuntu1.16.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Stephan, or anyone else affected,
Accepted virtualbox into artful-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/virtualbox/5.1.34
-dfsg-0ubuntu1.17.10.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Please be patient and use my ppa in case you really need it, we will ask
for feedbacks as soon as somebody pushes the button :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736116
Title:
[SRU]
They are getting reviewed right now, but considering that this is a major
release bump (python2->python3, qt4->qt5) and *a lot* changed in between (12MB
of patch diff), it will take a lot of more time I think.
We should probably put in the loop also Security Team, since this is fixing 3
serious
I'm not familiar with the upload queue procedure (and wasn't able to
gather any information about it on the net) but may I ask if it's normal
that the updates are stuck there unapproved since 5 days?
https://launchpad.net/ubuntu/xenial/+queue?queue_state=1_text=
--
You received this bug
** Summary changed:
- Host with kernel 4.13 freezes when starting a VM with VirtualBox
+ [SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox
** Also affects: virtualbox (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: virtualbox (Ubuntu Xenial)
43 matches
Mail list logo
