Mity CPU Platforms » MityDSP-L138 (ARM9 Based Platforms)

Vivek
Your best bet is the following:
Rename the existing VM
Re-import the VM from the ova image
Go in to settings for the newly imported VM and add your existing VM disk image to the new VM
mount the old VM image in your new VM as /mnt (or what ever you choose)
copy the files you want from the old image to the new

You can then remove the old disk from the new VM

Thanks Tim for your reply. As per your suggestion it seems I must have VM setup where it failed. But unfortunately, I did backup for .vmdk file only for my old VM setup.
I already installed new VM setup with ova image and now want to read from old .vmdk file. Is it possible?

Thanks,
Vivek

Hello Tim,

I also tried to add hard disk option in new VM for old .vmdk file . Then I tried to mount that in VM. below is the process.

mitydsp@vagrantup:~$ sudo fdisk -l
[sudo] password for mitydsp:

Disk /dev/sda: 128.8 GB, 128849018880 bytes
255 heads, 63 sectors/track, 15665 cylinders, total 251658240 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000ad2d4

Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048      499711      248832   83  Linux
/dev/sda2          501758   251656191   125577217    5  Extended
/dev/sda5          501760   251656191   125577216   8e  Linux LVM

Disk /dev/sdb: 128.8 GB, 128849018880 bytes
255 heads, 63 sectors/track, 15665 cylinders, total 251658240 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000ad2d4

Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *        2048      499711      248832   83  Linux
/dev/sdb2          501758   251656191   125577217    5  Extended
/dev/sdb5          501760   251656191   125577216   8e  Linux LVM

Disk /dev/mapper/vagrantup--vg-root: 127.0 GB, 127016108032 bytes
255 heads, 63 sectors/track, 15442 cylinders, total 248078336 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/vagrantup--vg-root doesn't contain a valid partition table

Disk /dev/mapper/vagrantup--vg-swap_1: 1572 MB, 1572864000 bytes
255 heads, 63 sectors/track, 191 cylinders, total 3072000 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/vagrantup--vg-swap_1 doesn't contain a valid partition table
mitydsp@vagrantup:~$ ls/mnt
bash: ls/mnt: No such file or directory
mitydsp@vagrantup:~$ sudo mount /dev/sdb1 /mnt
mitydsp@vagrantup:~$ ls /mnt
abi-4.2.0-27-generic memtest86+.bin
config-4.2.0-27-generic memtest86+.elf
grub memtest86+_multiboot.bin
initrd.img-4.2.0-27-generic System.map-4.2.0-27-generic
lost+found vmlinuz-4.2.0-27-generic

Now, how can I get the files from this. Please explain. Is anything I am missing?

Thanks,
Vivek.

I'm afraid the answer is probably to create a new ubuntu VM from scratch and then (after removing the image from any other VMs) add the vmdk image to it.
The problem with the approach I gave you is that the system is using LVM and the UUIDs of the LVM components are the same (as it is a clone).
If you create a new virtual machine (don't bother using LVM on it) and then add your existing disk to it any UUIDs present will be diffrent.

It might be a good idea to use VirtualBox's snapshot feature and take a snapshot of your machine as a sort of backup for cases like this.

cheers
/Tim