[Bug 249427] Creating bHyve virtual machines cause network flaps intel

2024-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249427 Michael Dexter changed: What|Removed |Added Resolution|--- |Works As Intended

[Bug 279901] glibc-2.39-2 and above on the host segfault

2024-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279901 --- Comment #34 from Koichiro Iwao --- (In reply to Konstantin Belousov from comment #32) > This is reportedly fixed in Alma Linux. I don't get exactly Michael Dexter meant but this is a misunderstanding. I, with a hat of AlmaLinux develop

[Bug 283375] dhclient refuses DHCP offer on FreeBSD 14.1-RELEASE as QEMU/KVM guest with virtio net

2024-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283375 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org See Also|

[Bug 279901] glibc-2.39-2 and above on the host segfault

2024-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279901 Michael Dexter changed: What|Removed |Added CC||edi...@callfortesting.org --- Com

[Bug 279901] glibc-2.39-2 and above on the host segfault

2024-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279901 --- Comment #33 from Florian Weimer --- If someone can provide me SSH access to a guest system that exhibits the issue once glibc is updated, I can try to debug it (assuming that GDB/ptrace works on the guest, but I don't see why it wouldn'

[Bug 279901] glibc-2.39-2 and above on the host segfault

2024-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279901 --- Comment #35 from Koichiro Iwao --- (In reply to Florian Weimer from comment #33) I can provide you access to the system if you're IPv6 reachable. Could you email me the public SSH key? -- You are receiving this mail because: You are t

[Bug 227956] Add an init script in base for bhyve vm's

2024-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227956 Michael Dexter changed: What|Removed |Added Resolution|--- |Not A Bug CC|

[Bug 282098] bhyve is eating my memory and running far beyond the configured limits

2024-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282098 Michael Dexter changed: What|Removed |Added CC||edi...@callfortesting.org --- Com

[Bug 279901] glibc-2.39-2 and above on the host segfault

2024-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279901 --- Comment #32 from Konstantin Belousov --- (In reply to Michael Dexter from comment #31) Can you provide any details on the supposed fix? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 279901] glibc-2.39-2 and above on the host segfault

2024-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279901 --- Comment #38 from Koichiro Iwao --- (In reply to Konstantin Belousov from comment #37) This didn't help. It still reports the same l3 cache size. $ ld.so --list-diagnostics |grep cache x86.cpu_features.data_cache_size=0x8000 x86.cpu_fea

[Bug 279901] glibc-2.39-2 and above on the host segfault

2024-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279901 --- Comment #36 from Florian Weimer --- Thanks for the offers of machine access. I should have studied the ld.so --list-diagnostics output. It's a recurrence of the previous rep_movsb_threshold bug because it ends up as zero. The bhyve bug

[Bug 279901] glibc-2.39-2 and above on the host segfault

2024-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279901 --- Comment #37 from Konstantin Belousov --- (In reply to Florian Weimer from comment #36) Do you see which CPUID leaf causes the trouble? As a guess, I wonder if the following bhyve patch helps (it tries to fix CPUID leaf 0x8000_001D %ecx