Custom Query (16363 matches)
Results (331 - 333 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3535 | obsolete | Delayed Write Failed error with Windows XP VM using Shared Folders | ||
| Description |
I'm running a Windows XP VM in VirtualBox 2.1.4 under RedHat (RHEL) 5.3. It's on a very beefy box -- Dell M6400 quad core extreme with 12GB RAM and an SSD. In general the VM runs great. More stable and faster than when Windows is running natively on my other laptop. The problem that I encounter is when I have active files located on a VB shared folder; I often will get a Delayed Write Failed error message and the files may be mangled. One file where this was occurring frequently was my primary Outlook data folder. I had to move it out of the shared folder and into the Windows dedicated C: drive. I constructed the shared folder as follows:
In VirtualBox, I then defined the Shared Folder for the VM using the administration GUI tool. The folder shows up on Windows as a Network Attached Drive mapped to a drive letter. Typical nonintensive tasks can manipulate the files fine. But if an application updates the file frequently, such as an Outlook PST, xcopy of a large number of files to an alternate drive, Word save files, etc., I receive the delayed write error. Attempts to backup the folder from Windows using tools like xcopy and robocopy fail with this error too, and I get very nervous going more than a day or two without a complete, versioned backup of my work. My intent is to be able to share access and update of these files concurrently from within Linux and Windows. I really don't want to be copying or synchronizing files between the environments, particularly since it is my intent to eventually be running 4-6 VM's concurrently. The complexity goes up exponentially with the number of VM's sharing the folder(s). Please tell me what additional information I can supply to assist you with diagnosing and correcting this problem. If Shared Folders really aren't intended to be used with highly volative files, is there an alternative approach that you would recommend. Since this is exposed on Windows as a network drive, I don't know of any way to manipulate things like the Windows file caching strategy, etc. I did set the VBOX_DISABLE_HOST_DISK_CACHE=1 in my /etc/profile so that VirtualBox would inherit the setting, but that didn't seem to correct the issue. I absolutely love the product. IMHO it's simple to use yet run's Windows in a VM far better than Windows is capable of running itself natively. I recommend it to all of my clients. So I'd really like to help you diagnose and fix this issue. Thanks! |
|||
| #3548 | obsolete | VBoxSVC holds vm xml definition file open after VM is unregistered => Fixed in SVN | ||
| Description |
Executing a VBoxManage unregistervm <vmname> successfully unregisters the VM from the host. VBoxSVC fails to close the vm definition xml file and continues to hold open a R/W lock (FD flag u). This is noticeable if another VM is running because VBoxSVC will continue to run. VBoxSVC should close any open files belonging to a vm when unregistering it. lsof output shows COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME VBoxSVC 27907 vmuser 25u REG 0,24 3053 106102849 /vmuser/vmachines/Machines/1084/1084.xml |
|||
| #3550 | obsolete | VboxSVC on windows does not always exit when run under two login names. | ||
| Description |
Hi Running vboxheadless as a service on windows (http://forums.virtualbox.org/viewtopic.php?f=6&t=15450&start=0) launches virtualbox using the localsystem account. If the user then launches the vbox gui logged in as a normal user then two vboxsvc processes are visible in taskmanager. Exiting both the user and the service seems to leave behind one of the vboxsvc process. This process cannot be 'end tasked' using task manager or Process Explorer. From that point the gui cannot be launched. It reports a locking error on the virtualbox.xml file. Only a reboot clears this left over vboxsvc process releasing the xml file. I believe that this problem is related to vboxsvc being run under two different user names concurrently but it is difficult to say exactly. Please let me know if I can provide further information (and what that information would be). Thanks |
|||

