Problem reports for virtualization@FreeBSD.org that need special attention

2022-01-16 Thread bugzilla-noreply
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

Re: Using bhyve to develop and OS -- tips on how?

2022-01-16 Thread Mehmet Erol Sanliturk
On Sun, Jan 16, 2022 at 8:59 PM Aryeh Friedman wrote: > It was/is off topic to discuss the motivations on the design I have in > mind but after thinking for it over 10 years (and using FreeBSD to build a > IaaS around bhyve) I have come to the conclusion that *NO* existing OS can > meet the desig

Re: Using bhyve to develop and OS -- tips on how?

2022-01-16 Thread Aryeh Friedman
It was/is off topic to discuss the motivations on the design I have in mind but after thinking for it over 10 years (and using FreeBSD to build a IaaS around bhyve) I have come to the conclusion that *NO* existing OS can meet the design requirements I have in mind. On Sun, Jan 16, 2022 at 11:13 AM

Re: Using bhyve to develop and OS -- tips on how?

2022-01-16 Thread Mehmet Erol Sanliturk
On Sat, Jan 15, 2022 at 1:54 PM Bakul Shah wrote: > You may be better off using qemu, at least initially as “legacy” booting > requires jumping through a few more hoops. Another suggestion is to check > out wiki.osdev.org. There are a lot of useful resources on this site. > > On Jan 15, 2022, at

[Bug 261198] bhyve host panics with: spin lock 0xffffffff81eac800 (callout) helpanic: spin lock held too long

2022-01-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261198 --- Comment #4 from Tom Jones --- Yeah can do, but not until wednesday the com cable I have was 2mm and the headers on the motherboard are 2.54mm. -- You are receiving this mail because: You are the assignee for the bug.