Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Moving Virtual Machine Files from one SSD to Another Post 302923828 by mrm5102 on Tuesday 4th of November 2014 04:31:36 PM
Old 11-04-2014
Moving Virtual Machine Files from one SSD to Another

Hello All,

I recently bought a new 500GB Samsung SSD drive to replace my current (*at that time) internal 256GB OCZ SSD drive.

Everyday I run my Windows virtual machine (*as guest) from my Linux OS (*OpenSuSE 11.4 as host) using VMware Player. I run the VM from an External SSD drive (*Kingston SSD 128GB) that I attach to my laptop's docking station using a eSata Hard Drive docking station.

What I want to do now is start using my old internal (*256GB) SSD as my External SSD for my Virtual Machines. I was wondering if anyone would suggest the best way to go about this and also if changing the SSD's format would corrupt the VM's files..?

My 128GB SSD that currently has all my VMs on it is formatted as ext3, and I realized earlier today that the SSD won't get mounted to my Internal SSD's Windows 7 partition because of the ext3 format.

So I guess my question is, what would be the best course of action for moving my VM's files?

Should I do one of these..?:
*
When I say "Old" SSD below, I mean the one currently containing the VM files, and when I say "New"I mean my old internal SSD (*the 256GB one)...
  1. Use 'dd' to simply write the Old drive over the New drive, then resize the partition afterward to use up the remaining space?
  2. Or: First, format the New SSD, then simply copy/transfer the files from the Old SSD to the New SSD
  3. I also have Clonezilla to copy from the Old to the New, if that would be better...
If number 2 is the easiest, since no partition resizing would be needed, would it be ok to format the New SSD to something like NTFS so the drive can get recognized by both my Linux and Windows Partitions?

And if doing that is ok, would there be any issue in copying/transferring the VMs from the Old SSD (*etx3) to the Newly formatted SSD (*as NTFS)?


If anyone has any thoughts or suggestions, it would be very much appreciated!


Thanks in Advance,
Matt
 

10 More Discussions You Might Find Interesting

1. Solaris

Is there any Virtual data center as we have Virtual Machine?

Do we have any Virtual Data Center software as we have Virtual Machine? I want to practice everything of Solaris practically but i don't have resources like data center which includes Servers, Data storages, switches, and other things. (2 Replies)
Discussion started by: karman0931
2 Replies

2. Shell Programming and Scripting

moving files from a dir in one machine to a dir in another machines

Hi, I am a unix newbie.I need to write a shell script to move my oracle READ WRITE datafiles from one serevr to another. I need to move it from /u01/oradata/W1KK/.. to /u01/oradata/W2KK, /u02/oradata/W1KK/.. to /u02/oradata/W2KK. That is, I actaully am moving my datafiles from one database to... (2 Replies)
Discussion started by: mathews
2 Replies

3. Red Hat

Virtual Machine

Hi All, In my Org we are using Xen Hypervisor on RHEL 5.Now now the biggest challenge for us is to take online snapshot of running VM Guests.But this feature is not available in Xen. So i am trying to figure it out with some of the blogs found on net,in one blog its saying to create... (0 Replies)
Discussion started by: ajaincv
0 Replies

4. Solaris

Change hostID of Solaris 10 virtual/guest machine installed by Virtual Box 4.1.12 on Windows-XP host

Trying to set or modify the randomly set hostID of a Solaris 10 virtual/guest machine that I installed on a Windows-XP host machine (using Virtual Box 4.1.12). I was able to set/modify the hostname of the Solaris 10 virtual/guest machine during installation as well as via the Virtual Box... (4 Replies)
Discussion started by: Matt_VB
4 Replies

5. Red Hat

My RHEL virtual Machine Does not have Virtual Machine Manager Desktop Tool

My RHEL virtual Machine Does not have Virtual Machine Manager Desktop Tool Hi, I don't seem to have the Virtual Machine Manager Desktop tool set up on my RHEL6 Machine. The Linux machine runs off VMWare player and I'm not sure whether it is a VMWare software issue or a problem with the RHEL6... (2 Replies)
Discussion started by: accipiter1
2 Replies

6. Red Hat

Moving boot SSD from a dead server to a new server

Hi all, We have a disk array that has the boot drive on an OCZ SSD on a PCIe card. Well, the motherboard died and we got a new motherboard. We moved the controllers, NICs, etc, to the exact same slots on the new motherboard, except now it won't boot. I guess it doesn't recognize the OS on the... (1 Reply)
Discussion started by: glowe57
1 Replies

7. UNIX for Advanced & Expert Users

Virtual machine

Can I please get some recommendations on virtual machine software? I am using Fedora. What do you think is the best software and why? I need a windows virtual machine to run some windows software. What do you think is the best Windows version to use and why (xp, vista, 7, 8, 8.1)? Is it hopefully... (2 Replies)
Discussion started by: cokedude
2 Replies

8. AIX

IBM Virtual Machine OS on intel x86 and x64? IBM AIX OS on IBM Virtual Machine?

Hi There, I have zero information and zero knowledge for IBM virtual machine except Amazon cloud and VMware ESXi (Only Linux OS available). Anyone could provide me the following answer - Can IBM VM been deploy on X86 and X64 (Intel Chip)? If answer is yes any chance to deploy AIX OS... (13 Replies)
Discussion started by: chenyung
13 Replies

9. SCO

Moving SCO Virtual Machine in VMWare Environment: Critical Licensing Error Messages

Some years ago our company chose to run a critical proprietary app under SCO Unix. My predecessor tried to move A SCO Unix virtual machine from our dedicated VMWare environment to a shared Cloud VMWare environment. My predecessor received licensing messages from these critical servers so... (2 Replies)
Discussion started by: timfox1234
2 Replies

10. UNIX for Beginners Questions & Answers

Providing virtual machine priority in kvm based virtual machines

Hi All, Is there any way I can prioritize my VMs when there is resource crunch in host machine so that some VMs will be allocated more vcpu, more memory than other VMs in kvm/qemu hypervisor based virtual machines? Lets say in my cloud environment my Ubuntu 16 compute hosts are running some... (0 Replies)
Discussion started by: SanjayK
0 Replies
CRYPTTAB(5)							     crypttab							       CRYPTTAB(5)

NAME
crypttab - Configuration for encrypted block devices SYNOPSIS
/etc/crypttab DESCRIPTION
The /etc/crypttab file describes encrypted block devices that are set up during system boot. Empty lines and lines starting with the "#" character are ignored. Each of the remaining lines describes one encrypted block device, fields on the line are delimited by white space. The first two fields are mandatory, the remaining two are optional. Setting up encrypted block devices using this file supports three encryption modes: LUKS, TrueCrypt and plain. See cryptsetup(8) for more information about each mode. When no mode is specified in the options field and the block device contains a LUKS signature, it is opened as a LUKS device; otherwise, it is assumed to be in raw dm-crypt (plain mode) format. The first field contains the name of the resulting encrypted block device; the device is set up within /dev/mapper/. The second field contains a path to the underlying block device or file, or a specification of a block device via "UUID=" followed by the UUID. The third field specifies the encryption password. If the field is not present or the password is set to "none" or "-", the password has to be manually entered during system boot. Otherwise, the field is interpreted as a absolute path to a file containing the encryption password. For swap encryption, /dev/urandom or the hardware device /dev/hw_random can be used as the password file; using /dev/random may prevent boot completion if the system does not have enough entropy to generate a truly random encryption key. The fourth field, if present, is a comma-delimited list of options. The following options are recognized: discard Allow discard requests to be passed through the encrypted block device. This improves performance on SSD storage but has security implications. cipher= Specifies the cipher to use. See cryptsetup(8) for possible values and the default value of this option. A cipher with unpredictable IV values, such as "aes-cbc-essiv:sha256", is recommended. hash= Specifies the hash to use for password hashing. See cryptsetup(8) for possible values and the default value of this option. keyfile-offset= Specifies the number of bytes to skip at the start of the key file. See cryptsetup(8) for possible values and the default value of this option. keyfile-size= Specifies the maximum number of bytes to read from the key file. See cryptsetup(8) for possible values and the default value of this option. This option is ignored in plain encryption mode, as the key file size is then given by the key size. luks Force LUKS mode. When this mode is used, the following options are ignored since they are provided by the LUKS header on the device: cipher=, hash=, size=. noauto This device will not be automatically unlocked on boot. nofail The system will not wait for the device to show up and be unlocked at boot, and not fail the boot if it does not show up. plain Force plain encryption mode. read-only, readonly Set up the encrypted block device in read-only mode. size= Specifies the key size in bits. See cryptsetup(8) for possible values and the default value of this option. swap The encrypted block device will be used as a swap device, and will be formatted accordingly after setting up the encrypted block device, with mkswap(8). This option implies plain. WARNING: Using the swap option will destroy the contents of the named partition during every boot, so make sure the underlying block device is specified correctly. tcrypt Use TrueCrypt encryption mode. When this mode is used, the following options are ignored since they are provided by the TrueCrypt header on the device or do not apply: cipher=, hash=, keyfile-offset=, keyfile-size=, size=. When this mode is used, the passphrase is read from the key file given in the third field. Only the first line of this file is read, excluding the new line character. Note that the TrueCrypt format uses both passphrase and key files to derive a password for the volume. Therefore, the passphrase and all key files need to be provided. Use tcrypt-keyfile= to provide the absolute path to all key files. When using an empty passphrase in combination with one or more key files, use "/dev/null" as the password file in the third field. tcrypt-hidden Use the hidden TrueCrypt volume. This implies tcrypt. This will map the hidden volume that is inside of the volume provided in the second field. Please note that there is no protection for the hidden volume if the outer volume is mounted instead. See cryptsetup(8) for more information on this limitation. tcrypt-keyfile= Specifies the absolute path to a key file to use for a TrueCrypt volume. This implies tcrypt and can be used more than once to provide several key files. See the entry for tcrypt on the behavior of the passphrase and key files when using TrueCrypt encryption mode. tcrypt-system Use TrueCrypt in system encryption mode. This implies tcrypt. Please note that when using this mode, the whole device needs to be given in the second field instead of the partition. For example: if "/dev/sda2" is the system encrypted TrueCrypt patition, "/dev/sda" has to be given. timeout= Specifies the timeout for querying for a password. If no unit is specified, seconds is used. Supported units are s, ms, us, min, h, d. A timeout of 0 waits indefinitely (which is the default). tmp The encrypted block device will be prepared for using it as /tmp; it will be formatted using mke2fs(8). This option implies plain. WARNING: Using the tmp option will destroy the contents of the named partition during every boot, so make sure the underlying block device is specified correctly. tries= Specifies the maximum number of times the user is queried for a password. The default is 3. If set to 0, the user is queried for a password indefinitely. verify If the encryption password is read from console, it has to be entered twice to prevent typos. At early boot and when the system manager configuration is reloaded, this file is translated into native systemd units by systemd- cryptsetup-generator(8). EXAMPLE
Example 1. /etc/crypttab example Set up four encrypted block devices. One using LUKS for normal storage, another one for usage as a swap device and two TrueCrypt volumes. luks UUID=2505567a-9e27-4efe-a4d5-15ad146c258b swap /dev/sda7 /dev/urandom swap truecrypt /dev/sda2 /etc/container_password tcrypt hidden /mnt/tc_hidden /null tcrypt-hidden,tcrypt-keyfile=/etc/keyfile SEE ALSO
systemd(1), systemd-cryptsetup@.service(8), systemd-cryptsetup-generator(8), cryptsetup(8), mkswap(8), mke2fs(8) systemd 208 CRYPTTAB(5)
All times are GMT -4. The time now is 05:39 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy