[Touch-packages] [Bug 2016252] Re: qemu-system-x86_64 crashes inside systemd autopkgtest (nested VM)
Spoke too soon: that commit is already present in qemu 8.0, of course.
The rest of what I wrote still applies, though: I need to see if I can
reproduce the failure here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2016252
Title:
qemu-system-x86_64 crashes inside systemd autopkgtest (nested VM)
Status in qemu package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
Systemd package has autopkgtests
the upstream-2 test cases use upstream systemd testsuite, i.e. make -C
str/test/TEST-70-TPM2 setup run
it launches a nested VM to do quick tests inside it.
It appears that qemu-system-x86_64 crashes in such cases:
TEST-70-TPM2 RUN: cryptenroll/cryptsetup with TPM2 devices
+ timeout --foreground 1800 /bin/qemu-system-x86_64 -smp 4 -net none -m 1024M
-nographic -vga none -kernel /boot/vmlinuz-6.2.0-1003-lowlatency -drive
format=raw,cache=unsafe,file=/var/tmp/systemd-test.G2RH6i/tpm2.img -device
virtio-rng-pci,max-bytes=1024,period=1000 -chardev
socket,id=chrtpm,path=/tmp/tmp.cRBa43SrLC/sock -tpmdev
emulator,id=tpm0,chardev=chrtpm -device tpm-tis,tpmdev=tpm0 -initrd
/boot/initrd.img-6.2.0-1003-lowlatency -append 'root=LABEL=systemd_boot rw
raid=noautodetect rd.luks=0 loglevel=2 init=/lib/systemd/systemd console=ttyS0
SYSTEMD_UNIT_PATH=/usr/lib/systemd/tests/testdata/testsuite-70.units:/usr/lib/systemd/tests/testdata/units:
systemd.unit=testsuite.target systemd.wants=testsuite-70.service oops=panic
panic=1 softlockup_panic=1 systemd.wants=end.service'
qemu-system-x86_64: ../../util/cacheflush.c:208: init_cache_info: Assertion
`(isize & (isize - 1)) == 0' failed.
timeout: the monitored command dumped core
..//test-functions: line 377: 152120 Aborted ( set -x;
"${qemu_cmd[@]}" "${qemu_options[@]}" -append "${kernel_params[*]}" )
E: qemu failed with exit code 134
The important bit seems to be:
qemu-system-x86_64: ../../util/cacheflush.c:208: init_cache_info:
Assertion `(isize & (isize - 1)) == 0' failed.
Which is an assert inside qemu source code.
Is the systemd test suite VM setup doing something wrong, or is there
something wrong in qemu?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2016252/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2016252] Re: qemu-system-x86_64 crashes inside systemd autopkgtest (nested VM)
The following upstream commit looks interesting:
https://github.com/qemu/qemu/commit/00b5032eaddb7193f03f0a28b10286244d2e2a7b
I'll see if I can reproduce the issue here, and then check if
backporting the commit above makes any difference.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2016252
Title:
qemu-system-x86_64 crashes inside systemd autopkgtest (nested VM)
Status in qemu package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
Systemd package has autopkgtests
the upstream-2 test cases use upstream systemd testsuite, i.e. make -C
str/test/TEST-70-TPM2 setup run
it launches a nested VM to do quick tests inside it.
It appears that qemu-system-x86_64 crashes in such cases:
TEST-70-TPM2 RUN: cryptenroll/cryptsetup with TPM2 devices
+ timeout --foreground 1800 /bin/qemu-system-x86_64 -smp 4 -net none -m 1024M
-nographic -vga none -kernel /boot/vmlinuz-6.2.0-1003-lowlatency -drive
format=raw,cache=unsafe,file=/var/tmp/systemd-test.G2RH6i/tpm2.img -device
virtio-rng-pci,max-bytes=1024,period=1000 -chardev
socket,id=chrtpm,path=/tmp/tmp.cRBa43SrLC/sock -tpmdev
emulator,id=tpm0,chardev=chrtpm -device tpm-tis,tpmdev=tpm0 -initrd
/boot/initrd.img-6.2.0-1003-lowlatency -append 'root=LABEL=systemd_boot rw
raid=noautodetect rd.luks=0 loglevel=2 init=/lib/systemd/systemd console=ttyS0
SYSTEMD_UNIT_PATH=/usr/lib/systemd/tests/testdata/testsuite-70.units:/usr/lib/systemd/tests/testdata/units:
systemd.unit=testsuite.target systemd.wants=testsuite-70.service oops=panic
panic=1 softlockup_panic=1 systemd.wants=end.service'
qemu-system-x86_64: ../../util/cacheflush.c:208: init_cache_info: Assertion
`(isize & (isize - 1)) == 0' failed.
timeout: the monitored command dumped core
..//test-functions: line 377: 152120 Aborted ( set -x;
"${qemu_cmd[@]}" "${qemu_options[@]}" -append "${kernel_params[*]}" )
E: qemu failed with exit code 134
The important bit seems to be:
qemu-system-x86_64: ../../util/cacheflush.c:208: init_cache_info:
Assertion `(isize & (isize - 1)) == 0' failed.
Which is an assert inside qemu source code.
Is the systemd test suite VM setup doing something wrong, or is there
something wrong in qemu?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2016252/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2016252] Re: qemu-system-x86_64 crashes inside systemd autopkgtest (nested VM)
I am seeing the same crash with systemd 253.5-1ubuntu1 upstream-{1,2}
tests and qemu 1:8.0.2+dfsg-2ubuntu1[1]. However, the systemd
252.5-2ubuntu3 upstream-{1,2} tests pass against the same version of
qemu[2].
[1]
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/s/systemd/20230720_070515_f604e@/log.gz
[2]
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/s/systemd/20230721_154608_28f76@/log.gz
** Changed in: qemu (Ubuntu)
Status: Expired => New
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2016252
Title:
qemu-system-x86_64 crashes inside systemd autopkgtest (nested VM)
Status in qemu package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
Systemd package has autopkgtests
the upstream-2 test cases use upstream systemd testsuite, i.e. make -C
str/test/TEST-70-TPM2 setup run
it launches a nested VM to do quick tests inside it.
It appears that qemu-system-x86_64 crashes in such cases:
TEST-70-TPM2 RUN: cryptenroll/cryptsetup with TPM2 devices
+ timeout --foreground 1800 /bin/qemu-system-x86_64 -smp 4 -net none -m 1024M
-nographic -vga none -kernel /boot/vmlinuz-6.2.0-1003-lowlatency -drive
format=raw,cache=unsafe,file=/var/tmp/systemd-test.G2RH6i/tpm2.img -device
virtio-rng-pci,max-bytes=1024,period=1000 -chardev
socket,id=chrtpm,path=/tmp/tmp.cRBa43SrLC/sock -tpmdev
emulator,id=tpm0,chardev=chrtpm -device tpm-tis,tpmdev=tpm0 -initrd
/boot/initrd.img-6.2.0-1003-lowlatency -append 'root=LABEL=systemd_boot rw
raid=noautodetect rd.luks=0 loglevel=2 init=/lib/systemd/systemd console=ttyS0
SYSTEMD_UNIT_PATH=/usr/lib/systemd/tests/testdata/testsuite-70.units:/usr/lib/systemd/tests/testdata/units:
systemd.unit=testsuite.target systemd.wants=testsuite-70.service oops=panic
panic=1 softlockup_panic=1 systemd.wants=end.service'
qemu-system-x86_64: ../../util/cacheflush.c:208: init_cache_info: Assertion
`(isize & (isize - 1)) == 0' failed.
timeout: the monitored command dumped core
..//test-functions: line 377: 152120 Aborted ( set -x;
"${qemu_cmd[@]}" "${qemu_options[@]}" -append "${kernel_params[*]}" )
E: qemu failed with exit code 134
The important bit seems to be:
qemu-system-x86_64: ../../util/cacheflush.c:208: init_cache_info:
Assertion `(isize & (isize - 1)) == 0' failed.
Which is an assert inside qemu source code.
Is the systemd test suite VM setup doing something wrong, or is there
something wrong in qemu?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2016252/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
