9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi fellas!
I make a sh script which the following:
sudo mkdir Temp
sudo mount -o loop output.img Temp
The command mounts the img.Thats fine.But it moun s it as read only.But I need to edit/delete some files inside it and repack it as ext4 using this command:
sudo ./mkuserimg.sh -s Temp... (3 Replies)
Discussion started by: vijai
3 Replies
2. UNIX for Advanced & Expert Users
Hi, all:
The vmlinuz-3.0.4.old is a kernel previous to the current running kernel vmlinuz-3.0.4 which is compiled the most currently. Could I get the initrd.img-3.0.4.old without recompile under the condition that the config-3.0.4.old, System.map-3.0.4.old and vmlinuz-3.0.4.old exist? if it... (1 Reply)
Discussion started by: liklstar
1 Replies
3. UNIX for Dummies Questions & Answers
I've been trying to create an IMG file for the past week with no success. I've tried using:
dd if=/dev/zero of=myimage.img bs=512 count=2880
mke2fs myimage.img
mkdir /media/mount_point
mount -o loop myimage.img /media/mount_point
cp -aR <file> /media/mount_point
umount /media/mount_point
... (30 Replies)
Discussion started by: neur0n
30 Replies
4. Red Hat
I have a 80GB hard disk with WinXP already installed.I had tried installing Fedora 10 earlier without creating new partitions(real foolish and ignorant of me :o:o ) and tried creating partitions using Fedora10 bootable.It didnt work.Then I created a free partition and again tried installing... (4 Replies)
Discussion started by: ganesh.k28
4 Replies
5. Filesystems, Disks and Memory
COuld you please telle me the diffrence between DSK and RDSK with exemple if possible...
Thanks a lot in advance.
Regards. (7 Replies)
Discussion started by: guillaume35
7 Replies
6. Solaris
We use imaging software from a cardiology clinic on SunOS 5.8 and I want to be able to see these image files (.img extension) on Windows XP. Can this be done? If so, with what software (on Windows XP)? On Windows XP, I've used software like Ulead PhotoImpact and Corel PhotoPaint but I've had no... (16 Replies)
Discussion started by: sreyes27
16 Replies
7. Solaris
Hi all,
I just find some strange device (at least to me) on my Sun Blade server, CP3060, like below:
bash-3.00# cd /dev/dsk
bash-3.00# ls c3*
c3t600A0B80002FA5F50000000000000000d0s0 c3t600A0B80002FA60C0000000000000000d0s4
c3t600A0B80002FA5F50000000000000000d0s1 ... (6 Replies)
Discussion started by: sleepy_11
6 Replies
8. UNIX for Dummies Questions & Answers
Hello!
When I use "sar -d" I get information about disk activities like:
sd0 ...
sd0,a ...
sd0,b ...
.....
sd22 ...
sd22,a ...
.....
How I can find by , for example sd22,a , what physical disk is it. For example /dev/dsk/c1t3d0s1 easy to read and I can find by it physical disk.... (4 Replies)
Discussion started by: Colf
4 Replies
9. Programming
hey, i just found this forum...how cool.
question:
does anybody know code or know where i can get the code to get a certain image URL from user? say user input URL from shell prompt when run the program. What is the code to take that URL open internet and download the image.
thanks alot. (2 Replies)
Discussion started by: bb00y
2 Replies
QEMU-IMG(1) QEMU-IMG(1)
NAME
qemu-img - QEMU disk image utility
SYNOPSIS
usage: qemu-img command [command options]
OPTIONS
The following commands are supported:
check [-f fmt] filename
create [-s] [-f fmt] [-o options] filename [size]
commit [-f fmt] filename
convert [-c] [-s] [-f fmt] [-O output_fmt] [-o options] filename [filename2 [...]] output_filename
info [-f fmt] filename
snapshot [-l | -a snapshot | -c snapshot | -d snapshot] filename
rebase [-u] -b backing_file [-F backing_fmt] filename
Command parameters:
filename
is a disk image filename
fmt is the disk image format. It is guessed automatically in most cases. See below for a description of the supported disk formats.
size
is the disk image size in bytes. Optional suffixes "k" or "K" (kilobyte, 1024) "M" (megabyte, 1024k) and "G" (gigabyte, 1024M) and T
(terabyte, 1024G) are supported. "b" is ignored.
output_filename
is the destination disk image filename
output_fmt
is the destination format
options
is a comma separated list of format specific options in a name=value format. Use "-o ?" for an overview of the options supported by the
used format or see the format descriptions below for details.
-c indicates that target image must be compressed (qcow format only)
-h with or without a command shows help and lists the supported formats
Parameters to snapshot subcommand:
snapshot
is the name of the snapshot to create, apply or delete
-a applies a snapshot (revert disk to saved state)
-c creates a snapshot
-d deletes a snapshot
-l lists all snapshots in the given image
Command description:
create [-f fmt] [-o options] filename [size]
Create the new disk image filename of size size and format fmt. Depending on the file format, you can add one or more options that
enable additional features of this format.
If the option backing_file is specified, then the image will record only the differences from backing_file. No size needs to be
specified in this case. backing_file will never be modified unless you use the "commit" monitor command (or qemu-img commit).
The size can also be specified using the size option with "-o", it doesn't need to be specified separately in this case.
commit [-f fmt] filename
Commit the changes recorded in filename in its base image.
convert [-c] [-f fmt] [-O output_fmt] [-o options] filename [filename2 [...]] output_filename
Convert the disk image filename to disk image output_filename using format output_fmt. It can be optionally compressed ("-c" option) or
use any format specific options like encryption ("-o" option).
Only the formats "qcow" and "qcow2" support compression. The compression is read-only. It means that if a compressed sector is
rewritten, then it is rewritten as uncompressed data.
Image conversion is also useful to get smaller image when using a growable format such as "qcow" or "cow": the empty sectors are
detected and suppressed from the destination image.
You can use the backing_file option to force the output image to be created as a copy on write image of the specified base image; the
backing_file should have the same content as the input's base image, however the path, image format, etc may differ.
info [-f fmt] filename
Give information about the disk image filename. Use it in particular to know the size reserved on disk which can be different from the
displayed size. If VM snapshots are stored in the disk image, they are displayed too.
snapshot [-l | -a snapshot | -c snapshot | -d snapshot ] filename
List, apply, create or delete snapshots in image filename.
Supported image file formats:
raw Raw disk image format (default). This format has the advantage of being simple and easily exportable to all other emulators. If your
file system supports holes (for example in ext2 or ext3 on Linux or NTFS on Windows), then only the written sectors will reserve space.
Use "qemu-img info" to know the real size used by the image or "ls -ls" on Unix/Linux.
host_device
Host device format. This format should be used instead of raw when converting to block devices or other devices where "holes" are not
supported.
qcow2
QEMU image format, the most versatile format. Use it to have smaller images (useful if your filesystem does not supports holes, for
example on Windows), optional AES encryption, zlib based compression and support of multiple VM snapshots.
Supported options:
"backing_file"
File name of a base image (see create subcommand)
"backing_fmt"
Image format of the base image
"encryption"
If this option is set to "on", the image is encrypted.
Encryption uses the AES format which is very secure (128 bit keys). Use a long password (16 characters) to get maximum protection.
"cluster_size"
Changes the qcow2 cluster size (must be between 512 and 2M). Smaller cluster sizes can improve the image file size whereas larger
cluster sizes generally provide better performance.
"preallocation"
Preallocation mode (allowed values: off, metadata). An image with preallocated metadata is initially larger but can improve
performance when the image needs to grow.
qcow
Old QEMU image format. Left for compatibility.
Supported options:
"backing_file"
File name of a base image (see create subcommand)
"encryption"
If this option is set to "on", the image is encrypted.
cow User Mode Linux Copy On Write image format. Used to be the only growable image format in QEMU. It is supported only for compatibility
with previous versions. It does not work on win32.
vdi VirtualBox 1.1 compatible image format.
vmdk
VMware 3 and 4 compatible image format.
Supported options:
"backing_fmt"
Image format of the base image
"compat6"
Create a VMDK version 6 image (instead of version 4)
vpc VirtualPC compatible image format (VHD).
cloop
Linux Compressed Loop image, useful only to reuse directly compressed CD-ROM images present for example in the Knoppix CD-ROMs.
SEE ALSO
The HTML documentation of QEMU for more precise information and Linux user mode emulator invocation.
AUTHOR
Fabrice Bellard
2010-07-01 QEMU-IMG(1)