-
Notifications
You must be signed in to change notification settings - Fork 0
troubleshooting
Don't panic; what I need you to do is reboot the host/remove the devices (excluding the GPU) from the VM that you've passed through; usually your mice and keyboard, next I would need you to add display spice, channel spice and usb redirector.
Next i need you to boot into the VM with the GPU still passed though and to check windows update, it should find the GPU automatically, afterwards remove usb redirector, display spice, channel spice (doesn't have to be in order).
After that you should be good to go.
Sidenote; it would be highly recommended to pass though your mice and keyboard last and to remove all the spice stuff last that way your graphics card can get installed with windows/windows update.
Strange... did you try host-model mode in cpu configurations?
You may also try placing this inside your modprobe file kvm.conf
options kvm ignore_msrs=1
And it will boot successfully!
Try setting your client to beta and restart, it should work then, if you'd want you may switch it back.
If you ever want to use an exisitng installation on your NTFS drive you'll need to do the following
- Rename the Steam folder to Steam-old, create a new Steam folder
- Open steam
- Point the new steam install directory to your "new" install directory on the old drive
- Close Steam
- Delete the Steam folder DO NOT DELETE THE STEAM-OLD FOLDER
- Rename the steam-old folder to Steam
- ???
- Profit
There could be issues with NTFS; firstly see if you can verify the steam files, if this doesn't work then you'll have to run chkdsk with windows in recovery mode; you should know how to pass a phyical drive by now.
Here's an article on how to do so
for chkdsk you'll need to run diskpart to figure out the drive and then list volume
then for example:
chkdsk G: /F /R
you may also need to defrag the drive.
I have an error about /qemu-7.0.0/accel/accel-softmmu.c:82:accel_init_ops_interfaces: assertion failed: (ops != NULL) or my VM doesn't work mysteriously after a system update
do the following below.
Here is a shell command script, save the script and run the script as root (sudo) if you are running it inside /usr/bin, otherwise save it to where you copied the emulator; edit the values when needed. Also be sure to chmod +x binary as an executable as sudo.
#!/bin/bash
hexdump -ve '1/1 "%.2x"' ./qemu-system-x86_64 |
sed -e 's/424f4348/434f4348/g' -e 's/42585043/44585043/g' |
xxd -r -p > ./qemu-system-x86_64-pass
This was pointed out in my guide, here
If you are using an older gigabyte motherboard; disable CSM as it tries boot into the card you may be passing though.
For example according to dmidecode -t 2 I have:
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: AB350M-Gaming 3-CF
If you still have issues and suspect it's CSM you should probably disable that feature. Sometimes CSM is enabled again after a pacman update, I have no idea why that happens though; if someone can figure this out for me feel free to tell me.