![Kpartx read vmdk](https://kumkoniak.com/69.jpg)
![kpartx read vmdk kpartx read vmdk](https://miro.medium.com/max/1400/1*z1aq6D2xWEot8nVbOqnEBg.png)
The end result is that, from inside VBox, it looks like you have prepended the partition table on to the front of the partition image, without having to do the lengthy copy operation. (Of course, replace 63 with the actual offset to the first partition, usually 2048 these days). This means that the 63 sectors starting from offset 0 are read from the raw file “parttable.bin”, but sector 63 and upwards come from the raw partition dump “partition-image.bin”. vmdk file from a test I did a while ago: RW 63 FLAT "parttable.bin" 0 vmdk format image that refers to separate extent files for the partition table and for the partition contents.
![kpartx read vmdk kpartx read vmdk](https://www.sysprobs.com/wp-content/uploads/2010/03/convertrawcommand.png)
One way to avoid copying the whole image would be to create a. I’m sure the original problem was solved long ago, but for anybody with a similar problem:
![Kpartx read vmdk](https://kumkoniak.com/69.jpg)