Displaying 4 results from an estimated 4 matches for "380p".
Did you mean:
380
2018 Jul 10
2
dmesg shows Intel Virt., lsmod shows kvm_intel; "Host does not [have] virt. options"
Hello,
I've tried over at IRC and it appears the solution to this problem may not
be obvious.
I'm working with a Centos7 box on HP ProLiant 380p hardware. The BIOS is a
bit outdated, but both Intel Virtualization Options and VT-d are present
and enabled in the firmware.
Some relevant command outputs below:
-bash-4.2$ dmesg | grep Virtualization
[ 1.299295] DMAR: Intel(R) Virtualization Technology for Directed I/O
-bash-4.2$ lsmod | gre...
2018 Jul 27
2
Trouble passing PCI device in isolated IOMMU group
I'm attempting PCI-passthrough from host to guest on an HP ProLiant 380P,
which has an outdated BIOS (2014), but it does support VT-d. I'm running
CentOS 7, kernel 3.10.0-862.9.1.el7.x86_64.
I have an Intel 82580 NIC installed with 4 ports. Each of these ports is in
its own IOMMU group (I enabled SR-IOV at the BIOS, which might be the
reason they show up separately...
2018 Jul 10
0
Re: dmesg shows Intel Virt., lsmod shows kvm_intel; "Host does not [have] virt. options"
On Tue, Jul 10, 2018 at 07:47:49AM -0600, Quincy Wofford wrote:
> Hello,
>
> I've tried over at IRC and it appears the solution to this problem may not
> be obvious.
>
> I'm working with a Centos7 box on HP ProLiant 380p hardware. The BIOS is a
> bit outdated, but both Intel Virtualization Options and VT-d are present
> and enabled in the firmware.
>
> Some relevant command outputs below:
>
> -bash-4.2$ dmesg | grep Virtualization
> [ 1.299295] DMAR: Intel(R) Virtualization Technology for...
2018 Aug 06
0
Re: Trouble passing PCI device in isolated IOMMU group
On 07/27/2018 11:51 AM, Quincy Wofford wrote:
> I'm attempting PCI-passthrough from host to guest on an HP ProLiant
> 380P, which has an outdated BIOS (2014), but it does support VT-d. I'm
> running CentOS 7, kernel 3.10.0-862.9.1.el7.x86_64.
>
> I have an Intel 82580 NIC installed with 4 ports. Each of these ports is
> in its own IOMMU group (I enabled SR-IOV at the BIOS, which might be the
> reaso...