Date: Tue, 07 May 2013 11:07:47 +0300 From: Alexander Motin <mav@FreeBSD.org> To: Victor Miasnikov <vvm@tut.by> Cc: larry.melia@ieee.org, freebsd-virtualization@freebsd.org Subject: Re: ATA controller and Hyper-V "synthetic storage driver" handle the IDE disks devices ( but not for the CD-ROM) Re: Hyper-V on FreeBSD Message-ID: <5188B653.5020207@FreeBSD.org> In-Reply-To: <A45F0063B66A43ECBA57AFCAA57676DD@local.st.by> References: <A45F0063B66A43ECBA57AFCAA57676DD@local.st.by>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07.05.2013 10:40, Victor Miasnikov wrote: >> prevent default OS driver from attaching to emulated ATA controller >> when Hyper-V > > Disable both primary and secondary ATA controller prevent use CD-ROM > device in VM ( guest) > > Because "synthetic storage driver" not handle CD-ROM devices > ( IMHO, even more: Hyper-V host work with CD-ROM only as "PCI bus" device) Then may be possibility of blocking/hiding specific ATA channels or devices could be investigated. > http://lists.freebsd.org/pipermail/freebsd-virtualization/2013-April/001180.html > > == > . . . > On 23.04.2013 17:07, Larry Melia wrote: > . . . >> Removing our ATA patches, on the other hand, results in a huge >> performance loss. This is because the root file system is managed by the >> ATA driver, which is emulated under Hyper-V. > == > > Place on IDE disk only "\boot" ( and bootloader), other on SCSI . May be instead of splitting filesystem it could be better to boot from "SCSI" completely and forget about "ATA"? Or there is no option ROM for SCSI boot in Hyper-V? -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5188B653.5020207>