Re: [osv-dev] OSv page_fault assert during "bsd: initializing"?

And I was also able to replicate it on QEMU running OSv in PVH mode on microvm machine (similar to how firecracker runs it) again in nested virtualization. ./scripts/run.py -k -p qemu_microvm --nics=0 -c 1 I have used the same recipe - 3 terminals running similar commands to start C native ex

Re: [osv-dev] OSv page_fault assert during "bsd: initializing"?

I have installed VMWare Fusion Pro on my other Mac (OSX - 10.15.7, 2.3GHz, 8-core, i9) with Fedora 33 server in it, enabled the 2 settings to allow KVM in nested virtualization and I was able to replicate the crashes. So there is most likely something about nested virtualization that possibly t

[osv-dev] [PATCH V2] dynamic linker: properly handle STT_NOTYPE symbols

Some ELF files define global variables symbols with STT_NOTYPE like in this example: 13030: 0243b390 0 NOTYPE GLOBAL DEFAULT 13 v8_Default_embedded_blob_size_ 13136: 02d09db8 0 NOTYPE GLOBAL DEFAULT 24 v8_Default_embedded_blob_ Currently OSv dynamic linker will r

[osv-dev] [COMMIT osv master] aarch64: unmask clock event interrupt on secondary CPUs

From: Waldemar Kozaczuk Committer: Nadav Har'El Branch: master aarch64: unmask clock event interrupt on secondary CPUs As the issue #1132 explains, in order for the timer interrupts to "work", many dots need to be connected. Firstly, when the timer condition is met (CVAL <= global system count

Re: [osv-dev] [PATCH] dynamic linker: properly handle STT_NOTYPE symbols

On Wed, Apr 28, 2021 at 4:27 AM Waldemar Kozaczuk wrote: > Some ELF files define global variables symbols with STT_NOTYPE > like in this example: > > 13030: 0243b390 0 NOTYPE GLOBAL DEFAULT 13 > v8_Default_embedded_blob_size_ > 13136: 02d09db8 0 NOTYPE GLOBAL DEFAULT