i need to move VMware if possible as i am running low in space on my /home directory...is there anyway i can move it to root or to another partition?
Announcement
Collapse
No announcement yet.
any way to move VMware from one partition (disk) to another? [SOLVED]
Collapse
This topic is closed.
X
X
-
Re: any way to move VMware from one partition (disk) to another?
All you need to copy are the two files that end with .vmdk and .vmx. The .vmdk one is your actual VM -- it is the large "virtual disk". The .vmx is the "settings" for it. The rest of the files in the VM folder are not needed -- they will be regenerated upon first running your VM in its new location.
- Top
- Bottom
Comment
-
Re: any way to move VMware from one partition (disk) to another?
also, i have a separate disk that i am now going to try to VMware on, but that disk is not integrated with /home and /root, which is strange as ive given my user the permissions similar to /root, but still i need to enter the disk in dolphin for the computer to fully recognize it...is there a way to solve this, the partitions are all Ext4, i have a few ntfs partitions too, but they are better left as they are and are not needed as part of the system in the same manner...
it worked, now i will reboot and see if it still works before destroying the old copy...
- Top
- Bottom
Comment
-
Re: any way to move VMware from one partition (disk) to another?
Originally posted by evon
also, i have a separate disk that i am now going to try to VMware on, but that disk is not integrated with /home and /root
If it is a USB disk and you don't have it permanently connected, then you're stuck with whatever HAL and Dolphin will do for you. Don't forget to "eject" it when you're done, or your filesystem type might change from "ext4" to "screwed up beyond repair".
Here's an example /etc/fstab file for you, from my own beloved Kubuntu desktop system:
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/sda1 during installation
UUID=8cd86caa-8f74-46d5-829a-32b92bb77c2c / ext4 noatime,errors=remount-ro 0 1
# swap was on /dev/sdc2 during installation
UUID=8f03cf64-35dd-4d7f-b055-2d42aa291028 none swap sw 0 0
# /dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
UUID=bef7fc54-d120-4869-920c-edc64a214bae /mnt/DOCS ext4 auto,users,rw,exec,noatime 0 2
UUID=2b7ce29a-4550-4c6f-9171-8406d9688da7 /mnt/DOCSPIXBAK jfs auto,users,rw,exec,noatime 0 2
UUID=1e908a65-7ddb-4a1f-9913-d5a82ddb3137 /mnt/MUSIC ext4 auto,users,rw,exec,noatime 0 2
UUID=b69c6415-23e4-4e96-9f72-17d2d7736b93 /mnt/MUSICBAK jfs auto,users,rw,exec,noatime 0 2
UUID=dfd5d21c-b8d7-4dd7-8d44-ac3146008354 /mnt/SIDUX jfs auto,users,rw,exec,noatime 0 2
UUID=932854dc-d16b-4612-9bd7-37345d1def09 /mnt/VIDEOS ext4 auto,users,rw,exec,noatime 0 2
UUID=86da0233-4b7e-4ff9-b9f1-0ca338922c37 /mnt/VIDEOSBAK jfs auto,users,rw,exec,noatime 0 2
UUID=a1934295-3ff7-4700-901a-637513a74cfa /mnt/WHATEVER ext4 auto,users,rw,exec,noatime 0 2
/dev/cdrom /media/cdrom udf,iso9660 noauto,ro,users 0 0
/dev/fd0 /media/fd0 auto noauto,rw,users 0 0
- Top
- Bottom
Comment
Comment