Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
hypervisor:base:xcp-xapi [2015/03/29 03:48] admin [Using kpartx] |
hypervisor:base:xcp-xapi [2015/03/29 13:06] (current) admin [kpartx for Mapping Partition Tables] |
||
---|---|---|---|
Line 255: | Line 255: | ||
---- | ---- | ||
- | ===== Create and Access a VDI from Dom0 ===== | + | ===== Create and Access File Based VDI from Dom0 ===== |
---- | ---- | ||
Line 281: | Line 281: | ||
</code> | </code> | ||
+ | We'll now have a new vhd file at:\\ | ||
+ | //**/run/sr-mount/<sr-uuid>/<vdi-uuid>.vhd**// | ||
+ | |||
+ | Which, in our example, translates to:\\ | ||
+ | /run/sr-mount/26b9d87b-f344-1c8d-c5c5-a155d4e4e2e0/72e00fc6-98bb-48fe-ab4d-b52d1ef721b5.vhd | ||
---- | ---- | ||
==== Create a VBD for the VDI and plug it ==== | ==== Create a VBD for the VDI and plug it ==== | ||
Line 337: | Line 342: | ||
kpartx lets you inspect an img file, showing its contained partitions using the -l command: | kpartx lets you inspect an img file, showing its contained partitions using the -l command: | ||
<code> | <code> | ||
- | > kpartx /opt/xen/X-Local-ISO/<image_file_name>.img | + | > kpartx -l /opt/xen/X-Local-ISO/<image_file_name>.img |
loop0p1 : 0 122880 /dev/loop0 8192 | loop0p1 : 0 122880 /dev/loop0 8192 | ||
loop0p3 : 0 1536000 /dev/loop0 131072 | loop0p3 : 0 1536000 /dev/loop0 131072 | ||
Line 343: | Line 348: | ||
</code> | </code> | ||
---- | ---- | ||
+ | |||
+ | === Add the partition mappings to the recognized devices in /dev/mapper/ === | ||
+ | <color darkorange>**THIS DOESN'T WORK!**</color> | ||
+ | <code> | ||
+ | > kpartx -av /run/sr-mount/26b9d87b-f344-1c8d-c5c5-a155d4e4e2e0/72e00fc6-98bb-48fe-ab4d-b52d1ef721b5.vhd | ||
+ | </code> | ||
==== END ==== | ==== END ==== | ||
---- | ---- |