Bug#964793: qemu-system-x86: qemu 1:5.0-6 causes xen 4.11.4-1 HVM domains to crash at boot
On Sun, 12 Jul 2020 at 19:55, Michael Tokarev wrote: > > 10.07.2020 17:29, 小太 wrote: > > Package: qemu-system-x86 > > Version: 1:5.0-5 > > > I upgraded my qemu-system-x86 from 1:5.0-5 to 1:5.0-6 today (since it was > > just > > migrated to testing). > [bug/crash] > > > After downgrading qemu-system-x86 back down to 1:5.0-5, functionality was > > restored and the DomU was able to boot again. > > So, I'm not sure I understand, -- why did you file this bug against -5, when > what you describe sounds like -5 didn't have it while -6 did? Am I right > guessing that you just used the wrong version number when filing the > bugreport? I used the reportbug tool, which never asked me for a qemu version. Presumably it just put the currently-installed version into the bug report, rather than the version I actually wanted to report the bug against > > Thanks! > > /mjt
Bug#964793: qemu-system-x86: qemu 1:5.0-6 causes xen 4.11.4-1 HVM domains to crash at boot
10.07.2020 17:29, 小太 wrote: > Package: qemu-system-x86 > Version: 1:5.0-5 > I upgraded my qemu-system-x86 from 1:5.0-5 to 1:5.0-6 today (since it was just > migrated to testing). [bug/crash] > After downgrading qemu-system-x86 back down to 1:5.0-5, functionality was > restored and the DomU was able to boot again. So, I'm not sure I understand, -- why did you file this bug against -5, when what you describe sounds like -5 didn't have it while -6 did? Am I right guessing that you just used the wrong version number when filing the bugreport? Thanks! /mjt
Bug#964793: qemu-system-x86: qemu 1:5.0-6 causes xen 4.11.4-1 HVM domains to crash at boot
On Sat, 11 Jul 2020 at 20:37, Michael Tokarev wrote: > > 10.07.2020 17:29, 小太 wrote: > > Package: qemu-system-x86 > > Version: 1:5.0-5 > > Severity: important > > > > I upgraded my qemu-system-x86 from 1:5.0-5 to 1:5.0-6 today (since it was > > just > > migrated to testing). > > > > After upgrading, trying to boot a Xen HVM DomU (in this case named > > "windows") > > crashes immediately, with the following logs in /var/log/xen/xl-windows.log: > > Can you see where exactly it is failing, can you get a backtrace for it? I'm not sure where it's failing - running qemu under gdb results in it receiving a SIGHUP, after xl has claimed the domain has exited. Starting the domain as paused and attaching to it shows the memory as empty, and then unpausing the domain immediately exits it (despite gdb paused on the first instruction). Perhaps it's somewhere in Xen code? Though I don't really know how to debug Xen itself (xl dmesg doesn't show anything unusual). Maybe it's something better suited for a Xen dev to debug? > > There's no changes in 5.0-6 (compared to 5.0-5) which are related to xen. > However there is a significant change in the toolchain, I wonder if this > might be related.. With this in mind, I wonder if compiling 5.0-5 with > current toolchain will make any difference, in this case if it will make > the same issue to pop up in 5.0-5 too. > > Thanks! > > /mjt
Bug#964793: qemu-system-x86: qemu 1:5.0-6 causes xen 4.11.4-1 HVM domains to crash at boot
10.07.2020 17:29, 小太 wrote: > Package: qemu-system-x86 > Version: 1:5.0-5 > Severity: important > > I upgraded my qemu-system-x86 from 1:5.0-5 to 1:5.0-6 today (since it was just > migrated to testing). > > After upgrading, trying to boot a Xen HVM DomU (in this case named "windows") > crashes immediately, with the following logs in /var/log/xen/xl-windows.log: Can you see where exactly it is failing, can you get a backtrace for it? There's no changes in 5.0-6 (compared to 5.0-5) which are related to xen. However there is a significant change in the toolchain, I wonder if this might be related.. With this in mind, I wonder if compiling 5.0-5 with current toolchain will make any difference, in this case if it will make the same issue to pop up in 5.0-5 too. Thanks! /mjt
Bug#964793: qemu-system-x86: qemu 1:5.0-6 causes xen 4.11.4-1 HVM domains to crash at boot
Package: qemu-system-x86 Version: 1:5.0-5 Severity: important I upgraded my qemu-system-x86 from 1:5.0-5 to 1:5.0-6 today (since it was just migrated to testing). After upgrading, trying to boot a Xen HVM DomU (in this case named "windows") crashes immediately, with the following logs in /var/log/xen/xl-windows.log: > Waiting for domain windows (domid 1) to die [pid 2583] > Domain 1 has shut down, reason code 3 0x3 > Action for shutdown reason code 3 is destroy > Domain 1 needs to be cleaned up: destroying the domain > Done. Exiting now (reason code 3 means "crashed": https://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=xen/include/public/sched.h;hb=3fdc211b01b29f252166937238efe02d15cb5780#l178) I tried again with a minimal xl.cfg file, and it resulted in the same crash. The minimal xl.cfg contents: > name = "windows" > builder = "hvm" > vcpus = "4" > memory = "1024" > boot = "c" After downgrading qemu-system-x86 back down to 1:5.0-5, functionality was restored and the DomU was able to boot again. --- I vaguely remember these crash-at-boot problems are often caused by Xen and Qemu versions being out of sync. I see a new version of xen in unstable (4.11.4+24-gddaaccbbab-1), but not yet promoted to testing yet, so I haven't installed or tested it. However, if it ends up fixing the problem with qemu 1:5.0-6, then maybe the real bug is that qemu and xen releases should be coordinated to be promoted together? -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages qemu-system-x86 depends on: ii ipxe-qemu 1.0.0+git-20190125.36a4c85-5 ii libaio1 0.3.112-8 ii libasound21.2.2-2.3 ii libbrlapi0.7 6.0+dfsg-6 ii libc6 2.30-8 ii libcacard01:2.6.1-1 ii libcapstone3 4.0.1+really+3.0.5-2 ii libepoxy0 1.5.4-1 ii libfdt1 1.6.0-1 ii libgbm1 20.1.2-1 ii libgcc-s1 10.1.0-4 ii libglib2.0-0 2.64.3-2 ii libgnutls30 3.6.14-2 ii libibverbs1 29.0-1 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libncursesw6 6.2-1 ii libnettle73.5.1+really3.5.1-2 ii libnuma1 2.0.12-1+b1 ii libpixman-1-0 0.36.0-1 ii libpmem1 1.8-1 ii libpng16-16 1.6.37-2 ii librdmacm129.0-1 ii libsasl2-22.1.27+dfsg-2 ii libseccomp2 2.4.3-1+b1 ii libslirp0 4.2.0-2 ii libspice-server1 0.14.3-1 ii libtinfo6 6.2-1 ii liburing1 0.6-3 ii libusb-1.0-0 2:1.0.23-2 ii libusbredirparser10.8.0-1+b1 ii libvdeplug2 2.3.2+r586-2.2+b1 ii libvirglrenderer1 0.8.2-2 ii libxendevicemodel14.11.4-1 ii libxenevtchn1 4.11.4-1 ii libxenforeignmemory1 4.11.4-1 ii libxengnttab1 4.11.4-1 ii libxenmisc4.114.11.4-1 ii libxenstore3.04.11.4-1 ii libxentoolcore1 4.11.4-1 ii qemu-system-common1:5.0-6 ii qemu-system-data 1:5.0-6 ii seabios 1.13.0-1 ii zlib1g1:1.2.11.dfsg-2 Versions of packages qemu-system-x86 recommends: ii ovmf 2020.05-2 ii qemu-system-gui 1:5.0-6 ii qemu-utils 1:5.0-6 Versions of packages qemu-system-x86 suggests: pn qemu-block-extra ii qemu-system-data [sgabios] 1:5.0-6 pn samba pn vde2 -- no debconf information
