https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
Michael Gmelin changed:
What|Removed |Added
CC||gre...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256422
Chuck Tuffli changed:
What|Removed |Added
CC||ch...@freebsd.org
--- Comment #1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256422
--- Comment #2 from d...@syix.com ---
Installing guest again, using virtio-blk instead of nvme results in a working
client.
Same guest, just change nvme to ahci-hd, works.
Appears nvme support in UEFI bios has a change in the new RHEL
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256422
--- Comment #5 from Jason Tubnor ---
I successfully updated CentOS from 8.3 to 8.4 and it is running fine on a NVMe
bhyve device.
It is looking more like how the installer deals with determining the boot
device and then writing this and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256422
Jason Tubnor changed:
What|Removed |Added
CC||ja...@tubnor.net
--- Comment #4
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256498
Bug ID: 256498
Summary: [bhyve] Assertion failed: (!st->run), function
hda_stream_start, file
/usr/src/usr.sbin/bhyve/pci_hda.c, line 660.
Product: Base System
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256422
Peter Grehan changed:
What|Removed |Added
CC||gre...@freebsd.org
--- Comment #3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #55 from Tomoyuki Sakurai ---
on my 14-CURRENT, the patch works. i do not have sysctl tuning for aio in
/etc/sysctl.conf. I tried disabling AIO option in the port, but to no avail.
with the patch, guests OSes do not hang
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256422
--- Comment #7 from Peter Grehan ---
This looks to be an edge condition in the EFI NVMe driver, caused by the large
maximum data transfer size advertised by bhyve NVMe (2MB), and the increase in
size of grubx64.efi from 1.9MB in centos
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256422
--- Comment #8 from Jason Tubnor ---
I can confirm the patch from grehan@ works as described. Tested against:
CentOS 8.4
Windows Server 2022
OpenBSD 6.9
No regression was introduced into the latter two existing operating systems on
our
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256683
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|virtualization@FreeBSD.org
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|virtualization@FreeBSD.org
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256683
shamsher changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256422
--- Comment #9 from Chuck Tuffli ---
To document this a bit more, the error in pci_nvme.c is:
...
nvme doorbell 1, SQ, val 0x1
nvme_handle_io qid 1 head 0 tail 1 cmdlist 0x8c1885000
pci_nvme_io_done error 14 Bad address
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256422
--- Comment #10 from Chuck Tuffli ---
I think nvme_write_read_blockif() has a bug:
}
static void
@@ -1978,7 +1984,7 @@ nvme_write_read_blockif(struct pci_nvme_softc *sc,
/* PRP2 is pointer to a physical region page list
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256683
--- Comment #4 from Ed Maste ---
But I mean t17proc does not exist in FreeBSD, so this appears to be some
derivative or modified OS?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256683
--- Comment #5 from Ed Maste ---
Please attach a verbose boot log to this PR.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256422
--- Comment #13 from Chuck Tuffli ---
Actually, Peter's analysis helped me immediately zero in on the problem :)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256422
--- Comment #14 from Chuck Tuffli ---
Change up for review https://reviews.freebsd.org/D30897
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255571
--- Comment #2 from jcap...@blackberry.com ---
*** Bug 256696 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=252445
Gleb Popov changed:
What|Removed |Added
CC||arr...@freebsd.org
--- Comment #16
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256422
--- Comment #6 from Chuck Tuffli ---
Is it possible to recompile pci_nvme.c and enable debug in the failing case?
I.e. change the code to:
static int nvme_debug = 1;
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
Gordon Bergling changed:
What|Removed |Added
Status|New |In Progress
--- Comment #11
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256934
Artur Rojek changed:
What|Removed |Added
CC||a...@semihalf.com
--- Comment #2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256422
--- Comment #11 from Jason Tubnor ---
I reverted the grehan@ patch and applied chuck@ patch and tested against:
CentOS 8.4
Windows Server 2022
OpenBSD 6.9-snapshot
and all of the above installed, rebooted and booted correctly.
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256422
--- Comment #12 from Peter Grehan ---
Chuck's fix is the correct one; mine was just a bandaid.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250671
--- Comment #3 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=3f65cb8fda02c4f643c476f04655de843e31e563
commit 3f65cb8fda02c4f643c476f04655de843e31e563
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250671
Robert Wing changed:
What|Removed |Added
Resolution|--- |FIXED
Status|In
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256934
Mark Linimon changed:
What|Removed |Added
Keywords||panic, regression
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250671
--- Comment #4 from commit-h...@freebsd.org ---
A commit in branch stable/12 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=e63372af710790e6d583a0f1f7d0a3a6e55b5369
commit e63372af710790e6d583a0f1f7d0a3a6e55b5369
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #3 from Colin Percival ---
Exactly which instance type is this?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #18 from Colin Percival ---
Thanks for all the details. After some investigation, it looks like there's a
specific issue with TSC on T3/T3A instances which affects the clock
calibration.
In the long term we should switch over
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238068
Mark Linimon changed:
What|Removed |Added
CC||lini...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247489
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|virtualization@FreeBSD.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238068
--- Comment #4 from rai...@ultra-secure.de ---
Hi Mark,
it is relevant in that FreeBSD does not provide a cloud-ready image as of now.
Additionally, I've run into other problems running FreeBSD on top of KVM (which
are documented in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250516
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|virtualization@FreeBSD.org
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250516
rai...@ultra-secure.de changed:
What|Removed |Added
CC||rai...@ultra-secure.de
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254514
Jeffrey Gelens changed:
What|Removed |Added
CC||jeff...@gelens.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #4 from martin.stoya...@vertalo.com ---
Created attachment 226069
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=226069=edit
dmesg.boot
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #9 from Colin Percival ---
Hmm, very strange. I can't reproduce this.
Which EC2 region are you in? Have you tried other regions? It's possible that
AWS is rolling out a change which breaks things.
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #5 from martin.stoya...@vertalo.com ---
(In reply to Colin Percival from comment #3)
I get this behavior with t3 and t3a instances.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #6 from Colin Percival ---
It's possible that this is a problem with "stolen" CPU time.
Martin: Is the EC2 "CPU credit balance" positive on that instance?
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #7 from martin.stoya...@vertalo.com ---
Created attachment 226072
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=226072=edit
cpu utilization and credit balance graphs
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #14 from Colin Percival ---
Also, what does `sysctl kern.timecounter` say?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #8 from martin.stoya...@vertalo.com ---
(In reply to Colin Percival from comment #6)
Yes, it is positive, the instance isn't very loaded, and also the same thing
happens even if I just let it sit after it starts up. By the time
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #10 from martin.stoya...@vertalo.com ---
I am using the us-east-1 region.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #11 from Colin Percival ---
Ok, that's where I was testing too... have you tried all the different AZs?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #12 from martin.stoya...@vertalo.com ---
I think all my tests were in us-east-1a, I don't think I have tested other AZs
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #13 from Colin Percival ---
Can you try other AZs, and also tell me if running something CPU intensive
(say, 'dd if=/dev/random | sha256') changes how fast the clock runs?
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #15 from martin.stoya...@vertalo.com ---
Created attachment 226092
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=226092=edit
terraform testcase
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #17 from martin.stoya...@vertalo.com ---
(In reply to Colin Percival from comment #14)
ec2-user@freebsd:~ $ sysctl kern.timecounter
kern.timecounter.tsc_shift: 1
kern.timecounter.smp_tsc_adjust: 0
kern.timecounter.smp_tsc: 1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #16 from martin.stoya...@vertalo.com ---
(In reply to Colin Percival from comment #13)
I created a terraform file that launches an instance with this behavior in any
region (provided you update the region and the AMI). It seems
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250816
Michael Büker changed:
What|Removed |Added
CC||free...@michael-bueker.de
---
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256366
--- Comment #1 from Wei Hu ---
Code review available at
https://reviews.freebsd.org/D31150
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254514
Bjoern A. Zeeb changed:
What|Removed |Added
CC||b...@freebsd.org
--- Comment #4
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216493
com.my.network changed:
What|Removed |Added
CC||com.my.netw...@gmail.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256422
--- Comment #16 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=a7761d19dacd414c8b8269a6cf909ab4528783dc
commit a7761d19dacd414c8b8269a6cf909ab4528783dc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256422
--- Comment #17 from commit-h...@freebsd.org ---
A commit in branch stable/12 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=cd8a5d2316a12a8abca458c31467dc9dcf8361ce
commit cd8a5d2316a12a8abca458c31467dc9dcf8361ce
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256934
--- Comment #3 from Alex Dupre ---
(In reply to Artur Rojek from comment #2)
The machine had plenty of CPU credits when it happened, that possibility can be
discarded.
Until now, this was the only occurrence, but it happened after 15
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
Gordon Bergling changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236922
--- Comment #73 from Jamie Landeg-Jones ---
Created attachment 226337
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=226337=edit
kenv output from both instances
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236922
Jamie Landeg-Jones changed:
What|Removed |Added
CC||ja...@catflap.org
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243531
Warner Losh changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256422
--- Comment #15 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=91064841d72b285a146a3f1c32cb447251e062ea
commit 91064841d72b285a146a3f1c32cb447251e062ea
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #21 from Roger Pau Monné ---
(In reply to Colin Percival from comment #20)
That sounds like a bug in their implementation? As the hypervisor should keep
the TSC of the virtual CPU synchronised across physical CPU movements.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #22 from Colin Percival ---
They're the people who told me that we should use pvclock instead. ;-)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #23 from Roger Pau Monné ---
(In reply to Colin Percival from comment #22)
Oh OK. Maybe they don't do the vCPU TSC adjustments in order to avoid some of
the overhead of vCPU scheduling. Not sure exactly what are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #20 from Colin Percival ---
(In reply to Roger Pau Monné from comment #19)
> So this system reports invariant TSC, but the TSCs are not synchronized
> across CPUs?
My understanding is that it's even worse than that: The TSC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
Roger Pau Monné changed:
What|Removed |Added
CC||roy...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #24 from martin.stoya...@vertalo.com ---
(In reply to Roger Pau Monné from comment #19)
That seems to help, although one has to edit /boot/loader.conf and reboot the
instance to apply it... Also my only test is just running
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257969
Mark Linimon changed:
What|Removed |Added
Assignee|ports-b...@freebsd.org |virtualization@FreeBSD.org
--
You
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257798
--- Comment #3 from mario felicioni ---
now my file /etc/sysctl.conf is like this :
net.link.tap.up_on_open=1
net.inet.ip.forwarding=1
my /etc/rc.conf is like this :
hostname="marietto"
keymap="it.kbd"
ifconfig_em0="DHCP"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257798
--- Comment #2 from mario felicioni ---
ok. I did it. it does not work. I have the same situation as before.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258007
Mark Linimon changed:
What|Removed |Added
Assignee|ports-b...@freebsd.org |virtualization@FreeBSD.org
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258007
--- Comment #3 from mario felicioni ---
I tried to boot Ubuntu with these arguments :
Code:
bhyve -S -c 4 -m 8G -w -H \
-s 0,hostbridge \
-s 1,virtio-blk,/mnt/da1p1/vms/os/ubuntu-budgie-gpu/ubuntu-2104-gpu.img
\
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258007
--- Comment #5 from mario felicioni ---
Here we go. I've installed FreeBSD instead of Linux with bhyve and I tried to
pass thru the rtx 2080 ti using this command :
Code:
bhyve -S -c 4 -m 8G -w -H \
-s 0,hostbridge \
-s
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258007
mario felicioni changed:
What|Removed |Added
Summary|bhyve Assertion failed: |FreeBSD and Linux guest os
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258007
--- Comment #4 from mario felicioni ---
lldb -c bhyve.core -- bhyve
(lldb) thread backtrace all
Program aborted due to an unhandled Error:
Error value was Success. (Note: Success values must still be checked prior to
being destroyed).
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258007
--- Comment #12 from mario felicioni ---
root@marietto:/home/marietto # pciconf -vlb
hostb0@pci0:0:0:0: class=0x06 rev=0x0d hdr=0x00 vendor=0x8086
device=0x3e30 subvendor=0x1458 subdevice=0x5000
vendor = 'Intel
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258007
--- Comment #9 from mario felicioni ---
this :
/boot/loader.conf
pptdevs="1/0/0 1/0/1 1/0/2 1/0/3"
bhyve -S -c 4 -m 11G -w -H \
-s 0,hostbridge \
-s 1,virtio-blk,/mnt/da1p1/vms/os/ubuntu-budgie-gpu/ubuntu-2104-gpu.img \
-s
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258007
--- Comment #10 from mario felicioni ---
[drm] Unable to create a private tmpfs mount, hugepage support will be
disabled(-19).
Failed to add WC MTRR for [0x4000-0x5fff]: -22; performance may suffer
[drm] Got stolen memory base 0x0,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258007
--- Comment #8 from mario felicioni ---
this is the error message I get if I try to install the nvidia proprietary
driver on the ubuntu guest without that I haven't been able to pass trhu the
card before :
https://ibb.co/XtKqZTk
as I've
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258007
--- Comment #7 from mario felicioni ---
How can I install the nvidia proprietary driver in the guest if the guest can't
recognize the presence of the nvidia graphic card ?
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258007
Peter Grehan changed:
What|Removed |Added
CC||gre...@freebsd.org
--- Comment #6
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256159
Aleks Michajlow changed:
What|Removed |Added
Resolution|--- |Not A Bug
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256159
--- Comment #10 from Aleks Michajlow ---
I enabled "memory protection" in the BIOS and it worked.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258007
mario felicioni changed:
What|Removed |Added
Summary|FreeBSD and Linux guest os |Assertion failed: (error ==
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258007
--- Comment #11 from mario felicioni ---
I have installed the nvidia driver and then I did :
Code:
bhyve -S -c 4 -m 11G -w -H \
-s 0,hostbridge \
-s 1,virtio-blk,/mnt/da1p1/vms/os/ubuntu-budgie-gpu/ubuntu-2104-gpu.img \
-s
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251046
Mark Johnston changed:
What|Removed |Added
Status|Open|In Progress
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251046
--- Comment #11 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=42375556e5b2e68746d999b43d124040b6affb91
commit 42375556e5b2e68746d999b43d124040b6affb91
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257798
mario felicioni changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257969
mario felicioni changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
1 - 100 of 3928 matches
Mail list logo
