Hi,
I've found that there's an issue with shutdown minimal linux guest (just
minimal kernel and initramfs with busybox) via 'poweroff -f' and 'echo o
/proc/sysrq-trigger' and qemu-2.1.0 does not shutdown. I also tried to
boot the host's kernel+initramfs in qemu, the same result, however on
Hello,
On 01/15/2014 11:03 AM, Michael S. Tsirkin wrote:
Could you explain how you measure that exactly?
I check the resident memory (RES) of qemu-system-x86_64 proces.
Yes, this should not happen.
One interesting thing to try would be switching device type from
virtio-net to e1000.
On 01/15/2014 10:36 PM, Piotr Karbowski wrote:
Hello,
On 01/15/2014 11:03 AM, Michael S. Tsirkin wrote:
Could you explain how you measure that exactly?
I check the resident memory (RES) of qemu-system-x86_64 proces.
Yes, this should not happen.
One interesting thing to try would
Hi
On 01/08/2014 05:29 AM, Stefan Hajnoczi wrote:
On Sun, Dec 22, 2013 at 08:59:56PM +0100, Piotr Karbowski wrote:
Looks like netdev bridge have no support for vhost=on switch. Would
be ince if that could be added.
Try -netdev tap,helper=/path/to/qemu-bridge-helper,vhost=on,...
Sadly
On 01/09/2014 06:09 PM, Corey Bryant wrote:
You should be able to pass a command line like this:
-net tap,helper=/usr/local/libexec/qemu-bridge-helper --br=br0
Qemu treat it as one, single command as a whole. :
sh: /usr/libexec/qemu-bridge-helper --br=lebridge0: not found
failed to
On 01/09/2014 10:33 PM, Piotr Karbowski wrote:
On 01/09/2014 06:09 PM, Corey Bryant wrote:
You should be able to pass a command line like this:
-net tap,helper=/usr/local/libexec/qemu-bridge-helper --br=br0
Qemu treat it as one, single command as a whole. :
sh: /usr/libexec/qemu-bridge
Hello,
kernel 3.12.5, qemu-1.7.0.
With vhost=on, qemu shortly after start uses all its assigned memory (2G
for example), without vhost-net enabled it does not go to more than 200
MB on my idling test virtual machine. 100% reproducable. I think its not
how it should be.
Full command:
Hi,
Looks like netdev bridge have no support for vhost=on switch. Would be
ince if that could be added.
-- Piotr.
Hi,
Occasionally if I connect to monitor on unix socket and quickly
disconnect qemu process goes to 100% cpu usage until I connect to the
socket agian and actually read whatever there's, usually the qemu
welcome banner is printed twice, after the output is recieved qemu goes
back to not
