• Unraid OS version 6.6.0-rc1 available


    limetech
    • Closed

    Please report only issues/bugs which are new in the prerelease.

     

    We've been holding back on this release a few days waiting for updated Intel ixgbe (10Gbit) OOT driver which builds correctly with 4.18 kernel.  But no update yet so this release uses 4.17.19 kernel.

     

    Every major subsystem has been updated.  In addition @bonienl has added some really cool features and update the default themes to match our new branding.

     

    Release notes:

    Version 6.6.0-rc1 2018-08-31

    Base distro:

    • aaa_base: version 14.2 (rev 5)
    • aaa_elflibs: version 15.0 (rev 2)
    • acl: version 2.2.53
    • acpid: version 2.0.29
    • adwaita-icon-theme: version 3.28.0
    • appres: version 1.0.5 (rev 2)
    • at-spi2-atk: version 2.26.2
    • at-spi2-core: version 2.28.0
    • at: version 3.1.20 (rev 5)
    • atk: version 2.28.1
    • attr: version 2.4.48
    • avahi: version 0.7 (rev2)
    • bash: version 4.4.023
    • bin: version 11.1 (rev 2)
    • bridge-utils: version 1.5 (rev 2)
    • btrfs-progs: version v4.17
    • bzip2: version 1.0.6 (rev 3)
    • ca-certificates: version 20180409
    • cairo: version 1.15.12
    • celt051: version 0.5.1.3 (rev 2)
    • cifs-utils: version 6.7 (rev 2)
    • coreutils: version 8.29 (rev 2)
    • cpio: version 2.12 (rev 2)
    • cpufrequtils: version 08 (rev 2)
    • cryptsetup: version 1.7.5 (rev 2)
    • curl: version 7.61.0 (CVE-2018-1000300, CVE-2018-1000301, CVE-2018-0500)
    • cyrus-sasl: version 2.1.27_rc8
    • db48: version 4.8.30 (rev 4)
    • dbus: version 1.12.8
    • dcron: version 4.5
    • dejavu-fonts-ttf: version 2.37 (rev 4)
    • dhcpcd: version 7.0.6
    • diffutils: version 3.6 (rev 2)
    • dmidecode: version 3.1 (rev 2)
    • dnsmasq: version 2.79 (rev 2)
    • docker: version 18.06.1-ce
    • e2fsprogs: version 1.44.2
    • ebtables: version 2.0.10 (rev 2)
    • editres: version 1.0.7 (rev 2)
    • elvis: version 2.2_0 (rev 4)
    • encodings: version 1.0.4 (rev 2)
    • etc: version 15.0 (rev 6)
    • ethtool: version 4.17
    • eudev: version 3.2.5 (rev2)
    • file: version 5.33
    • findutils: version 4.4.2 (rev 2)
    • flex: version 2.6.4 (rev 3)
    • floppy: version 5.5 (rev 2)
    • fontconfig: version 2.12.6 (rev 2)
    • freetype: version 2.9 (rev 2)
    • fribidi: version 1.0.4
    • fuse: version 2.9.7 (rev3)
    • gawk: version 4.2.1 (rev 2)
    • gd: version 2.2.5 (rev2)
    • gdbm: version 1.15
    • gdk-pixbuf2: version 2.36.12
    • genpower: version 1.0.5 (rev 3)
    • getty-ps: version 2.1.0b (rev 4)
    • glew: version 2.1.0 (rev 2)
    • glib2: version 2.56.1
    • glibc-solibs: version 2.27 (rev 4)
    • glibc-zoneinfo: version 2018e (rev 3)
    • glibc: version 2.27 (rev 4)
    • glu: version 9.0.0 (rev 2)
    • gmp: version 6.1.2 (rev 2)
    • gnome-themes-standard: version 3.22.3 (rev 2)
    • gnupg: version 1.4.23 (CVE-2018-12020)
    • gnutls: version 3.6.2 (rev 2)
    • gptfdisk: version 1.0.3 (rev 2)
    • grep: version 3.1 (rev 2)
    • gtk+3: version 3.22.30
    • gzip: version 1.9 (rev 2)
    • harfbuzz: version 1.8.1
    • haveged: version 1.9.2
    • hdparm: version 9.56
    • hicolor-icon-theme: version 0.17 (rev 2)
    • hostname: version 3.18 (rev 2)
    • htop: version 2.2.0
    • icu4c: version 61.1
    • imlib2: version 1.5.1
    • inetd: version 1.79s (rev 11)
    • infozip: version 6.0 (rev 4)
    • inotify-tools: version 3.14 (rev 2)
    • intel-microcode: version 20180807
    • iproute2: version 4.17.0
    • iptables: version 1.6.2 (rev 2)
    • iputils: version s20140519 (rev 2)
    • kernel-firmware: version 20180814_f1b95fe
    • keyutils: version 1.5.10 (rev 2)
    • kmod: version 25 (rev 2)
    • lbzip2: version 2.5
    • less: version 530 (rev 3)
    • libaio: version 0.3.111
    • libarchive: version 3.3.2 (rev 3)
    • libcap-ng: version 0.7.8 (rev 3)
    • libcgroup: version 0.41 (rev 5)
    • libcroco: version 0.6.12 (rev 2)
    • libdaemon: version 0.14 (rev2)
    • libdmx: version 1.1.4
    • libdrm: version 2.4.92
    • libedit: version 20180525_3.1
    • libee: version 0.4.1 (rev 2)
    • libepoxy: version 1.4.3 (rev 2)
    • libestr: version 0.1.10 (rev 2)
    • libevdev: version 1.5.9 (rev 2)
    • libevent: version 2.1.8 (rev 3)
    • libfastjson: version 0.99.8 (rev2)
    • libffi: version 3.2.1 (rev 2)
    • libfontenc: version 1.1.3 (rev 2)
    • libgcrypt: version 1.8.3 (CVE-2018-0495)
    • libgpg-error: version 1.31
    • libgudev: version 232 (rev 2)
    • libICE: version 1.0.9 (rev 3)
    • libidn: version 1.35
    • libjpeg-turbo: version 1.5.3 (rev 2)
    • liblogging: version 1.0.6 (rev2)
    • libmnl: version 1.0.4 (rev 3)
    • libnetfilter_conntrack: version 1.0.7
    • libnfnetlink: version 1.0.1 (rev 2)
    • libnftnl: version 1.1.0
    • libnl3: version 3.4.0 (rev 2)
    • libpcap: version 1.8.1 (rev 2)
    • libpciaccess: version 0.14 (rev 2)
    • libpng: version 1.6.34 (rev 2)
    • libpthread-stubs: version 0.4 (rev 2)
    • librsvg: version 2.42.5
    • libseccomp: version 2.3.3 (rev2)
    • libSM: version 1.2.2 (rev 3)
    • libssh2: version 1.8.0 (rev 3)
    • libtasn1: version 4.13 (rev 2)
    • libtirpc: version 1.0.3 (rev 2)
    • libunistring: version 0.9.10
    • libunwind: version 1.2.1
    • libusb-compat: version 0.1.5 (rev2)
    • libusb: version 1.0.22
    • libvirt-php: version 0.5.4 (rev3)
    • libvirt: version 4.6.0
    • libwebsockets: version 2.4.2
    • libX11: version 1.6.5 (rev 2)
    • libx86: version 1.1 (rev 3)
    • libXau: version 1.0.8 (rev 3)
    • libXaw: version 1.0.13 (rev 2)
    • libxcb: version 1.13 (rev 2)
    • libXcomposite: version 0.4.4 (rev 3)
    • libXcursor: version 1.1.15 (rev 2)
    • libXdamage: version 1.1.4 (rev 3)
    • libXdmcp: version 1.1.2 (rev 3)
    • libXevie: version 1.0.3 (rev 3)
    • libXext: version 1.3.3 (rev 3)
    • libXfixes: version 5.0.3 (rev 2)
    • libXfont2: version 2.0.3 (rev 2)
    • libXfontcache: version 1.0.5 (rev 3)
    • libXft: version 2.3.2 (rev 4)
    • libXi: version 1.7.9 (rev 2)
    • libXinerama: version 1.1.3 (rev 3)
    • libxkbfile: version 1.0.9 (rev 2)
    • libxml2: version 2.9.8 (rev 2)
    • libXmu: version 1.1.2 (rev 3)
    • libXpm: version 3.5.12 (rev 2)
    • libXrandr: version 1.5.1 (rev 2)
    • libXrender: version 0.9.10 (rev 2)
    • libXres: version 1.2.0 (rev 2)
    • libxshmfence: version 1.3 (rev 2)
    • libxslt: version 1.1.32 (rev 2)
    • libXt: version 1.1.5 (rev 2)
    • libXtst: version 1.2.3 (rev 2)
    • libXxf86dga: version 1.1.4 (rev 3)
    • libXxf86misc: version 1.0.3 (rev 3)
    • libXxf86vm: version 1.1.4 (rev 3)
    • listres: version 1.0.4 (rev 2)
    • lm_sensors: version 3.4.0 (rev 2)
    • logrotate: version 3.14.0 (rev 2)
    • lsof: version 4.91
    • lsscsi: version 0.29
    • lvm2: version 2.02.177
    • lz4: version 1.8.2
    • mc: version 4.8.21
    • mesa: version 18.1.2
    • mkfontdir: version 1.0.7 (rev 2)
    • mkfontscale: version 1.1.3 (rev 2)
    • mozilla-firefox: version 61.0.2 (CVE-2018-12359, CVE-2018-12360, CVE-2018-12361, CVE-2018-12358, CVE-2018-12362, CVE-2018-5156, CVE-2018-12363, CVE-2018-12364, CVE-2018-12365, CVE-2018-12371, CVE-2018-12366, CVE-2018-12367, CVE-2018-12368, CVE-2018-12369, CVE-2018-12370, CVE-2018-5186, CVE-2018-5187, CVE-2018-5188)
    • mpfr: version 4.0.1 (rev 2)
    • mtdev: version 1.1.5 (rev 2)
    • nano: version 2.9.8
    • ncompress: version 4.2.4.4 (rev 2)
    • ncurses: version 6.1_20180616
    • net-tools: version 20170208_479bb4a (rev 2)
    • netatalk: version 3.1.11 (rev2)
    • nettle: version 3.4 (rev 2)
    • network-scripts: version 15.0
    • nghttp2: version 1.32.0 (CVE-2018-1000168)
    • nginx: version 1.14.0
    • ntfs-3g: version 2017.3.23 (rev 2)
    • ntp: version 4.2.8p12 (CVE-2016-1549, CVE-2018-12327)
    • numactl: version 2.0.11 (rev2)
    • openldap-client: version 2.4.46
    • openssh: version 7.7p1
    • openssl-solibs: version 1.1.0i
    • openssl10-solibs: version 1.0.2o
    • openssl: version 1.1.0i (CVE-2018-0732, CVE-2018-0737)
    • p11-kit: version 0.23.12
    • pango: version 1.42.1
    • patch: version 2.7.6 (rev 3) (CVE-2018-1000156)
    • pciutils: version 3.5.6 (rev 2)
    • pcre: version 8.42
    • php: version 7.2.8
    • pixman: version 0.34.0 (rev 2)
    • pkgtools: version 15.0 (rev 20)
    • pm-utils: version 1.4.1 (rev 6)
    • procps-ng: version 3.3.15 (CVE-2018-1124, CVE-2018-1126, CVE-2018-1125, CVE-2018-1123, CVE-2018-1122)
    • qemu: version 3.0.0
    • reiserfsprogs: version 3.6.27 (rev2)
    • rpcbind: version 0.2.4 (rev 4)
    • rsync: version 3.1.3 (rev 2)
    • rsyslog: version 8.36.0
    • samba: version 4.8.4 (CVE-2018-1139, CVE-2018-1140, CVE-2018-10858, CVE-2018-10918, CVE-2018-10919)
    • sed: version 4.5
    • sessreg: version 1.1.1 (rev 2)
    • setxkbmap: version 1.3.1 (rev 2)
    • shadow: version 4.2.1 (rev 4)
    • shared-mime-info: version 1.9 (rev 2)
    • spice: version 0.14.0 (rev2)
    • sqlite: version 3.24.0
    • ssmtp: version 2.64 (rev5)
    • startup-notification: version 0.12 (rev 3)
    • sudo: version 1.8.23
    • sysfsutils: version 2.1.0 (rev 2)
    • sysvinit-scripts: version 2.1 (rev 12)
    • sysvinit: version 2.90
    • talloc: version 2.1.13
    • tar: version 1.30 (rev 2)
    • tcp_wrappers: version 7.6 (rev 2)
    • tdb: version 1.3.15 (rev 2)
    • telnet: version 0.17 (rev 4)
    • tevent: version 0.9.36 (rev 2)
    • traceroute: version 2.1.0 (rev 2)
    • transset: version 1.0.2 (rev 2)
    • tree: version 1.7.0 (rev 2)
    • ttyd: version 1.4.0 (rev2)
    • usbredir: version 0.7.1 (rev2)
    • usbutils: version 010
    • utempter: version 1.1.6 (rev 3)
    • util-linux: version 2.32
    • vala: version 0.28.1 (rev2)
    • vbetool: version 1.2.2 (rev 2)
    • vsftpd: version 3.0.3 (rev 5)
    • vte3: version 0.44.3 (rev2)
    • wget: version 1.19.5 (CVE-2018-0494)
    • which: version 2.21 (rev 2)
    • xauth: version 1.0.10 (rev 2)
    • xcb-util: version 0.4.0 (rev 3)
    • xclock: version 1.0.7 (rev 3)
    • xdpyinfo: version 1.3.2 (rev 2)
    • xdriinfo: version 1.0.6 (rev 2)
    • xev: version 1.2.2 (rev 2)
    • xf86-input-evdev: version 2.10.6
    • xf86-input-keyboard: version 1.9.0 (rev 3)
    • xf86-input-mouse: version 1.9.3
    • xf86-input-synaptics: version 1.9.1
    • xf86-video-ast: version 1.1.5 (rev 5)
    • xf86-video-mga: version 1.6.5 (rev 3)
    • xf86-video-vesa: version 2.4.0 (rev 3)
    • xfsprogs: version 4.16.1
    • xhost: version 1.0.7 (rev 2)
    • xinit: version 1.4.0 (rev 2)
    • xkbcomp: version 1.4.2
    • xkbevd: version 1.1.4 (rev 2)
    • xkbutils: version 1.0.4 (rev 3)
    • xkeyboard-config: version 2.22 (rev 2)
    • xkill: version 1.0.5 (rev 2)
    • xload: version 1.1.3 (rev 2)
    • xlsatoms: version 1.1.2 (rev 2)
    • xlsclients: version 1.1.4 (rev 2)
    • xmessage: version 1.0.5 (rev 2)
    • xmodmap: version 1.0.9 (rev 2)
    • xorg-server: version 1.20.0 (rev 2)
    • xprop: version 1.2.3 (rev 2)
    • xrandr: version 1.5.0 (rev 2)
    • xrdb: version 1.1.1 (rev 2)
    • xrefresh: version 1.0.6 (rev 2)
    • xset: version 1.2.4 (rev 2)
    • xsetroot: version 1.1.2 (rev 2)
    • xsm: version 1.0.4 (rev 2)
    • xterm: version 333
    • xtrans: version 1.3.5 (rev 2)
    • xwd: version 1.0.7 (rev 2)
    • xwininfo: version 1.1.4 (rev 2)
    • xwud: version 1.0.5 (rev 2)
    • xz: version 5.2.4
    • zlib: version 1.2.11 (rev 2)

    Linux kernel:

    • version 4.17.19
    • intel ixgbe: version 5.3.7
    • intel ixgbevf: version 4.3.5
    • highpoint r750: version 1.2.11
    • highpoint rr3740a: version 1.17.0
    • added per customer request:
      • CONFIG_BLK_DEV_SKD: STEC S1120 Block Driver
      • CONFIG_BNXT: Broadcom NetXtreme-C/E support
      • CONFIG_CHR_DEV_ST: SCSI tape support
    • changed from built-in to module:
      • CONFIG_BLK_DEV_SR: SCSI CDROM support
    • removed CONFIG_SENSORS_IT87: ITE IT87xx and compatibles
    • it87: version 20180709 groeck Linux Driver for ITE LPC chips (https://github.com/groeck/it87)
    • set CRYPTO_DEV_SP_PSP=N otherwise udev deadlocks on threadripper

    Management:

    • Docker: add optional per-container wait before starting
    • Enable IPv6 for NTP
    • rc.cpufreq: For CPUs using intel_pstate, always use the performance governor.
      • This also provides power savings on Intel processors while avoiding the ramp-up lag present when using the powersave governor (which is the default if ondemand is requested on these machines).
    • restore docker custom networks upon docker start
    • update smartmontools drivedb and hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt}
    • webgui: docker: Correct docker container icon name generation
    • webgui: docker: added cpu load and memory load display
    • webgui: docker: added shell/bash selection for console
    • webgui: docker: Make cpu-load and mem-load only visible in advanced mode
    • webgui: Show accumulated encryption status
    • webgui: Prevent openbox from clipping
    • webgui: Plugins: Show support thread if present
    • webgui: Remove control codes, and extended ascii characters from plugin urls on install
    • webgui: Update link for privileged help text
    • webgui: fix regex matching for unraid.net domain name validation when using new openssl1.1
    • webgui: docker: Prevent arbitrary bash execution or redirection on docker create/run commands
    • webgui: Plugins: Preserve support link when updating plugin
    • webgui: diagnostics: Replace consecutive repeated lines in syslog
    • webgui: Remove empty entries when storing individual disk settings
    • webgui: docker: fix connect container console to new window
    • webgui: Use timeout in command execution of diagnostics
    • webgui: Fixed 'Update All Containers' button sometimes hidden in docker list
    • webgui: Added version control in docker API calls
    • webgui: Show docker allocations in column format
    • webgui: fix css help button in themes azure and gray
    • webgui: Added docker autostart wait period
    • webgui: Added CPU selection to docker container edit section
    • webgui: Verify internet access using NCSI method
      • NCSI = network connection status indicator. This method tries to access a specific Microsoft site to test internet access. The same method is used in Windows.
    • webgui: Added docker autostart wait period
    • webgui: New CPU pinning functionality
    • webgui: Change wording on dashboard page "memory total usable"
    • webgui: Include meminfo in diagnostics
    • webgui: Docker containers page: show container starting up message
      • Starting docker service and auto-starting containers has been decoupled. This lets the docker page return as soon as the service is ready. The container overview page shows a new message, and will automatically reload to update the status until all containers are auto-started
    • webgui: VMs: preserve XML custom settings in VM config updates
    • webgui: dockerMan: Avoid filename collisions on FAT32
    • webgui: Extract disk log from multiple rotated logs
    • webgui: theme-match marketing site

     

    Edited by limetech

    • Like 9



    User Feedback

    Recommended Comments



    With this plugin present, it will overwrite the style sheet files for the white and black themes.

    The white and black themes in earlier versions had minor updates/corrections. Too small to notice the overwriting, but version 6.6 has a complete new design which doesn't work at all with the old style sheets.

     

    Made a propossal (updated install script) to LT to include the deletion of the dynamix plugin when Unraid 6.6 gets installed.

     

    You may want to add a warning (or delete the plugin) in Update Assistent, so people are prepared  in advance.

     

    Link to comment

    hello, I have the problem that I can not update my vm Settings.

    internal error: Cannot parse <address> 'function' Attribute

    does one have an idea what I can do? otherwise 6.6 runs great!

    hello, I have the problem that I can not update my vm settings.

    Bild1.jpg

    Bild2.jpg

    Link to comment
    5 minutes ago, chatman64 said:

    does one have an idea what I can do?

    Something in the parsing goes wrong.

    Can you switch to XML view and post the complete XML file.

    Link to comment

    I used the Update Assistant before upgrading to pre-release/next, so I think that adding the dynamix plugin to the equation(or updating dynamix to remedy this) would be great, for this release that is :)

    Edited by dannen
    Link to comment

    Perhaps @ljm42 can update the upgrade notes?

    And include the remark to delete the file "/config/plugins/dynamix.plg" if exists on the USB device.

    Link to comment
    50 minutes ago, Squid said:

    Couple of times I've seen you post this.  Is there a problem that say my Update Assistant should look for?  Since he was coming from 6.5.3, I thought that an old version of dynamix.plg shouldn't attempt to load since it checked for OS versions.  (Only really ancient versions didn't check the OS version)

    see below:

     

    45 minutes ago, bisk said:

    I had to delete the dynamix.plg file as well.  I was getting the "File not found" error when trying to access the web GUI of the server.  I deleted the file, rebooted and then I was able to connect.  I too was updating from 6.5.3.

    Me too (see page 1).. would highly recommend you automate this file removal.. I have upgraded continuously starting with 6.3, and this file seems to have stuck around. Seems highly likely I am not the only one.

    • Upvote 1
    Link to comment

     

    1 hour ago, bonienl said:

    Perhaps @ljm42 can update the upgrade notes?

    And include the remark to delete the file "/config/plugins/dynamix.plg" if exists on the USB device.

    It is on the Upgrade Notes in two separate places already :) Interesting though, the notes say "the Update Assistant could have warned you of this in advance", so I guess it used to warn about that but no longer does?

    Link to comment

    Just a tip, if you want to test the new GUI but aren't ready to upgrade your main system, you can run unRAID in a VM on unRAID:

     

    It is not officially supported, but it is a great way to test out the new functionality.

    Link to comment

    Updated from 6.5.3. Stuck at the screen below. No idea how to get diagnostics via the command line.

     

    528480841_2018-09-0120_24_06-Discovery_.thumb.png.76be800127bb791a23ac1052cd494c42.png

     

    EDIT: Apparently I too had `dynamix.plg` installed. Removed it, rebooted, and was good to go.

    Edited by vanstinator
    Link to comment

    I'm still on  6.5.3 and checked my plugin page, no sign of "dynamix" but looking in config/plugins/ it is there..

    I think a ton of people are going to have this.. because back in the day we had to install the plugin to do the new gui on 6.2.x?

     

    So why does this plugin not show up on the plugin page? And if its not compatible, why isnt it just blacklisted from being loaded?

    on 6.5.3 it gives the warning.. but it still loads it?

    Jun 14 14:26:15 husky root: plugin: installing: /boot/config/plugins/dynamix.plg
    Jun 14 14:26:15 husky root: plugin: installed unRAID version is too high, require at most version 6.1.9

     

    so whats the proper way to uninstall a plugin that isnt being reported in the gui?

    :/boot/config/plugins# ls -alh | grep dynamix
    drwxrwxrwx  4 root root 4.0K Jun 14 14:28 dynamix/
    drwxrwxrwx  2 root root 4.0K Jan 18  2016 dynamix.apcupsd/
    drwxrwxrwx  2 root root 4.0K Jan 18  2016 dynamix.kvm.manager/
    -rwxrwxrwx  1 root root 1.8K Jul 28  2016 dynamix.plg*
    

    I assume just deleting anything with dynamix in the name would work. since none of that stuff is required because it got merged/turned into webgui

    Edited by zoggy
    Link to comment
    1 hour ago, zoggy said:

    I assume just deleting anything with dynamix in the name would work. since none of that stuff is required because it got merged/turned into webgui

    Just delete dynamix.plg

     

    Unless something has .plg extension it isn't going to load anyway, and there are still a lot of valid dynamix plugins, as well as files and folders with dynamix in the name that are still used.

    Link to comment

    Here my XML File:

    <?xml version='1.0' encoding='UTF-8'?>
    <domain type='kvm' id='14'>
      <name>W10 Download Papa</name>
      <uuid>d3f038e3-fef4-0769-833d-3abb3f18fb23</uuid>
      <metadata>
        <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
      </metadata>
      <memory unit='KiB'>4194304</memory>
      <currentMemory unit='KiB'>4194304</currentMemory>
      <memoryBacking>
        <nosharepages/>
      </memoryBacking>
      <vcpu placement='static'>4</vcpu>
      <cputune>
        <vcpupin vcpu='0' cpuset='4'/>
        <vcpupin vcpu='1' cpuset='10'/>
        <vcpupin vcpu='2' cpuset='5'/>
        <vcpupin vcpu='3' cpuset='11'/>
      </cputune>
      <resource>
        <partition>/machine</partition>
      </resource>
      <os>
        <type arch='x86_64' machine='pc-i440fx-3.0'>hvm</type>
        <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
        <nvram>/etc/libvirt/qemu/nvram/d3f038e3-fef4-0769-833d-3abb3f18fb23_VARS-pure-efi.fd</nvram>
      </os>
      <features>
        <acpi/>
        <apic/>
        <hyperv>
          <relaxed state='on'/>
          <vapic state='on'/>
          <spinlocks state='on' retries='8191'/>
          <vendor_id state='on' value='none'/>
        </hyperv>
      </features>
      <cpu mode='host-passthrough' check='none'>
        <topology sockets='1' cores='2' threads='2'/>
      </cpu>
      <clock offset='localtime'>
        <timer name='hypervclock' present='yes'/>
        <timer name='hpet' present='no'/>
      </clock>
      <on_poweroff>destroy</on_poweroff>
      <on_reboot>restart</on_reboot>
      <on_crash>restart</on_crash>
      <devices>
        <emulator>/usr/local/sbin/qemu</emulator>
        <disk type='file' device='disk'>
          <driver name='qemu' type='raw' cache='writeback'/>
          <source file='/mnt/disks/Samsung_SSD_960_EVO_500GB_S3EUNX0J128904Y/W10_Download_Papa/vdisk1.img'/>
          <backingStore/>
          <target dev='hdc' bus='virtio'/>
          <boot order='1'/>
          <alias name='virtio-disk2'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
        </disk>
        <disk type='file' device='cdrom'>
          <driver name='qemu' type='raw'/>
          <source file='/mnt/user/isos/SW_DVD5_WIN_ENT_10_1703_64BIT_German_MLF_X21-36490.ISO'/>
          <backingStore/>
          <target dev='hda' bus='ide'/>
          <readonly/>
          <boot order='2'/>
          <alias name='ide0-0-0'/>
          <address type='drive' controller='0' bus='0' target='0' unit='0'/>
        </disk>
        <disk type='file' device='cdrom'>
          <driver name='qemu' type='raw'/>
          <source file='/mnt/user/isos/virtio-win-0.1.141-1.iso'/>
          <backingStore/>
          <target dev='hdb' bus='ide'/>
          <readonly/>
          <alias name='ide0-0-1'/>
          <address type='drive' controller='0' bus='0' target='0' unit='1'/>
        </disk>
        <controller type='usb' index='0' model='ich9-ehci1'>
          <alias name='usb'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
        </controller>
        <controller type='usb' index='0' model='ich9-uhci1'>
          <alias name='usb'/>
          <master startport='0'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
        </controller>
        <controller type='usb' index='0' model='ich9-uhci2'>
          <alias name='usb'/>
          <master startport='2'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
        </controller>
        <controller type='usb' index='0' model='ich9-uhci3'>
          <alias name='usb'/>
          <master startport='4'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
        </controller>
        <controller type='pci' index='0' model='pci-root'>
          <alias name='pci.0'/>
        </controller>
        <controller type='ide' index='0'>
          <alias name='ide'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
        </controller>
        <controller type='virtio-serial' index='0'>
          <alias name='virtio-serial0'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
        </controller>
        <interface type='bridge'>
          <mac address='52:54:00:4a:10:d1'/>
          <source bridge='br4'/>
          <target dev='vnet1'/>
          <model type='virtio'/>
          <alias name='net0'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
        </interface>
        <serial type='pty'>
          <source path='/dev/pts/1'/>
          <target type='isa-serial' port='0'>
            <model name='isa-serial'/>
          </target>
          <alias name='serial0'/>
        </serial>
        <console type='pty' tty='/dev/pts/1'>
          <source path='/dev/pts/1'/>
          <target type='serial' port='0'/>
          <alias name='serial0'/>
        </console>
        <channel type='unix'>
          <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-14-W10 Download Papa/org.qemu.guest_agent.0'/>
          <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/>
          <alias name='channel0'/>
          <address type='virtio-serial' controller='0' bus='0' port='1'/>
        </channel>
        <input type='tablet' bus='usb'>
          <alias name='input0'/>
          <address type='usb' bus='0' port='1'/>
        </input>
        <input type='mouse' bus='ps2'>
          <alias name='input1'/>
        </input>
        <input type='keyboard' bus='ps2'>
          <alias name='input2'/>
        </input>
        <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='de'>
          <listen type='address' address='0.0.0.0'/>
        </graphics>
        <video>
          <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
          <alias name='video0'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
        </video>
        <memballoon model='virtio'>
          <alias name='balloon0'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
        </memballoon>
      </devices>
      <seclabel type='dynamic' model='dac' relabel='yes'>
        <label>+0:+100</label>
        <imagelabel>+0:+100</imagelabel>
      </seclabel>
    </domain>


     

    Edited by chatman64
    Format xml revised
    Link to comment
    4 hours ago, zoggy said:

    So why does this plugin not show up on the plugin page?

    At the start of Unraid 6 the plan was to have separate update schemes for the GUI and the OS itself, the thinking was that GUI updates would be issued more regularly than OS updates. This plan didn't work well and was changed to an all-in-one update plan. OS updates are now done on regular basis and are moved to their own update page. The "dynamix.plg" plugin is also considered an OS update, hence it doesn't appear under the user plugins page.

     

    4 hours ago, zoggy said:

    And if its not compatible, why isnt it just blacklisted from being loaded?

    Yeah, an oversight, but next release will ensure that this plugin gets removed upon installation.

    People installing 6.6.0-rc1 however need to delete the file dynamxi.plg (only this one file) manually.

     

    4 hours ago, zoggy said:

    I assume just deleting anything with dynamix in the name would work. since none of that stuff is required because it got merged/turned into webgui

    As @trurl mentioned do not delete the other dynamix plugins, these are user plugins and extensions to the base functionality of the GUI

    Link to comment

    upgrade worked here fine it seems, one question i have about igpu

     

    i915.alpha_support=1  <<-- still needed to get hardware modprobe i915 working on coffee lake cpu´s ?

    or can this be "updaated" to 965 (no idea if possible)

     

    and is it now possible to give dockers their own IP´s without isolating them from the host network ?

     

    thanks ahead

    Link to comment
    9 hours ago, ljm42 said:

     

    It is on the Upgrade Notes in two separate places already :) Interesting though, the notes say "the Update Assistant could have warned you of this in advance", so I guess it used to warn about that but no longer does?

    I did a (too) quick scan of the upgrade notes and didn't see a reference, hence my request.

    If it is already part of the notes and assistent, it looks like people are (1) unaware or (2) ignore the warning about this plugin.

    Anyway in the next release this plugin will be deleted automatically if present to avoid conflicts.

    Link to comment

    I updated from 6.5.3, switching back to white theme first, checking if dynamix.plg is existing (it wasn't). No issues except on first boot tons of pci express reset errors. After another reboot they disappeared. Strange. Whatever, everything else looked fine except from the already mentioned Docker update bug.

     

    Now i noticed the same bug as chatman64. Updating a VM in form-view isn't possible. I got the same error.

     

    EDIT: It doesn't matter what VM i tried, Windows, Linux, MacOS, with or without GPU passthrough. Even a newly created VM. Creating it works fine with standard settings, as soon as i try to edit it the error comes up.

     

    update_error.JPG

    log.JPG

    win7_outlook.xml

    Edited by bastl
    Link to comment
    1 hour ago, alturismo said:

    and is it now possible to give dockers their own IP´s without isolating them from the host network ?

    Unless something changes with the Linux kernel or the docker engine, this isn't going to happen. Maybe if we had the ipvlan drivers... but this has its own caveats and is not yet in prime time AFAIK.

    Link to comment

    ok, thanks for the info, then i stick with pipework for now.

    54 minutes ago, ken-ji said:

    Unless something changes with the Linux kernel or the docker engine, this isn't going to happen. Maybe if we had the ipvlan drivers... but this has its own caveats and is not yet in prime time AFAIK.

     

    Link to comment
    1 hour ago, bastl said:

    Creating it works fine with standard settings, as soon as i try to edit it the error comes up.

    What do you edit exactly?

    Link to comment
    1 hour ago, ken-ji said:

    Unless something changes with the Linux kernel or the docker engine, this isn't going to happen. Maybe if we had the ipvlan drivers... but this has its own caveats and is not yet in prime time AFAIK.

    AFAIK, the solution here is to not use the physical network interface directly. Simply create a macvlan interface for the host to use, just like with the dockers. This enables communication between host and containers. Might be something to consider.

    Link to comment
    9 minutes ago, bonienl said:

    What do you edit exactly?

    First I tried to change the memory from 4 to 8gigs. After that i tried to change the machine type from i440fx-2.11 to a newer version, and even changing the keyboard layout from de to us for vnc results in this error. Every change done one by one. Also without any changes pressing the update button brings up that error.

    Link to comment
    13 minutes ago, bastl said:

    First I tried to change the memory from 4 to 8gigs. After that i tried to change the machine type from i440fx-2.11 to a newer version, and even changing the keyboard layout from de to us for vnc results in this error. Every change done one by one. Also without any changes pressing the update button brings up that error.

    I used your XML file to create a new VM and in my case everything works. After creation I can do the changes you have tried. I am puzzled...

     

    Can you try to start the system in safemode (without plugins) and see if that makes a difference for your VM editing.

    Link to comment
    11 minutes ago, bonienl said:

    I used your XML file to create a new VM and in my case everything works. After creation I can do the changes you have tried. I am puzzled...

     

    Can you try to start the system in safemode (without plugins) and see if that makes a difference for your VM editing.

    Same behaviour in safemode. Creating a new VM works fine, editing brings up that error. 

     

    log2.thumb.JPG.ccde1eec117e66df6334fc89f60e5a96.JPG

     

    Btw. do you tried my xml on a Intel or AMD system?

    Link to comment



    Guest
    This is now closed for further comments

  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.