We will now set up the virtual machine for the class project. Roughly, you need to take the following steps. Download and install VirtualBox software
Download and import CS144 virtual machine image
Set up shared folder
Power on and log into the virtual machine
Step 1: Install VirtualBox Software Download and install the VirtualBox software.
In case you have a problem with the latest version, Version 4.3.20 for Windows and Mac OS X are known to work well. Follow the screen instructions to complete the installation.
If it asks for installation permission, give the permission.
Step 2: Import Virtual Machine Image Download the CS144.ova file. This is the virtual machine image for the class project. Since it is a very large file ( 1.2GB), it will take a while to download. Verify the integrity of the downloaded file by checking its checksum: SHA-1 checksum: 8c6118c805017c69a07e71ead54327f27efdd3a5 MD5 checksum: 5b33a6474925106639910f3890abb553 On OS X, you can run "shasum CS144.ova" to compute the SHA1 checksum of the downloaded file. On Windows, you can use this tool. Start VirtualBox.
Once it starts, select "File > Import Appliance..." menu. Choose the downloaded CS144.ova file and click "Next". Keep the default setting and click "Import" button. *Important*: DO NOT select "Reinitialize the MAC address..." option. Wait until import finishes. Once it is done, you will see the following window. Step 3: Setup Shared Folder You now need to set up a shared folder to transfer files between your host machine and the virtual machine easily. Create a new folder, say "C:\Users\cho\vm-shared", on your machine. This folder will be used as the shared folder between the host machine and the virtual machine. Press "Settings" button on VirtualBox. Select "Shared Folders" and double click "vm-shared" in "Folders List". Fill in the following information in the dialog box Folder Path: select the shared folder that you created. Folder Name: vm-shared. (*It has to be vm-shared* even if your created folder name is different.) Do not select "Read-only" and select "Auto-mount" Press "OK" buttons to close dialog boxes. Now your shared folder is set up. From now on, the "C:\Users\cho\vm-shared" folder on your host machine is accessible at "/home/cs144/shared/" in your virtual machine. If you copy a file to "C:\Users\cho\vm-shared" on your host machine, you can access the file in your virtual machine at "/home/cs144/shared/" and vice versa.Step 4: Start Virtual Machine and Login Press "Start" button on your VirtualBox. Once the system finishes booting up, you will see the following screen. Now you can login to the virtual machine using username: cs144 and password: password.SSH login to Virtual MachineIf desired, you can login to the virtual machine at "localhost" port 1442 using a secure shell client from the host machine. This access method will make it easy to "cut-and-past" some text from host to a file in your virtual machine, for example. On OS X, you can do it as follows: Open a terminal in the host and type the command 'ssh localhost -p 1442 -l cs144'
If the terminal asks 'Are you sure you want to continue connecting?', type 'yes'.
Then if the terminal asks for password, type 'password'.
Now you are inside the virtual machine.On Windows, you can use a secure shell client software, such as PuTTY.Turning Off VirtualBox To turn off your virtual machine, simply close the virtual machine terminal window. Then you will be prompted with 3 options. Save the machine state: Save the current state (and resume from the current sate later). This is the recommended "suspend" method.
Send the shutdown signal: Turn off the machine gracefully. This is the recommended "power off" method.
Power off the machine: Turns off the guest machine immdiately. Do NOT use this option.
For a reboot, type "sudo reboot" in the virtual machine terminal."Close"-->"Save the machine state". This will suspend the virtual machine. You can continue working at the suspended state when you run it next time. Powering off virtual machine: If you want to power off the virtual machine, you need to issue "sudo halt" within the command line of xterm and provide your password.
Rebooting virtual machine: For a reboot, issue "sudo reboot" inside the terminal of the virtual machine.
-->
The first step towards the Virtual installation is to get an ISO image of this old operating system. As I mentioned above that it is free and avail by Microsoft itself officially along with License key. Thus, use this link which will open the page of Archive.org, where click on the ISO image link given on the right side under the Download section, this will allow you to download Windows XP Professional SP3 x86 ISO image. Just on the same page, the free but official professional key for the same will have been given. Copy that and jot down somewhere like NotePad.
Windows Xp Ova Image Virtualboxl
To store the installation file we need to attach a Virtual Hard drive to our Virtual Machine. The VirtualBox will automatically set it to 10GB which is enough. Thus, leave the default settings and click on the NEXT. On the Next window, it will ask you to select the type of Virtual Hardrive, by default it will be VDI, however, here we are selecting VHD. It is because in case, tomorrow we want to run it under Windows Hyper-V, we can easily use the Windows XP VHD image. Next, Select Dynamic allocated option. File allocation and Size: By default, the VirtualBox will save all file of the machine on C: drive, if you want to change click on the folder icon and select the place. Finally, click on the Create button.
Select the created VirtualMachine and click on the Settings button given on the top menu of VBox. From Settings -> click on the Storage-> Empty CD icon under storage device-> again on CD icon of Attributes and then Choose Virtual Optical Disk File.An explorer will open select the downloaded Windows XP ISO image.
The import subcommand takes at least the path name of an OVF file as input and expects the disk images, if needed, to be in the same directory as the OVF file. Many additional command-line options are supported. These enable you to control in detail what is being imported and to modify the import parameters, depending on the content of the OVF file.
Use of the --options keepallmacskeepnatmacskeepdisknames option enables additional fine tuning of the import operation. The first two options enable you to specify how the MAC addresses of every virtual network card should be handled. They can either be reinitialized, which is the default setting, left unchanged (keepallmacs) or left unchanged when the network type is NAT (keepnatmacs). If you add keepdisknames all new disk images are assigned the same names as the originals, otherwise they are renamed.
In the above example, Item #1 specifies the name of the target machine in Oracle VM VirtualBox. Items #12 and #13 specify hard disk controllers, respectively. Item #14 describes a hard disk image. In this case, the additional --controller option indicates which item the disk image should be connected to, with the default coming from the OVF file.
You can combine several items for the same virtual system using the --vsys option. For example, to import a machine as described in the OVF, but without the sound card and without the USB controller, and with the disk image connected to the IDE controller instead of the SCSI controller, use the following command:
As the result of this operation, a file with the suffix .oci is downloaded to the local host. This file is a TAR archive which contains a bootable instance image in QCOW2 format and a JSON file with some metadata related to the imported instance.
Choose the format you would like to convert the image to. Hyper-V supports VHD and VHDX formats. VHDX is an improvement over the older virtual hard disk format, supporting up to 64 TBs of storage. Because this is a Windows XP VM, I will stick with a fixed VHD option called VHD Pre-allocated image.
ImgToVhd is a utility that creates VHD files from Macrium backup images. These can then be used to create a bootable virtual machine facilitating quick access to a failed machine whose repair would be time consuming or not possible.We have created a utility, ImgToVHD to enable the conversion of a Macrium backup image file to VHD files (one per disk). The VHD file(s) can then be used as the storage component of virtual machines from Microsoft (Virtual PC and HyperV), VMWare and Oracle/Sun (Virtual Box).This enables a previously backed up machine to be reincarnated as a virtual machine. A significant use of this is to quickly regain access to a machine that has suffered a fatal hardware failure.
Firstly, you will need an Macrium image file - a file and folder backup file will not work here. If you wish to create a bootable VM from scratch, and not just add a disk to an already bootable VM, then the image will need to contain an image of both the active and the windows system partition. Typically the system partition is also the active partition.You will need enough spare disk space to store the resulting VHD file. If you have selected all the partitions from the source image and the image is compressed, then the resulting VHD file size is likely to be rather larger than the source image as VHD files don't support compression and have a larger sparse granularity than the image files. Calculate the sum of the used space of the selected partitions and ensure that you have slightly more free space than this for the VHD file.Once you have selected a source image, a list of disks will be presented to you. Select from this, the one in which you will to convert to VHD and then you will be presented with a list of partitions. Select as many of these as you require. 2ff7e9595c
留言