[Bug 249427] Creating bHyve virtual machines cause network flaps intel
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249427 Michael Dexter changed: What|Removed |Added Resolution|--- |Works As Intended CC||edi...@callfortesting.org Status|New |Closed --- Comment #5 from Michael Dexter --- Solution provided: Disable hardware offloading. -- 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
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 developer, would say that the issue is not FIXED on AlmaLinux side. AlmaLinux just tried to revert the offending commit to AVOID the issue. It is not a FIX at all. There's no progress on the AlmaLinux side for a fundamental fix. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283375] dhclient refuses DHCP offer on FreeBSD 14.1-RELEASE as QEMU/KVM guest with virtio net
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283375 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=1650 ||59 -- 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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279901 Michael Dexter changed: What|Removed |Added CC||edi...@callfortesting.org --- Comment #31 from Michael Dexter --- This is reportedly fixed in Alma Linux. -- 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
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't). No root access or glibc update would be needed; the issue should reproduce with an uninstalled upstream rebuild of glibc. I'm not convinced if I will be able to reproduce it locally. -- 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
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 the assignee for the bug.
[Bug 227956] Add an init script in base for bhyve vm's
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227956 Michael Dexter changed: What|Removed |Added Resolution|--- |Not A Bug CC||edi...@callfortesting.org Status|New |Closed --- Comment #4 from Michael Dexter --- The underlying issue is that FreeBSD base does not offer process supervision beyond the limited daemon(8) command. This long-term issue is acknowledged and being addressed. See the Enterprise Working Group and Production User Calls for more information. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 282098] bhyve is eating my memory and running far beyond the configured limits
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282098 Michael Dexter changed: What|Removed |Added CC||edi...@callfortesting.org --- Comment #4 from Michael Dexter --- Please watch your ARC when the issue occurs. TrueNAS does little more than warn against possible memory exhaustion when using the the VM feature. -- 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
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
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_features.shared_cache_size=0x10 x86.cpu_features.level1_icache_size=0x8000 x86.cpu_features.level1_icache_linesize=0x40 x86.cpu_features.level1_dcache_size=0x8000 x86.cpu_features.level1_dcache_assoc=0x8 x86.cpu_features.level1_dcache_linesize=0x40 x86.cpu_features.level2_cache_size=0x8 x86.cpu_features.level2_cache_assoc=0x8 x86.cpu_features.level2_cache_linesize=0x40 x86.cpu_features.level3_cache_size=0x10 x86.cpu_features.level3_cache_assoc=0x0 x86.cpu_features.level3_cache_linesize=0x40 x86.cpu_features.level4_cache_size=0x0 x86.cpu_features.cachesize_non_temporal_divisor=0x4 -- 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
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
that triggers this is that it reports 1 TiB of L3 cache
(x86.cpu_features.level3_cache_size=0x100 in the diagnostic output).
This triggers an integer truncation in glibc's cache size computation.
Misreporting cache information like this typically impacts performance, so it
should be fixed independently of the glibc bug.
The glibc bug is below. I'll submit it upstream and we'll backport it.
diff --git a/sysdeps/x86/dl-cacheinfo.h b/sysdeps/x86/dl-cacheinfo.h
index e9579505..6a0a30ba 100644
--- a/sysdeps/x86/dl-cacheinfo.h
+++ b/sysdeps/x86/dl-cacheinfo.h
@@ -1021,11 +1021,11 @@ dl_init_cacheinfo (struct cpu_features *cpu_features)
non_temporal_threshold = maximum_non_temporal_threshold;
/* NB: The REP MOVSB threshold must be greater than VEC_SIZE * 8. */
- unsigned int minimum_rep_movsb_threshold;
+ unsigned long int minimum_rep_movsb_threshold;
/* NB: The default REP MOVSB threshold is 4096 * (VEC_SIZE / 16) for
VEC_SIZE == 64 or 32. For VEC_SIZE == 16, the default REP MOVSB
threshold is 2048 * (VEC_SIZE / 16). */
- unsigned int rep_movsb_threshold;
+ unsigned long int rep_movsb_threshold;
if (CPU_FEATURE_USABLE_P (cpu_features, AVX512F)
&& !CPU_FEATURE_PREFERRED_P (cpu_features, Prefer_No_AVX512))
{
With this fix, the testsuite is very clean, only nptl/tst-mutex10 fails with a
test timeout. Cause is unclear. (The test does not actually use elision because
the system does not support RTM.)
--
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
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 3): diff --git a/sys/amd64/vmm/x86.c b/sys/amd64/vmm/x86.c index a833b61786e7..8474666b5e6f 100644 --- a/sys/amd64/vmm/x86.c +++ b/sys/amd64/vmm/x86.c @@ -256,7 +256,7 @@ x86_emulate_cpuid(struct vcpu *vcpu, uint64_t *rax, uint64_t *rbx, func = 3; /* unified cache */ break; default: - logical_cpus = 0; + logical_cpus = sockets * threads * cores; level = 0; func = 0; break; -- You are receiving this mail because: You are the assignee for the bug.
