I have tried da0p3 da1p3 da2p3 da3p3 (There are 4 daX devices after
upgrade 10.2, only 1 in 10.1).
On Tue, Aug 18, 2015 at 12:56 PM, Wei Hu wrote:
> Try /dev/da1p2, /dev/da2p2, etc. If I remember correctly, there was a change
> in the Hyper-V storage code which started to use kernel's SCSI scann
Try /dev/da1p2, /dev/da2p2, etc. If I remember correctly, there was a change in
the Hyper-V storage code which started to use kernel's SCSI scanning code
instead of its own. This may cause the different order of disk discovery.
The commit might have merged into 10 stable branch after 10.1 was re
But GENERIC KERNEL already included
options HYPERV # Hyper-V kernel infrastructure
device hyperv # HyperV drivers
My kernel config file include GENERIC.
Is your VM HDD attached to IDE or SCSI? Mine is IDE, and wanna try SCSI.
--
@hshh
_
Wei Hu writes:
>
> Hi,
>
> Does FreeBSD 10.1 on 2012R2 work in your case? If you can provide detailed
reproducible steps, I will try to
> set it up and troubleshoot in house.
>
Hi, I have the same problem.
Yes, FreeBSD 10.1 on 2012R2 works in my case. When my kernel was upgrade
from 10.2 sour
hshh writes:
>
> After upgrade to 10.2-RELEASE from 10.1, my FreeBSD guest hang on boot.
> Kernel can not find out rootfs.
> All daX devices size is 0MB !!
> Someone has this issue too,
> https://forums.freebsd.org/threads/10-2-cant-see-hdd-on-hyper-v-2k8r2.52797/
I had the same situations - I
Hello,
El 15/08/15 a les 15.36, Outback Dingo ha escrit:
> HEAD UP on 10.2 the instructions found at
> http://wiki.xen.org/wiki/FreeBSD_Dom0
> git branch
> master
> * stable-4.5
>
>
>
> no longer appear to work
>
> gmake -j8 install-tools HOSTCC=gcc48 CC=gcc48
>
> fails with
> __SNI
After upgrade to 10.2-RELEASE from 10.1, my FreeBSD guest hang on boot.
Kernel can not find out rootfs.
All daX devices size is 0MB !!
Someone has this issue too,
https://forums.freebsd.org/threads/10-2-cant-see-hdd-on-hyper-v-2k8r2.52797/
Hyper-V host is win2008.
As 10.1, HDD mounted in freebsd
