Skip to contentSkip to conversation

qemu-system-aarch64: Failed to retrieve host CPU features

DISCUSSION Vitaly Chikunov 3 participants 8 messages Aug 12, 2022 – Aug 16, 2022 KVM arm64

lore
Share & tools
lore
#0 lore raw

Hi,

I 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 started to appear months before that.

strace shows in erroneous case:

1152244 ioctl(9, KVM_CREATE_VM, 0x30) = -1 EINTR (Interrupted system call)

And I see in target/arm/kvm.c:kvm_arm_create_scratch_host_vcpu:

    vmfd = ioctl(kvmfd, KVM_CREATE_VM, max_vm_pa_size);
    if (vmfd < 0) {
        goto err;
    }

Maybe it should restart ioctl on EINTR?

I don't see EINTR documented in ioctl(2) nor in Linux' Documentation/virt/kvm/api.rst for KVM_CREATE_VM, but for KVM_RUN it says "an unmasked signal is pending".

Thanks,

#1 lore raw
Quoted 20 lines · Vitaly Chikunov

Hi,

I 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 started to appear months before that.

strace shows in erroneous case:

1152244 ioctl(9, KVM_CREATE_VM, 0x30) = -1 EINTR (Interrupted system call)

And I see in target/arm/kvm.c:kvm_arm_create_scratch_host_vcpu:

    vmfd = ioctl(kvmfd, KVM_CREATE_VM, max_vm_pa_size);
    if (vmfd < 0) {
        goto err;
    }
Quoted 5 lines

Maybe it should restart ioctl on EINTR?

I don't see EINTR documented in ioctl(2) nor in Linux' Documentation/virt/kvm/api.rst for KVM_CREATE_VM, but for KVM_RUN it says "an unmasked signal is pending".

I am suggested that almost any blocking syscall could return EINTR, so I checked the strace log and it does not show evidence of arriving a signal, the log ends like this:

1152244 openat(AT_FDCWD, "/dev/kvm", O_RDWR|O_CLOEXEC) = 9
1152244 ioctl(9, KVM_CHECK_EXTENSION, KVM_CAP_ARM_VM_IPA_SIZE) = 48
1152244 ioctl(9, KVM_CREATE_VM, 0x30) = -1 EINTR (Interrupted system call)
1152244 close(9) = 0
1152244 newfstatat(2, "", {st_dev=makedev(0, 0xd), st_ino=57869925, st_mode=S_IFIFO|0600, st_nlink=1, st_uid=517, st_gid=517, st_blksize=4096, st_blocks=0, st_size=0, st_atime=1660268019 /* 2022-08-12T01:33:39.850436293+0000 */, st_atime_nsec=850436293, st_mtime=1660268019 /* 2022-08-12T01:33:39.850436293+0000 */, st_mtime_nsec=850436293, st_ctime=1660268019 /* 2022-08-12T01:33:39.850436293+0000 */, st_ctime_nsec=850436293}, AT_EMPTY_PATH) = 0 1152244 write(2, "qemu-system-aarch64: Failed to r"..., 58) = 58
1152244 exit_group(1) = ?
1152245 <... clock_nanosleep resumed> <unfinished ...>) = ?
1152245 +++ exited with 1 +++
1152244 +++ exited with 1 +++

Thanks,

Quoted 3 lines

Thanks,

#2 lore raw

I've added some more relevant mailing lists to the cc.

Quoted 29 lines · Vitaly Chikunov
Quoted 18 lines · Vitaly Chikunov

I 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 started to appear months before that.

strace shows in erroneous case:

1152244 ioctl(9, KVM_CREATE_VM, 0x30) = -1 EINTR (Interrupted system call)

And I see in target/arm/kvm.c:kvm_arm_create_scratch_host_vcpu:

    vmfd = ioctl(kvmfd, KVM_CREATE_VM, max_vm_pa_size);
    if (vmfd < 0) {
        goto err;
    }
Quoted 5 lines

Maybe it should restart ioctl on EINTR?

I don't see EINTR documented in ioctl(2) nor in Linux' Documentation/virt/kvm/api.rst for KVM_CREATE_VM, but for KVM_RUN it says "an unmasked signal is pending".

I am suggested that almost any blocking syscall could return EINTR, so I checked the strace log and it does not show evidence of arriving a signal, the log ends like this:

Quoted 10 lines

1152244 openat(AT_FDCWD, "/dev/kvm", O_RDWR|O_CLOEXEC) = 9
1152244 ioctl(9, KVM_CHECK_EXTENSION, KVM_CAP_ARM_VM_IPA_SIZE) = 48
1152244 ioctl(9, KVM_CREATE_VM, 0x30) = -1 EINTR (Interrupted system call)
1152244 close(9) = 0
1152244 newfstatat(2, "", {st_dev=makedev(0, 0xd), st_ino=57869925, st_mode=S_IFIFO|0600, st_nlink=1, st_uid=517, st_gid=517, st_blksize=4096, st_blocks=0, st_size=0, st_atime=1660268019 /* 2022-08-12T01:33:39.850436293+0000 */, st_atime_nsec=850436293, st_mtime=1660268019 /* 2022-08-12T01:33:39.850436293+0000 */, st_mtime_nsec=850436293, st_ctime=1660268019 /* 2022-08-12T01:33:39.850436293+0000 */, st_ctime_nsec=850436293}, AT_EMPTY_PATH) = 0 1152244 write(2, "qemu-system-aarch64: Failed to r"..., 58) = 58
1152244 exit_group(1) = ?
1152245 <... clock_nanosleep resumed> <unfinished ...>) = ?
1152245 +++ exited with 1 +++
1152244 +++ exited with 1 +++

KVM folks: should we expect that KVM_CREATE_VM might fail EINTR and need retrying?

(I suspect the answer is "yes", given we do this in the generic code in kvm-all.c.)

thanks
-- PMM
_______________________________________________
kvmarm mailing list
[email protected]
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

maintainer
#3 lore raw

Hi Peter,

Quoted 44 lines · Peter Maydell

I've added some more relevant mailing lists to the cc.

Quoted 29 lines · Vitaly Chikunov
Quoted 18 lines · Vitaly Chikunov

I 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 started to appear months before that.

strace shows in erroneous case:

1152244 ioctl(9, KVM_CREATE_VM, 0x30) = -1 EINTR (Interrupted system call)

And I see in target/arm/kvm.c:kvm_arm_create_scratch_host_vcpu:

    vmfd = ioctl(kvmfd, KVM_CREATE_VM, max_vm_pa_size);
    if (vmfd < 0) {
        goto err;
    }
Quoted 5 lines

Maybe it should restart ioctl on EINTR?

I don't see EINTR documented in ioctl(2) nor in Linux' Documentation/virt/kvm/api.rst for KVM_CREATE_VM, but for KVM_RUN it says "an unmasked signal is pending".

I am suggested that almost any blocking syscall could return EINTR, so I checked the strace log and it does not show evidence of arriving a signal, the log ends like this:

Quoted 10 lines

1152244 openat(AT_FDCWD, "/dev/kvm", O_RDWR|O_CLOEXEC) = 9
1152244 ioctl(9, KVM_CHECK_EXTENSION, KVM_CAP_ARM_VM_IPA_SIZE) = 48
1152244 ioctl(9, KVM_CREATE_VM, 0x30) = -1 EINTR (Interrupted system call)
1152244 close(9) = 0
1152244 newfstatat(2, "", {st_dev=makedev(0, 0xd), st_ino=57869925, st_mode=S_IFIFO|0600, st_nlink=1, st_uid=517, st_gid=517, st_blksize=4096, st_blocks=0, st_size=0, st_atime=1660268019 /* 2022-08-12T01:33:39.850436293+0000 */, st_atime_nsec=850436293, st_mtime=1660268019 /* 2022-08-12T01:33:39.850436293+0000 */, st_mtime_nsec=850436293, st_ctime=1660268019 /* 2022-08-12T01:33:39.850436293+0000 */, st_ctime_nsec=850436293}, AT_EMPTY_PATH) = 0 1152244 write(2, "qemu-system-aarch64: Failed to r"..., 58) = 58
1152244 exit_group(1) = ?
1152245 <... clock_nanosleep resumed> <unfinished ...>) = ?
1152245 +++ exited with 1 +++
1152244 +++ exited with 1 +++

Quoted 2 lines

KVM folks: should we expect that KVM_CREATE_VM might fail EINTR and need retrying?

In general, yes. But for this particular one, this is pretty odd.

The only path I can so far see that would match this behaviour is if mm_take_all_locks() (called from __mmu_notifier_register()) was getting interrupted by a signal (I'm looking at a 5.19-ish kernel, which may slightly differ from the 5.15 mentioned above).

But as Vitaly points out, it doesn't seem to be a signal delivered here.

Vitaly: could you please share your exact test case (full qemu command line), and instrument your kernel to see if mm_take_all_locks() is the one failing?

Thanks,

	M.
Signature · 5 lines
Without deviation from the norm, progress is not possible.
_______________________________________________
kvmarm mailing list
[email protected]
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
#4 lore raw

Marc,

Quoted 56 lines · Marc Zyngier
Quoted 44 lines · Peter Maydell

I've added some more relevant mailing lists to the cc.

Quoted 29 lines · Vitaly Chikunov
Quoted 18 lines · Vitaly Chikunov

I 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 started to appear months before that.

strace shows in erroneous case:

1152244 ioctl(9, KVM_CREATE_VM, 0x30) = -1 EINTR (Interrupted system call)

And I see in target/arm/kvm.c:kvm_arm_create_scratch_host_vcpu:

    vmfd = ioctl(kvmfd, KVM_CREATE_VM, max_vm_pa_size);
    if (vmfd < 0) {
        goto err;
    }
Quoted 5 lines

Maybe it should restart ioctl on EINTR?

I don't see EINTR documented in ioctl(2) nor in Linux' Documentation/virt/kvm/api.rst for KVM_CREATE_VM, but for KVM_RUN it says "an unmasked signal is pending".

I am suggested that almost any blocking syscall could return EINTR, so I checked the strace log and it does not show evidence of arriving a signal, the log ends like this:

Quoted 10 lines

1152244 openat(AT_FDCWD, "/dev/kvm", O_RDWR|O_CLOEXEC) = 9
1152244 ioctl(9, KVM_CHECK_EXTENSION, KVM_CAP_ARM_VM_IPA_SIZE) = 48
1152244 ioctl(9, KVM_CREATE_VM, 0x30) = -1 EINTR (Interrupted system call)
1152244 close(9) = 0
1152244 newfstatat(2, "", {st_dev=makedev(0, 0xd), st_ino=57869925, st_mode=S_IFIFO|0600, st_nlink=1, st_uid=517, st_gid=517, st_blksize=4096, st_blocks=0, st_size=0, st_atime=1660268019 /* 2022-08-12T01:33:39.850436293+0000 */, st_atime_nsec=850436293, st_mtime=1660268019 /* 2022-08-12T01:33:39.850436293+0000 */, st_mtime_nsec=850436293, st_ctime=1660268019 /* 2022-08-12T01:33:39.850436293+0000 */, st_ctime_nsec=850436293}, AT_EMPTY_PATH) = 0 1152244 write(2, "qemu-system-aarch64: Failed to r"..., 58) = 58
1152244 exit_group(1) = ?
1152245 <... clock_nanosleep resumed> <unfinished ...>) = ?
1152245 +++ exited with 1 +++
1152244 +++ exited with 1 +++

Quoted 2 lines

KVM folks: should we expect that KVM_CREATE_VM might fail EINTR and need retrying?

In general, yes. But for this particular one, this is pretty odd.

The only path I can so far see that would match this behaviour is if mm_take_all_locks() (called from __mmu_notifier_register()) was getting interrupted by a signal (I'm looking at a 5.19-ish kernel, which may slightly differ from the 5.15 mentioned above).

Quoted 6 lines

But as Vitaly points out, it doesn't seem to be a signal delivered here.

Vitaly: could you please share your exact test case (full qemu command line), and instrument your kernel to see if mm_take_all_locks() is the one failing?

Full command is `qemu-system-aarch64 -M accel=kvm:tcg -m 4096M -smp
cores=8 -nodefaults -nographic -no-reboot -fsdev local,id=root,path=/,security_model=none,multidevs=remap -device virtio-9p-pci,fsdev=root,mount_tag=/dev/root -device virtio-rng-pci -serial mon:stdio -kernel /boot/vmlinuz-5.18.16-un-def-alt1 -initrd /usr/src/tmp/initramfs-5.18.16-un-def-alt1.img -sandbox on,spawn=deny -M virt,gic-version=3 -cpu max -append 'console=ttyAMA0 mitigations=off nokaslr quiet panic=-1 SCRIPT=/usr/src/tmp/tmp.458pkF5r8d'`.

But a minified reproducer is qemu-system-aarch64 -M virt,accel=kvm -cpu max -kernel qwe.

I traced with kprobe event tracer with the probes:

echo 'p kvm_dev_ioctl' > kprobe_events

  echo 'r kvm_dev_ioctl $retval'      >> kprobe_events
  echo 'p mm_take_all_locks'          >> kprobe_events
  echo 'r mm_take_all_locks $retval'  >> kprobe_events

Then run reproducer in the loop

  for ((i=0;i<100;i++));do echo $i; strace -fvo bb.$i qemu-system-aarch64 -M virt,accel=kvm -cpu max -kernel qwe 2>&1 | grep Failed && break; done

And on 97th iteration it's failed, strace log to check that PID is the same with the following trace:

3611463 ioctl(9, KVM_CREATE_VM, 0x30) = -1 EINTR (Interrupted system call)

Event trace log:

qemu-system-aar-3611463 [002] d.... 342920.535549: p_kvm_dev_ioctl_0: (kvm_dev_ioctl+0x0/0x910)
qemu-system-aar-3611463 [002] d.... 342920.535635: p_mm_take_all_locks_0: (mm_take_all_locks+0x0/0x390) qemu-system-aar-3611463 [002] ..... 342920.535657: r_mm_take_all_locks_0: (__mmu_notifier_register+0x44/0x200 <- mm_take_all_locks) arg1=0xfffffffc qemu-system-aar-3611463 [002] ..... 342920.535695: r_kvm_dev_ioctl_0: (__arm64_sys_ioctl+0xcc/0x124 <- kvm_dev_ioctl) arg1=0xfffffffffffffffc

So that's mm_take_all_locks returns EINTR.

(I tried also to make C reproducer which opens /dev/kvm and call ioctl(kvm, KVM_CREATE_VM, 0) in the loop and it does not reproduce the problem, so it seems it's also something additional that QEMU does.)

Thanks,

maintainer
#5 lore raw
Quoted 76 lines · Vitaly Chikunov

Marc,

Quoted 56 lines · Marc Zyngier
Quoted 44 lines · Peter Maydell

I've added some more relevant mailing lists to the cc.

Quoted 29 lines · Vitaly Chikunov
Quoted 18 lines · Vitaly Chikunov

I 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 started to appear months before that.

strace shows in erroneous case:

1152244 ioctl(9, KVM_CREATE_VM, 0x30) = -1 EINTR (Interrupted system call)

And I see in target/arm/kvm.c:kvm_arm_create_scratch_host_vcpu:

    vmfd = ioctl(kvmfd, KVM_CREATE_VM, max_vm_pa_size);
    if (vmfd < 0) {
        goto err;
    }
Quoted 5 lines

Maybe it should restart ioctl on EINTR?

I don't see EINTR documented in ioctl(2) nor in Linux' Documentation/virt/kvm/api.rst for KVM_CREATE_VM, but for KVM_RUN it says "an unmasked signal is pending".

I am suggested that almost any blocking syscall could return EINTR, so I checked the strace log and it does not show evidence of arriving a signal, the log ends like this:

Quoted 10 lines

1152244 openat(AT_FDCWD, "/dev/kvm", O_RDWR|O_CLOEXEC) = 9
1152244 ioctl(9, KVM_CHECK_EXTENSION, KVM_CAP_ARM_VM_IPA_SIZE) = 48
1152244 ioctl(9, KVM_CREATE_VM, 0x30) = -1 EINTR (Interrupted system call)
1152244 close(9) = 0
1152244 newfstatat(2, "", {st_dev=makedev(0, 0xd), st_ino=57869925, st_mode=S_IFIFO|0600, st_nlink=1, st_uid=517, st_gid=517, st_blksize=4096, st_blocks=0, st_size=0, st_atime=1660268019 /* 2022-08-12T01:33:39.850436293+0000 */, st_atime_nsec=850436293, st_mtime=1660268019 /* 2022-08-12T01:33:39.850436293+0000 */, st_mtime_nsec=850436293, st_ctime=1660268019 /* 2022-08-12T01:33:39.850436293+0000 */, st_ctime_nsec=850436293}, AT_EMPTY_PATH) = 0 1152244 write(2, "qemu-system-aarch64: Failed to r"..., 58) = 58
1152244 exit_group(1) = ?
1152245 <... clock_nanosleep resumed> <unfinished ...>) = ?
1152245 +++ exited with 1 +++
1152244 +++ exited with 1 +++

Quoted 2 lines

KVM folks: should we expect that KVM_CREATE_VM might fail EINTR and need retrying?

In general, yes. But for this particular one, this is pretty odd.

The only path I can so far see that would match this behaviour is if mm_take_all_locks() (called from __mmu_notifier_register()) was getting interrupted by a signal (I'm looking at a 5.19-ish kernel, which may slightly differ from the 5.15 mentioned above).

Quoted 6 lines

But as Vitaly points out, it doesn't seem to be a signal delivered here.

Vitaly: could you please share your exact test case (full qemu command line), and instrument your kernel to see if mm_take_all_locks() is the one failing?

Full command is `qemu-system-aarch64 -M accel=kvm:tcg -m 4096M -smp
cores=8 -nodefaults -nographic -no-reboot -fsdev local,id=root,path=/,security_model=none,multidevs=remap -device virtio-9p-pci,fsdev=root,mount_tag=/dev/root -device virtio-rng-pci -serial mon:stdio -kernel /boot/vmlinuz-5.18.16-un-def-alt1 -initrd /usr/src/tmp/initramfs-5.18.16-un-def-alt1.img -sandbox on,spawn=deny -M virt,gic-version=3 -cpu max -append 'console=ttyAMA0 mitigations=off nokaslr quiet panic=-1 SCRIPT=/usr/src/tmp/tmp.458pkF5r8d'`.

Quoted 1 line

But a minified reproducer is qemu-system-aarch64 -M virt,accel=kvm -cpu max -kernel qwe.

Ah, couldn't be smaller! ;-) Thanks for that!

Quoted 24 lines

I traced with kprobe event tracer with the probes:

echo 'p kvm_dev_ioctl' > kprobe_events

  echo 'r kvm_dev_ioctl $retval'      >> kprobe_events
  echo 'p mm_take_all_locks'          >> kprobe_events
  echo 'r mm_take_all_locks $retval'  >> kprobe_events

Then run reproducer in the loop

  for ((i=0;i<100;i++));do echo $i; strace -fvo bb.$i qemu-system-aarch64 -M virt,accel=kvm -cpu max -kernel qwe 2>&1 | grep Failed && break; done

And on 97th iteration it's failed, strace log to check that PID is the same with the following trace:

3611463 ioctl(9, KVM_CREATE_VM, 0x30) = -1 EINTR (Interrupted system call)

Event trace log:

qemu-system-aar-3611463 [002] d.... 342920.535549: p_kvm_dev_ioctl_0: (kvm_dev_ioctl+0x0/0x910)
qemu-system-aar-3611463 [002] d.... 342920.535635: p_mm_take_all_locks_0: (mm_take_all_locks+0x0/0x390) qemu-system-aar-3611463 [002] ..... 342920.535657: r_mm_take_all_locks_0: (__mmu_notifier_register+0x44/0x200 <- mm_take_all_locks) arg1=0xfffffffc qemu-system-aar-3611463 [002] ..... 342920.535695: r_kvm_dev_ioctl_0: (__arm64_sys_ioctl+0xcc/0x124 <- kvm_dev_ioctl) arg1=0xfffffffffffffffc

Quoted 5 lines

So that's mm_take_all_locks returns EINTR.

(I tried also to make C reproducer which opens /dev/kvm and call ioctl(kvm, KVM_CREATE_VM, 0) in the loop and it does not reproduce the problem, so it seems it's also something additional that QEMU does.)

On my fast test box, it takes several hundreds of iterations to fire, but that's not completely impossible to trigger (strace actually helps here). I was expecting it to fire more on a slow one, but that's not the case.

And indeed, no signal seems to be delivered. I suspect that FIT_NOTIFY_SIGNAL is set, but I need to investigate more. With a reproducer, it should be easier to diagnose fully.

But we probably need to handle EINTR when creating the mini VM.

	M.
Signature · 5 lines
Without deviation from the norm, progress is not possible.
_______________________________________________
kvmarm mailing list
[email protected]
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
#6 lore raw
Quoted 1 line · Marc Zyngier

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 ioctls will never fail EINTR except for the one special-cased KVM_CREATE_VM, plus (more obviously) KVM_RUN...

thanks
-- PMM
_______________________________________________
kvmarm mailing list
[email protected]
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

maintainer
#7 lore raw
In reply to Peter Maydell
Quoted 44 lines · Peter Maydell

I've added some more relevant mailing lists to the cc.

Quoted 29 lines · Vitaly Chikunov
Quoted 18 lines · Vitaly Chikunov

I 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 started to appear months before that.

strace shows in erroneous case:

1152244 ioctl(9, KVM_CREATE_VM, 0x30) = -1 EINTR (Interrupted system call)

And I see in target/arm/kvm.c:kvm_arm_create_scratch_host_vcpu:

    vmfd = ioctl(kvmfd, KVM_CREATE_VM, max_vm_pa_size);
    if (vmfd < 0) {
        goto err;
    }
Quoted 5 lines

Maybe it should restart ioctl on EINTR?

I don't see EINTR documented in ioctl(2) nor in Linux' Documentation/virt/kvm/api.rst for KVM_CREATE_VM, but for KVM_RUN it says "an unmasked signal is pending".

I am suggested that almost any blocking syscall could return EINTR, so I checked the strace log and it does not show evidence of arriving a signal, the log ends like this:

Quoted 10 lines

1152244 openat(AT_FDCWD, "/dev/kvm", O_RDWR|O_CLOEXEC) = 9
1152244 ioctl(9, KVM_CHECK_EXTENSION, KVM_CAP_ARM_VM_IPA_SIZE) = 48
1152244 ioctl(9, KVM_CREATE_VM, 0x30) = -1 EINTR (Interrupted system call)
1152244 close(9) = 0
1152244 newfstatat(2, "", {st_dev=makedev(0, 0xd), st_ino=57869925, st_mode=S_IFIFO|0600, st_nlink=1, st_uid=517, st_gid=517, st_blksize=4096, st_blocks=0, st_size=0, st_atime=1660268019 /* 2022-08-12T01:33:39.850436293+0000 */, st_atime_nsec=850436293, st_mtime=1660268019 /* 2022-08-12T01:33:39.850436293+0000 */, st_mtime_nsec=850436293, st_ctime=1660268019 /* 2022-08-12T01:33:39.850436293+0000 */, st_ctime_nsec=850436293}, AT_EMPTY_PATH) = 0 1152244 write(2, "qemu-system-aarch64: Failed to r"..., 58) = 58
1152244 exit_group(1) = ?
1152245 <... clock_nanosleep resumed> <unfinished ...>) = ?
1152245 +++ exited with 1 +++
1152244 +++ exited with 1 +++

Quoted 5 lines

KVM folks: should we expect that KVM_CREATE_VM might fail EINTR and need retrying?

(I suspect the answer is "yes", given we do this in the generic code in kvm-all.c.)

Interestingly, this has cropped up in the (distant) past:

https://lists.gnu.org/archive/html/qemu-devel/2014-01/msg01031.html

and seems to point at the path I was mentioning earlier (the code hasn't changed too much since, apparently).

I'd still like to understand the underlying reason though.

Thanks,

	M.
Signature · 5 lines
Without deviation from the norm, progress is not possible.
_______________________________________________
kvmarm mailing list
[email protected]
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm