Bug 186909 - [hyper-v] [panic] Stable GENERIC kernel panic on hyperv 2012 OS
Summary: [hyper-v] [panic] Stable GENERIC kernel panic on hyperv 2012 OS
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-virtualization (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-20 08:00 UTC by Alexander
Modified: 2019-01-22 20:21 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander 2014-02-20 08:00:00 UTC 
On virtual box the same actions works.
On hyper-v 2012 OS these action leads to kernel panic.

I can't paste a text from vurtual machine, but i can provide screenshots, but not here, as i see there's no such ability. So ask me and i send it to email.

The similar errors, as i see, we can see here:
http://lists.freebsd.org/pipermail/freebsd-virtualization/2013-October/001679.html
and here
http://comments.gmane.org/gmane.os.freebsd.devel.virtualization/1335

Fix: 

Exclude fron kernel config next string:
device          hyperv          # HyperV drivers 
but i don't think it is a fix.
How-To-Repeat: Download the 10.0 release
pkg install subversion
svn checkout http://svn.freebsd.org/base/stable/10/ /usr/src
cd /usr/src
make -j4 buildworld
make -j4 buildkernel KERNCONF=GENERIC
mergemaster -p
make installkernel KERNCONF=GENERIC
make installworld
mergemaster

reboot
Comment 1 sukhorukov 2014-02-20 08:20:10 UTC 
-- 

------------------------------------------------------------------------
*(A)dmin01*
*Sukhorukov Alexander*
*www.admin01.ru* <http://www.admin01.ru/>
*twitteradmn01 <https://twitter.com/admn01>*
*livejournal.comadmin01ru.livejournal.com 
<http://admin01ru.livejournal.com>*
*+7(495)730-77-78*
www.admin01.ru
------------------------------------------------------------------------
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2014-02-24 06:57:43 UTC 
State Changed
From-To: open->open

reclassify and assign.
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2014-02-24 06:57:43 UTC 
Responsible Changed
From-To: freebsd-bugs->freebsd-emulation
Comment 4 Mark Linimon freebsd_committer freebsd_triage 2014-04-20 02:48:45 UTC 
State Changed
From-To: open->open

cleaning up text of PR.
Comment 5 Mark Linimon freebsd_committer freebsd_triage 2014-04-20 02:48:45 UTC 
Responsible Changed
From-To: freebsd-emulation->freebsd-emulation
Comment 6 Dexuan Cui 2015-12-09 10:45:05 UTC 
I think the bug has been fixed by  https://svnweb.freebsd.org/base?view=revision&revision=262789 ?
Comment 7 Mark Linimon freebsd_committer freebsd_triage 2016-05-20 07:36:25 UTC 
Canonicalize assignment.
Comment 8 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:48:51 UTC 
batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.
Comment 9 Oleksandr Tymoshenko freebsd_committer freebsd_triage 2019-01-22 20:21:53 UTC 
Closing as fixed per Dexuan