Difference between revisions of "Transfer files from the host OS to the virtual drive"
(Mention FTP / HTTP idea)
|Line 1:||Line 1:|
Many users prefer to test ReactOS under emulators and virtualization software like QEMU or VMware, but for testing their software they will need to copy their files into the .iso images and add them into proper directories which can become a difficult job. A way around this is to mount the virtual hard drives as disk drives attached to the system itself.
Many users prefer to test ReactOS under emulators and virtualization software like QEMU or VMware, but for testing their software they will need to copy their files into the .iso images and add them into proper directories which can become a difficult job. A way around this is to mount the virtual hard drives as disk drives attached to the system itself .
== In Windows==
== In Windows==
Revision as of 09:45, 30 June 2013
Many users prefer to test ReactOS under emulators and virtualization software like QEMU or VMware, but for testing their software they will need to copy their files into the .iso images and add them into proper directories which can become a difficult job. A way around this is to mount the virtual hard drives as disk drives attached to the system itself (an alternative way might be to have a machine with FTP or HTTP server and use ReactOS ftp or iexplore to receive files).
- 1 In Windows
- 2 Linux
ImDisk Virtual Disk Driver
ImDisk is a virtual disk driver for Windows NT/2000/XP/2003/Vista/2008. It can use one or more disk image files to create virtual hard disk, floppy or CD/DVD drives .The install package installs a console-mode control program called imdisk.exe and a Control Panel applet. After install is finished, type imdisk without parameters for syntax help or double click the ImDisk icon in the Control Panel. It also adds a menu item in Windows Explorer so that you can right-click on a file to mount it as a virtual disk drive. Users of mdconfig in FreeBSD will probably be familiar with the command line syntax of imdisk.exe. The driver, service and control program can be uninstalled using the Add/Remove programs applet in the Control Panel. No reboot is required for installing or uninstalling.
The install package also contains a user-mode helper service that enables the virtual disk driver to forward I/O requests to other computers on the network. This makes it possible to boot a machine with NTFS partitions with a *nix Live-CD and use the included devio tool to let ImDisk on another computer running Windows on the network mount the NTFS partition on the machine you booted with the *nix Live-CD. This way you can recover information and even run chkdsk on drives on machines where Windows does not boot.
Simple mount example,
imdisk -a -t vm -m #: -f C:\Users\encoded\.VirtualBox\HardDisks\reactos.vdi
VMware Disk Mount
- VMware Disk Mount Utility is easier to use but will work only with .vmdk files.(Official VMware virtual disk file format.)
- Download and install the tool which is available at the VMware website.
- Start Command Prompt.
- Move to the installation directory (e.g. C:\Program Files\VMware\VMware DiskMount Utility\)
- Mounting the virtual drive.
Issue the following command,
vmware-mount z: C:\ReactOS\ReactOS.vmdk
What it does,
vmware-mount - Starts the mount application. z: - Drive letter for the mounted drive. (You can use any free drive letter.) ...(Path) - Path to the virtual disk drive. NOTE: - The path above is an example. Use the path where you have saved your .vmdk file.
Unmounting the virtual drive
To unmount the virtual drive issue the following command,
vmware-mount z: /d
What it does,
vmware-mount - Starts the mount application. z: - Drive letter for the virtual drive to be unmounted. /d - Unmounts the drive.
- More information on other options can be found in the VMware mount documentation.
- VDK (Virtual Disk Driver) can mount vmdk and raw format virtual drives which are supported by QEMU and VMware.
Getting the driver (VDK)
You can download VDK from here (x64 here). At the time of writing of this HOWTO the latest version is version 3.2. Download the .zip file and extract it to your desired folder using your favourite archiver.
Setup the driver
- Open the command prompt and move to the folder where you have extracted VDK using
cdcommand (e.g. C:\VDK).
- Issue the following command with the command prompt in the same directory,
vdk install /auto
/AUTO Configures the driver to start at the system startup (Note: this option does not start the driver after installation is completed). By default the driver has to be started manually.
The Virtual Disk kernel-mode Driver (vdk.sys) is copied to %SYSTEMROOT%\system32, you may need administrator privileges to install the driver.
Start the Driver
Even though the driver is installed, it may not be actually running. To start it issue the following command,
If the driver is not already installed, this command attempts to install it with the default options. It is recommended that you use
vdk install /auto so that you do not have to manually start the driver every time.
Mounting the virtual drive
VDK.EXE OPEN disk# image [/RW | /WB | /UNDO] [/P:part#] [/L:drive]
disk# Specifies the virtual disk number. This must be the first parameter. '*' means the first available disk, and if all existing disk is busy a new virtual disk is created. image Specifies the path to the disk image file. This must be the second parameter. /RW Open the image in Read-Write mode. /WB Open the image in Write-Block mode. /UNDO Creates a REDO log for the image and open in Read-Write mode. /P:part# Specifies a partition number to set a drive letter. Drive letters can be set/removed later with LINK/ULINK commands. By default, drive letters are assigned to all mountable partitions. /L:drive Specifies drive letters to assign to partitions.By default, the first available drive letter is used.
Only one of /RW, /WB and /UNDO can be used at a time. When none of these is specified, the image is opened in Read-Only mode.
- Example of Vdk usage
In the vdk directory issue the following command,
vdk open * C:\ReactOS\ReactOS.vmdk /rw
Unmounting the virtual drive
Once you are done using the virtual drive it needs to be unmounted. This is done by issuing the following command,
vdk close *
Failure to do this will result in the drive being locked and usable to VMware or QEMU.
Stopping the driver
If you want you can stop the driver using,
More details and options are available in the Readme.txt in the previously downloaded .zip file.
Mounting a QEMU image
Most Linux distributions allow you to mount virtual disk images using the
mount command. Ubuntu is used in this example, but it should work in most distributions.
For most of these actions you will need root access, so use the
sudo command. You will need to enter a password for this.
First you need to create a mounting directory,
sudo mkdir /media/ReactOS
Then, make sure your virtual image file is in RAW format. I created my image in QEMU Launcher, where you can select this format. If your image is in QCOW format, you can use the following command to convert to RAW,
qemu-img convert <image-file> -O raw <image-file.raw>
After this is done, you can mount the image,
sudo mount -o loop,offset=32256 <image-file> /media/ReactOS -t vfat
When you are done using the image file, you can unmount it easily by using,
sudo umount /media/ReactOS