Am Fri, 19 Nov 2010 23:17:42 +0330 schrieb hadi golestani:
Hello,
I need to limit the port speed of a VM to 10 mbps ( or 5 mbps if it's
possible). What's the way of doing so?
Regards
maybe one of the virtual network cards is 10mbit? start kvm with -net
nic,model=? to get a list.
-
An option rom is required to be aligned to 512 bytes, and to have some
space for a signature.
Signed-off-by: Avi Kivity a...@redhat.com
---
pc-bios/optionrom/vapic.S |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/pc-bios/optionrom/vapic.S b/pc-bios/optionrom/vapic.S
On Sat, Nov 20, 2010 at 3:40 AM, Thomas Mueller tho...@chaschperli.ch wrote:
maybe one of the virtual network cards is 10mbit? start kvm with -net
nic,model=? to get a list.
wouldn't matter. different models emulate the hardware registers
used to transmit, not the performance.
if you had
if you had infinitely fast processors, every virtual network would be
infinitely fast.
I see on a Vyatta VM, that an interface's link speed attribute can be
explicitly defined, along with duplex.
Possible values are 10 100 1000 Mb, and are configured independently
of the driver/model of NIC.
Resending since the mail might have been lost...
List,
Please find attached a patch that add an initial iSCSI client library
and support to kvm-qemu.
This allows to use iSCSI devices without making them visible to the
host (and pollute the page cahce on the host)
and allows kvm-qemu to access
On 11/16/2010 03:19 PM, Alexander Graf wrote:
Rewriting it to use inb / stos works (jecxz ; insb; loop doesn't) so it
looks like a kernel bug in insb emulation.
Turns out is was a subtle bug in the tpr optimization we do for Windows XP.
The problem happens when we load the vapic
http://www.streetperformanceteam.ch/important.php
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On 11/05/2010 07:44 PM, Marcelo Tosatti wrote:
The following changes since commit d33ea50a958b2e050d2b28e5f17e3b55e91c6d74:
scsi-disk: Fix immediate failure of bdrv_aio_* (2010-11-04 13:54:37 +0100)
Pulled. Thanks.
Regards,
Anthony Liguori
are available in the git repository at:
Hi,
Seems that nobody is interested in this bug :(
Anyway I wanted to add a bit more to this investigation.
Once I put nohz=off highres=off clocksource=acpi_pm in guest kernel
options, the guests started to behave better - they do not stay in the
slow state, but rather get there for some
On 20.11.2010, at 20:52, ronnie sahlberg wrote:
Resending since the mail might have been lost...
List,
Please find attached a patch that add an initial iSCSI client library
and support to kvm-qemu.
This allows to use iSCSI devices without making them visible to the
host (and pollute
10 matches
Mail list logo
