bonzini

7 ms·

61.
by bonzini 3mo ago
That's not supposed to happen. I would like to have more info.
62.
by bonzini 3mo ago
Wikipedia does have a rule allowing "routine calculations" https://en.wikipedia.org/wiki/Wikipedia:No_original_research... Of course given the magnitude of the statement a bit of care is warranted, but the ru
63.
by bonzini 3mo ago
What is the manufacturing tooling that you mention?
64.
by bonzini 3mo ago
True, but adding the hollow tube to the bottom side greatly improved how much the bricks stuck together, compared to Kiddicraft. It's not a small change. Lego also tried other designs like crosses on the bottom but then kept the tube (
65.
by bonzini 3mo ago
It doesn't have a carry flag either. Multiprecision integer operations absolutely suck in RISC-V, you need three operations (SLT and two adds, with an awful dependency chain too) to do an add with carry, and op fusion can only do so mu
66.
by bonzini 3mo ago
Indeed, it's hard to find a balance between what's too verbose and what's too hard. For relatively complex models it's also almost impossible to do "quality control" without actually building it. However, I agr
67.
by bonzini 3mo ago
AI is good at coding if there's an oracle. If the system is ancient, unreadable, untestable, that's exactly the opposite. It won't get the exact set of corner cases.
68.
by bonzini 3mo ago
It depends on how much the code has changed, how easy it is to test old releases, how far back you need to merge the fix... "Cherry picking from the top of tree" is the most common workflow but git itself uses "merge the sam
69.
by bonzini 3mo ago
I interpreted "I squashed them" as "I used git rebase -i to squash the oopses and fixes". If that's not what the user does, and rather squashes the PRs, then indeed I would be disagreeing with him.
70.
by bonzini 3mo ago
The why for a commit belongs in the message or code comments not in the history.
71.
by bonzini 3mo ago
Nope. Perfectly curating history is indeed the opposite of squashing—you squash because you couldn't be bothered to curate your commits. Squashing is a workaround not an alternative solution.
72.
by bonzini 3mo ago
So you're "spending effort in perfectly curating git history" and agreeing with your parent comment.
73.
by bonzini 3mo ago
You can develop with failing tests and reorder them after the code change before publishing your branch.
74.
by bonzini 3mo ago
That's not possible, because files don't have ancestors in git. Each commit's tree is tracked independently and copy/move is just something that's detected via heuristics.
75.
by bonzini 3mo ago
I am not sure how lockdowns (millions of people not able to work) could be driven by profits.
76.
by bonzini 3mo ago
There are two ways to run the Libvirt daemon, which are unprivileged and privileged aka system. You are using unprivileged mode, the parent is using system mode which is more powerful and provides better isolation but does hide stuff in &#x
77.
by bonzini 3mo ago
Red Hat is still using and developing libvirt (though the user facing layer is Kubevirt instead of oVirt) and virt-install, and even though virt-manager is not growing new features libvirt takes backwards compatibility extremely seriously,
78.
by bonzini 3mo ago
Much less if you consider buy vs build+maintain.
79.
by bonzini 3mo ago
Point taken, I didn't go as far as scrolling comments and only checked the user page. Apologies to dataviz1000.
80.
by bonzini 3mo ago
Maybe, or maybe there is no yacht and no 2 star restaurant. Since your profile doesn't have any personal info (which is certainly your right, mind) I have only one data point and it tilts towards the latter.
81.
by bonzini 3mo ago
It's spelled osso buco though.
82.
by bonzini 3mo ago
On POWER, LPARs and the first level of hypervisor do not use any LPAR-specific nesting support in the processor. It's all handled by the firmware, not the hardware.
83.
by bonzini 3mo ago
If you're a cloud provider, it's all hands on deck. For everyone else it's dangerous enough to look seriously at getting an updated kernel or apply mitigations, especially since those are easy (disable nested virtualization,
84.
by bonzini 3mo ago
That's exactly the same as x86. Nested virtualization support is almost entirely in the hypervisor.
85.
by bonzini 3mo ago
No, even s390 needs shadow paging. Intel and AMD both have some small amount of acceleration of nested virtualization, respectively with shadow VMCS and virtualized VMLOAD/VMSAVE.
86.
by bonzini 3mo ago
KVM maintainer here, yes it is.
87.
by bonzini 3mo ago
Yes you can disable it via kernel module parameters kvm_intel.nested=0 or kvm_amd.nested=0.
88.
by bonzini 3mo ago
In that case you'd have to combine this vulnerability with a local privilege escalation to reach guest kernel mode. Also the vulnerability requires enabling nested virtualization on the VM.
89.
by bonzini 3mo ago
KVM maintainer here. For what it's worth, this is a variant of a vulnerability discovered via fuzzing last April, CVE-2026-46113.
90.
by bonzini 3mo ago
The initial definition of the meter would have been such that g=pi^2. It was then adjusted but enough for it to remain an interesting (if not too good) approximation.

More ›