[Bug 229167] [Hyper-V] [Jun 19, 2018] Recently FreeBSD VM panics during boot-up, especially with Mellanox VF configured

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229167

--- Comment #18 from Dexuan Cui  ---
(In reply to pete from comment #17)
I did both source code update and binary update, and can't repro the issue
either way.

For binary update, I referred
https://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html:

freebsd-update -r 11.2-RELEASE upgradd
freebsd-update install
reboot
freebsd-update install

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

[Bug 229167] [Hyper-V] [Jun 19, 2018] Recently FreeBSD VM panics during boot-up, especially with Mellanox VF configured

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229167

--- Comment #16 from Dexuan Cui  ---
(In reply to Dexuan Cui from comment #15)
I also created a 11.1 VM from the MicrosoftOSTC:FreeBSD:11.1:latest image, and
updated it to 11.2 (11.2-RELEASE FreeBSD 11.2-RELEASE #0 r335510: Fri Jun 22
04:32:14 UTC 2018 r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC
 amd64) and can't reproduce the issue: I have mlx4en_load="YES" in
/boot/loader.conf and the mlxen0 interface appears in "ifconfig" as expected.

According to the call-trace, the panic we previously saw happens in namei(),
which is in VFS code. So my feeling is: the file system may be somehow corrupt
or there is a race condition bug in the VFS code?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"