Thanks for bringing this up. In fact, I have also some sound distortion when passing sound from the Windows VM to Linux pulseaudio. I haven't done anything about it since it's good enough for me.dminuth wrote:Ok, all is working great.. Got low scores on both benchmarks, but i don't have the greatest hardware to begin with. I do have 1 issue.
the sound in the windows VM, seems laggy. kinda distorted. Once i am in game ie fallout 4 everything is ok, except in the menus, then the sound is the same quality as in windows. I have tried lowering the Hz of the sound used by windows to 44Hz and even a step lower, but it stays unchanged.
any ideas ?
am thinking maybe a pulseaudio thing, might have to switch to alsa or something along those lines, will have to search further.
I tried several options myself, including the following:dminuth wrote:Hey powerhouse,
was doing reading to see if i can increase Win10 performance on vm anyway, and came across some about i/o mode=native. Apparantly something to put into the same line where one declares the disks. Any idea about syntax for it, all i can find is for virsh.
Same idea with cache mode = none.
Am still researching to see how to implement as to test if it really does change anything, but thought maybe you might have already come across this.
http://unix.stackexchange.com/questions ... inside-kvm
it's on the above link about halfway down the page in bullet points.
Code: Select all
-drive if=none,id=drive0,cache=directsync,format=raw,file=/dev/mapper/os-win10 \
-device virtio-blk-pci,drive=drive0,scsi=off,x-data-plane=on \
Code: Select all
-device virtio-scsi-pci,id=scsi \
-drive id=disk0,if=virtio,cache=none,format=raw,file=/dev/mapper/os-win10 \Code: Select all
-drive id=disk1,if=virtio,cache=none,file=/dev/mapper/data-photos \
-device virtio-scsi-pci,id=scsi1 \
Code: Select all
#!/bin/bash
configfile=/etc/vfio-pci.cfg
vmname="windows7vm"
vfiobind() {
dev="$1"
vendor=$(cat /sys/bus/pci/devices/$dev/vendor)
device=$(cat /sys/bus/pci/devices/$dev/device)
if [ -e /sys/bus/pci/devices/$dev/driver ]; then
echo $dev > /sys/bus/pci/devices/$dev/driver/unbind
fi
echo $vendor $device > /sys/bus/pci/drivers/vfio-pci/new_id
}
#if ps -A | grep -q $vmname; then
# echo "$vmname is already running." &
# exit 1
#else
cat $configfile | while read line;do
echo $line | grep ^# >/dev/null 2>&1 && continue
vfiobind $line
done
# use pulseaudio
export QEMU_AUDIO_DRV=pa
cp /usr/share/edk2.git/ovmf-x64/OVMF_VARS-pure-efi.fd /tmp/my_vars.fd
qemu-system-x86_64 \
-name $vmname,process=$vmname \
-machine type=q35,accel=kvm \
-cpu host \
-smp 4,sockets=1,cores=2,threads=2 \
-enable-kvm \
-m 8G \
-mem-path /run/hugepages/kvm \
-mem-prealloc \
-balloon none \
-rtc clock=host,base=localtime \
-vga none \
-nographic \
-serial none \
-parallel none \
-soundhw hda \
-usb -usbdevice host:046d:c035 -usbdevice host:046a:0011 \
-device vfio-pci,host=06:00.0,multifunction=on \
-device vfio-pci,host=06:00.1 \
-drive if=pflash,format=raw,readonly,file=/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd \
-drive if=pflash,format=raw,file=/tmp/my_vars.fd \
-boot order=dc \
-device virtio-scsi-pci,id=scsi \
-drive id=disk0,if=virtio,cache=none,format=raw,file=/media/o_shovah/win.img \
-drive file=/home/o_shovah/ISO/de_windows_7_professional_with_sp1_x64_dvd_u_676919.iso,id=isocd,format=raw,if=none -device scsi-cd,drive=isocd \
-drive file=/home/o_shovah/Downloads/virtio-win-0.1.112.iso,id=virtiocd,format=raw,if=none -device ide-cd,bus=ide.1,drive=virtiocd \
-netdev type=tap,id=net0,ifname=tap0,vhost=on \
-device virtio-net-pci,netdev=net0,mac=00:16:3e:00:01:01
exit 0
fi
Another possibility would be to use a Windows install ISO and have it format a drive or partition. Warning: You need to physically disconnect all unused drives and make a complete external backup of the drive you want to format. Windows is known for wiping out entire disks. This is only a temporary partition where the Windows 7 ISO content is copied to. After that some UEFI files are modified to make the UEFI boot work with Windows 7.You'll need a copy of Windows 8 or 8.1. It's apparently possible to install Windows 7 but I found it was more trouble than it's worth. DO NOT try to install the Ultimate version - install Professional or Home
Your graphics card will need to be UEFI capable. Mine is an older AMD card for which there is no official UEFI bios .... but I was able to construct one (see the beginning of this post)
Create a disk image for the VM - I recommend an LVM partition. In my case I allocate LVM partitions on the mechanical drive until I'm happy everything's running ok and then copy them across to the SSD using dd.
You'll also need a small (4GB) Fat32 partition on a "GPT" drive which we'll copy the installation files to. The install iso should be copied to an install partition as accessible to a VM ie.
* Create a new partition for this purpose, can be LVM or 'flat' but must reside on a GPT disk not MBR
* Allocate the new partition to a VM – so it can be formatted. DO NOT format this using host format tools, it must be done from a VM
* Allocate the new partition to a windows VM
* Format as FAT32, consider adding the WIN xx bootloader as well. Not necessary but seems cleaner and make the partition bootable (set “active” or bootable flag in parition table)
* Copy the install iso to the newly formatted partition. This can be accomplished by passing the iso to the VM used to format the new install partition as a CD-ROM (use virt-manager)
* Check that the \efi\boot partition exists and contains the same files as \efi\microsoft\boot. If necessary copy files into a new \efi\boot partition. Also must contain a copy bootmgw.efi named bootx64.efi in \efi\boot
* Check the contents of \source\ei.cfg to ensure it nominates the correct OS product (best to use “Professional”).
* It can be beneficial to use Win Toolkit to include the linux qxl driver (spice screen driver) in the Windows build although I'm not convinced this is necessary.
* Exit the VM used to format the install partition
Code: Select all
-drive if=pflash,format=raw,readonly,file=/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd \
-drive if=pflash,format=raw,file=/tmp/my_vars.fd \
Code: Select all
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=137e9e77-b3c9-43c6-8704-7120972bdfc3 ro quiet splash intel_iommu=on nouveau.blacklist=1 pci-stub.ids=10de:13c2,10de:0fbb
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=137e9e77-b3c9-43c6-8704-7120972bdfc3 ro quiet splash intel_iommu=on nouveau.blacklist=1 pci-stub.ids=10de:13c2,10de:0fbb
[ 8.087113] pci-stub: add 10DE:13C2 sub=FFFFFFFF:FFFFFFFF cls=00000000/00000000
[ 8.087121] pci-stub 0000:02:00.0: claimed by stub
[ 8.087125] pci-stub: add 10DE:0FBB sub=FFFFFFFF:FFFFFFFF cls=00000000/00000000
[ 8.087129] pci-stub 0000:02:00.1: claimed by stub
[ 8.822413] pci-stub 0000:02:00.0: enabling device (0000 -> 0003)
Code: Select all
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=3
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_iommu=on nouveau.blacklist=1 pci-stub.ids=10de:13c2,10de:0fbb"
GRUB_CMDLINE_LINUX=""
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"Code: Select all
Intel i7 4790k
Asus z97-A USB3.1
32GB (4x8GB DDR3-1600) Memory
EVGA GTX750TI 2GB OC (Mint 17.3 Host)
EVGA GTX970 4GB FTW (Windows 7 Guest)That's the easy one: There is no communication between the Linux host and the guest VM. In other words, when you shutdown -h your Windows guest doesn't get any trigger to shutdown as well.steakikan wrote:Hi, do you know how to make sure the guest os shutdown when the host os shutdown? I try to setup automatic shutdown from a UPS but not sure if I sent shutdown -h to host does it directly kill qemu? Thanks
.You might need to create the bridge. In my hurry writing the tutorial I may have forgotten this part. Install "bridge-utils" and then follow step 6 in my Xen tutorial here: http://forums.linuxmint.com/viewtopic.p ... 13#p628768.steakikan wrote:Ah I see, that's mean I have to use some other means to shutdown the guest os. One more question, I have difficulty in connecting the network connection, can you help? In qemu there is an error message : W: /etc/qemu-ifup: no bridge for guest interface found. Thanks for your help.
I can Report the step 6 of your Xen tutorial to be working fine as i mentioned in my post abovepowerhouse wrote:You might need to create the bridge. In my hurry writing the tutorial I may have forgotten this part. Install "bridge-utils" and then follow step 6 in my Xen tutorial here: http://forums.linuxmint.com/viewtopic.p ... 13#p628768.steakikan wrote:Ah I see, that's mean I have to use some other means to shutdown the guest os. One more question, I have difficulty in connecting the network connection, can you help? In qemu there is an error message : W: /etc/qemu-ifup: no bridge for guest interface found. Thanks for your help.
Tell me if that works and I will add that step to the tutorial.
(Note: I was running Xen before using kvm, so I already had a bridge configured and working.)
Yep it works, thanks for your guide. It is really helpful as most guide either refer to Arch or Fedora. In regards to acpi shutdown the only one I found is to manually use socket or telnet to shutdown the guess gracefully then shutdown the host.powerhouse wrote:You might need to create the bridge. In my hurry writing the tutorial I may have forgotten this part. Install "bridge-utils" and then follow step 6 in my Xen tutorial here: http://forums.linuxmint.com/viewtopic.p ... 13#p628768.steakikan wrote:Ah I see, that's mean I have to use some other means to shutdown the guest os. One more question, I have difficulty in connecting the network connection, can you help? In qemu there is an error message : W: /etc/qemu-ifup: no bridge for guest interface found. Thanks for your help.
Tell me if that works and I will add that step to the tutorial.
(Note: I was running Xen before using kvm, so I already had a bridge configured and working.)
Code: Select all
0000:02:00.0
0000:02:00.1Just updating my own post, there is a way for safe shutdown guest using telnet protocol and qmp, i haven't found a way to lock the telnet to localhost but the idea is to use the telnet json protocol to send shutdown command and wait for qmp to reply then you execute the host shutdown command.steakikan wrote:Ah I see, that's mean I have to use some other means to shutdown the guest os. One more question, I have difficulty in connecting the network connection, can you help? In qemu there is an error message : W: /etc/qemu-ifup: no bridge for guest interface found. Thanks for your help.
Thanks for this - very helpful.steakikan wrote:Just updating my own post, there is a way for safe shutdown guest using telnet protocol and qmp, i haven't found a way to lock the telnet to localhost but the idea is to use the telnet json protocol to send shutdown command and wait for qmp to reply then you execute the host shutdown command.steakikan wrote:Ah I see, that's mean I have to use some other means to shutdown the guest os. One more question, I have difficulty in connecting the network connection, can you help? In qemu there is an error message : W: /etc/qemu-ifup: no bridge for guest interface found. Thanks for your help.
Code: Select all
W: /etc/qemu-ifup: no bridge for guest interface found
QEMU 2.1.2 monitor - type 'help' for more information
(qemu) qemu-system-x86_64: -device vfio-pci,host=02:00.0,multifunction=on: vfio: error, group 1 is not viable, please ensure all devices within the iommu_group are bound to their vfio bus driver.
qemu-system-x86_64: -device vfio-pci,host=02:00.0,multifunction=on: vfio: failed to get group 1
qemu-system-x86_64: -device vfio-pci,host=02:00.0,multifunction=on: Device initialization failed.
qemu-system-x86_64: -device vfio-pci,host=02:00.0,multifunction=on: Device 'vfio-pci' could not be initialized