June 22, 20179 yr UEFI support makes running unRAID in a vm easier. Prepare the usb key as you normally would, and set the vm bios to ovmf. No need for a disk image of the usb key. I was even able to upgrade from RC4 to RC5 via the plugin. On every boot, I'm dropped into the UEFI shell, and have to kick things off with "fs0:/EFI/boot/bootx64.efi". I added a boot entry using bcfg, but it gets wiped out on boot. Was this by design to keep people out of trouble?
June 22, 20179 yr That sounds far easier. If you have time would you mind listing out some steps for setting up the VM without having to use the disk image?
June 22, 20179 yr Author Sure. Watch Gridrunner’s excellent video for background information. Quote I’ll only describe what is different. You’ll need an additional usb key for the vm. Prepare it exactly as you would when installing unRAID on a physical machine. Run make_bootable. If you will be using a stubbed out passthrough usb controller for the vm usb key, you can leave the vm key label as UNRAID. If not, change the label and modify /syslinux/syslinux.cfg. I used UNRAID-VM and changed append initrd=/bzroot to append unraidlabel=UNRAID-VM initrd=/bzroot If running 6.4 RC4 in the vm, copy the modified /syslinux/syslinux.cfg to /EFI/boot/syslinux.cfg. Ignore everything in the video about making an image of the key, defining the image file as a virtual disk in the vm template, and copying the image to the domains folder. In the vm template, change the BIOS to OVMF. Boot the vm, then connect to the console with novnc or another vnc client. You’ll be at the UEFI shell. Type: fs0: cd EFI cd boot bootx64.efi or just fs0:\EFI\boot\bootx64.efi You should see the normal unRAID boot menu, and you’re up and running. So far, I haven’t found an alternative to booting unRAID from the shell each time. Also, the unRAID OS GUI Mode boot options don’t seem to work in VNC. They would have been useful.
June 23, 20179 yr Thanks for the tip on booting the VM using UEFI! Should definitely be easier to update BTW, I was able to get it to boot automatically by adding a file called "startup.nsh" in the root of the USB that contains this single line: \EFI\boot\bootx64.efi
June 23, 20179 yr Nice, makes things a bit easier. Going to try this tonight.Sent from my LG-H815 using Tapatalk
June 23, 20179 yr I only recreated my Unraid-VM this week as well after borking it...Sent from my LG-H815 using Tapatalk
July 29, 20178 yr Anyone else having issues with slow networking with this? Updated my VM to RC7a and whenever I wget or curl the speed is atrocious. I'm going to do some more investigating and check. I can't say whether it was ok on prev RCs as I didn't pay any attention and just let the scripts concerned run....
July 30, 20178 yr OK, same issue in RC1, so I tried going back to non-UEFI boot and that made no difference, next will be rolling back to 6.3.5.
July 30, 20178 yr Try the kernel... wget https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.12.3.tar.gz Thanks @peter_sm appreciate it...
July 30, 20178 yr 8 minutes ago, CHBMB said: Try the kernel... wget https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.12.3.tar.gz Thanks @peter_sm appreciate it... Her is the result .... root@Tower-VM:/tmp# wget https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.12.3.tar.gz --2017-07-30 19:02:59-- https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.12.3.tar.gz Resolving www.kernel.org (www.kernel.org)... 147.75.205.195, 2604:1380:2000:f000::7 Connecting to www.kernel.org (www.kernel.org)|147.75.205.195|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 151891306 (145M) [application/x-gzip] Saving to: ‘linux-4.12.3.tar.gz.1’ linux-4.12.3.tar.gz.1 100%[=================================================================>] 144.85M 6.68MB/s in 25s 2017-07-30 19:03:24 (5.77 MB/s) - ‘linux-4.12.3.tar.gz.1’ saved [151891306/151891306]
July 30, 20178 yr @peter_sm Any chance of the output of ethtool eth0 and ifconfig Please. This is what I'm getting... root@matrix:~# ethtool eth0 Settings for eth0: Supported ports: [ ] Supported link modes: Not reported Supported pause frame use: No Supports auto-negotiation: No Advertised link modes: Not reported Advertised pause frame use: No Advertised auto-negotiation: No Speed: Unknown! Duplex: Unknown! (255) Port: Other PHYAD: 0 Transceiver: internal Auto-negotiation: off Link detected: yes root@matrix:~# ifconfig docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 0.0.0.0 ether 02:42:ba:a4:86:c9 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.100 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::5054:ff:fea7:9e8a prefixlen 64 scopeid 0x20<link> ether 52:54:00:a7:9e:8a txqueuelen 1000 (Ethernet) RX packets 426 bytes 78767 (76.9 KiB) RX errors 0 dropped 64 overruns 0 frame 0 TX packets 185 bytes 26491 (25.8 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 2 bytes 140 (140.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2 bytes 140 (140.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:e8:bc:a3 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
July 30, 20178 yr root@Tower-VM:~# ethtool eth0 Settings for eth0: Supported ports: [ ] Supported link modes: Not reported Supported pause frame use: No Supports auto-negotiation: No Advertised link modes: Not reported Advertised pause frame use: No Advertised auto-negotiation: No Speed: Unknown! Duplex: Unknown! (255) Port: Other PHYAD: 0 Transceiver: internal Auto-negotiation: off Link detected: yes root@Tower-VM:~# ifconfig br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.244 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::902f:7ff:feab:2212 prefixlen 64 scopeid 0x20<link> ether 52:54:00:2a:ec:8e txqueuelen 1000 (Ethernet) RX packets 550011 bytes 380359040 (362.7 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 216261 bytes 45981507 (43.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 0.0.0.0 ether 02:42:09:44:2c:2a txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 inet6 fe80::5054:ff:fe2a:ec8e prefixlen 64 scopeid 0x20<link> ether 52:54:00:2a:ec:8e txqueuelen 1000 (Ethernet) RX packets 553387 bytes 388376942 (370.3 MiB) RX errors 0 dropped 7 overruns 0 frame 7 TX packets 216355 bytes 45992118 (43.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 2 bytes 140 (140.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2 bytes 140 (140.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 10.18.0.1 netmask 255.255.255.255 destination 10.18.0.2 inet6 fe80::6083:73a2:9a00:a57e prefixlen 64 scopeid 0x20<link> unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 100 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 36 bytes 1728 (1.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:68:f6:c5 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 root@Tower-VM:~#
July 30, 20178 yr Thanks @peter_sm Still none the wiser. Turned off all my VLANs, downgraded host to v6.4rc1 still the same issue. Might try downgrading host to v6.3.5 as I've got a feeling it's something to do with my setup not liking the new network stuff, but other than that got no idea what's going on.
Archived
This topic is now archived and is closed to further replies.