jmbrnt

Thanks, I'll give it a crack

Hi My problem for this week is building a lab for an upcoming exam I am taking. For this, I need to run a few virtual Junos firewalls (vSRX). Juniper recommend VirtualBox when using Windows, which is fine by me (performance isn't the key parameter here, volume of hosts I can get running is). I originally wanted to run the vSRX themselves on unraid, but I have struggled with that - so will go the Virtualbox route. Firing up my VMs inside virtualbox was pretty simple, but I could only assign a single 'CPU' to the VM.. Following jonp's instructions here: I did these steps in order: - shut down both of my VMs - disabled VM manager - ran the commands JonP recommends - turned everything back on Now I can assign 2 CPU to the nested Virtualbox VM, so it looks like things work. However, when I try to turn the nested VM on, Windows restarts.. It doesn't like it at all. This is fairly typical of the log output I see when the Windows 10 VM crashes: host,hostbus=1,hostaddr=3,id=hostdev3,bus=usb.0,port=2 -device usb-host,hostbus=1,hostaddr=5,id=hostdev4,bus=usb.0,port=3 -device usb-host,hostbus=1,hostaddr=6,id=hostdev5,bus=usb.0,port=4 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on Domain id=3 is tainted: high-privileges Domain id=3 is tainted: host-cpu char device redirected to /dev/pts/1 (label charserial0) 2017-04-30T20:03:14.829458Z qemu-system-x86_64: vfio: Cannot reset device 0000:00:1f.3, no available reset mechanism. 2017-04-30T20:03:14.829557Z qemu-system-x86_64: vfio: Cannot reset device 0000:00:1f.3, no available reset mechanism. 2017-04-30T20:05:17.133972Z qemu-system-x86_64: vfio: Cannot reset device 0000:00:1f.3, no available reset mechanism. I've attached the diagnostics file. Any help would be awesome, doing this inside Virtualbox would save me a lot of trouble. tower-diagnostics-20170501-0954.zip

You could change your PIA password and reboot the container - then try and pull a linux iso torrent - that won't work unless your PIA tunnel is up - which it won't be as the password has changed.

Ah, duh. Thanks. I notice however that when I go to dnsleaktest.com I'm not protected, and it shows up my ISP's IP address (despite icanhazip.com showing the VPN address). I have set the DNS of the container to dns.watch addresses.. Anyway - could it be that privoxy doesn't support HTTPS and dnsleaktest forces HTTPS?

So far, mostly so good for me. I configured the containers to use my VPN provider, all good. Torrents download just fine (testing on debian torrents). What I can't get going, is privoxy. It appears to start up OK - but I get this error when I access it on port 8118: "Invalid header received from client" When I look in the log, I see nothing for port 8118, suggesting IPTables isn't allowing it through - or something else funky is going on. I searched for that error string, to no avail. Any idea what it might be? I've attached a sanitised log (and paid you beer money) help_please.txt

Sorry for the thread necro - but this worked for me! I am running a Skylake Z170 and now I have passthrough of my on-board audio working perfectly. I was relying on HDMI audio via the GTX 1070 (into my monitor, then out via the headphone jack) - but that occasionally went all slow-mo and garbled. I had ACS enabled, but after adding serguey's code from above, removing ACS and rebooting - all good. The one thing I am wondering is, what am I missing out on? IOMMU group 0 00:00.0 Host bridge [0600]: Intel Corporation Skylake Host Bridge/DRAM Registers [8086:191f] (rev 07) IOMMU group 1 00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) [8086:1901] (rev 07) 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) 01:00.1 Audio device [0403]: NVIDIA Corporation GP104 High Definition Audio Controller [10de:10f0] (rev a1) IOMMU group 2 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) IOMMU group 3 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller [8086:a12f] (rev 31) 00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Thermal subsystem [8086:a131] (rev 31) IOMMU group 4 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-H CSME HECI #1 [8086:a13a] (rev 31) IOMMU group 5 00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] [8086:a102] (rev 31) IOMMU group 6 00:1b.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Root Port #17 [8086:a167] (rev f1) IOMMU group 7 00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #1 [8086:a110] (rev f1) 00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #5 [8086:a114] (rev f1) 00:1c.5 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #6 [8086:a115] (rev f1) 04:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03) 05:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) IOMMU group 8 00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #9 [8086:a118] (rev f1) 00:1d.4 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #13 [8086:a11c] (rev f1) 06:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1a5] (rev 03) IOMMU group 9 00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-H LPC Controller [8086:a145] (rev 31) 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-H PMC [8086:a121] (rev 31) [b]00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-H HD Audio [8086:a170] (rev 31)[/b] 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-H SMBus [8086:a123] (rev 31) IOMMU group 10 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I219-V [8086:15b8] (rev 31) I am running Windows 10, pc-i440fx-2.7, Unraid 6.3. I assume the other 3 things in IOMMU group 9 are now broken.. But I can't see anything obviously detrimental. Thanks Serguey!

I too have this issue, running a Debian 8 VM on cores 0/1 of my 6700k i7. I hadn't seen this on earlier VMs, but today I have been spending a lot more time inside the CLI - so it's possible the issue has always been there and I had missed it. This VM is CLI only, running Unraid 6.3.0-rc9

No, no, didn't come across rude at all - when dealing with mystical numbers it's good to have a dose of reality. I'm also in the UK, but was asleep from assembling my machine till 3am the night before. I'm in love with Unraid

I hate to be the one to disappoint your happiness in getting those speeds. The disk speeds you are getting are not right. Programmes like crystal disk etc dont work measuring vm disk speed due to the caching. You could try using a programme like https://sourceforge.net/projects/iometer/ or http://www.iozone.org/ Manufacturer reports your drive specs as read 1775MB/Sec, Write Speed: 560MB/Sec Haha, I am not quite so deluded to think they were real - in my heart I suspected they were synthetic numbers (I had in the back of my mind 2100MB/s read for the P600, but you are right). I have done some testing with iometer for work, good call, I will run it again at home. In fact, I was doing dd tests (writing to zero) to prove some raw IOPS speed on a RAID, only for both Dell and VMWare to suggest I use iometer instead. Even though my Crystal tests are bogus numbers, there is a definite difference in write speeds now it's passed directly to the VM (rather than passing a mounted partition)... The values aren't right, but the trend is upward - so I can take some happiness from that

Sorry to double post.. Oh boy, I changed from a mounted drive to a direct passthrough... Those write speeds are looking a bit more spicy now

Well, I finally got my new kit. This is an nvme P600 Intel drive, mounted and added to Win 10 directly (not part of the array). These numbers look suspicious to you (write speed seems very slow compared with others)?