August 6, 2014 at 22:30VMware ACE Workaround
Once I got into the hands of USB-hdd with software.
The necessary software was installed in a virtual machine and packaged in a
VMware ACE container . Nearby lay a small installation and configuration manual.
Since the disk was usb2.0, I, logically assuming that the operating speed when
starting the virtual machine would not be quite comfortable, started
copying to a test computer (total volume of about 500 GB.)
The next day I was "pleasantly" surprised by starting the installation . At the stage of
starting the virtual machine, a message appeared in which I was notified that the
launch is possible only from the source medium. I
did not begin to delete the copied data yet, but as it turns out later, we could safely press
shift + del.
To check, I tried to start from a usb drive. The virtual machine
started up successfully in VMware Player
With the thought “What will happen if the screw fails?” I began to study the insides and found the following points in
the virtual machine settings:
1. Changing the settings is prohibited in the properties of the ACE container (of
course there is no password ). But the virtual machine has
2. A network adapter that connects in bridge mode to the host adapter
3. A CD / DVD drive.
Further events could develop more rapidly, but the usb interface has
contributed.
In order:
1. Download the isone image of clonezilla (you can also use acronis, but I started cloning from one
virtual machine to another and all this happened within the same computer) 2. We create a virtual machine with approximately similar characteristics.
3. We start the virtual machine which is located on the USB drive and enter
its BIOS.
4. Right click on the cd / dvd drive icon. We mount the
iso-image downloaded in the first step .
5. Reboot. When downloading, press ESC (here I needed training) and
select the boot from disk.
6. We get into the familiar interface of your favorite distribution kit for cloning
disks.
7. Check that the virtual disk was successfully detected and run the
cloning interface on the source
8. On the newly created virtual machine, we perform steps 3-6, but specify the
parameters of the server from which the cloning and
destination disk will be executed (everything is extremely clear in the clonezilla interface).
9. We are waiting.
10. We are waiting.
11. We are waiting. My drives are not very fast. And the source is connected through, which
seemed fast five years ago, usb version 2.0
12. After the copy was finished, I received a copy of the virtual machine without being
tied to a specific device, and wrapped the disk with three layers of bubble wrap and put it in a safe.
I think I'm lucky.
The stars successfully converged.
But now I’m not worried because of possible problems with the external hard drive.
The necessary software was installed in a virtual machine and packaged in a
VMware ACE container . Nearby lay a small installation and configuration manual.
Since the disk was usb2.0, I, logically assuming that the operating speed when
starting the virtual machine would not be quite comfortable, started
copying to a test computer (total volume of about 500 GB.)
The next day I was "pleasantly" surprised by starting the installation . At the stage of
starting the virtual machine, a message appeared in which I was notified that the
launch is possible only from the source medium. I
did not begin to delete the copied data yet, but as it turns out later, we could safely press
shift + del.
To check, I tried to start from a usb drive. The virtual machine
started up successfully in VMware Player
With the thought “What will happen if the screw fails?” I began to study the insides and found the following points in
the virtual machine settings:
1. Changing the settings is prohibited in the properties of the ACE container (of
course there is no password ). But the virtual machine has
2. A network adapter that connects in bridge mode to the host adapter
3. A CD / DVD drive.
Further events could develop more rapidly, but the usb interface has
contributed.
In order:
1. Download the isone image of clonezilla (you can also use acronis, but I started cloning from one
virtual machine to another and all this happened within the same computer) 2. We create a virtual machine with approximately similar characteristics.
3. We start the virtual machine which is located on the USB drive and enter
its BIOS.
4. Right click on the cd / dvd drive icon. We mount the
iso-image downloaded in the first step .
5. Reboot. When downloading, press ESC (here I needed training) and
select the boot from disk.
6. We get into the familiar interface of your favorite distribution kit for cloning
disks.
7. Check that the virtual disk was successfully detected and run the
cloning interface on the source
8. On the newly created virtual machine, we perform steps 3-6, but specify the
parameters of the server from which the cloning and
destination disk will be executed (everything is extremely clear in the clonezilla interface).
9. We are waiting.
10. We are waiting.
11. We are waiting. My drives are not very fast. And the source is connected through, which
seemed fast five years ago, usb version 2.0
12. After the copy was finished, I received a copy of the virtual machine without being
tied to a specific device, and wrapped the disk with three layers of bubble wrap and put it in a safe.
I think I'm lucky.
The stars successfully converged.
But now I’m not worried because of possible problems with the external hard drive.