TheBlueKingLP
-
Posts
144 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by TheBlueKingLP
-
-
What is the brand and model of the 'modem'?
Sent from my iPhone using Tapatalk -
45 minutes ago, ghost82 said:
unfortunately it's not possible to have gpu passthrough+vnc, as described you need vnc server in the guest for gpu passthrough.
31 minutes ago, tjb_altf4 said:RDP still works with GPU passthough
My plan is to NOT give any kind of network access to the VM so both solution isn't possible.
-
8 hours ago, ghost82 said:
I've seen that already, but that does not have a solution inside. It just suggests me to use the built in RDP, which I can't do since the machine isn't connected to any network.
-
I have a Windows 10 VM that has a passed through GPU for hardware acceleration, but I will need to use it remotely(without giving network access to the VM itself), so I added VNC to the VM as well, but while the GPU output works, the VNC says "Guest have not initialized the display (yet).", how do I fix this? In the device manager I also see error code 31 for the VNC display adapter.
-
Use GUI mode boot and change it in the settings.
Or alternatively, use a spare router set to the old network range then connect the Unraid and your computer to the spare router then change it.
-
1
-
-
It has 1gbps Intel & 2.5gbps Realtek.
Didn’t you said combining 2 100mbps? -
Sorry?
What is the model of device that has the 100mbps ports -
What is providing the 100mbps ports?
-
I love how I can just add one drive to the array at a time unlike other raid which I’ll have to add multiple drive at a time.
I wish unraid VM editor can retain my custom xml edits so I can use the GUI editor even I have custom xml edits.
-
Yup sorry I should've included that info before.
unRAID, this desktop, the Pi-hole WebUI etc are all on the same subnet. Pi-hole and its UI are working fine and I can see traffic there + ads being blocked. Tested with speedtest.net and a few others that are known to be bad for ads.
I don't really use KVM on unRAID anymore so I'll just ignore it for now. Thanks, though.
Ok then -
how many subnet do you have? Is the computer that you tried to connect to pihole on the same subnet as the pihole? If not, try to use the same subnet, btw, pihole should have a web interface, try to open that as wellYes, same subnet - this part of the network is all on the same /24 (the other parts are DMZ etc, so completely isolated from unRAID). -
It is already configured as bridge. There's a setting for "Server IP" but no matter what I set that to, that IP doesn't respond to anything.
It's no biggie, though - stopping KVM has worked.
Is it set to the same subnet as your server?or subnet that you and the server can access? -
Hello -
Is dnsmasq required for the operation of KVM?
Asking as I'm trying to install Pihole but the Docker container is failing due to port 53 already being in use. Netstat tells me it is in use by dnsmasq on local address 192.168.122.1 and I've tracked that down to 192.168.122.0/24 being attached to virbir0 in the routing table.
Stopping KVM allows the container to work.
Can I still use KVM if I somehow remove/stop dnsmasq? Docker is more important than KVM on this server so it's not a biggie if the answer is no.
Use bridge so the container will have another IP address -
Happy birthday unraid, defiantly one of the best OS ever
-
Just recently I pulled 2 8TB Seagates Compute (SMR) drives
to replace them with 2 8TB IronWolf Drives and found problem. Please let me know what I did wrong.My understand was that since UNRAID was not a RAID I would be able to pull any drive (minus parity) and access the data using my USB 3.1 Drive HUB or other enclosure.
Well, I tried this theory and found that the drive which had 5TB out of 8TB used showed up as empty. See screenshot attached. ( DISK 4 & DISK 5 )
I have all the data archived so it's not an issue but since I'm rebuilding this array from scratch I want make sure the new setup drive array will be fully readable outside of the server just in case there was a hardware failure.
Please advise and thank you in advance for taking the time!
What is the format of the drive?Is it encrypted?
-
On 5/27/2019 at 3:29 PM, saarg said:
There is no driver loaded for the card, so you can add the card in the xml editor manually.
On mobile so not looking at your diagnostics, so don't know why it's not working.
Have you tried to use the normal stubbing using vfio-pci.ids?
I could passthrough it manually with xml edited, but I still have other things needed to passthrough, but those are used by some driver, the vfio-pci.id didn't work for those device.
-
On 5/27/2019 at 3:28 AM, saarg said:
You have to be a little bit more specific than it doesn't work if you want help.
First of all, post your diagnostics. Then we need to know what you mean by not working.
What is the output of
lspci -klspci -k:
root@Pegasus:~# lspci -k 00:00.0 Host bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DMI2 (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DMI2 00:01.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 1 (rev 01) Kernel driver in use: pcieport 00:01.1 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 1 (rev 01) Kernel driver in use: pcieport 00:02.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 2 (rev 01) DeviceName: Onboard IGD Kernel driver in use: pcieport 00:02.2 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 2 (rev 01) Kernel driver in use: pcieport 00:03.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 3 (rev 01) Kernel driver in use: pcieport 00:05.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Map/VTd_Misc/System Management (rev 01)00:05.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO Hot Plug (rev 01) 00:05.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO RAS/Control Status/Global Errors (rev 01) 00:05.4 PIC: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D I/O APIC (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D I/O APIC 00:11.0 Unassigned class [ff00]: Intel Corporation C610/X99 series chipset SPSR (rev 05) Subsystem: ASUSTeK Computer Inc. C610/X99 series chipset SPSR 00:11.4 SATA controller: Intel Corporation C610/X99 series chipset sSATA Controller [AHCI mode] (rev 05) Subsystem: ASUSTeK Computer Inc. C610/X99 series chipset sSATA Controller [AHCI mode] Kernel driver in use: ahci Kernel modules: ahci 00:14.0 USB controller: Intel Corporation C610/X99 series chipset USB xHCI Host Controller (rev 05) Subsystem: ASUSTeK Computer Inc. C610/X99 series chipset USB xHCI Host Controller Kernel driver in use: xhci_hcd 00:16.0 Communication controller: Intel Corporation C610/X99 series chipset MEI Controller #1 (rev 05) Subsystem: ASUSTeK Computer Inc. C610/X99 series chipset MEI Controller 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (2) I218-V (rev 05) DeviceName: Onboard LAN Subsystem: ASUSTeK Computer Inc. Ethernet Connection (2) I218-V Kernel driver in use: e1000e Kernel modules: e1000e 00:1a.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced Host Controller #2 (rev 05) Subsystem: ASUSTeK Computer Inc. C610/X99 series chipset USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation C610/X99 series chipset HD Audio Controller (rev 05) Subsystem: ASUSTeK Computer Inc. C610/X99 series chipset HD Audio Controller Kernel driver in use: vfio-pci 00:1c.0 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #1 (rev d5) Kernel driver in use: pcieport 00:1c.2 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #3 (rev d5) Kernel driver in use: pcieport 00:1c.4 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #5 (rev d5) Kernel driver in use: pcieport 00:1c.7 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #8 (rev d5) Kernel driver in use: pcieport 00:1d.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced Host Controller #1 (rev 05) Subsystem: ASUSTeK Computer Inc. C610/X99 series chipset USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1f.0 ISA bridge: Intel Corporation C610/X99 series chipset LPC Controller (rev 05) Subsystem: ASUSTeK Computer Inc. C610/X99 series chipset LPC Controller 00:1f.2 SATA controller: Intel Corporation C610/X99 series chipset 6-Port SATA Controller [AHCI mode] (rev 05) Subsystem: ASUSTeK Computer Inc. C610/X99 series chipset 6-Port SATA Controller [AHCI mode] Kernel driver in use: ahci Kernel modules: ahci 00:1f.3 SMBus: Intel Corporation C610/X99 series chipset SMBus Controller (rev 05) Subsystem: ASUSTeK Computer Inc. C610/X99 series chipset SMBus Controller Kernel driver in use: i801_smbus Kernel modules: i2c_i801 02:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2) Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] 02:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1) Subsystem: ASUSTeK Computer Inc. High Definition Audio Controller 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev e7) Subsystem: Sapphire Technology Limited Nitro+ Radeon RX 570/580 Kernel driver in use: vfio-pci 03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] Subsystem: Sapphire Technology Limited Device aaf0 Kernel driver in use: vfio-pci 07:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller Subsystem: ASUSTeK Computer Inc. ASM1142 USB 3.1 Host Controller Kernel driver in use: xhci_hcd 08:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller Subsystem: ASUSTeK Computer Inc. ASM1142 USB 3.1 Host Controller Kernel driver in use: xhci_hcd 09:00.0 PCI bridge: ASMedia Technology Inc. ASM1184e PCIe Switch Port Kernel driver in use: pcieport 0a:01.0 PCI bridge: ASMedia Technology Inc. ASM1184e PCIe Switch Port Kernel driver in use: pcieport 0a:03.0 PCI bridge: ASMedia Technology Inc. ASM1184e PCIe Switch Port Kernel driver in use: pcieport 0a:05.0 PCI bridge: ASMedia Technology Inc. ASM1184e PCIe Switch Port Kernel driver in use: pcieport 0a:07.0 PCI bridge: ASMedia Technology Inc. ASM1184e PCIe Switch Port Kernel driver in use: pcieport 0c:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) Subsystem: ASUSTeK Computer Inc. I211 Gigabit Network Connection Kernel driver in use: igb Kernel modules: igb 0e:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Wireless Network Adapter (rev 03) Subsystem: ASUSTeK Computer Inc. BCM4360 802.11ac Wireless Network Adapter ff:0b.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 ff:0b.1 Performance counters: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 Kernel driver in use: bdx_uncore ff:0b.2 Performance counters: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 Kernel driver in use: bdx_uncore ff:0b.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link Debug (rev 01) ff:0c.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent ff:0c.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent ff:0c.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent ff:0c.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent ff:0c.4 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent ff:0c.5 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent ff:0c.6 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent ff:0c.7 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent ff:0f.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent ff:0f.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent ff:0f.4 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent ff:0f.5 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent ff:0f.6 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent ff:10.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R2PCIe Agent (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R2PCIe Agent ff:10.1 Performance counters: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R2PCIe Agent (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R2PCIe Agent Kernel driver in use: bdx_uncore ff:10.5 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox ff:10.6 Performance counters: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox ff:10.7 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox ff:12.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Home Agent 0 (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Home Agent 0 ff:12.1 Performance counters: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Home Agent 0 (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Home Agent 0 Kernel driver in use: bdx_uncore ff:13.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Target Address/Thermal/RAS (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Target Address/Thermal/RAS ff:13.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Target Address/Thermal/RAS (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Target Address/Thermal/RAS ff:13.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder ff:13.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder ff:13.4 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder ff:13.5 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder ff:13.6 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Broadcast (rev 01) ff:13.7 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Global Broadcast (rev 01) ff:14.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 0 Thermal Control (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 0 Thermal Control Kernel driver in use: bdx_uncore ff:14.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 1 Thermal Control (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 1 Thermal Control Kernel driver in use: bdx_uncore ff:14.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 0 Error (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 0 Error ff:14.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 1 Error (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 1 Error ff:14.4 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface (rev 01) ff:14.5 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface (rev 01) ff:14.6 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface (rev 01) ff:14.7 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface (rev 01) ff:15.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 2 Thermal Control (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 2 Thermal Control Kernel driver in use: bdx_uncore ff:15.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 3 Thermal Control (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 3 Thermal Control Kernel driver in use: bdx_uncore ff:15.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 2 Error (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 2 Error ff:15.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 3 Error (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 3 Error ff:16.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Target Address/Thermal/RAS (rev 01) ff:16.6 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Broadcast (rev 01) ff:16.7 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Global Broadcast (rev 01) ff:17.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 1 - Channel 0 Thermal Control (rev 01) Kernel driver in use: bdx_uncore ff:17.4 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface (rev 01) ff:17.5 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface (rev 01) ff:17.6 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface (rev 01) ff:17.7 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface (rev 01) ff:1e.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit ff:1e.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit ff:1e.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit ff:1e.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit Kernel driver in use: bdx_uncore ff:1e.4 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01) Subsystem: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit ff:1f.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01) ff:1f.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01)by not working, I mean the the device is not showing in other pci device in the VM editor.
diagnostic:
-
Hello, I am on 6.7.0 and the vfio-pci.cfg isn't working for me. Location of the vfio-pci.cfg file: /config/vfio-pci.cfg inside the flash drive, /boot/config/vfio-pci.cfg inside the server.
content of the vfio-pci.cfg file:
BIND=0e:00.0
also tried:
BIND="0e:00.0"
lspcu -v of the device I wanted to passthrough:
0e:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Wireless Network Adapter (rev 03) Subsystem: ASUSTeK Computer Inc. BCM4360 802.11ac Wireless Network Adapter Flags: bus master, fast devsel, latency 0, IRQ 15, NUMA node 0 Memory at fb400000 (64-bit, non-prefetchable) [size=32K] Memory at fb200000 (64-bit, non-prefetchable) [size=2M] Capabilities: [48] Power Management version 3 Capabilities: [58] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [68] Vendor Specific Information: Len=44 <?> Capabilities: [ac] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [13c] Device Serial Number 00-00-00-ff-ff-00-00-01 Capabilities: [150] Power Budgeting <?> Capabilities: [160] Virtual Channel Capabilities: [1b0] Latency Tolerance Reporting Capabilities: [220] Resizable BAR <?>
p.s. I asked this a few months ago, I thought the issue was solved but it isn't.
-
On 3/28/2019 at 4:26 AM, lixe said:
Was someone able to install the latest version of clover (4895)?
I'm using 4674 right now an it works absolutely fine. If I update to 4895 or 4901 (which was released nearly an hour ago), I can't boot anymore. I get stuck at the TianoCore logo.
I've discovered a new driver AudioDxe-64.efi, which I guessed I won't need anyway and sounds like it could cause problems. After deleting it it shows "clover 4895, scan entries". But nothing more happens. Tried it with HFSPlus.efi and VBoxhfs.efi, neither worked and also not both at the same time...
Beside that, I don't use any unusual drivers. Also tried replacing the new drivers64UEFI folder with my backed up one, but won't boot either.
The image attached shows all the driver I'm currently using with clover 4674.
EDIT:
I've also tried removing my old drivers64UEFI folder before the installation, so all drivers will get installed. After that I've copied the Apple* ones over, but also doesn't work.
EDIT2:
So I found a version which could maybe work (4862 from tonymacx86). My external USB backup drive (HFS+) is recognized. But usually I'm using an NVMe drive with APFS. I'm pretty sure the APFS filesystem isn't working properly... and I've already tried different drivers.
EDIT3:
Finally got it working (at least 4862 from tonymacx86). The problem was ApfsDriverLoader-64.efi. Had to delete it completely and instead use only apfs-patched.efi. Now its working so far
Where can I find apfs-patched.efi?
-
Hello,' Apologies in advance for n00b questions.
I installed a VM with Ubuntu Server 18.04 LTS. I have properly (I think) edited the network /yaml file. But I am unable to ping this VM, neither can I ping from the VM to anything else. Can't SSH into it, though the VNC seems to be working fine. Netplan settings are applied.
Any help getting this VM on my network properly would be greatly appreciated.
An ifconfig reveals what appears to be appropriate settings:
My Unraid server is at 10.0.1.201. My router is at 10.0.1.1. There are no conflicting IPs on this network.
Net config file looks like so:
VNC works fine because the vnc is on the unraid, not the vnc. I am not sure, but do you have to install the driver for the network interface on Ubuntu?or you could try to change the model in the xml to e1000-82545em
Edit the cam then click the top right corner switch, then find the following code, change the model
I am not sure if it will work or not, since my VM is windows. -
Yes, you can, but not recommended. That opens all the port on your server, and there is no firewall.
-
22 hours ago, trurl said:
Does it happen in SAFE mode?
No, that issue does not present in safe mode
-
I never tried that before, I will try it tonight.
-
3 hours ago, trurl said:
If you try running without docker enabled, and with no Unassigned Devices, does it still happen?
Yes, I added that unassigned device just to backup something, it happen even without that device.
VM and Docker are disabled in the settings(no docker and vm tab)
Assign a physical NIC to a specific Docker
in General Support
Posted
Sorry but I have no idea, I asked what is the ONU you’re using because I had a similar problem before which I solved, but unfortunately the solution can’t be done on yours. My isp provides a router with a SFP port and the ONU part is in there SFP stick so I just swap out the router then use my own 10gbps router and switche to solve it(everything I needed to use the internet is in the SFP module so I don’t need their router)