Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

VM issues upgrading from 6.3.5 Stable > 6.4.0 rc6

Featured Replies

Firstly, I apologize if this is the wrong section to post. Perhaps the post belongs in the rc6 release thread. Someone please let me know if that's the case.

 

When I upgraded to 6.4 rc6 from 6.3.5, the first thing I did was enable UEFI booting, and returned my server to UEFI booting. I also enabled https with the config/go hack. Both of these appear to be working just fine.

 

The problems I'm having are with my VMs, specifically my Linux (Ubuntu 17.04) VMs. I also have 2 Windows VMs that do not exhibit any issues.

Issue #1) Network adapter names for all VMs changed. This caused obvious connectivity loss to VMs. Windows picked up on the change and adjusted automatically, Ubuntu did not. Needed to get interface name with sudo ifconfig -a, then edit /etc/network/interfaces with the new name. Now works fine. Did I miss something in the change notes that this would need to be done?

 

Issue #2) I can no longer boot my Ubuntu VMs using disk type "VirtIO" after changing to Qemu 2.9. I installed them as VirtIO, and ran them fine, until I messed with the Qemu version. At that point, even returning it to the original value of 2.7 still didn't work. What happens is it drops me into the EFI shell, with the error "no maps found", which prevents me from manually booting from the efi file. Swapping to SATA disk type seems to have resolved the problem. My Windows VMs were updated from i440fx 2.7 to i440fx 2.9, and did not exhibit this issue (they are also VirtIO). Booted and working fine? Anyone have any ideas on this one?

Edited by Aerowinder

  • 2 weeks later...

Confirmed #2.  Updated QEMU to 2.9 in a couple of my Ubuntu VMs and they gave me the same "no maps found" error.  I haven't been able to recover them by switching to SATA however. Something happens when you edit the VM in the GUI.  I recreated by creating a new VM then replacing everything except the UUID in XML editor with a working VM's XML (Working VM has no custom edits).  VM booted normally.  Entered the GUI edit page and just saved without making changes.  Afterwards I would get the UEFI boot menu with error "no maps found"  

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.