Questions
- Will there be updates?
- Will this expand to both 32 and 64bit to keep all in a single place?
- And, would installation of your QEMU PETs include the Launcher as a builtin feature of the offering this thread presents to ease knowledge to use?
The arrangement is that the checkbox ONLY appears if KVM is available ... so it's only giving the option of what is actually possible if that makes sense.Does the Launch utility checkbox for KVM feature, tell the user it is missing should they try to execute the Launcher with the KVM box checked?
The last person that said that to me I made sure I never did any work for him again.You enjoy a challenge!!
Code: Select all
# qemu_gui
debug: qemu-system-x86_64 -boot c -m 512 -hda /mnt/sdb1/tmp/qemu.img -hdb /dev/null -cdrom /mnt/sdb1/puppy/iso/slacko64-5.9.1.iso -smp 1
qemu-system-x86_64: error while loading shared libraries: libbluetooth.so.3: cannot open shared object file: No such file or directory
Code: Select all
# export QEMU_SOUND_DRV=alsa
# qemu-system-x86_64 -boot d -m 512 -enable-kvm -hda /dev/null -hdb /dev/null -cdrom /mnt/sda5/file/VM/fluxpup-1.5.1.iso -smp 1 -soundhw hda
Code: Select all
# QEMU_SOUND_DRV=alsa qemn_gui
debug: qemu-system-x86_64 -boot d -m 512 -enable-kvm -hda /dev/null -hdb /dev/null -cdrom /mnt/sda5/file/VM/precise-571RetroCsipeszPupV5EngHun2014Aug.iso -smp 1 -soundhw hda
I think you guessed right. Qemu_gui could set QEMU_SOUCE_DRV=alsa and leave it to the user to add additional parameters to effectively enable HD audio (perhaps a tool tip could remind of which parameters).mikeb wrote:I am also guessing that adding the QEMU_SOUND_DRV=alsa by itself may not...ie it could be made permanent with no detriment to users not needing sound...is this a decent bit of guesswork on my behalf? In which case the option is simply up to the user via the additional parameters without having to resort to the command line.
mike