[Bug 268736] FreeBSD boot stuck with comconsole in x86 Hyper-V Gen2
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 268736] FreeBSD boot stuck with comconsole in x86 Hyper-V Gen2"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 268736] FreeBSD boot stuck with comconsole in x86 Hyper-V Gen2"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 268736] FreeBSD boot stuck with comconsole in x86 Hyper-V Gen2"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 03 Jan 2023 18:47:08 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268736 Bug ID: 268736 Summary: FreeBSD boot stuck with comconsole in x86 Hyper-V Gen2 Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: schakrabarti@microsoft.com When booting current FreeBSD on Hyper-V x86 gen2 VM, if we set console="comconsole", then boot is getting stuck. boot -v Loading kernel... /boot/kernel/kernel text=0x18b088 text=0xe1ece8 text=0x6bfa3c data=0x140 data=0x1c9b60+0x4354a0 0x8+0x199f08+0x8+0x1ba8e1| Loading configured modules... can't find '/boot/entropy' can't find '/etc/hostid' staging 0xeec00000 (not copying) tramp 0xeeb64000 PT4 0xeeb5b000 Start @ 0xffffffff8038c000 ... EFI framebuffer information: addr, size 0xf8000000, 0x800000 dimensions 1024 x 768 stride 1024 masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000 GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb ---<<BOOT>>--- APIC: Using the MADT enumerator. No panic or call trace is seen. -- You are receiving this mail because: You are the assignee for the bug.