registry team mailing list archive

[Felix Joussein <615077@xxxxxxxxxxxxxxxxxx>]

Hi, I also encountered that problem:
I'm running Maverik Merkat 10.10:
Same message "operation failed: failed to retrieve chardev info in qemu with 'info chardev'"
I played around like when you have a physical machine, that won't work: You remove piece by piece until it boots to figure out the faulty hardware:
So I figured out, that when I reduce the used physical memory from 3072 MB RAM to 2048 the machine booted again.
Remains the question: why did it work before with 3072MB and suddenly it stoops.
BTW: I have 12GB physical memory in my server as well as 12 CPU Cores which gives me 24 threads.
I had this problem before, and then usually a reboot of the machine did it also, of course, I can't reboot a host that runs 4 productive machines during business hours...
What I'm curious about: The error message says error to retrieve chardev info... which console command could I use to directly check for "info chardev"?

I think this is a mayor issue, as else kvm/libvirt or what ever else is responsible to cause that, is not to be run in productive environments.
For me I switched from vmware-server to kvm to use pure open source... but I'm already thinking on going back as these issues, as well as still sometimes guests looses their network while still showing an up-state link within the guest - and so far there is no solution for that either.

Thank you for solving those issues!

-- 
[Maverick] SDL local window broken in last update
https://bugs.launchpad.net/bugs/615077
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for virtinst.