New answers tagged qemu
Are you using an abstraction layer such as libvirt? If so then simply add a disk image file as a USB Disk. If you're running kvm/qemu directly, then the man page (man kvm or man qemu) provides the answers: USB options: -usb Enable → the USB driver (will be the default soon) -usbdevice devname → Add the USB device devname. ...
An init script would be the way to go. Use of modprobe to ensure your kvm modules are loaded into the kernel may be unnecessary since they may already be loaded but if you run into problems you can always add it to your script.
It's a year-old subject, but someone may be still interested... I can confirm that qemu-kvm can be successfully wrapped with tsocks relay, using ssh SOCKS proxy. For DNS, ttdns is run on the host OS, so incoming UDP-DNS request from guest OS/qemu-kvm is converted to TCP-DNS request, and then relayed over tsocks+ssh. Actual command-line used: # env -i ...
Yes, the spice client just shows what a monitor would show. The machine continues to run in the background, even if you are not connected via spice. It also doesn't matter which spice client you are using. Of course the qemu process must keep running If you kill that one, it's like "pressing the button".
On my machine I could solve the problem by setting user-ID bit on execution on the "qemu-bridge-helper": sudo chmod u+s /usr/lib/qemu-bridge-helper ls -la /usr/lib/qemu-bridge-helper -rwsr-xr-x 1 root root 14336 Dez 16 15:36 /usr/lib/qemu-bridge-helper
qemu-kvm was indeed merged into QEMU, but that happened in version 1.3. Debian Wheezy ships QEMU 1.1.2 which still needs qemu-kvm for KVM support.
Top 50 recent answers are included