From: Serge Hallyn <1079713@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1079713] Re: failed to set sndbuf on VMs network interface
Date: Fri, 23 Nov 2012 22:20:34 -0000 [thread overview]
Message-ID: <20121123222035.2731.97152.malone@soybean.canonical.com> (raw)
In-Reply-To: 20121116150919.23777.65675.malonedeb@gac.canonical.com
Latest upstream qemu.git still reproduces this, so marking it as
affecting QEMU.
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1079713
Title:
failed to set sndbuf on VMs network interface
Status in QEMU:
New
Status in “qemu-kvm” package in Ubuntu:
Confirmed
Bug description:
I am trying to set "sndbuf" for a VMs network device to "0".
I inserted to my XML file:
<tune>
<sndbuf>0</sndbuf>
</tune>
The XML file validates, but I am not able to start the virtual machine.
# virsh edit vm3
<domain type='kvm'>
<name>vm3</name>
<uuid><HIDDEN></uuid>
<memory unit='KiB'>524288</memory>
<currentMemory unit='KiB'>524288</currentMemory>
<vcpu placement='static'>1</vcpu>
<os>
<type arch='x86_64' machine='pc-1.2'>hvm</type>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/bin/kvm</emulator>
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2'/>
<source file='<HIDDEN>'/>
<target dev='vda' bus='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
</disk>
<controller type='usb' index='0'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
</controller>
<interface type='bridge'>
<mac address='<HIDDEN>'/>
<source bridge='br2'/>
<model type='virtio'/>
<tune>
<sndbuf>0</sndbuf>
</tune>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</interface>
<serial type='pty'>
<target port='0'/>
</serial>
<console type='pty'>
<target type='serial' port='0'/>
</console>
<input type='mouse' bus='ps2'/>
<graphics type='vnc' port='-1' autoport='yes'/>
<sound model='ich6'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
</sound>
<video>
<model type='cirrus' vram='9216' heads='1'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
</video>
<memballoon model='virtio'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
</memballoon>
</devices>
</domain>
Domain vm3 XML configuration edited.
# LANG=en_US.utf-8 virsh start vm3
error: Failed to start domain vm3
error: internal error Process exited while reading console log output: char device redirected to /dev/pts/4
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1079713/+subscriptions
next parent reply other threads:[~2012-11-23 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121116150919.23777.65675.malonedeb@gac.canonical.com>
2012-11-23 22:20 ` Serge Hallyn [this message]
2017-10-26 13:09 ` [Qemu-devel] [Bug 1079713] Re: failed to set sndbuf on VMs network interface Thomas Huth
2017-12-26 4:17 ` Launchpad Bug Tracker
2017-12-26 4:17 ` Launchpad Bug Tracker
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=20121123222035.2731.97152.malone@soybean.canonical.com \
--to=1079713@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.