r at all "IDE". :)
4) In you SAS driver in storvsc_action() you have hardcoded
CTS_SCSI_FLAGS_TAG_ENB flag. While I guess it should not cause any
problems, it wont allow user to control it if he decide to experiment
with disabling it.
--
Alexander Motin
es to the ATA driver.
The changes are necessary to achieve significant performance gains by
replacing the native ATA driver with our synthetic storage driver
when when Hyper-V is detected. Alexander Motin, the maintainer of the
ATA code-base, however, expressed some concerns about making
ead 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
___
freebsd-virtualization@freebsd.org mailing list
ack
blocking CAM ada driver (ATA disk driver), but it still can be made
modular and non-invasive.
--
Alexander Motin
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To uns
owner-freebsd-virtualizat...@freebsd.org
[mailto:owner-freebsd-virtualizat...@freebsd.org] On Behalf Of Oleg Sidorkin
Sent: Monday, September 23, 2013 7:21 AM
To: freebsd-virtualization@freebsd.org
Cc: Alexander Motin
Subject: [Hyper-V][camlock] storvsc driver panics during boot with patches from
ca
se_boot() in callback.
Thanks
On Thu, Oct 24, 2013 at 9:50 AM, Alexander Motin wrote:
Hi.
I took some look and think problems are in scan_for_luns() routine:
- After the locking changes scanning normally uses different locks, not the
SIM one. That probably caused panic.
- But I think th
>
> I was about to report the same thing. I'm still running r280041 and
> wanted to repro with the latest changes before reporting.
>
> I've just now updates 7 bhyves to r280120 and am putting some load on it.
I also hit this problem, and I hope it should be fix
and ahci-hd drivers now report to guest logical and
physical block sizes of underlying storage, that allow guests properly
align partitions and I/Os for best compatibility and performance.
--
Alexander Motin
___
freebsd-virtualization@freeb
that complicates
CAM and the whole infrastructure.
--
Alexander Motin
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to
"freebsd-virtualization-unsubscr...@freebsd.org"
uires
additional memory allocation, and the copying is not free. May be some
cases could be optimized to work without copying but with some clever
page mapping, but that seems absolutely not trivial.
--
Alexander Motin
___
freebsd-virtualization@freebs
On 06.04.2015 23:38, Alexander Motin wrote:
>> I had some time to try it out today, but I'm still having issues:
>
> I've just made experiment alike to your with making bhyve to work on top
> of GEOM device instead of preferable "dev" mode of ZVOL. And I indee
mav added a comment.
It was definitely significant amount of work, but I am not sure what
motivation was behind it. Why do we need it after already having much more
featured AHCI-based ATA/ATAPI emulation? Are there any significant OS not
supporting AHCI? There is significant amount of code
mav added a comment.
In https://reviews.freebsd.org/D5473#117346, @iateaca wrote:
> The motivation is to run older versions of operating systems such as
FreeBSD 4 which does not have AHCI drivers.
> What do you mean by code duplication ? I think only the ATAPI CDROM logic
could be com
13 matches
Mail list logo
