Hello,
I do not know whose it is a problem - DragonFlyBSD vtnet(4) driver or FreeBSD
bhyve(4), so I decided to send on both maillist.
I've try to boot DragonFlyBSD 4.4 in bhyve. All goes well, however, there is
no network interface. During boot i see:
--
virtio_pci0: port 0x2000-0x201f mem
Hello,
Some time ago I announced a new project called the ClonOS[1].
At the moment the functinal for working with bhyve(8) and jail(8) stabilized,
so I invite to testing this anyone who is interested in such project.
Formally, this is the WEB interface for CBSD[2] (jail and bhyve management
Hello. NetBSD works fine in bhyve, except for the case when the bhyve
emulates eXtensible Host Controller Interface (xHCI) USB controller. (
-s 30,xhci,tablet )
Perhaps SIGSEGV of bhyve is caused by the abnormal behavior of xhci on
the NetBSD guest, so I decided to write both mailing lists.
LLDB
Hi,
most likely r344398[1] commit breaks bhyve with the following errors:
Subtable Type : 02
Error6302 - Flag value is too large ^ (Maximum 1 bit)
58: [0002] Flags (decoded below) : 0005
Error6302 - Flag value is too large ^ (Maximum 2 bit)
66:
On Thu, Feb 21, 2019 at 8:15 PM Conrad Meyer wrote:
> Would you mind filing a PR to track this investigation?
Done: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235922
Thanks!
___
freebsd-virtualization@freebsd.org mailing list
On Tue, Jul 2, 2019 at 3:00 PM
wrote:
> Message: 1
> Date: Tue, 2 Jul 2019 00:52:04 -0600
> From: The Doctor
> To: freebsd-virtualization@freebsd.org
> Subject: Debian 10, Current Kali and Current Parrot
> Message-ID: <20190702065204.ga63...@doctor.nl2k.ab.ca>
> Content-Type: text/plain;
On Thu, Apr 1, 2021 at 10:27 AM Ka Ho Ng wrote:
> On 4/1/21 3:21 pm, Oleg Ginzburg wrote:
> > However, the bhyve process is crashed:
> >
> > ..
> > fbuf frame buffer base: 0x84460 [sz 16777216]
> > pci_xhci no USB devices configured
> > ld-elf.
Hi,
Over the past two weeks some changes appeared, which lead to a panic while
trying to load the VMM kernel module.
Kernel and revision with which everything was fine:
FreeBSD 14.0-CURRENT #0 main-n245511-a771bf748f9: Thu Mar 18 06:35:21 UTC
2021
Latest builds get panic: