Date: Tue, 16 Jul 2024 08:16:47 -0700 From: Bakul Shah <bakul@iitbombay.org> To: Polarian <polarian@polarian.dev> Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@FreeBSD.org> Subject: Re: nmdm issues with bhyve Message-ID: <2137018B-1F61-423F-B17A-6EF8CC60314F@iitbombay.org> In-Reply-To: <20240716153851.60c1ea61@PolarianBSD> References: <20240716153851.60c1ea61@PolarianBSD>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jul 16, 2024, at 7:38=E2=80=AFAM, Polarian <polarian@polarian.dev> = wrote: >=20 > -s 31,lpc -l com1,/dev/nmdm3A \ I use the B device here, as in /dev/nmdm3B > ls /dev | grep nmdm >=20 > The above returns nothing, there is no nmdm device. I have tested it = to > ensure nmdm is in fact working, using cu to open both A and B and > verifying that the data is being passes between them. So nmdm is > working! They seem to get generated on demand. e.g if you do cu -l /dev/nmdm3A Both A and B devices will get generated.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2137018B-1F61-423F-B17A-6EF8CC60314F>