Working 12.2 system. Upgraded to 13.1. System now enters boot-loop if the /etc/fstab entry for the shared folders is present. I have to use the live cd to enter rescue mode and remove it. If I try to mount after boot, it also fails unless I run ‘modprobe vmhfgs’; I have to do that every time I boot to be able to mount. And even after that, I also get an error “unable to update mtab, continuing” but it still mounts.
Reinstalled VMware tools to latest version with no errors - no effect.
I manually added the following lines to both boot.local as a workaround and it seems to work:
modprobe vmhgfs
mount -t vmhgfs .host:/vmware /mnt/hgfs/vmware/
I wish SUSE would implement some kind of basic regression testing with releases. This is vanilla install in VMware with a shared folder. I’m willing to entertain that it’s VMware’s fault, but their software worked fine in 12.2.
On 2013-12-24 16:36, CountBakula wrote:
>
> Working 12.2 system. Upgraded to 13.1. System now enters boot-loop if
> the /etc/fstab entry for the shared folders is present. I have to use
> the live cd to enter rescue mode and remove it. If I try to mount after
> boot, it also fails unless I run ‘modprobe vmhfgs’; I have to do that
> every time I boot to be able to mount. And even after that, I also get
> an error “unable to update mtab, continuing” but it still mounts.
You can use “nofail” in fstab, then boot will not halt.
> I wish SUSE would implement some kind of basic regression testing with
> releases.
You are supposed to test those things that interest you and report. It is your responsibility to the
community to do the testing. Who do you think does the testing? YOU! >:-)
This is a community, not a business.
If you think it is a bug, report it in Bugzilla.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Elessar))
On Tue, 24 Dec 2013 15:36:01 +0000, CountBakula wrote:
> I wish SUSE would implement some kind of basic regression testing with
> releases.
Have a look at OpenQA, which is used with openSUSE now. But there
certainly are things that will get missed by any regression test -
because software is complex. That’s why, as a community distribution,
it’s important to get involved in testing if you can, and report bugs
when you find them.
On 2013-12-25 15:36, bugmenot101 wrote:
>
> I have the exact same problem, only with VirtualBox (4.3.6) with
> OpenSuse 13.1 (with latest updates).
>
> Same bootloop due to a failure to mount the shared folder.
Add the option “nofail” to the fstab entry.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Elessar))
On 2013-12-26 12:56, dontbugme wrote:
>
> robin_listas;2611369 Wrote:
>> Add the option “nofail” to the fstab entry.
> That would solve the bootloop, but it won’t mount the shared folder. I
> might as well not add it to fstab at all.
If it boots, then you get control of the machine and can do things. If it does not boot, you can not.
You need loading certain module first. There was an entry in sysconfig to tell the kernel to load
named modules on boot, but I heard it was removed on 13.1 :-? Maybe you can try adding it by hand.
/sysconfig/kernel:
MODULES_LOADED_ON_BOOT="..."
Someone mentioned the name of the module on another thread. I don’t use virtualbox, so I don’t
remember it.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Elessar))
On 2013-12-26 17:56, bugmenot101 wrote:
> I don’t know if it’s a new issue since this is my first Suse virtual
> machine, but it definitely seems like a bug.
Report it in bugzilla… let them find out.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Elessar))