On Wed, Apr 3, 2019, 8:35 AM Rebecca Cran via freebsd-virtualization <
freebsd-virtualization@freebsd.org wrote:
> I was wondering, has anyone done any work on supporting debugging UEFI
> code under Bhyve? If not, I can take a look at adapting DebugPkg
> (https://code.bluestop.org/w/tianocore/debu
On Sat, Mar 30, 2019, 4:14 PM Rodney W. Grimes <
freebsd-...@gndrsh.dnsmgr.net wrote:
> > On 3/29/19 9:29 PM, Rodney W. Grimes wrote:
> > >
> > > That, iirc, would be the SMBIOS version of ed2k, which yes should
> > > be updated if infact the newer ed2k has a new SBIOS implementation,
> > > if it
ebsd-virtualization-unsubscr...@freebsd.org"
>
This is a fantastic news!!!
I think after more tests done by the community, you should make a PR to
this repo: https://github.com/freebsd/uefi-edk2 and then I can update the
ports.
Well done job, thanks!
--
--
Marcelo Arauj
If you have Nvme devices or you want store disks in ram yes, otherwise no.
BR,
On Tue, Feb 12, 2019, 9:05 PM Victor Sudakov Jason Tubnor wrote:
> >
> > > What's that disk0_type="nvme" thing?
> > >
> > > I'm curious. In 11.2-RELEASE there is nothing about nvme in bhyve(8).
> > > Should I be runni
/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to "
> freebsd-virtualization-unsubscr...@freebsd.org"
>
--
--
Marcelo Araujo(__)ara...@freebsd.org
\\\'',)http://www.FreeBSD.org <http://www.freebsd.org/> \/ \
nderstood well your case, but have you tried to set this
sysctl: net.link.tap.up_on_open?
Best,
--
--
Marcelo Araujo(__)ara...@freebsd.org
\\\'',)http://www.FreeBSD.org <http://www.freebsd.org/> \/ \ ^
Power To Server. .\. /_)
___
fr
On Tue, Aug 28, 2018, 9:54 PM Rodney W. Grimes <
freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> > On Tue, Aug 28, 2018, 9:38 PM Rodney W. Grimes <
> > freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> >
> > > > >> Currently, bhyve does not expose any of these statistics. All the
> > > stats
> > > > > ava
On Tue, Aug 28, 2018, 9:38 PM Rodney W. Grimes <
freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> > >> Currently, bhyve does not expose any of these statistics. All the
> stats
> > > available through bhyvectl --get-stats seem to be coming from the VMM,
> > > not from the userspace emulation.
> >
> >
rt.org/html/libvirt-libvirt-domain.html#
> virDomainBlockStats
> ___
> freebsd-virtualization@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to "freeb
-virtualization
> To unsubscribe, send any mail to "freebsd-virtualization-unsubs
> cr...@freebsd.org"
>
--
--
Marcelo Araujo(__)ara...@freebsd.org
\\\'',)http://www.FreeBSD.org <http://www.freebsd.org/> \/ \ ^
Power To Server. .\. /_)
or is returned, recoding this in shell is just
> setting yourself up for "future" bugs.
>
> The kernel knows what features are supported but does not expose these, so
> all I can do is similar to libvirt and run bhyve with different options to
>
ebsd or multicore freebsd guests, and as you say
> missing from some early VT-x capable processors)?
>
> >I went and looked at why vm-bhyve is groveling around in
> /var/run/dmesg.boot and found that it is simply trying to determine if the
> host CPU is vmm capable,
> >specifi
not exist?
>
> I think the question vm-bhyve wants to answer is: does the CPU have the
> required features to run a multicore VM.
>
> These or similar sysctls do seem to be the correct way to communicate that
> support.
>
You are correct!
The question in case as I unde
uot;: "virtio-blk,path,nocache,
> direct,ro,sectorsize=logical/physical",
>"description": "Virtio block device"
> },
> {"options": "fbuf,rfb,rfb=IP:port,w=width,
> h=heigh
://borderworlds.dk/~xi/bhyve-get-all-vulcan.txt
>
> Any suggestions?
>
> Best regards
> Christian
>
> ___
> freebsd-virtualization@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To un
y mail to "freebsd-virtualization-
> unsubscr...@freebsd.org"
>
Hello Alexandru,
Excited to see your work!
I have Cc manu@ as I know he works a lot with embedded devices and probably
he can give you some suggestions.
I'm sure he is on freebsd-arm@ mailing list, but even though
rc/usr.sbin/bhyve/block_if.h
> ===
> --- usr.sbin/bhyve/block_if.h (Revision 325745)
> +++ usr.sbin/bhyve/block_if.h (Arbeitskopie)
> @@ -39,7 +39,7 @@
> #include
> #include
>
> -#define BLOCK
freebsd.org mailing list
> >> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> >> To unsubscribe, send any mail to "
> > freebsd-virtualization-unsubscr...@freebsd.org"
>
> ___
> freebsd-virtual
2018-03-16 9:55 GMT+08:00 Kyle Evans :
> On Thu, Mar 15, 2018 at 8:46 PM, Marcelo Araujo
> wrote:
> >
> >
> > 2018-03-16 7:07 GMT+08:00 Kyle Evans :
> >>
> >> On Thu, Mar 15, 2018 at 5:01 PM, Kyle Evans wrote:
> >> > On Thu, Mar 15, 2
e here, but the console stopped working after the kernel handoff.
>
> Thanks,
>
> Kyle Evans
> ___
> freebsd-virtualization@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, s
> > To unsubscribe, send any mail to "freebsd-virtualization-
> > unsubscr...@freebsd.org"
> >
> ___
> freebsd-virtualization@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To
ebsd-virtualization@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to "freebsd-virtualization-
> unsubscr...@freebsd.org"
>
As Allan said, it is likely to be your ARC cache holding memory and
unfortuna
> FreeBSD and FreeNAS to resolve the issue.
> >
> > > I could not find this information anywhere other than that FreeNAS is
> > based
> > > on FreeBSD.
> >
> > I think if you read the bug report carefully you should find the
> > following text excerpt:
&
; freebsd-virtualization@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to "freebsd-virtualization-unsubs
> cr...@freebsd.org"
>
--
--
Marcelo Araujo(__)ara...@freebsd.org
\\\&
24 matches
Mail list logo
