Hello again again [😊]
Noticed that when i do vfio-bind for the gpu it works, but then when i do it
for the audio it does not work it ends up in D+. This is the script:
#!/bin/bash
modprobe vfio-pci
for dev in "$@"; do
vendor=$(cat /sys/bus/pci/devices/$dev/vendor)
device=$(c
You really think vfio-pci never send commands to the card?
If it is the case, how linux can put this device to sleep? Vfio-pci manage
the card. It just pass command from vm to the card :)
I know, i have ~5 pcie controllers linked to my vm, gpu, nvme disk, usb
controller, audio controller and sata
On Tue, 2017-04-18 at 14:02 +0200, Quentin Deldycke wrote:
> In your case, another OS (linux) use this card at a moment or another,
> reset some bus (when re-binded to vfio). The reset of cards is already
> hardly supported by windows / linux driver.
This is a pass-through device. The whole point
On Tue, Apr 18, 2017 at 10:09 AM, Graham Neville
wrote:
> Has there been any feedback on this at all?
>
> I'm still struggling to get a Windows and Linux VM working at the same time
> with npt=1. Annoying as I'm having to reboot in to a different kernel if I
> want to use one or the other.
>
> Are
Has there been any feedback on this at all?
I'm still struggling to get a Windows and Linux VM working at the same time
with npt=1. Annoying as I'm having to reboot in to a different kernel if I
want to use one or the other.
Are you able to share your Kernel command line and XML for the Linux hos
Yes, but windows *knows* the passed device is then shutdown. At reboot
windows *knows* that the device is "freshly" rebooted.
In your case, another OS (linux) use this card at a moment or another,
reset some bus (when re-binded to vfio). The reset of cards is already
hardly supported by windows /
On Tue, 2017-04-18 at 13:32 +0200, Quentin Deldycke wrote:
> You can't do like this. Even sleep is not correctly supported.
>
> What is happening to the card during reboot? How windows can know?
Windows supports hibernation on some machines (e.g. laptops and
tablets). That presumably does save th
You can't do like this. Even sleep is not correctly supported.
What is happening to the card during reboot? How windows can know?
--
Deldycke Quentin
On 18 April 2017 at 13:27, Patrick O'Callaghan wrote:
> Am I correct in assuming that KVM/QEMU VMs cannot be frozen and
> restored (e.g. in ord
Am I correct in assuming that KVM/QEMU VMs cannot be frozen and
restored (e.g. in order to reboot the host), if passthrough is
enabled?Â
I tried it with:
$ sudo virsh save NewWin10 NewWin10.saved
error: Failed to save domain NewWin10 to NewWin10.saved
error: Requested operation is not valid: doma
