From owner-freebsd-virtualization@freebsd.org Thu Aug 24 15:53:40 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 34070DE2A27 for ; Thu, 24 Aug 2017 15:53:40 +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 2181B8199F for ; Thu, 24 Aug 2017 15:53:40 +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 v7OFrdq3072467 for ; Thu, 24 Aug 2017 15:53:39 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: Thu, 24 Aug 2017 15:53:40 +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: Thu, 24 Aug 2017 15:53:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218731 --- Comment #8 from ds --- (In reply to Sepherosa Ziehau from comment #7) ---------------------------------------------------------------------------- In addition to dmesg, please also give me your SCSI disk configuration: the SCSI controller index, the disk location, and whether it's virtual disk or = real disk, etc. ---------------------------------------------------------------------------- I don't know what a dmesg is. I run this operating system embedded as par= t of NAS4FREE 11.1 NAS O/S, therefore I don't touch the FREEBSD operating system itself. I also tried running the other open source NAS O/S, FREENAS11. Bo= th of these are now using FREEBSD 11.1 as base. See my comments above on the= se.=20 I'm not familiar enough with pure FREEBSD to run it on its own. I have reported this issue to both NAS suppliers and they have confirmed that it's= not part of their software, but part of base O/S and therefore can't help me.= =20=20 Someone else also reported this same issue on VMWARE virtualization platform which I can't verify since I don't have that platform. As for SCSI drive, it is a physical hard drive, either blank unformatted or sometimes it might have NTFS on it, however when I go into NAS platform, I usually format it for ZFS file system. Since the drive can't be seen at all when defined as SCSI to HYPER-V, I can't proceed as usual. The disk is on= a standard onboard SATA3 port connected disk, with AHCI chosen on the motherb= oard bios as it is for all drives.=20 Not sure what you mean by SCSI controller index. As mentioned above, this issue does not occur with previous generation of FREEBSD 10.X embedded as part of NAS o/s platforms. I'm still running tho= se successfully. Only since 11.X has this started to happen. --=20 You are receiving this mail because: You are the assignee for the bug.=