Search results

Re: poblem with fresh installation of proxmox 4 with adaptec maxview (can't access it @vigilian: Did you receive an answer from adaptec technical support?

That's strange. I'm using proxmox 3.4 and tested qga with an ubuntu 14.04 vm. When starting a backup in snapshot-mode, guest-fsfreeze is invoked according to syslog of guest vm: Wolfgang, doesn't this contradict your statement?

Your issue seems to be similar as described in these threads: http://forum.proxmox.com/threads/18184-GPU-Passthrough-issue-with-HD7770-Sapphire-Flex http://forum.proxmox.com/threads/19682-kvm-gpu-passthrough-windows-vm Both were more or less solves by switching to an nvidia card. You should...

Why did you turn off x-vga? You need to turn it on for vga passthrough.

Which error do you get with kernel 3.10? Just post the log. Please also post your vmid.conf which you use for kernel 3.10. The one which you have posted does not match with the example of the wiki (machine q35, x-vga, pcie and vfio must be enabled).

It seems you missed that this isn't a german forum. Most probably you'll get more help if you write in english. Did you read the wiki already? There you'll find the basic setup you need! https://pve.proxmox.com/wiki/Pci_passthrough#PCI_EXPRESS_PASSTHROUGH

Yesterday I built the latest git qemu-server 3.1-31 package (including patch generate spice devices cmd line after pci bridge). Now machine q35 works as expected with and without spice (vga qxl). Spirit, thanks for investigating and fixing this issue!

mcflym, can you explain why this behaviour is expected? I, as a enduser, would expect that it doesn't matter which video device I choose (even if q35/pcie is enabled).

I'm on pvetest and noticed that "machine: q35" is only working if spice (vga: qxl) is disabled. See configs/logs for details: # pveversion -v proxmox-ve-2.6.32: 3.2-134 (running kernel: 3.10.0-4-pve) pve-manager: 3.2-23 (running version: 3.2-23/bd7b6eb4) pve-kernel-3.10.0-4-pve: 3.10.0-15...

Thanks for this hint! That happens if you don't copy&paste commandlines ;). Just saw that the wiki also contains the wrong path to "modprobe.d". @Spirit: Would you mind correcting this? As a general note to "pcie_acs_override". I was wondering why I needed this patch with the earlier 3.10...

Did you use a patched kernel for pcie_acs_override? Because pvetest kernel does not include pcie_acs_override... (if you used pvetest kernel, pcie_acs_override is ignored). I'm just curious if pcie_acs_override really was the reason that your iommu_groups were split up.

I didn't figure out how to send private messages... so here's the link* to latest git kernel (3.10) with pcie_acs_override patch applied. Patch can be found here. Download is valid until tomorrow. Password is: proxmox * Update: Link was removed because it's not valid anymore.

Did you apply the pcie_acs_override patch to the kernel? The commandline itself is useless if the kernel doesn't provide this function. If you don't want to build the kernel yourself, I can provide you the latest git kernel with patch applied.

Adaptec has EOLed the older 6405 and 6805 controllers (at least according to their homepage). That must be the reason why they don't list them for new driver releases. I first read the wrong link, that's why I've updated my last post. Sorry for that. @ekin06: You don't have to wait for the next...

Another possibility would be the pcie_acs_override patch (worked for me as described here).

These are two different lists. One for the latest adaptec driver, the other for the maxView software! Update: Just saw that the old driver had a longer list of devices, as you wrote. Maybe that's just adaptec's fault not listing all devices (or the older devices are EOLed and thus are not...

vfio_iommu_type1 is a module. You'll have to add a module parameter: # cat /etc/modprobe/iommu_unsafe_interrupts.conf options vfio_iommu_type1 allow_unsafe_interrupts=1

Latest testing kernel 3.10 works great for me. 1. I've enabled allow_unsafe_interrupts, otherwise pci-passthrough didn't work. # cat /etc/modprobe.d/iommu_unsafe_interrupts.conf options vfio_iommu_type1 allow_unsafe_interrupts=1 2. Add vfio config to your VMID.conf hostpci0...

pcie_acs_override isn't part of the default kernel (additional patch necessary). This is a quirk which is needed for some special hardware.

According to your output of lspci, you tried already to passthrough the pci device (pci-stub driver is in use). Maybe you can also post the output of both lspci commands after a fresh system restart without trying to passthrough the pci device. I can only try to give some hints because I...