Ticket #1369 (new defect)

Opened 7 years ago

Last modified 7 years ago

createrawvmdk with partition switch: sharing violation

Reported by: SAP.pie Owned by:
Priority: major Component: virtual disk
Version: VirtualBox 1.5.6 Keywords: VERR_SHARING_VIOLATION
Cc: Guest type: other
Host type: other


Good afternoon,

after a flawless installation of a W2K Professional SP4 Guest on a Vista SP1 Host (not all of my programs are cooperating well with Vista) I tried to enable the raw hard disk support of Virtual Box.

I have several NTFS-Partitions, the last one listed is intended to be accessible to the guest.

The listpartitions command gives me the partition no. 4:

VBoxManage internalcommands listpartitions -rawdisk \.\PhysicalDrive1

Output: VirtualBox Command Line Management Interface Version 1.5.6 (C) 2005-2008 innotek GmbH All rights reserved.

Number Type StartCHS EndCHS Size (MiB) Start (Sect) 1 0x27 0 /32 /33 130 /170/40 1024 2048 2 0x07 130 /171/1 1023/254/63 30728 2099223 5 0x07 1023/1 /2 1023/254/63 102437 65031184 6 0x07 1023/1 /1 1023/254/63 5122 274824018 4 0x07 1023/0 /1 1023/254/63 13311 285314400

O.K., so I entered:

VBoxManage internalcommands createrawvmdk -filename "C:\P4.vmdk" -rawdisk \.\PhysicalDrive1 - partitions 4

Output: ERROR: VMDK: could not create new partition data file 'C:\P4-pt.vmdk' Error code VERR_SHARING_VIOLATION at C:\vbox\branch\w32-1.5\src\VBox\Devices\Storage\VmdkHDDCore.cpp(2224) in function vmdkCreateImage Error while creating the raw disk VMDK: VERR_SHARING_VIOLATION

Even dismounting the partition by removing the drive letter in Vista's Disk Management leads to the same effect.

Omitting the -partition parameter works, no sharing violation, but then all my physical partitions are accessible to the guest.

Any suggestions would be appreciated. Thanks in advance.

Change History

comment:1 Changed 7 years ago by frank

  • Component changed from other to virtual disk
Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use