From owner-freebsd-virtualization@freebsd.org Sat Aug 26 18:11:00 2017 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 92B3DDD741E for ; Sat, 26 Aug 2017 18:11:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 80802736E1 for ; Sat, 26 Aug 2017 18:11:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7QIAxSl009101 for ; Sat, 26 Aug 2017 18:11:00 GMT (envelope-from bugzilla-noreply@freebsd.org) 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 Date: Sat, 26 Aug 2017 18:11:00 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: mx5arbc@hotmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Aug 2017 18:11:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218731 --- Comment #16 from ds --- 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.=