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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271134
--- Comment #8 from Chris Moerz ---
Related to this topic, there's now a review for improving the bhyve man page
further:
https://reviews.freebsd.org/D43940
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258755
Michal Vanco changed:
What|Removed |Added
Version|13.0-RELEASE|13.2-RELEASE
--- Comment #4 from Mi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258755
--- Comment #5 from Michal Vanco ---
This issue is still present in 13.2-RELEASE-p10. Is really nobody interested in
solving this?
--
You are receiving this mail because:
You are the assignee for the bug.
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277326
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|virtualization@FreeBSD.org
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277326
--- Comment #4 from Zhenlei Huang ---
(In reply to Roger Pau Monné from comment #3)
> Hm, I guess I'm a bit confused.
While debugging PR 274810, I see the behavior, that FreeBSD guests report
HyperV rather than KVM when Hyper-V enlightenmen
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277326
--- Comment #5 from Zhenlei Huang ---
(In reply to Zhenlei Huang from comment #4)
> I see lots of comparing of vm_guest in hyperv device drivers. I guess they
> should be removed to correctly probe Hyper-V devices, to correctly support
>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277326
Miroslav Lachman <000.f...@quip.cz> changed:
What|Removed |Added
CC||000.f...@quip.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277326
--- Comment #7 from Roger Pau Monné ---
(In reply to Miroslav Lachman from comment #6)
That's the same on Xen, the first CPUID signature is the HyperV one, but the
following one is the Xen one, and we want to use the Xen one, as the Viridia
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276524
--- Comment #18 from Alexander Motin ---
Format Device mode page reports physical sector size, not physical block size.
That concept is used for bad block marking/relocation and appeared very early
in SCSI specs, long before logical blocks
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276524
--- Comment #19 from Alexander Motin ---
Thinking more, those physical sectors should somehow fit into disk CHS
geometry, based on logical sectors, and I don't want to get even close to that
legacy disaster. I think I'll just remove it all
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276524
--- Comment #20 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=7c667affb7b09fcdcb81f6f2635e9dfab7bc1fa8
commit 7c667affb7b09fcdcb81f6f2635e9dfab7bc1fa8
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276524
Alexander Motin changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237636
Morgan Davis changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264253
Mark Peek changed:
What|Removed |Added
CC||m...@freebsd.org
--- Comment #6 from M
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277530
Bug ID: 277530
Summary: vmm(4) manpage doesn't emphasize importance of early
loading
Product: Base System
Version: 15.0-CURRENT
Hardware: amd64
OS: An
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277530
Mateusz Piotrowski <0...@freebsd.org> changed:
What|Removed |Added
Status|New |Open
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277559
Mark Linimon changed:
What|Removed |Added
Keywords||crash
Assignee|b...@freeb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277559
Peter Grehan changed:
What|Removed |Added
CC||gre...@freebsd.org
--- Comment #1 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277559
--- Comment #2 from John F. Carr ---
Loading vmm sometimes hangs on either type of CPU. Hangs appear to be more
likely on the low numbered A53 CPUs.
The bits are the same whichever CPU is in charge, tcr_el2=80823510 and
vtcr_el2=80023559.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277559
--- Comment #3 from Peter Grehan ---
Thanks for giving that a try: rules out that theory.
--
You are receiving this mail because:
You are the assignee for the bug.
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277627
Bug ID: 277627
Summary: Passthru NVIDIA GeForce GTX 1080 Ti not work
Product: Base System
Version: 13.3-RELEASE
Hardware: amd64
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277627
Konstantin changed:
What|Removed |Added
Severity|Affects Only Me |Affects Some People
--
You are recei
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277627
mario felicioni changed:
What|Removed |Added
CC||marietto2...@gmail.com
--- Comme
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277627
--- Comment #2 from mario felicioni ---
ohhh I Forgot,you should create,inside Linux,a xorg.conf file with this content
:
Section "Device"
Identifier "Card0"
Driver "nvidia"
BusID "PCI:8:0:0"
EndSection
i
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277627
--- Comment #3 from Konstantin ---
it doesn't work.
And I don't understand why to install drivers in the mother OS, the device is
not used in it.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277627
Konstantin changed:
What|Removed |Added
Summary|Passthru NVIDIA GeForce GTX |Passthru NVIDIA GeForce GTX
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277627
--- Comment #4 from mario felicioni ---
Lets create these script files :
1) build_branch_releng-140 :
set -e
set -u
readonly script_path="$(cd "$(dirname "${0}")" && pwd)"
readonly branch="${1?Missing $(usage)}"
shift
echo $branch
cd /u
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277627
--- Comment #5 from Konstantin ---
Thank you very much.
It works. And the last question. Why is this patch missing in the release?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277627
Konstantin changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264253
--- Comment #7 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=63a7c4be4ad524629292eee659d6542f1c5e9c21
commit 63a7c4be4ad524629292eee659d6542f1c5e9c21
Author:
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
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278058
Bug ID: 278058
Summary: Simultaneous use of Bhyve AND vnet on network PCI
devices causes network failure
Product: Base System
Version: 14.0-RELEASE
Hardware: amd64
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264253
--- Comment #8 from commit-h...@freebsd.org ---
A commit in branch stable/14 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=a1f89082dcb591886acc22c5503a2d5a82b267d9
commit a1f89082dcb591886acc22c5503a2d5a82b267d9
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264253
--- Comment #9 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=a26e93052a3897bb55301954dff7e40547d7f291
commit a26e93052a3897bb55301954dff7e40547d7f291
Author:
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278058
Mark Linimon changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273372
Mark Linimon changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278121
Marek Zarychta changed:
What|Removed |Added
CC||virtualization@FreeBSD.org
--
Yo
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264253
Mark Peek changed:
What|Removed |Added
Status|Open|Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278245
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|virtualization@FreeBSD.org
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278289
Bug ID: 278289
Summary: nvme_opc_delete_io_sq NOT PERMITTED queue id 0
Product: Base System
Version: 14.0-RELEASE
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277559
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
Stat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271134
Jason Mann changed:
What|Removed |Added
CC||jason.m...@gmail.com
--- Comment #9 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277559
--- Comment #5 from John F. Carr ---
I moved the set of vbar_el2 after the set of vtcr_el2. The problem is not
fixed but it is much better. I was able to load and unload the vmm module
about 270 times before the system hung.
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277559
--- Comment #6 from John F. Carr ---
I noticed that the instruction cache types are different for the two processor
types. A-53 is virtually indexed and A-72 is physically indexed.
Cache Type = <64 byte D-cacheline,64 byte I-cacheline,VIP
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277559
--- Comment #7 from John F. Carr ---
Moving the set of vbar_el2 was not the cause of improvement. I just saw two
runs of over 2,000 successful kldloads before a hang without it. I also saw
the system hang on the first load last night.
I
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278318
Bug ID: 278318
Summary: bhyve fails to boot OpenBSD unless -w is specified
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
S
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278338
Bug ID: 278338
Summary: bhyve deletes tap LINK0 flag (regression)
Product: Base System
Version: 13.3-RELEASE
Hardware: amd64
OS: Any
Status: New
Sev
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277559
John F. Carr changed:
What|Removed |Added
Severity|Affects Only Me |Affects Some People
--
You are rec
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278289
Chuck Tuffli changed:
What|Removed |Added
CC||ch...@freebsd.org
Statu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277559
--- Comment #8 from Andrew Turner ---
It looks like the issue is due to the tlbi in handle_hyp_init having
insufficient barriers around it.
I have a fix I'm testing that seems to fix the issue.
--
You are receiving this mail because:
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277559
Andrew Turner changed:
What|Removed |Added
URL||https://reviews.freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277559
--- Comment #9 from John F. Carr ---
The change in review D44799 fixes the problem for me – about 780,000
kldload/kldunload pairs without a hang on the RockPro64. (I got distracted and
let the loop run for a couple hours.)
--
You are rec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278338
cr...@rlwinm.de changed:
What|Removed |Added
CC||cr...@rlwinm.de
--- Comment #1 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278338
--- Comment #2 from Peter Much ---
(In reply to crest from comment #1)
crest, thank You for explaining the rationale behind this. So this is rather a
/cultural/ change, then.
I.)
Yes, it is expected that the tap goes down on closing. And
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277559
--- Comment #10 from John F. Carr ---
There is still a problem, but less common. One out of five reboots with the
patch the RockPro64 hung the first time I ran kldload. The ssh session was
responsive for a few seconds:
# kldload vmm
load
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278392
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|virtualization@FreeBSD.org
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278449
Bug ID: 278449
Summary: Linux emulation not working same as bhyve instance
Product: Base System
Version: 14.0-RELEASE
Hardware: amd64
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278448
--- Comment #1 from Li-Wen Hsu ---
*** Bug 278449 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278449
Li-Wen Hsu changed:
What|Removed |Added
Resolution|--- |DUPLICATE
CC|
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278448
p...@nomadlogic.org changed:
What|Removed |Added
CC||p...@nomadlogic.org
--- Comme
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278448
--- Comment #3 from crb ---
I've used a read_verilog/add_files/import_files (I've tried them all) to read
in a file. Vivado, in the GUI (there is no error from the tcl shel) lists
these as non-module files. And when I try to instanciate o
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278448
--- Comment #4 from crb ---
Created attachment 250159
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=250159&action=edit
picture of vivado running
This shows the files read in as non modules files
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278535
Bug ID: 278535
Summary: bhyve: occasional long delays during boot
Product: Base System
Version: 15.0-CURRENT
Hardware: Any
OS: Any
Status: New
Sever
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278535
John F. Carr changed:
What|Removed |Added
CC||j...@mit.edu
--- Comment #1 from Jo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277559
--- Comment #11 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=ef80df0a71912500ad84060334a24e903869f00b
commit ef80df0a71912500ad84060334a24e903869f00b
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265444
Mark Felder changed:
What|Removed |Added
CC||f...@freebsd.org
--- Comment #3 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270966
depeo changed:
What|Removed |Added
CC||dan...@flygpost.com
--- Comment #22 from d
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271134
Bug 271134 depends on bug 266336, which changed state.
Bug 266336 Summary: Angle brackets < and > misrepresented as underscore
characters in online manual pages
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266336
What|R
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278058
--- Comment #1 from Mark McBride ---
I listened the the bhyve production user call [1] and noticed people still
speculating that bhyve+vnet SR-IOV issues might be PCI card specific. To
clarify, I can reproduce this issue 100% of the time on
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277326
er...@microsoft.com changed:
What|Removed |Added
CC||er...@microsoft.com
--- Comme
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277326
--- Comment #9 from Roger Pau Monné ---
(In reply to ernis from comment #8)
I'm not doing any work on this because I think there's nothing to be fixed.
If FreeBSD runs on QEMU, and QEMU exposes part of the Viridian extensions, the
primary
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278892
Li-Wen Hsu changed:
What|Removed |Added
Component|Individual Port(s) |bhyve
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278892
--- Comment #1 from mario felicioni ---
The error that I have shown happens in FreeBSD 13 and 14,maybe even 12. It
never worked. Anyway,I'm using FreeBSD 14.0-RELEASE-p6.
The next step is to explain on the nvidia forums the situation that
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278941
Bug ID: 278941
Summary: Virtual machine with Debian 12 guest gets stuck after
S3 mode
Product: Base System
Version: 14.0-RELEASE
Hardware: amd64
OS: A
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278941
mario felicioni changed:
What|Removed |Added
CC||marietto2...@gmail.com
--- Comme
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278941
--- Comment #2 from Vurefozu ---
I created a specially new virtual machine, installed clean Debian 12 from
scratch with the iso image "debian-12.5.0-amd64-netinst.iso".
The problem is reproducible.
Just for fun, try installing pure Debian
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278941
--- Comment #3 from mario felicioni ---
zip and share the debian img file that has the problem. I want to check if I
have it also. I need to exclude that it belongs to your specific image and / or
to bhyve.
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278941
--- Comment #4 from mario felicioni ---
or maybe to the wrapper,that I don't use.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278941
--- Comment #5 from Vurefozu ---
I indicated a link in the message - https://disk.yandex.ru/d/Lp31Io92aFtDhA
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278941
--- Comment #6 from mario felicioni ---
I tried to boot your image with my bhyve parameters :
bhyve -S -c sockets=2,cores=2,threads=2 -m 4G -w -H -A \
-s 0,hostbridge \
-s 1,ahci-hd,/bhyve/debian12-test1/disk0.img,bootindex=1 \
-s 13,virti
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278941
--- Comment #7 from Vurefozu ---
Loader: grub
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278941
--- Comment #8 from mario felicioni ---
Can you try recreating your vm using UEFI ? We are trying to change something
to see what happens.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278941
--- Comment #9 from Vurefozu ---
definitely not UEFI. It turns out BIOS.
login password root/root
Here is the virtual machine launch log:
мая 14 09:06:27: initialising
мая 14 09:06:27: [loader: grub]
мая 14 09:06:27: [cpu: 1]
мая 14 09:0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278941
--- Comment #10 from Vurefozu ---
I see from the logs that the launch occurs through the program
/usr/local/sbin/grub-bhyve
This application is from the "grub2-bhyve" package.
--
You are receiving this mail because:
You are the assignee f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278941
--- Comment #11 from mario felicioni ---
You are using vm-bhyve and booting the vm using the legacy BIOS. I want to
exclude these parameters. In the past I saw that some obscure problems can
arise using them. So,recreate the problematic vm
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278941
--- Comment #12 from mario felicioni ---
Probably you don't even need to recreate the vm. Try to apply the workaround
only inside the vm.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278941
--- Comment #13 from Vurefozu ---
I made a new installation in a UEFI virtual machine, the problem is reproduced.
dik0.img - https://disk.yandex.ru/d/IReY9xa7Kq7hfw
I ran it like this:
bhyve -S -c sockets=1,cores=1,threads=1 -m 1G -w -H -A
1 - 100 of 1873 matches
Mail list logo
