Recent content by ringerl

Kernel 3.10 is what I would need - this is why I wrote "Proxmox 3.2 using kernel 3.10". I believe I would need vfio (at least I see references here http://forum.proxmox.com/threads/17690-Beta-packages-for-Proxmox-VE-3-2-pvetest/page2)

I'm not familiar with the state of passthrough support in Proxmox 3.2 using Kernel 3.10. I want to pass through a SATA controller - can someone who has already done this write a quick tutorial of the needed commands? As far as I know the wiki is not up to date...

Re: FreeNAS 64bit hangs on boot I have now installed pve kernel 3.10 on a machine with an Intel-Core-i5-4570 CPU (Haswell) and can report success. FreeNAS 9.2.1.1 booting just fine.

I have now installed pve kernel 3.10 and can report success. The FreeNAS 9.2.1.1 booting just fine.

I believe we should channel all these non resolved threads into this one FreeBSD/FreeNAS VMs freeze at menu on boot to get things going on this issue.

Re: FreeNAS 64bit hangs on boot Hi fellow sufferers! I believe we should join forces. As asemyc2013 pointed out using 32bit FreeBSD is no solution. This issue effectivly renders proxmox unusable for users with recent Intel-based hardware (I believe this an issue on all Haswell setups) and the...

With my setup on an Intel-Core-i5-4570 CPU (Haswell) this was no good - the vm would freeze with 100% cpu not matter what. I strongly believe that this is an issue with all Haswell based cpus.

See http://forum.proxmox.com/threads/12957-FreeBSD-FreeNAS-VMs-freeze-at-menu-on-boot

upgraded to the latest from pvetest but still facing the same 100%-CPU-freeze-issue.

Is this update out already?

Could someone from the dev team look into this issue? Obviously something is wrong with the way this is handled automatically in Proxmox - manually passthrough works just fine.

First I just tried to add the device like that: qm> device_add pci-assign,host=01:00.0,id=mydevice PCI region 5 at address 0xf7c10000 has size 0x200, which is not a multiple of 4K. You might experience some performance hit due to that. Failed to assign device "mydevice" : Device or resource...

See reports of similar problems here - no solution yet though: http://forum.proxmox.com/threads/11811-PCI-Passthrough-quot-can-t-reset-pci-device-quot

Have you guys figured something out? Facing the same issues as you mentioned: FreeBSD 9.1/2 on kvm64 is a no go for me on proxmox 3.1. Hardware here is a i5-4570 (Haswell) and a H87 board.

Having the same issue here with a lynx point sata hba in ahci mode. I tried to hotadd the device with device_add pci-assign,host=01:00.0,id=mydevice which seemingly worked fine after doing all the unbinding in /sys/bus/pci/* Is there some problem with the unbinding process in proxmox?