Thank you for reporting this bug to Ubuntu.
Ubuntu Intrepid isn't supported anymore.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
** Changed in: virtualbox-ose (Ubuntu)
Status: Triaged = Invalid
--
[intrepid] failed to power virtual
Hi all,
I ran into the same problem today. It is quite easy to resolve by performing
the following.
On intrepid:
packages that have to be installed are:
virtualbox-ose
virtualbox-ose-source
dkms
linux-headers-server|generic|
dkms will compile the driver once it retrieves the new
Hi Daniel,
I maybe f$#k'd-up my laptop yesterday evening for you, so I hope we get a
step closer to a solution for you ;-)
I upgraded my installation to Intrepid, and I have VirtualBox 2.0.2 running.
Can we compare these commands' results between us please?:
--
[EMAIL PROTECTED]:/etc/init.d$
I was suffering of various Intrepid problems, so I reinstalled
completely the system using the latest daily image (20081006). All
virtualbox related problems disappeared including the spawning session
problem. But when I run the commands you ask for I still have a
different results :
/etc/init.d$
probably I installed package virtualbox-2.0 and you virtualbox-ose and
that could cause the described difference. Close this down?
--
Stephan van Ingen
Freelance IT
(IBM Power, Ubuntu, RPG, Cobol, ILE, php, databases)
[EMAIL PROTECTED]
--
2008/10/8 Daniel Stoyanov [EMAIL PROTECTED]
I was
As I have mentioned in my bug report (the first message) :
System :
Intrepid up to date
Virtualbox :
virtualbox-ose (2.0.2-dfsg-0ubuntu2)
virtualbox-ose-source (2.0.2-dfsg-0ubuntu2)
I have the latest virtualbox from the repositories.
--
[intrepid] failed to power virtual machine
My command gives this result:
Usage: /etc/init.d/vboxdrv
{start|stop|stop_vms|restart|force-reload|status|setup}
I assume you have an earlier version of VirtualBox running: I suggest you
upgrade that to 2.0.2 first,
--
Stephan van Ingen
Freelance IT
(IBM Power, Ubuntu, RPG, ILE, php,
$ sudo /etc/init.d/vboxdrv setup
* Usage: /etc/init.d/vboxdrv {start|stop|restart|status}
If you mean status :
$ sudo /etc/init.d/vboxdrv status
* VirtualBox kernel module is not loaded.
I tried also :
$ sudo /etc/init.d/vboxdrv start
* Starting VirtualBox kernel module vboxdrv
This issue is back again for me, I have not changed any virtualbox.*
package or virtualbox related configuration. I think it's related to
upgrade of other package. Friday virtualbox was working as usual, I
launched it today and the bug reappeared. I have put as attachment all
the package upgrades
Yes it is related to upgrade. Run:
*sudo /etc/init.d/vboxdrv setup*
What's the result?
--
Stephan van Ingen
Freelance IT
(IBM Power, Ubuntu, RPG, ILE, php, databases)
[EMAIL PROTECTED]
--
2008/10/5 Daniel Stoyanov [EMAIL PROTECTED]
This issue is back again for me, I have not changed any
So, I ran this:
*sudo /etc/init.d/vboxdrv setup*
... and my Virtualbox as running again with the new kernel-version.
So: is this now still a bug or just a
virtualbox-startup-check-improvement-opportunity (or how do I phrase that?
;-))
ciao,
Stephan.
--
Stephan van Ingen
Freelance IT
(IBM
I have the impression that the problem came up at the moment I received a
kernel update via apt/update manager: is that plausible?
I rebooted with previous version of linux kernel, and Virtualbox started
without problems.
To my understanding this bug needs to be forwarded to Sun/Innotek to
tell
Hi Stephan did you try to purge the package and then reinstall it (as
described above), this worked for me and I don't have this issue
anymore.
--
[intrepid] failed to power virtual machine message spawning session... freeze
https://bugs.launchpad.net/bugs/272064
You received this bug
Thanks, I haven't tried that yet since my hypothesis is that only one last
step of installation is to be re-done, I assume that that would indeed work:
but only for that one kernel-upgrate. At the next kernel-upgrade the same
issue will come up, I think...
I first want to test a bit further to
I purged and reinstalled, and it now works fine. /dev/vboxdrv exists. It
must be an upgrade issue of some kind.
virtualbox-ose/intrepid uptodate 2.0.2-dfsg-0ubuntu3
--
[intrepid] failed to power virtual machine message spawning session... freeze
https://bugs.launchpad.net/bugs/272064
You
Hew:
What packages did you start from when you were doing upgrades? If it was
within intrepid that it broke, we'll need to get someone to test the
hardy-intrepid upgrade to see if it breaks there too (which is the higher
priority)
On Sat, Sep 20, 2008 at 01:49, Hew McLachlan
[EMAIL
This install is fresh Intrepid (starting Alpha 1). I started with
virtualbox-ose 1.6.2-dfsg-1ubuntu2.
** Changed in: virtualbox-ose (Ubuntu)
Status: Confirmed = Triaged
--
[intrepid] failed to power virtual machine message spawning session... freeze
https://bugs.launchpad.net/bugs/272064
Make sure that you have a /dev/vboxdrv . If not, did the module not get
loaded automatically?
** Changed in: virtualbox-ose (Ubuntu)
Status: New = Incomplete
--
[intrepid] failed to power virtual machine message spawning session... freeze
https://bugs.launchpad.net/bugs/272064
You
I'm getting this problem as well. It was working fine in previous
sessions..
I don't have /dev/vboxdrv , and can't see any vbox module. Any ideas?
** Changed in: virtualbox-ose (Ubuntu)
Importance: Undecided = Medium
Status: Incomplete = Confirmed
--
[intrepid] failed to power
Try to /etc/init.d/vboxdrv restart and see if the module gets loaded
On Fri, Sep 19, 2008 at 12:43, Hew McLachlan
[EMAIL PROTECTED]wrote:
I'm getting this problem as well. It was working fine in previous
sessions..
I don't have /dev/vboxdrv , and can't see any vbox module. Any ideas?
**
Thanks Mario sudo /etc/init.d/vboxdrv restart , solved the freeze, but
I have to do it on every reboot.
--
[intrepid] failed to power virtual machine message spawning session... freeze
https://bugs.launchpad.net/bugs/272064
You received this bug notification because you are a member of Ubuntu
Hi Daniel:
Can you check your init script run levels for vboxdrv? When the init script
was initially installed, it should have installed to runlevels 2 3 4 5 I
believe.
On Fri, Sep 19, 2008 at 13:58, Daniel Stoyanov
[EMAIL PROTECTED]wrote:
Thanks Mario sudo /etc/init.d/vboxdrv restart ,
/etc/init.d/vboxdrv restart fixed the problem for me as well (at least
for this session).
It looks like runlevels 2 3 4 5 to me. I think this is the relevant
section of /etc/init.d/vboxdrv :
### BEGIN INIT INFO
# Provides: vboxdrv
# Required-Start: $syslog
# Required-Stop:
# Default-Start:
If you purge and reinstall the package, can you see if it gets installed to
the appropriate runlevels? It's working on startup for me, but I did a
fresh install. We can identify or rule out upgrade problems here if you
give this a shot.
On Fri, Sep 19, 2008 at 23:32, Hew McLachlan
[EMAIL
24 matches
Mail list logo
