9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have a couple of Rescue Disks I was experimenting with and someone suggested that I use Knoppix instead. I have the newest version of it and it seems more like an Emergency O.S than anything else. The only useful tool I can find on it is Gparted. Do you have to add Emergency Applications to it? ... (5 Replies)
Discussion started by: theKbStockpiler
5 Replies
2. UNIX for Dummies Questions & Answers
Hello All,
I have a Knoppix CD. I am able to boot Knoppix(Linux) from the CD.
How do I save a document that I created using OpenOffice(Writer) to either my harddrive on Windows or to a USB instead of the CD itself.
I am new to Knoppix and am not sure of the GUI. I tried mounting the USB... (2 Replies)
Discussion started by: AnilAnand
2 Replies
3. SuSE
Hi,
I want to learn linux but I don't want to install on my hard drive. I came to know about knoppix that could give me the answer. But If I download the same (approx 700 MB) from free download site and copy it to CD, Will it work ? please help. (2 Replies)
Discussion started by: sanjay1979
2 Replies
4. Ubuntu
Umm How can I get the Knoppix can be booted off my hard drive instead of the CD. I dont like using the CD. :confused: (4 Replies)
Discussion started by: shade11
4 Replies
5. Filesystems, Disks and Memory
Sorry if this post is in the wrong location. I'm trying to pull some files off of an old Dell box. I've not been able to get it to boot off of the HD, so I tried to use Knoppix. At boot time; I get the following error:
Loading spec packet failed, trying to wing it
isolinux 2.04: failed to... (3 Replies)
Discussion started by: ECBROWN
3 Replies
6. UNIX for Advanced & Expert Users
I hv boot my crashed RH server with knoppix linux cd , the server can connect internet now , I want to copy some files from my server to internet , but now I only found the below device path , could suggest how can I see my original path (eg. /home/ , /usr , / tmp etc, because I hv some important... (1 Reply)
Discussion started by: ust
1 Replies
7. Debian
hi all again!!
just a stupide question: how do you find the version of a knoppix? like the /etc/mandrake-release on mdk machines??
I have no idea of where to search..
Jason (5 Replies)
Discussion started by: penguin-friend
5 Replies
8. UNIX for Dummies Questions & Answers
I have downloaded KNOPIIX and burned it on a CD, it niether boots from CD nor could I open the file, it seems the extension is .iso, would you mind sending me your comment,please.
Thank you very much (2 Replies)
Discussion started by: amir
2 Replies
9. UNIX for Dummies Questions & Answers
i need help running Knoppix on my comp (which is windows). I have the cd with the iso on it and it works on my moms computer but not mine :( this is what it says to do
How do I run KNOPPIX?
In order to start the CD, first adjust the boot list in the BIOS Setup of your computer to boot from CD... (4 Replies)
Discussion started by: smokinchili21
4 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)