Disk issues on Hyper-V

[Justin Sherrill]

The date on the Digest post that you linked to is exactly when I tried it.
I went to real hardware a few days later.

On Sat, Apr 4, 2020 at 11:22 PM David Arroyo <david at aqwari.net> wrote:

> How recently did you set it up? I'm trying to figure out if it's something
> that was broken with a recent release of Hyper-V or if it's something about
> my system that's messed up. Although if it's the latter I'm not sure why
> other operating systems work fine. I'm on Windows 10 Pro.
>
> On Sat, Apr 4, 2020, at 16:34, Justin Sherrill wrote:
>
> I realize this is not the most helpful answer, but I didn't encounter this
> problem when I set up Hyper-V and DragonFly before.  I ended up going to
> real hardware because I wanted to have DragonFly talking out of the serial
> port.
>
> It might have been the Hyper-V image type that affected it, or the legacy
> BIOS option in the DragonFly installer as I had mentioned in my posts about
> it.  Those are guesses, however, cause I don't have a Windows 10 machine
> handy that I can test this with anytime soon.  My DragonFly machine that I
> ended up setting up for that experiment is currently broadcasting grdc
> output through a VT320 terminal into an empty cube in a near empty office.
>
> On Sat, Apr 4, 2020 at 11:17 AM David Arroyo <david at aqwari.net> wrote:
>
> Hello,
>
> I'm trying to run Dragonfly 5.8.0 on Hyper-V on my Windows 10 machine.
> Going off of this article from 2018[1], I created a Gen 1 VM with a legacy
> network adapter and used IDE for the virtual disk. However, when booting
> the system I see these errors in dmesg:
>
> ad0: 81920MB <Virtual HD 1.1.0> at ata0-master WDMA2
> ad0: FAILURE - SETFEATURES ENABLE WCACHE status=51<READY,DSC,ERROR> error=0
> ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=0
> ad0: FAILURE - SETFEATURES ENABLE WCACHE status=51<READY,DSC,ERROR> error=0
> ad0: TIMEOUT - READ_DMA retrying (0 retries left) LBA=0
> ad0: FAILURE - SETFEATURES ENABLE WCACHE status=51<READY,DSC,ERROR> error=0
> ad0: FAILURE - READ_DMA timed out LBA=0
> ad0: reading primary partition table: error accessing offset 000000000000
> for 512
>
> Trying to read anything from the disk times out. If I switch the mode from
> WDMA2 to PIO4 I can read but writes give an I/O error:
>
> # natacontrol mode ad0 PIO4
> current mode = PIO4
> # dd if=/dev/ad0 of=/dev/null bs=1M count=1
> 1+0 records in
> 1+0 records out
> 1048576 bytes transferred in 0.134417 secs (7800912 bytes/sec)
> # dd if=/dev/zero of=/dev/ad0 bs=1M count=1
> ad0: timeout waiting for write DRQ
> dd: /dev/ad0: Input/output error
> 1+0 records in
> 0+0 records out
> 0 bytes transferred in 0.201104 secs (0 bytes/sec)
>
> I tried turning on debug logging for Hyper-V but nothing was logged while
> I reproduced the issue. I then tried FreeBSD and Ubuntu VMs with the same
> configuration and didn't see the issue. I also tried switching the disk
> from the IDE controller to the SCSI controller, but when I did that,
> dragonfly couldn't see the disk any longer.
>
> I'm not sure where to go from here. I work with Linux at $dayjob, so I am
> not really familiar with Hyper-V *or* BSD. Has anyone else built a
> dragonfly VM on Hyper-V recently, and did you have any trouble? Does anyone
> have any advice for troubleshooting the read timeouts?
>
> Cheers,
> David
>
> [1]: https://www.dragonflydigest.com/2018/09/28/21850.html
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20200404/47b5f2df/attachment-0004.htm>