[Bug 278448] Linux emulation not working same as bhyve instance
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 278448] Linux emulation not working same as bhyve instance"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 278448] Linux emulation not working same as bhyve instance"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 278448] Linux emulation not working same as bhyve instance"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 278448] Linux emulation not working same as bhyve instance"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 19 Apr 2024 03:43:23 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278448
Bug ID: 278448
Summary: Linux emulation not working same as bhyve instance
Product: Base System
Version: 14.0-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: bhyve
Assignee: virtualization@FreeBSD.org
Reporter: crb@ChrisBowman.com
I struggle to know where to correctly report this:
I filed this under bhyve but I think the bhyve is working correctly I think
Linux emulation isn't. I think I'm the only one using this tool this way but
anyone else trying would experience the same issue (I believe).
I am running the AMD/Xilinx Vivado 2032.2 tool chain on FreeBSD using Linux
emulation. For the most part things seem to work fine, sort of. I can run
vivado in tcl mode and in GUI mode. Some simple scripts work just fine. There
is one script I have that is a little (not much) more complex and it reliably
fails. I have a setup where I can run essentially the same vivado process on
both the same box using the same files under FreeBSD using the Linux emulation
and under a bhyve instance of Centos 7.9 running on that same box access the
same file. The Centos bhyve works as expected the Linux emulation behaves
differently. This is completely 100% reproducible. I couldn't tell you what's
going on under the hood and have no idea why it behaves differently. I can
provide the complete small project along with scripts and everything. I might
even be able to provide access to the box on which all this happens. I'd be
happy to try to debug this but haven't a clue where to start.
--
You are receiving this mail because:
You are the assignee for the bug.