aims team mailing list archive

[Doug Coulter <dcfusor@xxxxxxxxx>]

No.  Frankly, I've avoided upgrading to precise as long as I could as I
detest the new desktop (along with the huge majority of real old timer
computer devs/users).  Now that there's Mate, I'm moving a few machines
over to get the new kernel etc.  This is a new-build machine, so I had to
use 12.04/64 to get past the UEFI issues.  I'd just as soon be using 32
bit, sigh, but had to go with the UEFI flow, you know.

I tried the advice above - using sudo apt-get install
virtualbox-dkms/precise-
proposed

Which removed VB 4.2 and put in 4.1.something.  I don't care about that one
- I am not "stressing" VB much here - just using it to run windows to run
some lab tools that aren't compatible with linux (for my mass spectrometer
and suchlike, which barely run on windows, no hope in wine, and some of my
uP dev ide's for things like PIC uPs I write code for.)
.
Trying virtualbox from a terminal gives me an error - "Error opening file
for reading: permission denied (when run as me).  It doesn't get this error
running as sudo but...
It still crashes during *any* VM bootup - all the way back to my bios.
(Glad I have an SSD, I've never ever had to reboot linux at all, much less
6 times an hour).
Doesn't matter about what VM I try to boot - Xp or Win7, several versions,
& re-import the "appliance" on every try (they get internally corrupted on
the attempt that fails).  I did add the extension pack suitable for this
version of VB since those images do use USB.

Since the thing won't boot an image at all - kills the entire machine
partway through, I've not been able to install/update the guest additions
on these images...This is a real show stopper here - I'd hate to kick off
linux and have to build a windows-only box, but my physics lab has to
run...(www.coultersmithing.com/forums)

Precise is not making me at all happy.  VB does work on machines I
"upgraded" that had it already, but not on this new build.  The thing is, a
fusor sometimes fries a nearby data aq PC - so I need to keep making more
machines now and again...(something about a 100kv power supply arcing and
making gigawatt emp - despite shielding, sometimes fries a mobo).  This
machine is intended to be ready for when the one in service has that happen
to it.

I can't get 10.04 to install at all on a UEFI mobo, even trying my best to
turn the UEFI junk off in the bios (ASUS P8H 77-M/i5/8gig ram).

Is there anything else I can use that will import .ova files?  I'm not wed
to VB or especially anything oracle...just need something that'll get my
job done.


On Mon, Apr 8, 2013 at 5:49 PM, Andre <1081307@xxxxxxxxxxxxxxxxxx> wrote:

> @Doug The problem with the guest system sounds like a different bug.
> Maybe related to the guest-additions? Did you ever get your guests to
> run in VirtualBox on Ubuntu Precise with Linux-kernel 3.2.0-xx ?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1165520).
> https://bugs.launchpad.net/bugs/1081307
>
> Title:
>   virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
>   failed to build [merge request]
>
> Status in “virtualbox” package in Ubuntu:
>   Fix Released
> Status in “virtualbox” source package in Precise:
>   Fix Committed
> Status in “virtualbox” source package in Quantal:
>   Fix Released
> Status in “virtualbox” source package in Raring:
>   Fix Released
>
> Bug description:
>   I'm using aptitude as a packet manager.
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 12.04
>   Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2
>   ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
>   Uname: Linux 3.5.0-26-generic x86_64
>   NonfreeKernelModules: nvidia
>   ApportVersion: 2.0.1-0ubuntu15
>   Architecture: amd64
>   DKMSKernelVersion: 3.5.0-18-generic
>   Date: Tue Nov 20 23:13:23 2012
>   InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
> (20120425)
>   MarkForUpload: True
>   PackageArchitecture: all
>   PackageVersion: 4.1.12-dfsg-2ubuntu0.2
>   SourcePackage: virtualbox
>   Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
> failed to build
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
>   [Impact]
>   Users are not able to use virtualbox from the repository on 12.04 with
> 3.5 kernel. It is totally broken.
>   The patch proposed backports only the relevant parts from upstream to
> fix the bug.
>   The patch is from: https://www.virtualbox.org/changeset/41660/vbox
>
>   [Test Case]
>   Upgrade to 3.5 kernel on 12.04 and install virtualbox.
>
>   [Development Fix]
>   Fixed during Quantal cycle.
>
>   [Stable Fix]
>   Is being fixed in 4.1.12-dfsg-2ubuntu0.3 upload to precise-proposed.
>
>   [Regression Potential]
>   It is best to use the latest upstream version. But since that will cause
> major disruption, we have to track this package and corresponding bugs for
> regressions.
>
>   jamespage: Please also check backwards compatibility with the 3.2
>   kernel; the patch should support this but best to make sure (not all
>   12.04 installs with have 3.5).
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1081307/+subscriptions
>


-- 
Why guess when you can know.  Measure!

-- 
You received this bug notification because you are a member of AIMS,
which is subscribed to a duplicate bug report (1126315).
https://bugs.launchpad.net/bugs/1081307

Title:
  virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
  failed to build [merge request]

Status in “virtualbox” package in Ubuntu:
  Fix Released
Status in “virtualbox” source package in Precise:
  Fix Committed
Status in “virtualbox” source package in Quantal:
  Fix Released
Status in “virtualbox” source package in Raring:
  Fix Released

Bug description:
  I'm using aptitude as a packet manager.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
  Uname: Linux 3.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu15
  Architecture: amd64
  DKMSKernelVersion: 3.5.0-18-generic
  Date: Tue Nov 20 23:13:23 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
  MarkForUpload: True
  PackageArchitecture: all
  PackageVersion: 4.1.12-dfsg-2ubuntu0.2
  SourcePackage: virtualbox
  Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

  [Impact]
  Users are not able to use virtualbox from the repository on 12.04 with 3.5 kernel. It is totally broken.
  The patch proposed backports only the relevant parts from upstream to fix the bug.
  The patch is from: https://www.virtualbox.org/changeset/41660/vbox

  [Test Case]
  Upgrade to 3.5 kernel on 12.04 and install virtualbox.

  [Development Fix]
  Fixed during Quantal cycle.

  [Stable Fix]
  Is being fixed in 4.1.12-dfsg-2ubuntu0.3 upload to precise-proposed.

  [Regression Potential]
  It is best to use the latest upstream version. But since that will cause major disruption, we have to track this package and corresponding bugs for regressions.

  jamespage: Please also check backwards compatibility with the 3.2
  kernel; the patch should support this but best to make sure (not all
  12.04 installs with have 3.5).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1081307/+subscriptions