[SOLVED] Qemu/KVM issue, kernel 4.19.3-towo.1-siduction-amd64

[dibl]

Attempting to start a VM results in this error:

Code Auswählen Erweitern

Error starting domain: internal error: qemu unexpectedly closed the monitor:2018-11-22T11:13:56.341729Z qemu-system-x86_64:cannot set up guest memory 'pc.ram': Cannot allocate memory

Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper
  callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb
  callback(*args, **kwargs)

Same result two times.  VM starts correctly with 4.19.2-towo.2-siduction-amd64.

Code Auswählen Erweitern

virt-manager:
  Installed: 1:1.5.1-1
  Candidate: 1:1.5.1-1
  Version table:
*** 1:1.5.1-1 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status
qemu:
  Installed: 1:2.12+dfsg-3+b1
  Candidate: 1:2.12+dfsg-3+b1
  Version table:
*** 1:2.12+dfsg-3+b1 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status

Code Auswählen Erweitern

System:    Host: dibl-patience Kernel: 4.19.2-towo.2-siduction-amd64 x86_64 bits: 64
           Desktop: KDE Plasma 5.13.5 Distro: siduction 18.3.0 Patience - kde - (201805132121)
Machine:   Type: Desktop Mobo: ASUSTeK model: ROG STRIX X299-E GAMING v: Rev 1.xx serial: <filter>
           UEFI: American Megatrends v: 1401 date: 05/21/2018
CPU:       Topology: Quad Core model: Intel Core i7-7740X bits: 64 type: MT MCP L2 cache: 8192 KiB
           Speed: 1509 MHz min/max: 800/4500 MHz Core speeds (MHz): 1: 1509 2: 2029 3: 1597 4: 2072 5: 2013
           6: 1396 7: 1606 8: 1590

[towo]

That has nothing to do with the kernel, that are pyton errors.
You have seen, there is an ongoing python transition?

And btw, errors from virt-manager have also nothing to do with the function of qemu.

[dibl]

OK, yes I have seen the python transition.  But how is the VM running correctly with 4.19.2, and failing on 4.19.3?

[towo]

How much host ram?
Does it work after

Code Auswählen Erweitern

echo 3 |  tee /proc/sys/vm/drop_caches

??

If not, try the new kernel (towo.2), which is 4.19.4-rc1.
Mabe it was a kernel regression, since that rc was released shortly after the release of 4.19.3.

[dibl]

Code Auswählen Erweitern

root@dibl-patience:/# free
              total        used        free      shared  buff/cache   available
Mem:       32853120    12834848    17351780      690876     2666492    19161436
Swap:       5242876           0     5242876

Does it work after

Code Auswählen Erweitern

echo 3 |  tee /proc/sys/vm/drop_caches ??

YES.

[dibl]

This problem does not occur with kernel 4.19.4-towo-1 -- apparently there was a regression. Marking "Solved".