This bug was fixed in the package virtualbox-ose - 3.2.0-dfsg-1ubuntu1
---
virtualbox-ose (3.2.0-dfsg-1ubuntu1) maverick; urgency=low
* Merge from Debian unstable, remaining changes:
- Set x11 backport switch to lucid.
- VirtualBox should go in Accessories, not in System
The upcoming release 3.2 as well as the maintenance release 3.1.8 will
rename the kernel module from vboxvfs.ko to vboxsf.ko. This will allow
the kernel to load the module on demand so no further change should be
necessary.
--
[lucid] vboxsf mounts defined on /etc/fstab cause errors on boot:
** Changed in: virtualbox-ose (Ubuntu)
Status: New = Triaged
** Changed in: virtualbox-ose (Ubuntu)
Importance: Undecided = Medium
** Tags added: upstart
** Summary changed:
- [lucid] vboxsf mounts defined on /etc/fstab cause errors on boot
+ [lucid] vboxsf mounts defined on
Sensiva,
you report relates 2 different problems.
The fact that there was an error and the filesystem was not mounted is
the one being addressed on this bug report, the fix requires a change
to the virtualbox-ose package.
The fact that the boot stopped *even in recovery mode*, is related to
bug
On Tue, 2010-04-20 at 23:46 +, Steve Langasek wrote:
Scott, would 'start on mounting TYPE=vboxsf' also work here?
Yes!
That's a really good idea, I hadn't thought of that.
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
[lucid] vboxsf mounts defined on /etc/fstab cause errors on boot
On Tue, 2010-04-20 at 22:38 +, Sensiva wrote:
So bottom line is the expected behavior in normal boot mode is either
mounting that shared folder or skipping it if error occurs with a
warning message. In recovery boot mode it should continue to the
recovery menu even if an error occurred.
Sensiva,
the fact that the error was not shown is related to the bug Scott was setting
the duplicate to.
I am re-opening the bug for the aspect that the filesystem is not
mounted and causing an error instead.
Scott,
The mount.vboxfs is provided by the virtualbox-guest-additions package.
The
mountall doesn't care about modular filesystems; it sounds like
virtualbox-guest-additions needs an Upstart job to load the module on
starting mountall
** Changed in: mountall (Ubuntu)
Status: Incomplete = Invalid
--
[lucid] vboxsf mounts defined on /etc/fstab cause errors on boot
I will attempt to provide a patch to replace the current
/etc/init.d/virtualbox-ose-guest-utils with an upstart job.
According to Scott's feedback the start should be something like:
start on starting mountall
task
exec modprobe vboxsf
--
[lucid] vboxsf mounts defined on /etc/fstab cause errors
Please note that vboxsf stops the boot process even when choosing
recovery mode (an error message is given tho). I am not sure this is
related to plymouth too or not. In such situation I used to recover
using alternate CD.
So bottom line is the expected behavior in normal boot mode is either
That script is from the virtualbox-ose source package; not sure why this
was assigned to virtualbox-guest-additions.
Scott, would 'start on mounting TYPE=vboxsf' also work here?
** Package changed: virtualbox-guest-additions (Ubuntu) = virtualbox-
ose (Ubuntu)
--
[lucid] vboxsf mounts defined
11 matches
Mail list logo
