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 with Windows Server and Hyper-V enabled

Featured Replies

Hello,

I know that "nested virtualisation" is not the brightest idea - but I have to do a labor and I want to use my passthrough Nvme drive.

The thing that's a little bit strange is following is that as soon as I enable Hyper-V on the VM I'm not able to reach my Unraid SMB anymore.

The Network Model is: virtio-net.

What's happening is:

  • Fresh install of W2022 (I wanted to use 2025, but it peaks in CPU usage as soon as I enable Hyper-V role, so I reverted to 2022):
    • I can connect via RDP to my VM
    • I can ping my Unraid Server (segmented network 10.x.x.x/24) and try to connect to the SMB share, I'm asked to put the username and password and I can connect
  • Enabling Hyper-V role and rebooting the server
    • I can connect via RDP to my VM
    • I can ping my Unraid Server, but when I try to reach the share I get : "Windows cannot find \\ip\share"
  • Created the virtual switch:
    • I can connect via RDP to my VM
    • I can ping my Unraid Server, but when I try to reach the share I get : "Windows cannot find \\ip\share"

 

So I'm a little confused what's preventing the connection to the SMB as soon as I enable Hyper-V.

 

Thanks in advance

Edited by TDA

  • Author
1 hour ago, TDA said:

Hello,

I know that "nested virtualisation" is not the brightest idea - but I have to do a labor and I want to use my passthrough Nvme drive.

The thing that's a little bit strange is following is that as soon as I enable Hyper-V on the VM I'm not able to reach my Unraid SMB anymore.

The Network Model is: virtio-net.

What's happening is:

  • Fresh install of W2022 (I wanted to use 2025, but it peaks in CPU usage as soon as I enable Hyper-V role, so I reverted to 2022):
    • I can connect via RDP to my VM
    • I can ping my Unraid Server (segmented network 10.x.x.x/24) and try to connect to the SMB share, I'm asked to put the username and password and I can connect
  • Enabling Hyper-V role and rebooting the server
    • I can connect via RDP to my VM
    • I can ping my Unraid Server, but when I try to reach the share I get : "Windows cannot find \\ip\share"
  • Created the virtual switch:
    • I can connect via RDP to my VM
    • I can ping my Unraid Server, but when I try to reach the share I get : "Windows cannot find \\ip\share"

 

So I'm a little confused what's preventing the connection to the SMB as soon as I enable Hyper-V.

 

Thanks in advance

I tried to disable Disabling Large Send Offload (LSO), and I was able to do so (kind of) and now it *seems* to work - for the moment.
I'll have to do extensive tests

  • Author

So - the Hypervisor itself "seems" to work.

Unfortunately every VM which is inside doesn't have access to the network (strangely enough).
They receive an IP over DHCP, but aren't able to reach the internet.
Anyone has experience whit such a construct (hyper-V VM with VM inside)

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.