Re: [kvm-unit-tests] its-migration segmentation fault

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On 11/20/20 12:34 PM, Andrew Jones wrote:
> On Fri, Nov 20, 2020 at 12:02:10PM +0000, Alexandru Elisei wrote:
>> When running all the tests with taskset -c 0-3 ./run_tests.sh on a rockpro64 (on
>> the Cortex-a53 cores) the its-migration test hangs.[..]
> Is your ncat segfaulting? It looks like it from this output. Have you
> tried running your ncat with a UNIX socket independently of this test?
>
> Is this the first time you've tried this test in this environment, or
> is this a regression for you?

Looks like it's a regression in nmap. I downgraded to nmap 7.80 and the test
passes, thank you for the help!

>
>> If I run the test manually:
>>
>> $ taskset -c 0-3 ./arm-run arm/gic.flat -smp 4 -machine gic-version=3 -append
>> 'its-migration'
> This won't work because we need run_tests.sh to setup the run_migration()
> call. The only ways to run migration tests separately are
>
>  $ ./run_tests.sh its-migration
>
> and
>
>  $ tests/its-migration
>
> For the second one you need to do 'make standalone' first.
>
>
>> /usr/bin/qemu-system-aarch64 -nodefaults -machine virt,gic-version=host,accel=kvm
>> -cpu host -device virtio-serial-device -device virtconsole,chardev=ctd -chardev
>> testdev,id=ctd -device pci-testdev -display none -serial stdio -kernel
>> arm/gic.flat -smp 4 -machine gic-version=3 -append its-migration # -initrd
>> /tmp/tmp.OtsTj3QD4J
>> ITS: MAPD devid=2 size = 0x8 itt=0x403a0000 valid=1
>> ITS: MAPD devid=7 size = 0x8 itt=0x403b0000 valid=1
>> MAPC col_id=3 target_addr = 0x30000 valid=1
>> MAPC col_id=2 target_addr = 0x20000 valid=1
>> INVALL col_id=2
>> INVALL col_id=3
>> MAPTI dev_id=2 event_id=20 -> phys_id=8195, col_id=3
>> MAPTI dev_id=7 event_id=255 -> phys_id=8196, col_id=2
>> Now migrate the VM, then press a key to continue...
>>
>> And the test hangs here after I press a key.
> The test doesn't get your input because of the '</dev/null' in run_qemu(),
> which ./arm-run calls. So it's not hanging it's just waiting forever on
> the key press.

I see, thanks for the explanation!

Thanks,
Alex



[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux