All of lore.kernel.org
 help / color / mirror / Atom feed
From: Launchpad Bug Tracker <1687214@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1687214] Re: Rapid tremendous memory hog when using -net nic, vlan=0 -net user, vlan=0
Date: Sat, 09 Jan 2021 04:17:39 -0000	[thread overview]
Message-ID: <161016586011.8490.16331632271455566116.malone@loganberry.canonical.com> (raw)
In-Reply-To: 20170429175305.26812.79902.malonedeb@gac.canonical.com

[Expired for QEMU because there has been no activity for 60 days.]

** Changed in: qemu
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1687214

Title:
  Rapid tremendous memory hog when using -net nic,vlan=0 -net
  user,vlan=0

Status in QEMU:
  Expired

Bug description:
  A rapid tremendous memory hog is occuring when I use -net nic,vlan=0
  -net user,vlan=0. Tested with QEMU 2.8.0 & 2.9.0 in Gentoo. All
  available memory (8GB) + swap (over 20GB) is exhausted very rapidly.

  This bug is possibly related to 
  https://bugs.launchpad.net/qemu/+bug/1310714 
  and maybe to
  https://bugs.launchpad.net/qemu/+bug/1288620

  The bug IS present wheh I use -net nic,vlan=0 -net user,vlan=0 (tested
  with no model and model=e1000 and model=virtio, with all these the bug
  is present)

  The bug is NOT present with I use this:
  -netdev type=user,id=mynet0 -device virtio-net-pci,netdev=mynet0

  I tested this bug only using windows guests (Windows XP & Windows 8).

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1687214/+subscriptions


      parent reply	other threads:[~2021-01-09  4:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-29 17:53 [Qemu-devel] [Bug 1687214] [NEW] Rapid tremendous memory hog when using -net nic, vlan=0 -net user, vlan=0 Alamot
2020-11-09 12:29 ` [Bug 1687214] " Thomas Huth
2021-01-09  4:17 ` Launchpad Bug Tracker [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=161016586011.8490.16331632271455566116.malone@loganberry.canonical.com \
    --to=1687214@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.