Project

General

Profile

Actions

action #167317

closed

[qe-core][sle15sp7]sporadic issue to start a xen vm

Added by rfan1 3 months ago. Updated 2 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Start date:
2024-09-25
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Description

I can get some error messages like

[2024-09-23T14:40:15.620628Z] [debug] [pid:9354] Using existing SSH connection (key:hostname=unreal6.qe.nue2.suse.org,username=root,port=22)
[2024-09-23T14:40:16.199266Z] [debug] [pid:9354] [run_ssh_cmd(virsh  start openQA-SUT-3 2> >(tee /tmp/os-autoinst-openQA-SUT-3-stderr.log >&2))] stdout:


[2024-09-23T14:40:16.199401Z] [debug] [pid:9354] [run_ssh_cmd(virsh  start openQA-SUT-3 2> >(tee /tmp/os-autoinst-openQA-SUT-3-stderr.log >&2))] stderr:
  error: Failed to start domain 'openQA-SUT-3'
  error: internal error: libxenlight failed to create new domain 'openQA-SUT-3'

Observation

openQA test in scenario sle-15-SP7-Online-x86_64-create_hdd_gnome@svirt-xen-hvm fails in
bootloader_svirt

Test suite description

image creation job used as parent for other jobs testing based on existing installation. To be used as START_AFTER_TEST=create_hdd_gnome

Reproducible

Fails since (at least) Build 18.1 (current job)

Expected result

Last good: 14.1 (or more recent)

Further details

Always latest result in this scenario: latest


Files

Screenshot from 2024-10-08 15-50-18.png (42 KB) Screenshot from 2024-10-08 15-50-18.png phy memory is 16GB rfan1, 2024-10-08 07:54

Related issues 1 (1 open0 closed)

Copied to openQA Project (public) - action #167908: [tools][xen] openQA didn't show clear error messages when starting a VM failed due to "Cannot allocate memory"New

Actions
Actions #1

Updated by rfan1 3 months ago

I noticed the xen server unreal6 is upgraded to leap15.6 now, and xen pkg is:

unreal6:~ # rpm -qi xen-libs-4.18.3_04-150600.3.9.1.x86_64
Name        : xen-libs
Version     : 4.18.3_04
Release     : 150600.3.9.1
Architecture: x86_64
Install Date: Wed 25 Sep 2024 03:26:17 AM CEST
Group       : System/Kernel
Size        : 1752152
License     : GPL-2.0-only
Signature   : RSA/SHA256, Mon 16 Sep 2024 05:19:59 PM CEST, Key ID 70af9e8139db7c82
Source RPM  : xen-4.18.3_04-150600.3.9.1.src.rpm
Build Date  : Mon 16 Sep 2024 05:18:19 PM CEST
Build Host  : h03-ch2d
Relocations : (not relocatable)
Packager    : https://www.suse.com/
Vendor      : SUSE LLC <https://www.suse.com/>
URL         : http://www.cl.cam.ac.uk/Research/SRG/netos/xen/
Summary     : Xen Virtualization: Libraries
Description :
Xen is a virtual machine monitor for x86 that supports execution of
multiple guest operating systems with unprecedented levels of
performance and resource isolation.

This package contains the libraries used to interact with the Xen
virtual machine monitor.

In addition to this package you need to install xen and xen-tools
to use Xen.

https://openqa.suse.de/tests/15526219# The issue is gone, but let us monitor it in next few days since it is a sporadic issue

Actions #2

Updated by rfan1 2 months ago

  • Status changed from New to In Progress
  • Assignee set to rfan1
Actions #3

Updated by rfan1 2 months ago

Well, the issue can be seen again. https://openqa.suse.de/tests/15612615#

So, seems the issue is caused by allocating memory to vm

libxl-driver.log:19269:2024-10-05 02:07:28.986+0000: libxl: libxl_dom.c:581:libxl__build_dom: xc_dom_boot_mem_init failed: Device or resource busy
libxl-driver.log:19280:2024-10-05 02:18:19.610+0000: xc: panic: xg_dom_x86.c:1316: meminit_pv: failed to allocate 0x80000 pages: Internal error
libxl-driver.log:19282:2024-10-05 02:18:19.610+0000: libxl: libxl_dom.c:581:libxl__build_dom: xc_dom_boot_mem_init failed: Device or resource busy
libxl-driver.log:19351:2024-10-05 06:27:36.180+0000: libxl: libxl_dom.c:581:libxl__build_dom: xc_dom_boot_mem_init failed: Device or resource busy
libxl-driver.log:19355:2024-10-05 06:27:38.275+0000: libxl: libxl_dom.c:581:libxl__build_dom: xc_dom_boot_mem_init failed: Device or resource busy
libxl-driver.log:19361:2024-10-05 06:27:44.722+0000: xc: panic: xg_dom_x86.c:1316: meminit_pv: failed to allocate 0x100000 pages: Internal error
libxl-driver.log:19363:2024-10-05 06:27:44.722+0000: libxl: libxl_dom.c:581:libxl__build_dom: xc_dom_boot_mem_init failed: Device or resource busy
libxl-driver.log:19367:2024-10-05 06:27:45.212+0000: libxl: libxl_dom.c:581:libxl__build_dom: xc_dom_boot_mem_init failed: Device or resource busy
libxl-driver.log:19370:2024-10-05 06:29:19.841+0000: xc: panic: xg_dom_x86.c:1316: meminit_pv: failed to allocate 0x100000 pages: Internal error
libxl-driver.log:19372:2024-10-05 06:29:19.841+0000: libxl: libxl_dom.c:581:libxl__build_dom: xc_dom_boot_mem_init failed: Device or resource busy
libxl-driver.log:19376:2024-10-05 06:30:09.525+0000: libxl: libxl_dom.c:581:libxl__build_dom: xc_dom_boot_mem_init failed: Device or resource busy
libxl-driver.log:19380:2024-10-05 06:30:09.653+0000: libxl: libxl_dom.c:581:libxl__build_dom: xc_dom_boot_mem_init failed: Device or resource busy
libxl-driver.log:19384:2024-10-05 06:30:09.847+0000: libxl: libxl_dom.c:581:libxl__build_dom: xc_dom_boot_mem_init failed: Device or resource busy
libxl-driver.log:19387:2024-10-05 06:30:09.854+0000: libxl: libxl_create.c:720:libxl__domain_make: domain creation fail: Cannot allocate memory
libxl-driver.log:19390:2024-10-05 06:32:16.124+0000: libxl: libxl_dom.c:581:libxl__build_dom: xc_dom_boot_mem_init failed: Device or resource busy
libxl-driver.log:19400:2024-10-05 06:48:48.446+0000: libxl: libxl_dom.c:581:libxl__build_dom: xc_dom_boot_mem_init failed: Device or resource busy
libxl-driver.log:19408:2024-10-05 06:51:05.700+0000: libxl: libxl_dom.c:581:libxl__build_dom: xc_dom_boot_mem_init failed: Device or resource busy
libxl-driver.log:19446:2024-10-05 08:52:23.451+0000: libxl: libxl_dom.c:581:libxl__build_dom: xc_dom_boot_mem_init failed: Device or resource busy
libxl-driver.log:19450:2024-10-05 08:52:47.094+0000: libxl: libxl_dom.c:581:libxl__build_dom: xc_dom_boot_mem_init failed: Device or resource busy
libxl-driver.log:19453:2024-10-05 08:52:47.101+0000: libxl: libxl_create.c:720:libxl__domain_make: domain creation fail: Cannot allocate memory

Actions #5

Updated by rfan1 2 months ago

  • Copied to action #167908: [tools][xen] openQA didn't show clear error messages when starting a VM failed due to "Cannot allocate memory" added
Actions #6

Updated by rfan1 2 months ago

I will move all gnome test to openqaw5-xen which has 40+GB memory.

Actions #7

Updated by rfan1 2 months ago

  • Status changed from In Progress to Feedback
Actions #8

Updated by rfan1 2 months ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF