Vbox installation VM import or export problems

The problem of Virtual Machine import or export installed in vbox was previously solved by red hat installed in vmware. Now, by installing vbox, it is said that it cannot be started after the import is compatible. Then, reinstall vbox and find that it is installed on drive C, export it to drive E, delete drive C, and re-import the vbox_linux.ova file of drive E. The same reason is that it cannot be started.
After google, we finally solved the problem. The steps for www.2cto.com are as follows: 1. Place the Linux installation disc (if a CD disc is used, the first boot disc) into the optical drive and set the firmware CMOS/BIOS as the boot disc, when the Linux installation screen appears, enter "linux rescue" at the "boot:" prompt and press enter to enter rescue mode. (For details about the rescue mode, press F5 to View Details)
2. The system detects the hardware, guides the Linux environment on the CD, and prompts you to select the language you want to use in rescue mode in sequence. (We recommend that you select the default English language. Based on the test conducted by the author, in some Linux systems, garbled characters are displayed when Chinese characters are selected. The default "us" is used for keyboard settings. network settings can be used as needed. Most fault fixes do not require network connections, select "No ".
3. The system will try to find the root partition. By default, in rescue mode, the root partition of the hard disk is mounted to the/mnt/sysimage directory of the CD Linux environment. The default option "continue" indicates that the mounting permission is read/write; "Read-only" is Read-only. If detection fails, you can select "skip" to skip. In this example, you need to have the read and write permissions to fix the system. The default option is "continue ". After entering the next step, the system prompts to run the "chroot/mnt/sysimage" command to mount the root directory to the root directory of our hard disk system.
1. If you want to recover the dual-system boot, first use the above method to enter the rescue mode, and execute the chroot command as follows: java code sh-3.1 # chroot/mnt/sysimage www.2cto.com 2. Switch the root directory to the root directory of the hard drive system, and then run the grub-install command to reinstall GRUB: java code sh-3.1 # grub-install/dev/hda "/dev/hda" is the hard disk name, such as using a SCSI hard disk or Linux to install it on the second IDE hard disk, this setting must be adjusted accordingly. 3. Execute the exit command in sequence to exit the chroot mode and rescue mode (execute the exit command twice): Java code sh-3.1 # exit sh-3.1 # exit or: System Repair: java code # chroot/mnt/sysimage # cd/boot # mkinitrd-f initrd-· uname-r ·. img · uname-r ·
This is the command to re-package the core. For example, if you modify the driver of a device, you need to re-package the core if the driver is to be added to the core level, compile the newly added configuration into the core! The error you reported above is that you write the initrd-2.6.25.img into the initrd-2.6.265.img www.2cto.com but your format seems wrong, the complete mode is: # cd/boot/# mv initrd-2.6.25.img initrd-2.6.25.img.bak (back up the original core) # mkinitrd/boot/initrd-2.6.25.img 2.6.25 (rebuild the core) the last step can also be achieved through the following command: # mkinitrd/boot/initrd-'uname-R '. img 'uname-R' note that it is not a single quotation mark, but the character before 1 on the keyboard