Simics Virtual Machine Solaris8 operating system obtains files on host system win7 in two ways

Simics Virtual Machine Solaris8 operating system obtains files on host system win7 in two ways
1. The environment settings described in this article are as follows:
? Host operating system: Windows 7 Ultimate
? Parasitic Operating System: Solaris 8 iSCSI (SunOS 5.8)
? Virtual Environment: Simics 3.0.4
This document assumes that the Solaris 8 iSCSI operating system has been installed on Simics.
Motivation: GraphGen, a binary file that can run in a Unix environment, cannot run on a single computer with Ubuntu, because the hardware architecture of the computer is based on X86, graphGen is a program that can run under the iSCSI architecture. I installed Virtual Box on my laptop Win7 system, and then installed Solaris 8 on The iSCSI architecture. The installation was unsuccessful, this cannot be achieved because of AMD, my laptop. the feasible solution is to install the Solaris 8 or higher-level Linux OS using the Simics virtual environment on the laptop, then, copy the GraphGen file on Win7 to the Solaris 8 operating system in Simics to run the GraphGen program. This "copy" process is not as easy as it involves communication between the host operating system and the parasitic operating system. This document describes the "copy" method and process.
2. Two methods for obtaining files on the host system. 2.1 use mount cd to obtain files on the host system. The main steps are as follows:
1. package the files that need to be used by the Solaris 8 iSCSI system on Windows 7 into the iso Image File Format (UltraISO can be used in this packaging process. I use UltraISO Premium Edition 9.6.2.3059, because I did not find the registration code for the software, I only use the trial version, but it does not affect file packaging. In fact, the specific version does not matter); for example, the Simics installation directory \ import \ sun4u under the two files mount_simicsfs and simicsfs-sol8 package into the file myimage. iso (the operation in UltraISO is very simple. Select the two files and save them as myimage. iso ).
2. put the packaged iso image file in the Simics working directory folder (for example, F: \ OS \ simics \ workspace). For example. copy iso to F: \ OS \ simics \ workspace.
3. If the Solaris 8 parasitic system has been successfully started, enter the following commands on the Simics Main Interface: new-file-cdrom myimage. iso and cd0.insert myimage, 1.
Figure 1: input the command to load the iso file in Simics 4. in this case, under the folder/cdrom/cdrom0/of the parasitic system Solaris 8 iSCSI, you will see the two files before packaging (see figure 2 ), this allows you to access the host operating system files. You can copy these files to any place you need. As you can see, the parasitic system Solaris 8 only retains the first eight digits of the file name, but the file content does not change.
Figure 2: view files in iso in the parasitic system Solaris 8 iSCSI
2.2 perform corresponding settings to directly access the files on the host system. When we often use the parasitic system, we will feel that it is inconvenient to obtain the files on the host system through the mount cd method, therefore, it is best to use a method to directly access a drive disk of the host system (for example, the content under drive C of Win7 system ). The methods to achieve the above objectives are as follows:
1. create a new folder (mkdir/usr/lib/fs/simicsfs/) in the parasitic system Solaris 8 /), mount the simicsfs file in the \ import \ sun4u installation directory of Simics to the preceding folder and rename it mount. Similarly, put the file simicsfs-sol8 under \ import \ sun4u in the Simics installation directory to the folder of the parasitic operating system/usr/kernel/fs/sparcv9, and name it simicsfs (actually the parasitic system will automatically truncate the file name to 8 bits, in Solaris8, we don't see the file name simicsfs-sol8, 2 ).
2. Edit the/etc/vfstab file in Solaris 8 of the parasitic system and add a line (separated by spaces-) to the file -),
Simicsfs-/host simicsfs-no-
Note: When you use vi to edit the file, the content displayed on the screen is not the actual file content. You can use the up and down arrows to press the buttons to display the actual content. After adding the content, run the cat command to check whether the specifications have been added.
3. In the root directory of the parasitic system, create the host folder (mkdir host ).
4. Execute the mount/host command in the parasitic system. Then, you will find that all files in the host folder are in the C drive of the Win7 system. 3.

Figure 3: directly obtain the content of drive C in Win7 from the parasitic system Solaris 8 or later. 3. The virtual machine operating system under Simics stores the operating state of the parasitic system, which is non-memory, when you restart the parasitic operating system next time, all changes to the last operating system will disappear. After obtaining the files of the host operating system in the preceding two methods, or saving some response settings, we must save the operating status of the parasitic operating system, to facilitate the next startup. The procedure is as follows:
Save the status at a time point:
1. In the Simics command input area, enter stop; 2. In the Simics command input area, enter save-persistent-state [your own status name];
3. Enter run in the Simics command input area to continue running the system.
Start from a certain status:
1. enable new session from peanut-common.simics;
2. In the Simics command input area, enter the load-persistent-state [your own status name];
3. In the Simics command input area, enter run to run the system.
For example, I named solaris_8_sf.boot from the status in section 2.2. 4. The problem is as shown in Figure 3. I have successfully transferred the GraphGen program to the parasitic operating system and can run it in Solaris 8. The program is still not running successfully. The following result is displayed:
Ld. so.1:./GraphGen: fatal: libstdc ++. so.2.10.0: open failed: no such file or directory
It can be seen that this program can run on the Solaris 8 iSCSI, but a shared library is missing. It can be seen that the hardware architecture has been broken through, and it is a step further to the successful running of the program.