Keyon Jie

2 years passed, looks we have to carry this manually with ourselves.

> sn't use VMs (it uses container no Thanks for sharing @rosera . I am going to try what you have shared. Can you share more details about your environment?...

@rosera it fails at my chromebook (Debian 11): $ minikube start --driver=kvm2 😄 minikube v1.26.1 on Debian 11.4 (amd64) ✨ Using the kvm2 driver based on existing profile 👍 Starting...

oh, it works after changing the /etc/libvirt/qemu.conf and rebooting the chrome book! Thanks @cbandy ! add these lines: user = "root" group = "root" remember_owner = 0

I am seeing the same issue. The logs show that we are lack of OVERLAY_FS and BRIDGE_NETFILTER support. Similar issue for minikube here: https://github.com/kubernetes/minikube/issues/6411

> Why is this issue not caught initially? please share a model to check on our side. Hi @rkazants , the issue was not caught, as no matter with tf.keras.activations.gelu...

@plbossart it looks to be even larger than 0x10000 from the programming reference, e.g. the SDW IP registers are located in 0x30000~0x6FFFF. From the result, I guess accessing to some...

@plbossart Yes I have the same feeling. Previously I observed that we get all 0xffffffffs if the registers are not readable, but not sure if reading without ownership hold will...

@plbossart the issue is still there, maybe this can be covered by security check? @libinyang @RanderWang FYI.

@lgirdwood since the whole OS is panic when this happen, so you can't see any log anymore, hardware reboot is only thing you can do. @plbossart will be really appreciate...