SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have verifed that the iso and img do exist and are where I say they are. The .img was made using qemu-img. No matter what I do, qemu (well, qemu-x86_64, as there is no actual qemu) prints the same "help" screen. It does not say anythng about the parameters passed to it.
By the way, the docs say that typing "qemu -cpu ?" will list the possible cpu choices and that "-soundhw ?" will list the possible sound card choices, but that is false. Instead, qemu prints the identical "help" screen.
To summarize, typing "qemu-x86_64" with any parameters is equivalent to typing "qemu-x86_64" without any parameters. Every time.
Is qemu being retarded or am I?
Can I have a hint? What am I missing? Are the docs out of date? The goal in my example above is to boot off a cd rom to then partition the emulated hard drive.
edit: i shoudl have put this in a general section, not a specific t this distro section. Damn, out of time, can't be helped.
Last edited by jr_bob_dobbs; 02-25-2016 at 05:42 PM.
How did you install qemu? Check if the command you are running is a symlink or a binary as allend mentioned above.
I tried the your command on my system and instead of telling me the files don't exist it printed the help message too
Code:
gzamudio@hades:~ $ qemu-x86_64 -cpu kvm64 \
> -soundhw sb16 \
> -vga std \
> -drive media=cdrom,if=ide,index=1,file=$HOME/Downloads/live_cds/gparted-live-0.16.1-1-i486.iso \
> -drive media=disk,if=ide,index=0,file=new_disk_image.img
usage: qemu-x86_64 [options] program [arguments...]
Linux CPU emulator (compiled for x86_64 emulation)
Options and associated environment variables:
Argument Env-variable Description
-h print this help
-g port QEMU_GDB wait gdb connection to 'port'
-L path QEMU_LD_PREFIX set the elf interpreter prefix to 'path'
-s size QEMU_STACK_SIZE set the stack size to 'size' bytes
-cpu model QEMU_CPU select CPU (-cpu help for list)
-E var=value QEMU_SET_ENV sets targets environment variable (see below)
-U var QEMU_UNSET_ENV unsets targets environment variable (see below)
-0 argv0 QEMU_ARGV0 forces target process argv[0] to be 'argv0'
-r uname QEMU_UNAME set qemu uname release string to 'uname'
-B address QEMU_GUEST_BASE set guest_base address to 'address'
-R size QEMU_RESERVED_VA reserve 'size' bytes for guest virtual address space
-d item[,...] QEMU_LOG enable logging of specified items (use '-d help' for a list of items)
-D logfile QEMU_LOG_FILENAME write logs to 'logfile' (default stderr)
-p pagesize QEMU_PAGESIZE set the host page size to 'pagesize'
-singlestep QEMU_SINGLESTEP run in singlestep mode
-strace QEMU_STRACE log system calls
-seed QEMU_RAND_SEED Seed for pseudo-random number generator
-version QEMU_VERSION display version information and exit
Defaults:
QEMU_LD_PREFIX = /usr/gnemul/qemu-x86_64
QEMU_STACK_SIZE = 8388608 byte
You can use -E and -U options or the QEMU_SET_ENV and
QEMU_UNSET_ENV environment variables to set and unset
environment variables for the target process.
It is possible to provide several variables by separating them
by commas in getsubopt(3) style. Additionally it is possible to
provide the -E and -U options multiple times.
The following lines are equivalent:
-E var1=val2 -E var2=val2 -U LD_PRELOAD -U LD_DEBUG
-E var1=val2,var2=val2 -U LD_PRELOAD,LD_DEBUG
QEMU_SET_ENV=var1=val2,var2=val2 QEMU_UNSET_ENV=LD_PRELOAD,LD_DEBUG
Note that if you provide several changes to a single variable
the last change will stay in effect.
I checked each option using ?
Code:
gzamudio@hades:~ $ qemu-kvm -cpu ?
x86 qemu64 QEMU Virtual CPU version 2.4.1
x86 phenom AMD Phenom(tm) 9550 Quad-Core Processor
x86 core2duo Intel(R) Core(TM)2 Duo CPU T7700 @ 2.40GHz
x86 kvm64 Common KVM processor
x86 qemu32 QEMU Virtual CPU version 2.4.1
x86 kvm32 Common 32-bit KVM processor
x86 coreduo Genuine Intel(R) CPU T2600 @ 2.16GHz
gzamudio@hades:~ $ qemu-kvm -soundhw ?
Valid sound card names (comma separated):
pcspk PC speaker
hda Intel HD Audio
cs4231a CS4231A
gus Gravis Ultrasound GF1
adlib Yamaha YM3812 (OPL2)
ac97 Intel 82801AA AC97 Audio
es1370 ENSONIQ AudioPCI ES1370
sb16 Creative Sound Blaster 16
gzamudio@hades:~ $ qemu-kvm -drive ?
qemu-kvm: -drive ?: Must specify either driver or file
So far it looks like the values you passed to each option were correct until the -drive option. Something there may be incorrect. I checked the man page for qemu
Code:
-drive option[,option[,option[,...]]]
Define a new drive. Valid options are:
media=media
This option defines the type of the media: disk or cdrom
-cdrom file
Use file as CD-ROM image (you cannot use -hdc and -cdrom at the same time). You
can use the host CD-ROM by using /dev/cdrom as filename.
Instead of -cdrom you can use:
qemu-system-i386 -drive file=file,index=2,media=cdrom
Further down the man page one of the examples they list uses this syntax:
Try adding
"""
-boot order=cd \
"""
after your vga line without the quotes
this should cause qemu to look at d drive (windows nomenclature for the cdrom) to boot when it doesn't find a bootable OS on the image file
Hope that helps
John
Last edited by AlleyTrotter; 02-25-2016 at 08:21 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.