Works for me with latest HWE kernel in Ubuntu Xenial.
sudo add-apt-repository ppa:costamagnagianfranco/autoconf
sudo apt update
sudo apt full-upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736
Hi,
I can confirm that these changes work with
Linux 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
and
virtualbox_5.1.34-dfsg-0ubuntu1.16.04.1~16.04.1_amd64.deb
virtualbox-dkms_5.1.34-dfsg-0ubuntu1.16.04.1~16.04.1_all.deb
virtualbox-qt_5.1.
Hello, I fixed the packages and uploaded there
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/autoconf/+packages
It has been a real long work, please test and if I get enough good
feedbacks, I'll upload in Ubuntu later today or by the end of the week
** Changed in: virtualbox (Ubuntu
This persists with 4.13.0-36-generic. Updating to VirtualBox package
server is a workaround but not always possible (due to available rights
etc) so no solution !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
This report is about kernel 4.13 on host, not on guest
--
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:
Host with kernel 4.13 freezes when starting a VM with VirtualBox
To manage notifi
As per VirtualBox website:
Important: The Guest Additions which come with VirtualBox 5.2.6 and
5.1.32 do not work properly on Linux guests with 3D enabled.
I installed the updated version provided on the website
(https://www.virtualbox.org/download/testcase/VBoxGuestAdditions_5.2.7-120528.iso)
to
For those getting error:
VBoxManage: error: The virtual machine 'VM1' has terminated unexpectedly during
startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component
MachineWrap, interface IMachine
Comment #52
(https://bugs.launchpad.net/ubuntu/+sourc
#53 Thank you!
--
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:
Host with kernel 4.13 freezes when starting a VM with VirtualBox
To manage notifications about this bug go to:
https://bu
Thanks @launchpad-startport at
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1736116/comments/50
and @isalexandru at
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1736116/comments/52.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
@Lonnie Lee #39
Thank You, you made my day !!!
--
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:
Host with kernel 4.13 freezes when starting a VM with VirtualBox
To manage notifications
Then it's easier to settle for 5.1.x which is still supported upstream.
--
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:
Host with kernel 4.13 freezes when starting a VM with VirtualBox
@LocutusOfBorg, first of all, thank you very much for your continuous
effort in maintaining VirtualBox.
After you mentioned that "upstream vbox ships a custom qt version", I asked
about it in #vbox, and they said:
> [...] qt5 was pretty much unusable rubbish until 5.5/5.6. and then they
> decide
#50 followed by #52 solved the problem for me, thank you very much.
--
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:
Host with kernel 4.13 freezes when starting a VM with VirtualBox
To
So, in my case, the kernel modules were not removed properly.
Here are the details:
root@Dell5280 [~]# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.3 LTS
root@Dell5280 [~]# uname -r
4.13.0-31-generic
Problem:
root@Dell52
problem possibly started with linux-image-4.13.0-26-generic or
linux-image-4.13.0-25-generic (didn't existed in previous updates, not sure
which were installed in my system during "daily update", and if any of previous
was installed). Problem still exists with the new linux-image-4.13.0-31-gener
I'm sorry if the command I wrote didn't work for you. Here's the whole
thing:
sudo sh -c 'echo "deb http://download.virtualbox.org/virtualbox/debian
xenial contrib" >> /etc/apt/sources.list' ; wget -q
https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-
key add ; sudo apt remov
@ Lonnie Lee Best - I applied what you have suggested at #39. But when I
launched VirtualBox, it says as under:
RTR3InitEx failed with rc=-1912 (rc=-1912)
The VirtualBox kernel modules do not match this version of VirtualBox.
The installation of VirtualBox was apparently not successful. Executing
I'm the maintainer, please use my ppa:
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1736116/comments/34
And please stop asking and re-asking the same questions.
Upstream has a CUSTOM qt version, I can't obviously push that in Ubuntu.
If you know how to fix qt to make the new vbox bu
I usually prefer the Ubuntu packaging to whatever upstream packaging.
But in this case, Ubuntu requires dkms, while upstream doesn't, for a long time
now. There's no module compilation on each kernel upgrade.
It's an additional significant reason to prefer the upstream package.
Maybe it's time to
Thanks Lonnie Lee Best, your command did it for me. VirtualBox is not
freezing the host anymore :)
--
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:
Host with kernel 4.13 freezes when sta
@pedrocr - No, the PPA isn't missing anything, it's just showing you the
_source_ packages used to build all the packages (DEBs) you mentioned.
Click on the "virtualbox" package and at the end of the changelog you'll
see all the DEBs built/available.
The PPA is simply a backport of the official vi
alindt, that PPA is missing at least the -dkms, -qt and all the -guest
packages. And at least for me the point of not using the official Oracle
archive is to make sure I'm getting the Ubuntu packaged code. A PPA
doesn't really guarantee that as the code could have been tampered with.
I'm obviously
...and here's a PPA for backported 5.1.30 from Artful:
https://launchpad.net/~alindt/+archive/ubuntu/build-deps/+packages
sudo add-apt-repository ppa:alindt/xenial-backports-virtualbox
sudo apt-get update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Sorry, wrong link in previous post.
https://launchpad.net/~alindt/+archive/ubuntu/xenial-backports-
virtualbox
sudo add-apt-repository ppa:alindt/xenial-backports-virtualbox
sudo apt-get update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I was seeing more screen tearing after going back to the 4.4 kernel and
corresponding xserver so I decided I wanted to be able to use the HWE
stack again. I almost moved to virtualbox 5.2 from the virtualbox.org
repos but then I just decided to backport virtualbox 5.1.30 from artful
and that worked
Kernel 4.4 also has been patched for these Intel bugs, so you can use it
instead of 4.13 if you don't need the latest hardware support.
--
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:
H
xoristzatziki's suggestion of backporting VirtualBox 5.2.6 to 16.04 LTS
is what I think needs to happen here.
Following Alkis Georgopoulos's advice, I can confirm that 5.2.6 works
great on the 4.13 kernel
To install it, I ran all of this as one command:
sudo sh -c 'echo "deb http://download.virt
Isn't 4.13 the first kernel to fix that Intel bug that was all over the
news earlier this month?
I've been booting with 4.10 in order to use virtualbox; does that make
me susceptible to that kernel-memory-leaking-intel-bug?
http://www.businessinsider.com/linus-torvalds-linux-inventor-is-furious-
The latest upstream VirtualBox 5.2.6-120293~Ubuntu~xenial, runs fine
with 4.13, using the stock Xenial Qt version.
Why does the Ubuntu package need a new Qt when the upstream package
doesn't?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
https://www.virtualbox.org/wiki/Linux_Downloads
5.1.30 from their official repo runs fine with 4.13 and doesn't require
any Qt modifications.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736116
Tit
Hello, for people experiencing issues with qt and my ppa, please add this
additional repo
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay
(note: this upgrades qt to a newer version, I don't know the side effects).
Unfortunately 5.2.6 *doesn't* build with xenial qt
Hello, for people experiencing issues with qt and my ppa, please add this
additional repo
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay
(note: this upgrades qt to a newer version, I don't know the side effects).
Unfortunately 5.2.6 *doesn't* build with xenial qt
Sorry for my tone. You are right.
(Unfortunately I do not like to use any of the options mentioned.)
--
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:
Host with kernel 4.13 freezes when s
@ xoristzatziki (simsonbike-bugs) wrote 1 hour ago:
> Otherwise we should somehow change the "Support lifespan" there in order not
> to direct people to
> loose confidence for LTS versions and UBUNTU itself.
Slow down a little, and think about what you are saying:
$ apt-cache show virtualbox
If 16.04 is still considered LTS supported up to 5 years
(https://wiki.ubuntu.com/XenialXerus/ReleaseNotes) then we must backport it.
Otherwise we should somehow change the "Support lifespan" there in order not
to direct people to loose confidence for LTS versions and UBUNTU itself.
Many other
Install VB 5.2.6 works fine. The previous version freezed entire system
and require hard reboot.
--
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:
Host with kernel 4.13 freezes when start
This is a screenshot of the host crash: https://snag.gy/HkOoeK.jpg
This happens only on 64bit 4.13 kernels, while 32bit installations with 4.13
work fine.
It happens with any guest, even if there's no guest OS installed yet.
It does not happen at all if the host has kernel=4.10.
It does not hap
@LocutusOfBorg
I can confirm the dependency problem with your ppa. #21
--
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:
Host with kernel 4.13 freezes when starting a VM with VirtualBox
Virtualbox 5.0.40 also crashed for me on kernel 4.13.0-26.
After I click start, 4-5 lines get printed in dmesg, then the entire system
freezes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736116
T
I can confirm Virtualbox 5.2 from virtualbox.org also works with linux-
hwe 4.13.0-29.32~16.04.1 from ppa:canonical-kernel-team/pti which fixes
Spectre with IBRS/IBPB.
And I hope Virtualbox implements IBRS/IBPB path through to also allow
Spectre protection in vms.
--
You received this bug notifi
LocutusOfBorg, re #21: There are missing dependencies in your ppa
(virtualbox-qt):
libqt5core5a (>= 5.6.0~beta), libqt5widgets5 (>= 5.6.0~beta),
libqt5x11extras5 (>= 5.6.0)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Just downgrading to non-HWE LTS seems to have fixed things for me so
I'll probably stick with that instead.
--
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:
Host with kernel 4.13 freezes
I solved same problem by installing virtualbox 5.2 from virtualbox.org:
$ sudo apt remove --purge virtualbox*
$ sudo sh -c 'echo "deb http://download.virtualbox.org/virtualbox/debian xenial
contrib" >> /etc/apt/sources.list'
$ wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- |
@LocutusOfBorg: Will 5.2.4 be rolled out in multiverse in the near
future or do users experiencing that freeze need to stick with your PPA?
--
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:
Please use my ppa
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/virtualbox-ppa
--
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:
Host with kernel 4.13 freezes when starting
Virtualbox 5.0.40 is not working with the new kernel (4.13.0-26), but
the new version of VBox (5.2) works fine.
Download it from VirtualBox page or add the source to your sources.list:
sudo sh -c 'echo "deb http://download.virtualbox.org/virtualbox/debian
xenial contrib" >> /etc/apt/sources.list'
Using kernel 4.13.0.26 will also completely freeze the host when you
click start in Virtualbox.
--
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:
Host with kernel 4.13 freezes when starti
I have the same problem on my Lenovo t450s (Intel i7-5600U). Virtualbox
worked with 4.10 and freezes the host on 4.13. Disabling VT-x/AMD-V
didn't solve the problem. Also disabling the new kernel page table
isolation (kernel command-line: nopti) doesn't solve the issue.
--
You received this bug n
Freezes happen on Intel PCs only here, whilst AMD PCs don't.
Could more people test this, please?
Disabling the VT-x virtualization option (#15) often isn't an option
since 64 Bit guests do need the host to have this option enabled.
I'm fully agreeing with Pedro Côrte-Real's (#16) suggestion tha
Given the recent accelerated upgrade to 4.13 in 16.04 HWE wouldn't a
simple option be to also upgrade virtualbox in 16.04 to 5.1 to get
around this issue? Before this was something that probably only affected
a few people on HWE-edge but now with Spectre/Meltdown people will be
hitting this much mo
I am seeing these symptoms exclusively for guests with VT-x/AMD-V option
enabled. Guests without that option boot fine.
Identical virtualbox/kernel versions and kernel upgrade scenario as comment
#14. Various guest OS. Host CPU Intel Core i5-6600T.
--
You received this bug notification because
Lubuntu 16.04 LTS 64 bit up-to-date
Freezes ---> linux-image-4.13.0-26-generic 4.13.0-26.29~16.04.2
Fine --> linux-image-4.10.0-42-generic 4.10.0-42.46~16.04.1
virtualbox 5.0.40-dfsg-0ubuntu1.16.04.2
virtualbox-dkms 5.0.40-dfsg-0ub
So I'm now on kernel 4.13 after the update of -hwe kernel from 4.10, and
my vbox 5.1.30 (from the official virtualbox.org repo) runs fine on this
host. Apparently, only 5.0.40, which is in Xenial repos, has this
problem.
--
You received this bug notification because you are a member of Ubuntu
Bug
Package from virtualbox.org cannot be used as the latest 5.0 build is
5.0.40 and even this needs to be patched as described in #1729568 to
build the kernel modules.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
I have the same issue with latest the candidate kernel required to fix Meltdown
on Xenial.
linux-hwe-edge 4.13.0-25.29~16.04.1 from ppa:canonical-kernel-team/pti
Because "the Rolling HWE kernel for Ubuntu 16.04 will go to 4.13 early,
instead of also fixing 4.10 HWE kernel" I cannot stay on 4.10 a
For those people having host freezes, please try to reproduce them using
packages from virtualbox.org and open a bug report there if appropriate.
It would be appreciated if you link to any appropriate Launchpad bugs,
but still provide all information on the virtualbox.org bug, including a
log file
Xenial VM with kernel 4.14
** Attachment added: "Screenshot from 2017-12-12 10-30-28.png"
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1736116/+attachment/5022613/+files/Screenshot%20from%202017-12-12%2010-30-28.png
--
You received this bug notification because you are a member
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: virtualbox (Ubuntu)
Status: New => Confirmed
--
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:
** Changed in: virtualbox (Ubuntu)
Status: Confirmed => New
--
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:
Host with kernel 4.13 freezes when starting a VM with VirtualBox
To m
** Summary changed:
- Host freezes when starting a VM with VirtualBox
+ Host with kernel 4.13 freezes when starting a VM with VirtualBox
--
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:
60 matches
Mail list logo
