VMware - Revision history

Pew at 06:50, 4 January 2019

2019-01-04T06:50:24Z

Pew: Undo revision 2373 by imported>Pew (talk)

2019-01-04T06:49:48Z

Undo revision 2373 by [[Special:Contributions/imported>Pew|imported>Pew]] ([[User talk:imported>Pew|talk]])

imported>Pew: Replaced content with "Category:Pending deletion"

2018-01-04T02:59:03Z

Replaced content with "Category:Pending deletion"

imported>Pew at 07:40, 3 January 2018

2018-01-03T07:40:56Z

imported>Pew at 07:04, 3 January 2018

2018-01-03T07:04:53Z

imported>Cov: /* Cracking Open VMDK Images with DD */

2010-03-01T22:42:19Z

‎Cracking Open VMDK Images with DD

imported>Cov at 22:41, 1 March 2010

2010-03-01T22:41:32Z

imported>Cov: /* Converting the Raw Image */

2010-03-01T13:41:35Z

‎Converting the Raw Image

imported>Cov at 13:24, 1 March 2010

2010-03-01T13:24:15Z

imported>Cov: Created page with ''''VMware''' is a proprietary virtualization brand. Their popularity is probably due to their early start in the field of virtualization and cross-platform host capabilities. [[V…'

2010-03-01T12:51:19Z

Created page with ''''VMware''' is a proprietary virtualization brand. Their popularity is probably due to their early start in the field of virtualization and cross-platform host capabilities. [[V…'

New page

'''VMware''' is a proprietary virtualization brand. Their popularity is probably due to their early start in the field of virtualization and cross-platform host capabilities. [[VirtualBox]] and [[QEMU]] are [[free software]] alternatives to VMware.

=Cracking Open VMDK Images with DD=
While VirtualBox and QEMU should support VMDK images, they may not, in which case it's back to the basics. The <code>dd</code> utility can be used to crack open a <code>-flat.vmdk</code> file.

==Offset and Length Information==
To get the offset and length of each partition, run the <code>file</code> command it.

<pre>
$ file Red\ Hat\ Enterprise\ Linux\ 4-flat.vmdk Red Hat Enterprise Linux 4-flat.vmdk: x86 boot sector; GRand Unified Bootloader, stage1 version 0x3, boot drive 0x80, 1st sector stage2 0xac03f, GRUB version 0.94; partition 1: ID=0x83, active, starthead 1, startsector 63, 5526297 sectors; partition 2: ID=0x82, starthead 0, startsector 5526360, 530145 sectors; partition 3: ID=0x83, starthead 0, startsector 6056505, 224910 sectors, code offset 0x48
</pre>

If you're dealing with Linux partitions, look for IDs of 0x83. 0x82 is Linux swap. Partition one generally begins at offset 63, but in this example, you can see a second partition at offset 6056505. The sector sizes are in multiples of 512 bytes.

==Dumping the Partitions==
The key components of the <code>dd</code> command are the <code>skip</code> and <code>count</code> settings. They are, respectively, the offset and length of the data to copy, copied from the information given by the <code>file</code> command.

The following will dump the root partition.
<pre>
$ dd if=Red\ Hat\ Enterprise\ Linux\ 4-flat.vmdk of=~/centosroot.img skip=63 count=5526297
</pre>

The other partition in this example was the <code>/home</code> partition. Since it was at the end of the file, the <code>count</code> variable was left unspecified. The partition was extracted with the following line.
<pre>
$ dd if=Red\ Hat\ Enterprise\ Linux\ 4-flat.vmdk of=~/centoshome.img skip=6056505 bs=512
</pre>

==Mounting the Partitions==
Mounting images on Linux is relatively straightforward.

<pre>
# mount -o loop /home/user/centosroot.img /mnt/mymountpoint
# mount -o loop /home/user/centoshome.img /mnt/mymountpoint/home
</pre>

You may need specify the filesystem type, i.e. <code>-t ext3</code>. Also, if you're having trouble mounting, it might be possible that you got the parameters wrong or potentially just got a bad copy. Try again to see if that's the case.

← Older revision		Revision as of 06:50, 4 January 2019
Line 1:		Line 1:
−	'''VMware''' is a proprietary virtualization brand. Their popularity is probably due to their early start in the field of virtualization and cross-platform host capabilities. [[VirtualBox]] and [[QEMU]] are [[free software]] alternatives to VMware.	+	'''VMware''' is a proprietary virtualization brand. Their popularity is probably due to their early start in the field of virtualization and cross-platform host capabilities. [[VirtualBox]] and [[w:QEMU\|QEMU]] are [[gp:free software\|free software]] alternatives to VMware.

	=Converting to VDI=		=Converting to VDI=

← Older revision		Revision as of 02:59, 4 January 2018
Line 1:		Line 1:
−	~~TODO: Move to software page~~	+	[[Category:Pending deletion]]
−
−	'''VMware''' is a proprietary virtualization brand. Their popularity is probably due to their early start in the field of virtualization and cross-platform host capabilities. [[VirtualBox]] and [[QEMU]] are [[free software]] alternatives to VMware.
−
−	~~=Converting to VDI=~~
−	~~Follow the instructions in the [[VirtualBox#Converting_a_Flat_VMDK_to_a_VDI\|VirtualBox article]] to convert a flat (raw) image into VirtualBox's virtual desktop image format.~~
−
−	~~=Cracking Open VMDK Images with DD=~~
−	~~The <code>dd</code> utility can be used to crack open a <code>-flat.vmdk</code> file.~~
−
−	~~==Offset and Length Information==~~
−	~~To get the offset and length of each partition, run the <code>file</code> command it.~~
−
−	~~<pre>~~
−	$ file Red\ Hat\ Enterprise\ Linux\ 4-flat.vmdk Red Hat Enterprise Linux 4-flat.vmdk: x86 boot sector; GRand Unified Bootloader, stage1 version 0x3, boot drive 0x80, 1st sector stage2 0xac03f, GRUB version 0.94; partition 1: ID=0x83, active, starthead 1, startsector 63, 5526297 sectors; partition 2: ID=0x82, starthead 0, startsector 5526360, 530145 sectors; partition 3: ID=0x83, starthead 0, startsector 6056505, 224910 sectors, code offset 0x48
−	~~</pre>~~
−
−	If you're dealing with Linux partitions, look for IDs of 0x83. 0x82 is Linux swap. Partition one generally begins at offset 63, but in this example, you can see a second partition at offset 6056505. The sector sizes are in multiples of 512 bytes.
−
−	~~==Dumping the Partitions==~~
−	The key components of the <code>dd</code> command are the <code>skip</code> and <code>count</code> settings. They are, respectively, the offset and length of the data to copy, copied from the information given by the <code>file</code> command.
−
−	~~The following will dump the root partition.~~
−	~~<pre>~~
−	~~$ dd if=Red\ Hat\ Enterprise\ Linux\ 4-flat.vmdk of=~/centosroot.img skip=63 count=5526297~~
−	~~</pre>~~
−
−	The other partition in this example was the <code>/home</code> partition. Since it was at the end of the file, the <code>count</code> variable was left unspecified. The partition was extracted with the following line.
−	~~<pre>~~
−	~~$ dd if=Red\ Hat\ Enterprise\ Linux\ 4-flat.vmdk of=~/centoshome.img skip=6056505 bs=512~~
−	~~</pre>~~
−
−	~~==Mounting the Partitions==~~
−	~~Mounting images on Linux is relatively straightforward.~~
−
−	~~<pre>~~
−	~~# mount -o loop /home/user/centosroot.img /mnt/mymountpoint~~
−	~~# mount -o loop /home/user/centoshome.img /mnt/mymountpoint/home~~
−	~~</pre>~~
−
−	You may need specify the filesystem type, i.e. <code>-t ext3</code>. Also, if you're having trouble mounting, it might be possible that you got the parameters wrong or potentially just got a bad copy. Try again to see if that's the case.
−
−	[[Category:~~Needs restoration~~]]

← Older revision		Revision as of 07:40, 3 January 2018
Line 41:		Line 41:
	You may need specify the filesystem type, i.e. <code>-t ext3</code>. Also, if you're having trouble mounting, it might be possible that you got the parameters wrong or potentially just got a bad copy. Try again to see if that's the case.		You may need specify the filesystem type, i.e. <code>-t ext3</code>. Also, if you're having trouble mounting, it might be possible that you got the parameters wrong or potentially just got a bad copy. Try again to see if that's the case.

−	~~[[Category:Proprietary course software]]~~
−	~~[[Category:Howtos]]~~
	[[Category:Needs restoration]]		[[Category:Needs restoration]]

@@ Line 1: / Line 1: @@
 '''VMware''' is a proprietary virtualization brand. Their popularity is probably due to their early start in the field of virtualization and cross-platform host capabilities. [[VirtualBox]] and [[QEMU]] are [[free software]] alternatives to VMware.
@@ Line 41: / Line 43: @@
 [[Category:Proprietary course software]]
 [[Category:Howtos]]

@@ Line 1: / Line 1: @@
 '''VMware''' is a proprietary virtualization brand. Their popularity is probably due to their early start in the field of virtualization and cross-platform host capabilities. [[VirtualBox]] and [[QEMU]] are [[free software]] alternatives to VMware.
 =Cracking Open VMDK Images with DD=
@@ Line 35: / Line 38: @@
 You may need specify the filesystem type, i.e. <code>-t ext3</code>. Also, if you're having trouble mounting, it might be possible that you got the parameters wrong or potentially just got a bad copy. Try again to see if that's the case.
 [[Category:Proprietary course software]]
 [[Category:Howtos]]

← Older revision		Revision as of 06:49, 4 January 2019
Line 1:		Line 1:
−	[[Category:~~Pending deletion~~]]	+	'''VMware''' is a proprietary virtualization brand. Their popularity is probably due to their early start in the field of virtualization and cross-platform host capabilities. [[VirtualBox]] and [[QEMU]] are [[free software]] alternatives to VMware.
		+
		+	=Converting to VDI=
		+	Follow the instructions in the [[VirtualBox#Converting_a_Flat_VMDK_to_a_VDI\|VirtualBox article]] to convert a flat (raw) image into VirtualBox's virtual desktop image format.
		+
		+	=Cracking Open VMDK Images with DD=
		+	The <code>dd</code> utility can be used to crack open a <code>-flat.vmdk</code> file.
		+
		+	==Offset and Length Information==
		+	To get the offset and length of each partition, run the <code>file</code> command it.
		+
		+	<pre>
		+	$ file Red\ Hat\ Enterprise\ Linux\ 4-flat.vmdk Red Hat Enterprise Linux 4-flat.vmdk: x86 boot sector; GRand Unified Bootloader, stage1 version 0x3, boot drive 0x80, 1st sector stage2 0xac03f, GRUB version 0.94; partition 1: ID=0x83, active, starthead 1, startsector 63, 5526297 sectors; partition 2: ID=0x82, starthead 0, startsector 5526360, 530145 sectors; partition 3: ID=0x83, starthead 0, startsector 6056505, 224910 sectors, code offset 0x48
		+	</pre>
		+
		+	If you're dealing with Linux partitions, look for IDs of 0x83. 0x82 is Linux swap. Partition one generally begins at offset 63, but in this example, you can see a second partition at offset 6056505. The sector sizes are in multiples of 512 bytes.
		+
		+	==Dumping the Partitions==
		+	The key components of the <code>dd</code> command are the <code>skip</code> and <code>count</code> settings. They are, respectively, the offset and length of the data to copy, copied from the information given by the <code>file</code> command.
		+
		+	The following will dump the root partition.
		+	<pre>
		+	$ dd if=Red\ Hat\ Enterprise\ Linux\ 4-flat.vmdk of=~/centosroot.img skip=63 count=5526297
		+	</pre>
		+
		+	The other partition in this example was the <code>/home</code> partition. Since it was at the end of the file, the <code>count</code> variable was left unspecified. The partition was extracted with the following line.
		+	<pre>
		+	$ dd if=Red\ Hat\ Enterprise\ Linux\ 4-flat.vmdk of=~/centoshome.img skip=6056505 bs=512
		+	</pre>
		+
		+	==Mounting the Partitions==
		+	Mounting images on Linux is relatively straightforward.
		+
		+	<pre>
		+	# mount -o loop /home/user/centosroot.img /mnt/mymountpoint
		+	# mount -o loop /home/user/centoshome.img /mnt/mymountpoint/home
		+	</pre>
		+
		+	You may need specify the filesystem type, i.e. <code>-t ext3</code>. Also, if you're having trouble mounting, it might be possible that you got the parameters wrong or potentially just got a bad copy. Try again to see if that's the case.
		+
		+	[[Category:Software]]
		+	[[Category:Campus computing resources]]
		+	[[Category:Howtos]]

@@ Line 5: / Line 5: @@
 =Cracking Open VMDK Images with DD=
-While VirtualBox and QEMU should support VMDK images, they may not, in which case it's back to the basics. The <code>dd</code> utility can be used to crack open a <code>-flat.vmdk</code> file.
+The <code>dd</code> utility can be used to crack open a <code>-flat.vmdk</code> file.
 ==Offset and Length Information==

@@ Line 37: / Line 37: @@
 ==Converting the Raw Image==
-Follow the instructions in the [[VirtualBox#Converting_a_Raw_Image|VirtualBox article]] to convert the raw image into a VirtualBox dynamic image.
+Follow the instructions in the [[VirtualBox#Converting_a_Raw_Image|VirtualBox article]] to convert the raw image into a virtual desktop image.
 [[Category:Proprietary course software]]
 [[Category:Howtos]]

← Older revision		Revision as of 13:24, 1 March 2010
Line 35:		Line 35:

	You may need specify the filesystem type, i.e. <code>-t ext3</code>. Also, if you're having trouble mounting, it might be possible that you got the parameters wrong or potentially just got a bad copy. Try again to see if that's the case.		You may need specify the filesystem type, i.e. <code>-t ext3</code>. Also, if you're having trouble mounting, it might be possible that you got the parameters wrong or potentially just got a bad copy. Try again to see if that's the case.
		+
		+	==Converting the Raw Image==
		+	Follow the instructions in the [[VirtualBox#Converting_a_Raw_Image\|VirtualBox article]] to convert the raw image into a VirtualBox dynamic image.
		+
		+	[[Category:Proprietary course software]]
		+	[[Category:Howtos]]