On Sat, 13 Aug 2022 at 14:32, Marc Zyngier wrote:
> But we probably need to handle EINTR when creating the mini VM.
It's easy enough to add a retry-on-EINTR loop to the KVM_CREATE_VM
ioctl in the target/arm/ code. But do we need to do that more
widely ? At the moment QEMU seems to assume that KVM
ailing lists to the cc.
> > >
> > > On Fri, 12 Aug 2022 at 09:45, Vitaly Chikunov wrote:
> > > > On Fri, Aug 12, 2022 at 05:14:27AM +0300, Vitaly Chikunov wrote:
> > > > > I noticed that we starting to get many errors like this:
> > > > >
> > On Fri, Aug 12, 2022 at 05:14:27AM +0300, Vitaly Chikunov wrote:
> > > > I noticed that we starting to get many errors like this:
> > > >
> > > > qemu-system-aarch64: Failed to retrieve host CPU features
> > > >
> > > > Where
t we starting to get many errors like this:
> > >
> > > qemu-system-aarch64: Failed to retrieve host CPU features
> > >
> > > Where many is 1-2% per run, depends on host, host is Kunpeng-920, and
> > > Linux kernel is v5.15.59, but it sta
noticed that we starting to get many errors like this:
> > >
> > > qemu-system-aarch64: Failed to retrieve host CPU features
> > >
> > > Where many is 1-2% per run, depends on host, host is Kunpeng-920, and
> > > Linux kernel is v5.15.59, but it sta
I've added some more relevant mailing lists to the cc.
On Fri, 12 Aug 2022 at 09:45, Vitaly Chikunov wrote:
> On Fri, Aug 12, 2022 at 05:14:27AM +0300, Vitaly Chikunov wrote:
> > I noticed that we starting to get many errors like this:
> >
> > qemu-system-aarch64: F
