Search results

now i did try blacklisting of the kernel driver of the RAID modul (hpsa) and did acording to this https://forum.proxmox.com/threads/cant-blacklist-mpt2sas-module.26950/ the # update-initramfs -k all -u after updateing the blacklist.conf by adding "blacklist hpsa" no sucess then i added echo...

i made a litte progress.... my fans start to go ape when i issue the comand echo 0000:07:00.0 > /sys/bus/pci/drivers/pci-stub/bind I did follow this post: http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM and first did load pci_stub with the command modprobe pci_stub I...

and this is the verbose output of lspci -vvv for the RAID controler. In know that passthrough works for the HP420 with the HP version of VMware ESXi. 07:00.0 RAID bus controller: Hewlett-Packard Company Smart Array Gen8 Controllers (rev 01) Subsystem: Hewlett-Packard Company P420...

Just for test I changened hostpci0: 07:00.0,pcie=1 to hostpci0: 03:00,pcie=1 if you look in the first post, its both of my NICs. I then started the VM and my websession to the PVE GUI went dead instantly. So i switched to the server itself and run qm for the 200 vmid, but the vm was dead...

i see, thanks for the hint. will do asap after i got my problem with PCIe passthrough solfed https://forum.proxmox.com/threads/pcie-passthrough-on-4-4-acces-denied.27608/ as right now no container is availabe on the host. Cheers Manne

i also did try hostpci0: 07:00.0,pcie=1,driver=vfio nothing changed everytime i start up the host, everything is fine. after i tryed to start up the VM the fans went into overdrive. but it takes about 30 seconds after the startup fails. repeated startups from VM does not change anything

i did get immou group seperation by adding GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on pcie_acs_override=downstream" w/o the pcie_acs_override=downsteram i had the HP Raid Controler in the same group as the PCIe Root port. it was in 00:01.0 while the right now 00:01.0 was 00:01.1 now it...

Hi Folks, i run a HP Proliant Micro Gen8 Server with 16 GB Ram and the Xeon E3-1280V2 CPU. I want to pass through a HP P420 Smart Array Controler to my OMV VM. I am up to date with kernel: pve-manager/4.2-5/7cf09667 (running kernel: 4.4.8-1-pve) I did follow the proxmox guid...

Well it seems, i just wasn't patient enought. This is the output of dmesg, and I didnt try right away with SSH, but made me a coffe. Then all was well. But it seems the system takes a long time to start up. dmesg: see file

well, thanks for your input, but indeed i do have systemd as the kernel used in pve4 is jessie (8) and the CT is running on this kernel too. so i will ceck this out and report back, but it will take a while as im a bit loaded with work right now.

175 views an nobody got a hot brianchild? I didnt expect to be so special... ;-)

Hi Folks, I got myself a new (power safing) node to replace my very hungry ProLiant-DL380 Gen5, so I thought this would be the perfect situation to go from PVE3.4 to current, as the DL380 still is working, I could play with the new HP-Gen8 as long as it would take to make it nice and tidy...

Hi ned, ive got a similar problem. Well, I got a new node. So i thought, this would be the perfect time to convert from 3.4 to 4.x, since I did not want some downtime from compatibitlity issues. The migration from 3.4 to current 4 went sofar ok, just some trouble with the openvz containers...