[[6.6.1] AMD Reboot bug]

EDIT:

 

Remove the "<boot dev='hd'/>" part only in your xml and try if that fixes it.

  <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/f7924a7b-24f4-a50f-9c47-8bca810aa128_VARS-pure-efi.fd</nvram>
    <boot dev='hd'/>
  </os>

EDIT END

 

 

 

@J89eu

If i use this xml i get the same error

 

Removing the following part removes that error for me. I guess thats the part you added to passthrough your NVME.

 

Can you try to passthrough your NVME like i did with my second SSD.

 

    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source dev='/dev/disk/by-id/ata-Samsung_SSD_850_EVO_1TB_S2RFNX0J606029L'/>
      <backingStore/>
      <target dev='hdd' bus='virtio'/>
      <alias name='virtio-disk3'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </disk>

 

[[6.6.1] AMD Reboot bug]

Do you use the old method passthing through the NVME controller and using a clover image? Still works for me as it's shown in SpaceInvaders Video. Can you post the XML throwing out that error?

[[6.6.1] AMD Reboot bug]

Did you tried to recreate the VM from scratch? @J89eu Add a new VM and configure everything as before with the GUI? Don't copy paste your old XML settings into it. Set up your core pinnings, amount of RAM and the GPU to passthrough.

[[6.6.1] AMD Reboot bug]

@J89eu You passthrough your UPS (Cyber Power System, Inc. CP1500 AVR UPS) to the VM right? The last libvirt logs showing that a USB device can't be found. Looks like your UPS isn't recognized bei UNRAID or is not connected. For me VMs wont start if i passthrough a USB mouse or keyboard for example that aren't connected.

[[6.6.1] AMD Reboot bug]

I remember that bug also appeared on AMD systems and was fixed for most people by updating the kernel + BIOS update. I think 4.16 or 4.17 fixed it. Unraid 6.6 is on kernel 4.18 now. You might check, if there is a newer BIOS available. Yours is from 2017 and i guess there will be lots of updates for your board.

[6.6 Upgrade - GPU Passthrough Issues]

On older versions of UNRAID i had to use the pcie_acs_override=downstream,multifunction option to break down my IOMMU groups to get the GPUs in its own groups. With the newest BIOS (AGESA 1.1.0.0) + Unraid 6.6 this isn't needed anymore. At least for me. All my network adapters are still in one group and the USB controllers which i don't passthrough anyway. Maybe check if you're on an up-to-date BIOS? @CSeK I also dissabled the ACS-Override option in the VM-Manager settings and everything works.

 

Edit:

Your logs show you're on an old BIOS

Sep 20 16:41:34 unRAID kernel: DMI: System manufacturer System Product Name/ROG ZENITH EXTREME, BIOS 0902 12/21/2017

 

ASUS released a new version in august with the newer AGESA version. 

ROG ZENITH EXTREME BIOS 1402
Update AGESA 1.1.0.1 Patch A to support AMD 2nd Gen Ryzen™ Threadripper™ processors

 

 

[Unraid OS version 6.6.0-rc3 available]

As you said @bonienl it first happened with the RC1 build. The domain "msftncsi.com" i have in an alias list in PFsense since 2017 for blocking Microsofts telemetry stuff. No issues with updating any Windows PC so far in that time by blocking that domain. Windows never showed any connection issues.

 

I had to remove the domain from the list and also "msftncsi.com.edgesuite.net" for the update check to work. Currently the domains resolve to "a1961.g2.akamai.net" which aren't filtered by my alias list. But i have a couple more "*.akamai.net" domains in there. Let's hope the name resolving doesn't change. Thanks for the hint  

[Unraid OS version 6.6.0-rc3 available]

Manual update from RC2 worked without any problems so far. But same issue as before, RC3 didn't showed up in the update section. I only see the status as "unknown". Can't figure it out where my issues are. AWS download servers are reachable within the browser. Nothing gets blocked from my PFsense box. I appreciate any advice.

[Unraid OS version 6.6.0-rc2 available]

Manual update passed without errors. Looks like everything is ok. Status from the Update dialog still shows "unknown"

[Unraid OS version 6.6.0-rc2 available]

On 9/8/2018 at 7:56 PM, Squid said:

Go to Update OS, and then post your diagnostics.

Here are my diagnostics.

 

 

I checked my PFSense box but nothing gets blocked. AWS servives are accessible.

 

If i check the link with Google Chrome

On 9/8/2018 at 7:56 PM, bonienl said:

https://s3.amazonaws.com/dnld.lime-technology.com/next/unRAIDServer.plg

something comes up in the browser from inside am VM on Unraid. Looks some sort of XML file with the download instructions. I will try the manual install. Will report back in a second.

[Unraid OS version 6.6.0-rc2 available]

There is no RC2 shown up anywhere. Second picture is running the Update Assistant for next branch.

 

 

[Unraid OS version 6.6.0-rc2 available]

I'am trying to update from RC1 to RC2 but the Tools/Update OS Section didn't come up with the new version. Update assistant doesn't show any errors. Am I missing something or do i have to downgrade to 6.5.3 first? On RC1 I had to call the docker "check for updates" manually by executing the dockerupdate.php. Is there a way to trigger the update manually?

[Unraid OS version 6.6.0-rc1 available]

Hi @gridrunner

 

First of all big thanks for all your great Unraid tutorials. Helped me a lot to configure my system. I myself use a first gen 1950x so far without any big issues, but what i noticed and earlier reported in this thread, after an upgrade from 6.5.3 to the 6.6.0-rc1 i can't edit any existing VM in the form view without getting an error. Creating one works fine, but not the editing later. Did you upgraded from an earlier version or did you tried a fresh install?

 

If i remember correctly you had an 1950x before, right? If you still have that chip can you check the following thread and maybe can post your core pairings how it looks on your system.

 

https://forums.unraid.net/topic/73509-ryzenthreadripper-psa-core-numberings-andassignments/?do=findComment&comment=678031

[Unraid OS version 6.6.0-rc1 available]

2 minutes ago, chatman64 said:

the path does not exist

For me the mounted libvirt.img is accessible under this path via the webterminal

 

[Unraid OS version 6.6.0-rc1 available]

10 minutes ago, chatman64 said:

I modified the XML in the old post. I do not know how I can make a backup of the original file.

You can find the xml files in /etc/libvirt/qemu

[Unraid OS version 6.6.0-rc1 available]

8 minutes ago, bonienl said:

Unraid reads the CPU information from linux. What is the output of this command

cat /sys/devices/system/cpu/*/topology/thread_siblings_list

 

The command brings up the following:

 

 

For whatever reason every pair is shown twice.

 

My current syslinux config looks like this

 

 

I removed the following today after i tested disabling the ACS override patch.

 

"pcie_acs_override=downstream,multifunction"

 

IOMMU groups are fine now with the current kernel and my updated BIOS yesterday. With the older BIOS from end of last year i wasn't able to passthrough a GPU or the nvme controller without this line. Now it works without. All the issues with core pairings or the noneditable VMS existed on both configurations.

 

I don't really sure if i ever touched the go file. 

 

 

 

 

[Unraid OS version 6.6.0-rc1 available]

@chatman64 Are you german same as me? I asked because in your screenshot i see you have configured VNC to use a german layout. Maybe something with the localisation causes that error. I already checked if the VNC layout is the issue, but it wasn't the case. Tested a VM without VNC added to it, same error and chossing us layout causes it. And as mentioned earlier, creating a new vm without editing anything caused that error on the first edit afterwards.  

[Unraid OS version 6.6.0-rc1 available]

8 minutes ago, bonienl said:

Intel

I have a feeling it's an AMD releated issue with Unraid 6.60-RC1. In earlier Versions i hadn't had any issues like this. Maybe someone with a Ryzen or Threadripper system reading this can test my xml or can try to reproduce this error. 

 

win7_outlook.xml

 

This looks like another Threadripper/Ryzen related issue i posted in another thread couple days ago. The shown core pairings in unraid didn't really match the real pairing of the cores. I did a couple of test to find out which core is on which die and which ones are the threads only. It looks like the pairings presented to the user by unraid isn't correct. This hasn't changed with the 6.60-RC1 version.

 

 

[Unraid OS version 6.6.0-rc1 available]

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. 

 

 

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

[Unraid OS version 6.6.0-rc1 available]

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.

[Unraid OS version 6.6.0-rc1 available]

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.

 

win7_outlook.xml