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.

VMs hang the Unraid host

Featured Replies

Unraid 6.12.13 (and earlier 6.12.x versions)

 

I'm only running one Windows 10 VM 24x7 and it has been pretty stable for a few years.  I've recently tried adding/starting other VMs and they're mostly hanging the Unraid server (completely unresponsive, although sometimes responds to pings; I have to power-cycle and endure a full parity check that takes over 24h), or occasionally crashes the other running VM.

 

My running VM is a Q35-3.0 machine with OVMF bios, running Windows 10 with NO pass-through of GPU, USB, Unraid shares, etc. (I haven't had any luck with Unraid shares via Virtiofs, but that's a separate issue).  It's running Blue Iris, connected to IP cameras and writing to virtual disks and occasionally moving files to the array via SMB share.

 

The "new" VM type doesn't seem to make a difference; I can't seem to install Windows 11, Windows 10, or Ubuntu Server 24.x in a new VM without major issues with the Unraid host.  They start to boot and go through the OS installation process before the host hangs or the other VM crashes.  I think I have tried different machine/BIOS types but I didn't keep notes.

 

I have attached diagnostics exported shortly after the latest issue, where the Unraid server hung during installation of Ubuntu Server (latest LTS version).  The last message that I recall seeing in the VNC console during Ubuntu installation was "waiting for cloud-init" - I have no idea whether that's relevant.

 

Thanks in advance for any help.  At this point I'm waiting on the parity check and very apprehensive about trying to start or troubleshoot VMs without some clear guidance.

argon-diagnostics-20241208-1334.zip

Edited by loqus

Thanks for posting a diag file. Sadly while diags are a good start and help with alot VMs and Docker specific are not always captured...

Usually when this happens. it's due to resource allocation and limitation in hardware.

 Q35-3.0 is a old machine type? With Windows 10 you should be using q7.2 or higher.
 

  • Author
1 hour ago, bmartino1 said:

 Q35-3.0 is a old machine type? With Windows 10 you should be using q7.2 or higher.

 

Thanks for the reply.  One of the things I'm trying to accomplish right now is to rebuild and replace that Win10 VM with more modern VM settings and OS.  But if I can't start a new VM...

 

Any recommendations for where to look or what to try re: resources and hardware?  Thanks!

Sorry, A more experienced user may need to assist here.
Not seeing anything outright in the logs.

Since I went proxmox for virtualization. I'm not in the know for the current unraid xml and fixes or resources assigning.

Though unraids web UI for VM edits.... A unraid windows needs a mini of 4 threads with resource pinning. (4 cpu cores pined/assigned to it) and a min of 4 GB of ram that for the OS alone for general use....

 

if its for gaming a min of 6 cores (maybe 8 ) and atleast 8 GB of ram if not more... with a g card pass through for 3d rending. Its hard to say. 

 

There nothing wrong with using a older q35 machine type. a new unraid VM (reusing the same vdsik) may be required here to bring you to a more up-to-date xml file and use for your setup.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

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.