#10408 closed defect (fixed)

Can't open a Word document located on a shared folder => Fixed in SVN

Reported by:	mbutton	Owned by:
Component:	shared folders	Version:	VirtualBox 4.1.12
Keywords:		Cc:
Guest type:	Windows	Host type:	Linux

Description ¶

Hey guys,

since I upgraded to 4.1.10 and then 4.1.12, I just can't open a Word file located on my shared folder anymore. I tried several times, with different docs and the problem is confirmed. Using 4.1.10, the VM crashes at once, and using 4.1.12, it freezes severly and I have no other choice than to kill it.

Didn't have any problem in 4.0.16 ...

Thanks !

Attachments (3)

20120404_VBoxCrash.tar.gz (88.3 KB ) - added by mbutton 13 years ago.: Logs of VirtualBox (4.1.8 working, 4.1.10 & 4.1.12 crashing)
Mini080911-01.dmp (128.0 KB ) - added by mbutton 13 years ago.: WindowsMiniDump
VBoxSF.zip (121.0 KB ) - added by sunlover 13 years ago.: Windows 32 bit shared folders driver for VBox 4.1

Download all attachments as: .zip

Change History (32)

comment:1 by Frank Mehnert, 13 years ago

Please attach a VBox.log file of such a VM session.

follow-up: 3 comment:2 by sunlover, 13 years ago

How exactly do you open the Word file? Do you use the File/Open menu in Word? Or may be double click on the file icon in a folder? If you use Word, which version of Word is that?

in reply to: 2 comment:3 by mbutton, 13 years ago

Replying to sunlover:

How exactly do you open the Word file? Do you use the File/Open menu in Word? Or may be double click on the file icon in a folder? If you use Word, which version of Word is that?

I'm simply double-clicking on the Word file, in a Windows explorer, in my shared folder. Then I can see Word launching, thinking for a sec and then my VM crashes.

by mbutton, 13 years ago

Attachment:	20120404_VBoxCrash.tar.gz added

Logs of VirtualBox (4.1.8 working, 4.1.10 & 4.1.12 crashing)

follow-up: 5 comment:4 by sunlover, 13 years ago

Which version of Word do you use?

in reply to: 4 comment:5 by mbutton, 13 years ago

Replying to sunlover:

Which version of Word do you use?

Word 2007, more specifically, (12.0.6212.1000) SP1 MSO (12.0.6213.1000)

Last edited 13 years ago by mbutton (previous) (diff)

comment:6 by mbutton, 13 years ago

I then switched back to VB4.1.8 and everything's now back to normal.

comment:7 by Frank Mehnert, 13 years ago

With 'crash' you mean 'segfault'? In the logs you provided I don't see a crash, it seems the machines powered down normally.

follow-up: 9 comment:8 by Frank Mehnert, 13 years ago

You probably mean a BSOD in the guest. With 'switching back' to VBox 4.1.8 you mean that you downgraded the Guest Additions to 4.1.8, right?

in reply to: 8 comment:9 by mbutton, 13 years ago

Replying to frank:

You probably mean a BSOD in the guest. With 'switching back' to VBox 4.1.8 you mean that you downgraded the Guest Additions to 4.1.8, right?

By "crash", I mean the VM is brutally going back to the VirtualBox welcome screen an then Windows starts, detecting something went wrong since it offers to boot in safe mode.

Yes you're right : I took a look at the log to see what went wrong and I saw nothing there. I thought I wasn't qualified enough to get the messages right.

And switching back means I uninstalled VB4.1.12 and reinstalled 4.1.8 (as well as the Guest Additions)

follow-up: 11 comment:10 by Frank Mehnert, 13 years ago

I think downgrading the Guest Additions should be sufficient. And it would also help to verify that the problem is in the Guest Additions and not in the host part of VirtualBox.

in reply to: 10 comment:11 by mbutton, 13 years ago

Replying to frank:

I think downgrading the Guest Additions should be sufficient. And it would also help to verify that the problem is in the Guest Additions and not in the host part of VirtualBox.

Ok, makes sense. I'll let you know as soon as I update VB back to 4.1.12. For now, I really need to make my work progress ...

follow-up: 13 comment:12 by sunlover, 13 years ago

Do you use Vista 64 bit as the guest OS? I could not reproduce the problem with Vista 64 bit guest, Word 2007 and a Windows Vista host. May be this problem happens with the Linux hosts only.

Also please attach a recent minidump from you guest, if there are any. The minidump is usually located at c:\windows\minidump directory.

by mbutton, 13 years ago

Attachment:	Mini080911-01.dmp added

WindowsMiniDump

in reply to: 12 comment:13 by mbutton, 13 years ago

Replying to sunlover:

Do you use Vista 64 bit as the guest OS? I could not reproduce the problem with Vista 64 bit guest, Word 2007 and a Windows Vista host. May be this problem happens with the Linux hosts only.

Also please attach a recent minidump from you guest, if there are any. The minidump is usually located at c:\windows\minidump directory.

The minidump has been uploaded. As for the versions of the OS I'm using, here they are : Host : Ubuntu (11.04 Natty Narwhal) 64 bits Guest : Windows Vista SP1 32 bits

I guess it's interesting to see that the problem has evolved between VB4.1.10 & 4.1.12 : with 4.1.10, the VM immediately shuts down (no BSOD : straight to VirtualBox welcome screen), and with 4.1.12, the VM freezes badly : I completely lose control over it (no mouse nor keyboard response).

comment:14 by mbutton, 13 years ago

And I have to precise that it works fine with VB4.1.8.

comment:15 by sunlover, 13 years ago

The minidump is from August 2011. There are no newer minidumps in the guest, right?

comment:16 by Frank Mehnert, 13 years ago

priority:	blocker → major

comment:17 by mbutton, 13 years ago

Yes you're right, the minidump I uploaded is the only one present in that folder.

I'll try to reinstall VBox 4.1.10 without touching to the VBGA, as suggested by Frank

comment:18 by sunlover, 13 years ago

BTW, in the VBox.log I see that the VM has RAM size = 3GB. Please decrease the RAM size to 1GB and check if the problem still reproducible. Thanks.

comment:19 by mbutton, 13 years ago

Ok, I'll try this test tomorrow too, to help you diagnose more precisely the problem.

Still, I'm not sure this test is relevant since my VM did not have any problem with VB4.1.8 and 3GB RAM. (I didn't change the RAM amount just before the upgrade : it's always run with 3GB)

What do you think ?

Thanks

comment:20 by sunlover, 13 years ago

The shared folders code has been updated after 4.1.8. May be the new code fails with a bigger guest RAM. I could not reproduce the problem with a guest with 512MB. And at the moment I can't test a guest with 3+GB.

comment:21 by sunlover, 13 years ago

I finally was able to reproduce the problem. You do not have to test with 1GB guest RAM, thanks.

comment:22 by mbutton, 13 years ago

Okay great especially since I haven't taken the time to reinstall VB4.1.12 yet (shame on me).

Tell me if you need more information from me, I'll be glad to help (but as my Win VM is a work tool, I'm unfortunately not able to install / uninstall / start / restart as often as I'd like to)

by sunlover, 13 years ago

Attachment:	VBoxSF.zip added

Windows 32 bit shared folders driver for VBox 4.1

comment:23 by sunlover, 13 years ago

You can use the attached VBoxSF.sys. It fixes the problem.

How to install: Start a command line window in the guest as administrator. Make a backup copy of c:\windows\system32\drivers\VBoxSF.sys. Copy the attached VBoxSF.sys to c:\windows\system32\drivers\VBoxSF.sys. Reboot the guest.

comment:24 by mbutton, 13 years ago

Thanks for your reply.

Just out of curiosity, can you please explain in a line what happened ? Thanks

comment:25 by sunlover, 13 years ago

This was a bug introduced in 4.1.10, when we have rewritten the shared folders driver, while fixing other bugs. Some initialization was missed for the file control block.