Jump to content

bonienl

Community Developer
  • Posts

    10,233
  • Joined

  • Last visited

  • Days Won

    65

Report Comments posted by bonienl

  1. Step 1: I created a new VM using your XML file (excluding the part which you added later)

    Step 2: I added the hostdev part

    Step 3: switched to Form view and changed cpu pinning assignment. This works

    Step 4: changed memory from 32G to 16G. This works

     

    I don't start the VM upon creation because I don't have a NMVE device, but all appears to work when the VM is never started. Can you do a similar test?

  2. 17 minutes ago, bastl said:

    And as mentioned earlier, creating a new vm without editing anything caused that error on the first edit afterwards.  

    Do you have anything special in your syslinux.cfg file or go file which may affect VMs?

     

    The error message indicates it can not parse the PCI device address <bus> <slot> <function> (it fails on the 'function' part)

  3. 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.

  4. 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.

  5. 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

  6. To investigate this better, the complete XML file is required. This is not included in the diagnostics, but requires manual upload.

    Perhaps you can highlight which part in the XML file you change that causes the issue.

     

  7. 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.

     

  8. 3 minutes ago, ZataH said:

    I am getting this when I try do update

    
    plugin: installing: /var/tmp/unRAIDServer.plg
    plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/next/unRAIDServer-6.6.0-rc1-x86_64.zip ... failed (File I/O error)
    plugin: wget: https://s3.amazonaws.com/dnld.lime-technology.com/next/unRAIDServer-6.6.0-rc1-x86_64.zip download failure (File I/O error)

     

    That looks like a problem on your flash device.

    Powerdown your system and take the USB stick out. Let it do a scan and repair on a Windows machine

×
×
  • Create New...