Date: Sat, 26 Aug 2017 18:11:00 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 218731] FREEBSD 11 SCSI drive issue with all 11.xxxx versions running under HYPER-V as a VM Message-ID: <bug-218731-27103-5SpAvnMeBu@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-218731-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-218731-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218731 --- Comment #16 from ds <mx5arbc@hotmail.com> --- Adding some additional testing I performed. Just to ensure I didn't have some anomaly in my test system described above (given that your internal test showed that running on Windows server 2016 HYPER-V didn't seem to reveal a problem running with virtual SCSI drives - I can't replicate this as I don't have the server version of Windows), I repe= ated a test with another pc, running same O/S platform as my test platform (Win= dows 10PRO64 - but older 3rd gen Intel CPU platform, i5-3570K, 16 GB RAM). That system is running a VM image of NAS4FREE 10.3 based on FREEBSD 10.3 successfully with a ZFS volume of 4 drives using RAID-Z1 resiliency. I created a new VM with newer NAS4FREE 11.1 image and imported the config f= ile of the 10.3 NAS image which all ran fine, however the SCSI-defined disk dri= ves attached to VM were no longer visible - same problem as reported on my test platform. I've done enough testing to know that this process doesn't dam= age the content of an existing ZFS volume, so I wasn't concerned about going ba= ck to 10.3 after doing this (which worked fine).=20=20=20 If NAS4FREE 11 with FREEBSD11 runs fine in the Server 2016 version of HYPER= -V but not on the desktop version (which is the same series - Server 2016 late= st and W10 PRO Creators' Update then it begs the question as to what is differ= ent with those 2 platforms as it relates to virtual machines with integrations services and how FREEBSD11 works with them differently than 10.3 did.=20=20= =20 In the NAS4FREE support forum, someone else also reported running into this problem with VMWARE ESX hypervisor but don't know which version so that led= me to think that HYPER-V was not be cause. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-218731-27103-5SpAvnMeBu>