| Summary: | VirtualBox fails to start VDM after Cauldron s/w update Sept.4 (OK on 32-bit) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Maurice Batey <maurice77> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | bittwister2, maurice77, tmb |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | virtualbox-4.3.14-2.mga5.src.rpm | CVE: | |
| Status comment: | |||
|
Maurice Batey
2014-09-09 17:03:18 CEST
CC:
(none) =>
maurice FYI: latest virtualbox update fixed my problem. CC:
(none) =>
junknospam already fixed *** This bug has been marked as a duplicate of bug 14074 *** Status:
NEW =>
RESOLVED Bit Twister 2014-09-09 17:09:58 CEST: > FYI: latest virtualbox update fixed my problem. Lucky you! I tried the update but it messed up (as did a repeat). The update session log can be seen here: https://dl.dropboxusercontent.com/u/10969499/sw-update-log-9-9-14 If that is a showstopper for me I will think about trying a Mageia-5A2 'update' install, otherwise hold off until Beta1. You can try to tell urpmi to go 1 package at a time, so: urpmi --auto-update --split-length=1 Oh, and I see you also have a non-mga package also blocking the install ooRexx-4.2.0-9940.opensuse1230.x86_64 So nuke that one and let the update continue... Thomas Backlund 2014-09-09 19:16:58 CEST:
> You can try to tell urpmi to go 1 package at a time, so:
> urpmi --auto-update --split-length=1
Tried that and the update then worked perfectly, also VirtualBox is back to normal!
Many thanks, Thomas.
Why would the 'split-length=1' option make such a huge difference, I wonder...
> I see you also have a non-mga package also blocking the install
> ooRexx-4.2.0-9940.opensuse1230.x86_64
> So nuke that one and let the update continue...
I've been using ooRexx for years now, and have never had an update mess up because of it. How is it 'blocking the install'?
This highly-successful update seems to have ignored it apart from - right at the end - reporting:
"Installation failed: /sbin/service is needed by (installed) ooRexx- 4.2.0-9940.opensuse1230.x86_64"
But /sbin/service *is* there, and ooRexx does work, so why does the installer put that message out for this Cauldron update?
|
Description of problem: Virtualbox fails when starting VDM: "Failed to open a session for the virtual machine Windows XP SP3. Failed to load VMMR0.r0 (VERR_NO_EXEC_MEMORY). Result Code: NS_ERROR_FAILURE (0x80004005) Component: Console Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}" Version-Release number of selected component (if applicable): virtualbox-4.3.14-2.mga5.src.rpm How reproducible: Steps to Reproduce: 1. Start VirtualBox 2. Request start a VDM 3. Fails as described above N.B. This failure (which appears not to affect 32-bit Mageia-5A2) happens since a Cauldron s/w update on Septeember 4th, when e.g. the following were installed: virtualbox-kernel-3.17.0-desktop-0.rc3.1.mga5-4.3.14-2.mga5.x86_64.rpm kernel-desktop-devel-latest-3.17.0-0.rc3.1.mga5.x86_64.rpm from Further details of that update can be seen at: https://dl.dropboxusercontent.com/u/10969499/sw-update-mga5A2-4-9-14-edited N.B. This problem has been reported by two other users recently in gmane.linux.mageia.devel under the the header: "Since latest kernel upgrade - virtualbox fails" Reproducible: Steps to Reproduce: