Lines Matching full:qemu
143 attempt to do disk IO directly to the guests memory. QEMU may still perform
154 qemu -drive file=file,index=2,media=cdrom
160 qemu -drive file=file,index=0,media=disk
161 qemu -drive file=file,index=1,media=disk
162 qemu -drive file=file,index=2,media=disk
163 qemu -drive file=file,index=3,media=disk
168 qemu -drive file=file,if=ide,index=1,media=cdrom
173 qemu -drive if=ide,index=1,media=cdrom
178 qemu -drive file=file,if=scsi,bus=0,unit=6
183 qemu -drive file=file,index=0,if=floppy
184 qemu -drive file=file,index=1,if=floppy
190 qemu -drive file=a -drive file=b"
194 qemu -hda a -hdb b
293 qemu -soundhw sb16,adlib disk.img
294 qemu -soundhw es1370 disk.img
295 qemu -soundhw ac97 disk.img
296 qemu -soundhw all disk.img
297 qemu -soundhw ?
336 means qemu is able to report the mouse position without having to grab the
398 Normally, QEMU uses SDL to display the VGA output. With this option,
399 you can totally disable graphical output so that QEMU is a simple
401 the console. Therefore, you can still use QEMU to debug a Linux kernel
412 Normally, QEMU uses SDL to display the VGA output. With this option,
413 QEMU can display the VGA output when in text mode using a
425 available screen space. This makes the using QEMU in a dedicated desktop
512 Normally, QEMU uses SDL to display the VGA output. With this option,
513 you can have QEMU listen on VNC display @var{display} and redirect the VGA
591 system / user's SASL configuration file for the 'qemu' service. This
592 is typically found in /etc/sasl2/qemu.conf. If running QEMU as an
776 Qemu can emulate several different models of network card.
798 configure script is @file{/etc/qemu-ifup} and the default network
799 deconfigure script is @file{/etc/qemu-ifdown}. Use @option{script=no}
803 qemu linux.img -net nic -net tap
808 qemu linux.img -net nic,vlan=0 -net tap,vlan=0,ifname=tap0 \
814 Connect the VLAN @var{n} to a remote VLAN in another QEMU virtual
816 specified, QEMU waits for incoming connections on @var{port}
818 another QEMU instance using the @option{listen} option. @option{fd}=@var{h}
823 # launch a first QEMU instance
824 qemu linux.img -net nic,macaddr=52:54:00:12:34:56 \
828 qemu linux.img -net nic,macaddr=52:54:00:12:34:57 \
834 Create a VLAN @var{n} shared with another QEMU virtual
836 every QEMU with same multicast address @var{maddr} and @var{port}.
840 Several QEMU can be running on different hosts and share same bus (assuming
851 # launch one QEMU instance
852 qemu linux.img -net nic,macaddr=52:54:00:12:34:56 \
854 # launch another QEMU instance on same "bus"
855 qemu linux.img -net nic,macaddr=52:54:00:12:34:57 \
857 # launch yet another QEMU instance on same "bus"
858 qemu linux.img -net nic,macaddr=52:54:00:12:34:58 \
864 # launch QEMU instance (note mcast address selected
866 qemu linux.img -net nic,macaddr=52:54:00:12:34:56 \
876 communication port. This option is available only if QEMU has been compiled
883 # launch QEMU instance
884 qemu linux.img -net nic -net vde,sock=/tmp/myswitch
888 Dump network traffic on VLAN @var{n} to file @var{file} (@file{qemu-vlan0.pcap} by default).
923 qemu -hda linux.img -boot n -tftp /path/to/tftp/files -bootp /pxelinux.0
944 Then @file{@var{dir}} can be accessed in @file{\\smbserver\qemu}.
947 @file{/usr/sbin/smbd}. QEMU was tested successfully with smbd version
970 qemu -redir tcp:6001::6000 [...]
980 qemu -redir tcp:5555::23 [...]
1025 @code{hci0}) on the computer running QEMU. Only available on @code{bluez}
1043 qemu [...OPTIONS...] -bt hci,vlan=5 -bt vhci,vlan=5
1048 (default @code{0}). QEMU can only emulate one type of bluetooth devices
1155 @code{nc}, by starting qemu with: @code{-serial udp::4555} and nc as:
1156 @code{nc -u -l -p 4555}. Any time qemu writes something to that port it
1160 and start qemu a lot of times, you should have qemu use the same
1162 udp::4555@@:4556} to qemu. Another approach is to use a patched
1167 telnet on port 5555 to access the qemu port.
1169 @item Qemu Options:
1181 the @var{server} option QEMU will wait for a client socket application
1258 Store the QEMU process PID in @var{file}. It is useful if you launch QEMU
1282 stdio are reasonable use case. The latter is allowing to start qemu from
1285 (gdb) target remote | exec qemu -gdb stdio ...
1301 Output log in /tmp/qemu.log
1307 " translation (t=none or lba) (usually qemu can guess them)\n")
1312 translation mode (@var{t}=none, lba or auto). Usually QEMU can guess
1381 " xend will use this when starting qemu\n")
1395 Don't exit QEMU on guest shutdown, but instead only stop the emulation.
1410 "-daemonize daemonize QEMU after initializing\n")
1414 Daemonize the QEMU process after initialization. QEMU will not detach from
1416 This option is a useful way for external programs to launch QEMU without having
1587 The @var{action} controls what QEMU will do when the watchdog timer
