Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
Dear Gianfranco, thank you very much for your fix indeed. It works like a charm on my siduction box. You really saved my a... . Best wishes jk On Thu, 12 Jul 2018 08:52:59 + (UTC) Gianfranco Costamagna wrote: > Hello, > > > >VMMR0.r0 has been built (presumably due to the recent binutils upgrades in unstable) with the new PLT32 relocation type, which the virtualbox ELF relocation >code cannot handle at the moment. Having a quick glance at .text and .rela.text of VMMR0.r0, it seems to me that PC32 and PLT32 can be handled identically, >similar to what commit b21ebf2fb4cd of the Linux kernel did? > > > I really liked the analysis, the linux commit and the binutils stuff, I crafted a patch based on this comment, and uploaded in unstable > > If anybody wants to test the "fix", please grab the deb files from there > http://debomatic-amd64.debian.net/distribution#unstable/virtualbox/5.2.14-dfsg-2/buildlog > > > or wait some hours for the package to appear on unstable repositories/mirrors. > > I'm not sure if this causes regressions or whatever else, the assumption "they might behave in the same way" might not apply as it did in the kernel, > even if my basic tests confirmed the VM to start. > > Use at your own risk, like everything that comes from unstable, the urgency is set to low, so I presume we will have 10 days of people testing this before > going in buster. > > thanks you all, I also submitted the patch to upstream mail list and irc for review > > G. > >
Bug#902897: Info received (Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type))
(adding a few more pieces of information) ... and they also messed this up in SVN r73086; they fixed only the switch/case statement in RelocateSectionExecDyn(), exactly the function that is *not* exercised for VMMR0.r0 as that's an ET_REL file, not an ET_DYN. :) Reiterating: the rev2 patch in the upstream bugreport looks good; they imported the wrong version into SVN. Jan
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
Hi Gianfranco, please include upstream's v2 patch, they missed one occurrence of _PC32 in ldrELFRelocatable.cpp.h in the first version... Jan
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
On 13 juil. 2018 11:55, Roy Enoch wrote: > You are not the only one with this issue again. Same here. Christian
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
You are not the only one with this issue again.
Roy
On Fri, Jul 13, 2018, 11:48 AM j P wrote:
> Hello,
>
> currently I have virtualbox 5.2.14-dfsg-4 installed and I still can't
> start any of my VMs. The error is the same:
>
>
> Failed to open a session for the virtual machine ubuntu.
>
> Failed to load R0 module /usr/lib/virtualbox/VMMR0.r0: RTLdrGetBits failed
> (VERR_LDRELF_RELOCATION_NOT_SUPPORTED).
>
> Failed to load VMMR0.r0 (VERR_LDRELF_RELOCATION_NOT_SUPPORTED).
>
> Result Code: NS_ERROR_FAILURE (0x80004005)
> Component: ConsoleWrap
> Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
>
>
> "apt update" does not give any updates.
>
> Am I the only one with this error in the new version? Please let me know
> if you have any questions or how can I help with troubleshooting. So far I
> have tried purging virtualbox and installing again with the same result.
> Thank you!
>
> Best regards,
> athmoss
>
>
> On Thu, 12 Jul 2018 08:28:03 -0500 Roy wrote:
> > Works for me also. Thank you. -Roy
> >
> >
> > On 07/12/2018 07:30 AM, Christian Marillat wrote:
> > > On 12 juil. 2018 11:14, Volker Christian <
> volker.christ...@fh-hagenberg.at> wrote:
> > >
> > >> I can confirm that the virtual machines start again with this fix!
> > > Works for me too with 32 and 64 bits guests.
> > >
> > >> Thank you very much!
> > > Me too.
> > >
> > > Christian
> > >
> >
> >
> >
>
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
Ditto. Had to back-rev to 5.2.14-dfsg-3, which seems to be operational.
-- sRw
On 07/13/18 11:45, j P wrote:
Hello,
currently I have virtualbox 5.2.14-dfsg-4 installed and I still can't
start any of my VMs. The error is the same:
Failed to open a session for the virtual machine ubuntu.
Failed to load R0 module /usr/lib/virtualbox/VMMR0.r0: RTLdrGetBits
failed (VERR_LDRELF_RELOCATION_NOT_SUPPORTED).
Failed to load VMMR0.r0 (VERR_LDRELF_RELOCATION_NOT_SUPPORTED).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
"apt update" does not give any updates.
Am I the only one with this error in the new version? Please let me
know if you have any questions or how can I help with troubleshooting.
So far I have tried purging virtualbox and installing again with the
same result. Thank you!
Best regards,
athmoss
On Thu, 12 Jul 2018 08:28:03 -0500 Roy > wrote:
> Works for me also. Thank you. -Roy
>
>
> On 07/12/2018 07:30 AM, Christian Marillat wrote:
> > On 12 juil. 2018 11:14, Volker Christian
> wrote:
> >
> >> I can confirm that the virtual machines start again with this fix!
> > Works for me too with 32 and 64 bits guests.
> >
> >> Thank you very much!
> > Me too.
> >
> > Christian
> >
>
>
>
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
Hello,
currently I have virtualbox 5.2.14-dfsg-4 installed and I still can't start
any of my VMs. The error is the same:
Failed to open a session for the virtual machine ubuntu.
Failed to load R0 module /usr/lib/virtualbox/VMMR0.r0: RTLdrGetBits failed
(VERR_LDRELF_RELOCATION_NOT_SUPPORTED).
Failed to load VMMR0.r0 (VERR_LDRELF_RELOCATION_NOT_SUPPORTED).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
"apt update" does not give any updates.
Am I the only one with this error in the new version? Please let me know if
you have any questions or how can I help with troubleshooting. So far I
have tried purging virtualbox and installing again with the same result.
Thank you!
Best regards,
athmoss
On Thu, 12 Jul 2018 08:28:03 -0500 Roy wrote:
> Works for me also. Thank you. -Roy
>
>
> On 07/12/2018 07:30 AM, Christian Marillat wrote:
> > On 12 juil. 2018 11:14, Volker Christian <
volker.christ...@fh-hagenberg.at> wrote:
> >
> >> I can confirm that the virtual machines start again with this fix!
> > Works for me too with 32 and 64 bits guests.
> >
> >> Thank you very much!
> > Me too.
> >
> > Christian
> >
>
>
>
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
Andrey Rahmatullin wrote: On Thu, Jul 12, 2018 at 10:16:36AM -0500, Kent West wrote: > > ... once I learned that the fix had been uploaded to stable, > To unstable (the only place where it was broken). D'oh! I mean "unstable". > But if I'm understanding this error, for some months (years?), I've been > > pulling VirtualBox from virtualbox.org > No, the extension pack can be installed on the Debian Virtualbox > separately and I don't think it's installed by default even with the > official package. > > instead of from Debian, and whilst > > doing that, had configured my VMs with USB support. And my fix should > just > > be to disable the USB support in my VMs > The fix should be to upgrade the extension pack after you upgraded > virtualbox itself... Good to know. Thanks! -- Kent West<")))>< Westing Peacefully - http://kentwest.blogspot.com
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
Actually, if you had virtualbox-ext-pack installed, you just need to install back/reinstall/upgrade it. -- WBR, wRAR signature.asc Description: PGP signature
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
On Thu, Jul 12, 2018 at 10:16:36AM -0500, Kent West wrote: > > Note! This error could also mean that an incompatible version of the > > 'Oracle VM VirtualBox Extension Pack' is installed (VERR_NOT_FOUND). > While VirtualBox was broken this week, I had tried various things ( > snapshot.debian.org, virtualbox.org, etc), but once I learned that the fix > had been uploaded to stable, To unstable (the only place where it was broken). > But if I'm understanding this error, for some months (years?), I've been > pulling VirtualBox from virtualbox.org No, the extension pack can be installed on the Debian Virtualbox separately and I don't think it's installed by default even with the official package. > instead of from Debian, and whilst > doing that, had configured my VMs with USB support. And my fix should just > be to disable the USB support in my VMs The fix should be to upgrade the extension pack after you upgraded virtualbox itself... -- WBR, wRAR signature.asc Description: PGP signature
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
On Thu, Jul 12, 2018 at 10:08:06AM -0500, Kent West wrote: > I just did an "aptitude udpate" and "aptitude dist-upgrade", and got a new > version of VirtualBox. > > When I try to start a virtual machine, I get a new error: > > > Implementation of the USB 2.0 controller not found! > > Because the USB 2.0 controller state is part of the saved VM state, the VM > cannot be started. To fix this problem, either install the > 'Oracle VM VirtualBox Extension Pack' or disable USB 2.0 support in the VM > settings. > > Note! This error could also mean that an incompatible version of the > 'Oracle VM VirtualBox Extension Pack' is installed (VERR_NOT_FOUND). Update the extension pack. -- WBR, wRAR signature.asc Description: PGP signature
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
On Thu, Jul 12, 2018 at 10:08 AM, Kent West wrote:
> I just did an "aptitude udpate" and "aptitude dist-upgrade", and got a new
> version of VirtualBox.
>
> When I try to start a virtual machine, I get a new error:
>
>
> Implementation of the USB 2.0 controller not found!
>
> Because the USB 2.0 controller state is part of the saved VM state, the VM
> cannot be started. To fix this problem, either install the
> 'Oracle VM VirtualBox Extension Pack' or disable USB 2.0 support in the
> VM settings.
>
> Note! This error could also mean that an incompatible version of the
> 'Oracle VM VirtualBox Extension Pack' is installed (VERR_NOT_FOUND).
>
> Result Code:
>
> NS_ERROR_FAILURE (0x80004005)
>
> Component:
>
> ConsoleWrap
>
> Interface:
>
> IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
>
>
>
While VirtualBox was broken this week, I had tried various things (
snapshot.debian.org, virtualbox.org, etc), but once I learned that the fix
had been uploaded to stable, I made sure my sources.list was "clean" of
anything non-Debian, but didn't think to look in my sources.list.d
directory for additional "add-ons". I found that I did have a virtualbox
file in that directory, which I have since removed.
But if I'm understanding this error, for some months (years?), I've been
pulling VirtualBox from virtualbox.org instead of from Debian, and whilst
doing that, had configured my VMs with USB support. And my fix should just
be to disable the USB support in my VMs, but those options are grayed
(because my VMs are in a saved state, maybe?). Once I get this figured out,
I suspect VirtualBox will work. I'll let you know.
--
Kent West<")))><
Westing Peacefully - http://kentwest.blogspot.com
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
Got it!
I had to "Discard" the saved state, and then I could turn off the USB
support (actually just lowered it to USB 1.0), and now my VMs work!
Yea! You did great! Thanks!
On Thu, Jul 12, 2018 at 10:16 AM, Kent West wrote:
>
>
> On Thu, Jul 12, 2018 at 10:08 AM, Kent West wrote:
>
>> I just did an "aptitude udpate" and "aptitude dist-upgrade", and got a
>> new version of VirtualBox.
>>
>> When I try to start a virtual machine, I get a new error:
>>
>>
>> Implementation of the USB 2.0 controller not found!
>>
>> Because the USB 2.0 controller state is part of the saved VM state, the
>> VM cannot be started. To fix this problem, either install the
>> 'Oracle VM VirtualBox Extension Pack' or disable USB 2.0 support in the
>> VM settings.
>>
>> Note! This error could also mean that an incompatible version of the
>> 'Oracle VM VirtualBox Extension Pack' is installed (VERR_NOT_FOUND).
>>
>> Result Code:
>>
>> NS_ERROR_FAILURE (0x80004005)
>>
>> Component:
>>
>> ConsoleWrap
>>
>> Interface:
>>
>> IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
>>
>>
>>
> While VirtualBox was broken this week, I had tried various things (
> snapshot.debian.org, virtualbox.org, etc), but once I learned that the
> fix had been uploaded to stable, I made sure my sources.list was "clean" of
> anything non-Debian, but didn't think to look in my sources.list.d
> directory for additional "add-ons". I found that I did have a virtualbox
> file in that directory, which I have since removed.
>
> But if I'm understanding this error, for some months (years?), I've been
> pulling VirtualBox from virtualbox.org instead of from Debian, and whilst
> doing that, had configured my VMs with USB support. And my fix should just
> be to disable the USB support in my VMs, but those options are grayed
> (because my VMs are in a saved state, maybe?). Once I get this figured out,
> I suspect VirtualBox will work. I'll let you know.
>
> --
> Kent West<")))><
> Westing Peacefully - http://kentwest.blogspot.com
>
--
Kent West<")))><
Westing Peacefully - http://kentwest.blogspot.com
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
I just did an "aptitude udpate" and "aptitude dist-upgrade", and got a new
version of VirtualBox.
When I try to start a virtual machine, I get a new error:
Implementation of the USB 2.0 controller not found!
Because the USB 2.0 controller state is part of the saved VM state, the VM
cannot be started. To fix this problem, either install the
'Oracle VM VirtualBox Extension Pack' or disable USB 2.0 support in the VM
settings.
Note! This error could also mean that an incompatible version of the
'Oracle VM VirtualBox Extension Pack' is installed (VERR_NOT_FOUND).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
--
Kent West<")))><
Westing Peacefully - http://kentwest.blogspot.com
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
Works for me also. Thank you. -Roy On 07/12/2018 07:30 AM, Christian Marillat wrote: On 12 juil. 2018 11:14, Volker Christian wrote: I can confirm that the virtual machines start again with this fix! Works for me too with 32 and 64 bits guests. Thank you very much! Me too. Christian
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
On 12 juil. 2018 11:14, Volker Christian wrote: > I can confirm that the virtual machines start again with this fix! Works for me too with 32 and 64 bits guests. > Thank you very much! Me too. Christian
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
I can confirm that the virtual machines start again with this fix! Thank you very much! Volker On Donnerstag, 12. Juli 2018 10:52:59 CEST Gianfranco Costamagna wrote: > Hello, > > > >VMMR0.r0 has been built (presumably due to the recent binutils upgrades in > >unstable) with the new PLT32 relocation type, which the virtualbox ELF > >relocation >code cannot handle at the moment. Having a quick glance at .text > >and .rela.text of VMMR0.r0, it seems to me that PC32 and PLT32 can be > >handled identically, >similar to what commit b21ebf2fb4cd of the Linux > >kernel did? > > > I really liked the analysis, the linux commit and the binutils stuff, I > crafted a patch based on this comment, and uploaded in unstable > > If anybody wants to test the "fix", please grab the deb files from there > http://debomatic-amd64.debian.net/distribution#unstable/virtualbox/5.2.14-dfsg-2/buildlog > > > or wait some hours for the package to appear on unstable repositories/mirrors. > > I'm not sure if this causes regressions or whatever else, the assumption > "they might behave in the same way" might not apply as it did in the kernel, > even if my basic tests confirmed the VM to start. > > Use at your own risk, like everything that comes from unstable, the urgency > is set to low, so I presume we will have 10 days of people testing this before > going in buster. > > thanks you all, I also submitted the patch to upstream mail list and irc for > review > > G. > >
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
Hello, >VMMR0.r0 has been built (presumably due to the recent binutils upgrades in >unstable) with the new PLT32 relocation type, which the virtualbox ELF >relocation >code cannot handle at the moment. Having a quick glance at .text >and .rela.text of VMMR0.r0, it seems to me that PC32 and PLT32 can be handled >identically, >similar to what commit b21ebf2fb4cd of the Linux kernel did? I really liked the analysis, the linux commit and the binutils stuff, I crafted a patch based on this comment, and uploaded in unstable If anybody wants to test the "fix", please grab the deb files from there http://debomatic-amd64.debian.net/distribution#unstable/virtualbox/5.2.14-dfsg-2/buildlog or wait some hours for the package to appear on unstable repositories/mirrors. I'm not sure if this causes regressions or whatever else, the assumption "they might behave in the same way" might not apply as it did in the kernel, even if my basic tests confirmed the VM to start. Use at your own risk, like everything that comes from unstable, the urgency is set to low, so I presume we will have 10 days of people testing this before going in buster. thanks you all, I also submitted the patch to upstream mail list and irc for review G.
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
Hi, VMMR0.r0 has been built (presumably due to the recent binutils upgrades in unstable) with the new PLT32 relocation type, which the virtualbox ELF relocation code cannot handle at the moment. Having a quick glance at .text and .rela.text of VMMR0.r0, it seems to me that PC32 and PLT32 can be handled identically, similar to what commit b21ebf2fb4cd of the Linux kernel did? Best regards Jan Nordholz
