| 1 |
Am 2018-06-07 um 09:33 schrieb Stefan G. Weichinger: |
| 2 |
> Am 2018-05-30 um 17:06 schrieb Marko Weber: |
| 3 |
>> hello, |
| 4 |
>> |
| 5 |
>> Am 2018-05-30 12:09, schrieb Stefan G. Weichinger: |
| 6 |
>>> Am 2018-05-30 um 10:46 schrieb Bill Kenworthy: |
| 7 |
>>>> error messages? - I get this happening sometimes from the oom killer |
| 8 |
>>>> when the server runs out of memory - semi-random (usually but not |
| 9 |
>>>> always the same vm) |
| 10 |
>>> |
| 11 |
>>> And the VM itself idles at 1,8 GB RAM used right now. |
| 12 |
>> |
| 13 |
>> Do you use qemu-guest-agent in the windows vm? |
| 14 |
> |
| 15 |
> Hm, I don't know. |
| 16 |
> |
| 17 |
>> Have you tried recompiling qemu, libvirt-* against the actual kernel on |
| 18 |
>> the host? |
| 19 |
>> |
| 20 |
>> maybe /var/log/libvirt/qemu/<windowsVM>.log tells something interesting. |
| 21 |
> |
| 22 |
> I mentioned the errors in the first posting. |
| 23 |
> |
| 24 |
>> in another case it helped here to recompile complete gentoo server. |
| 25 |
>> |
| 26 |
>> Do you use stable atoms or unstable? |
| 27 |
> |
| 28 |
> stable |
| 29 |
> |
| 30 |
> libvirt-4.3.0 yesterday, installed that and re-compiled qemu as well |
| 31 |
> |
| 32 |
> I also rebuilt spice. |
| 33 |
> |
| 34 |
> - |
| 35 |
> |
| 36 |
> As far as I see the upstream patch mentioned here: |
| 37 |
> |
| 38 |
> https://bugzilla.redhat.com/show_bug.cgi?id=1575541 |
| 39 |
> |
| 40 |
> might not yet be included in 4.3.0 |
| 41 |
> |
| 42 |
|
| 43 |
same crash again as I accessed the VM via virt-manager |
| 44 |
|
| 45 |
I think this patch is missing: |
| 46 |
|
| 47 |
https://github.com/qemu/qemu/commit/a89fe6c329799e47aaa1663650f076b28808e186 |
| 48 |
|
| 49 |
Commented that on: |
| 50 |
|
| 51 |
https://bugs.gentoo.org/656886 |
Archives