Windows 10: @KARI access Linux HDD's in HYPER-V VM

Hi there

particularly @Kari.

I'm playing around now with HYPER-V.

I want to access 1 X 9 TB and 1 X 7 TB Linux internal HDD's from a HYPER-V VM (Centos 7). I'm running HOST W10 pro x-64.

I've taken the two HDD's offline to the HOST but can't seem to get the VM to see them.

These are INTERNAL HDD's. (4 physical volumes, computer sees as 2 logical HDD's - RAID 0 via hardware at boot)

I've backed up the data just in case it all goes pearshaped. !!!! The two HDD's are formatted XFS (but not in LVM group) so they should be accessible individually.

I've also got 2 physical NIC's in the hardware so network switch should be fine. ( HP Ethernet 1Gb 2-port 332i adapter )

Any help here would be appreciated. I need to access these HDD's in the VM in Native mode (I presume that's the point of the pass-thru).

This can't be done in VMWARE or VBOX -- you can only attach USB HDD's. So if this can be done then a good reason for using HYPER-V. Time Illearned it properly anyway.

(I'm trying to create a Virtual Media server - my media files are on the Linux HDD's).

Thanks

Cheers
jimbo

:)

 

Unable to install fall creators update 1709

Oh i see.

I use Ubuntu on a VM.

Windows 10 has Hyper-V so you can download Ubuntu and create a Ubuntu VM.

More work yes, but i like it because it is more isolated too.

https://www.windowscentral.com/how-run-linux-di...

 

Remote Desktop Connection problem with Virtual Machine

We made the big mistake of configuring a WINDOWS-10 VM to allow for Remote Desktop Connections. We are unable to disassociate the VM from RDM. We can no longer access the VM!!! The following is the pertinenet
information:

• Server is running Windows-10 Professional 64 with Hyper-V installed.
• VM is Windows-10 Professional 64.
• In VM allowed Remote Desktop Connections.
• From server successfully connected to VM via RDM.
• Closed RDM connection. Unable to access VM.
• Turned off VM from Hyper-V Manager.
• Attempted to restart VM, unable to connect via Hyper-V from message box the following is displayed:
  
  Video Remoting was disconnected. The virtual maching is currently using the Remote X 3D video adapter. A user is currently connected via Remote Desktop Connect to the virtual machine by using Remote Desktop Connection.
• Connected via Remote Desktop Connection. Attempted to turn off allowing Remote Desktop Connection. VM hung.
• VM Wouldn't turn off via Hyper-V manager.
• Shutdown host system and rebooted.
• Unable to connect via console or RDM.
• Shutdown host system and rebooted.
• Deleted VM via Hyper-V Manager.
• Restored VM system disk from backup prior to RDM usage.
• Created new VM. the messages in itm 7 above are displayed.

What can be done to recover? Why does Hyper-V retain a broken connection?

 

Shouldn't be a problem. Remember that you have to add physical disks (must be offline) as SCSI device, even if your vm were Generation 1 which by default adds virtual hard disks as IDE.

Shawn has made an excellent tutorial for this, see Option One steps 5 & 6 for adding the disks as SCSI device: Hyper-V Virtual Machine - Add or Remove Physical Hard Disk - Windows 10 Forums

 

Hi there

Thanks especially @Kari

Working now SCSI is the trick and option 1 (This system doesn't have UEFI - that was mistake nr 1 !!!) still it's all learning.

I could get "addicted" to this !!!

SAMBA works to share HDD's with Windows Host too -- using 1 NIC for 2.4Ghz and 1 NIC for 5 GHZ wifi connections (Using 2X routers as Ethernet-->wifi Bridges --works fine !!) --hate loads of LAN cable over the place - 5GHZ wifi gives max of 433 mb/s transfer --more than fast enough for media server testing !!). I'm lucky here --wifi up to 1tb !!! good thing about Nordic countries - wifi infrastructure first class.

Cheers

jimbo

 

That with SCSI is the most important factor, logics tell us to put the disk offline but not that when added to vm it must be added as SCSI *Smile