ModEdit; related ticket:#18766: 6.0.10 r132072 crashes Windows VM when Shared Folders are used
Anyone seeing a bluescreen in the guest using the latest 6.0.9 guest addtions? Medium or even some shared folder usage will trigger it. Latest working for me is 6.0.9-130641.
Tried with Server 2012 R2 and 2016 so far. Win 7 seems to be unaffected.
Log excerpts rarely are helpful. Zipped full logs have a better chance.
Additionally, we are users, not the devs. If you are using a test build (odd-numbered version) this info should go to those who provided the test build. Check for where you downloaded the test build and see if there is a place to post this zipped full log & description of the problem there.
> Log excerpts rarely are helpful. Zipped full logs have a better chance.
I just want some confirmation before I open a bug report or pursue this further. If you are using a test build its pretty easy to confirm. If not just skip this post
Win 10 1903 just dies when accessing the vm shared folder. The 6.0.97 130969 actually actually work despite probably not supported in any way with 6.0 so this seems to be confined to current 6.0.9.
frg wrote:I just want some confirmation before I open a bug report or pursue this further
Right. Don't open a ticket yet. And as scottgus1 said, start by posting a complete VBox.log from such a session.
We need to see a complete VBox.log, from a complete VM run, where the problem occurs:
Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Hello,
I just upgraded my Virtual Box to 6.0.10 on my Mac. After upgrading, I installed the extension pack and the guest edition pack for my Windows 10 guest.
The Windows 10 guest mounts 2 folders from my MAC as all my software development is done using these folders. When I try and run applications from these 2 mounted folders Windows 10 gives me an inpage fault error and says it cannot run these applications. If I move these .exe files to the "C" drive then everything works.
This did not happen to me on the previous version of Virtual Box.
RegF wrote:This did not happen to me on the previous version of Virtual Box.
Does it not happen if you downgrade VirtualBox? And what's the previous version you're talking about, 6.0.8?
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
What's your host? Exactly please, including build, version, bitness (32- or 64-bit).
What's your guest? Exactly please, including build, version, bitness (32- or 64-bit).
What's the share type? Read-Only or Read-Write? Auto-mounted or not? Letter manually assigned or not, if auto-mounted?
Examples that I've actually tried:
Host: OSX 10.11.6 (15G22010).
Guest: Windows 7, build 7601 SP1, 32-bit.
Share: Read-only, NOT automounted.
Result: NO CRASH
Host: Mint 19, 4.18.0-17-generic !#18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019 x86_64.
Guest: Windows 7, build 7601 SP1, 32-bit.
Share: Read-only, NOT automounted.
Result: NO CRASH
I have a feeling that it's for Read-Write shares, where the Windows Explorer is trying to create or modify the "Thumbnails.db". I have that turned off on my Win VMs, maybe that's why I can't reproduce it.
Adding the ticket info in the first post...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Try to remember your last version, or look at your older logs, they might still be logs from the older version.
Downgrade a couple of versions in the 6.0.x series, or to the 5.2.x series.
We can't go on without any evidence. You got to help us help you...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
For me it occurs with a r/w automounted share. 2 Different 8.1 Pro hosts (Core2Duo and Dual Xeon E5 V2). Windows 7 x64 sometimes takes longer to go down. Server 2012 R2 2016 Windows 10 x64 Windows 8.1 more or less an immediate guest crash. Log from above still applies.