Hi all,
After that I migrated my home sever from xen to kvm, I noticed very
bad I/O performance,
tried many combination versions/scsi-ide-virtio I got best by using
kernel mod. 70 with
userspace 69 and virtio.
Now I have upgraded to 2.6.26.2 and kvm-72, and the performance has
dropped again. SO
hi,
I am running kvm-74 and it's getting worse for me (compared to 73, or
70,71 w/o issues), I tried virtio, rtl8139 and e1000,
the network will stall. With 8139 it happens very quick (few MB via
nfs) and I noticed that I can bring up the network
by setting the stalled NIC (in the guest) by
Most likely the guest's rx queue length is greater than the host's. You
might try
ifconfig vnet0 txqueuelen 1500
(and so on for every interface)
or perhaps reducing the guests' txqueuelen.
I have the same issue (overruns) and I have stalled network (in my other
report I can only
What is the oldest version that doesn't work? (i.e. when was the regression
introduced?)
I can (almost) be sure the kvm-70 did not have stalls and that kvm 73 certainly
has this problem.
Never tried 71 and I am not sure about 72 (haven't ran it for long
time and upgraded to 73)
--
To
For the past 5-6 months I've been using the e1000 nic in rhel3 and rhel4
guests without a problem -- and without the need for guest hacks like
noapic.
It doesn't matter which NIC, SMP, UP or noapic. See below.
I am running kvm-74 and it's getting worse for me (compared to 73, or
70,71 w/o
Nikola,
can you try:
ifconfig tapX txqueuelen 1500 on the host, this work around solved my
problem, well
at least it doesn't hang every few miniutes.
On Tue, Sep 16, 2008 at 8:34 AM, Nikola Ciprich [EMAIL PROTECTED] wrote:
Hi David, well, I tried e1000, but it's actualy much worse for me.
On Sun, Sep 14, 2008 at 7:56 PM, xming [EMAIL PROTECTED] wrote:
What is the oldest version that doesn't work? (i.e. when was the regression
introduced?)
I can (almost) be sure the kvm-70 did not have stalls and that kvm 73
certainly
has this problem.
Never tried 71 and I am not sure
What is the oldest version that doesn't work? (i.e. when was the regression
introduced?)
I can (almost) be sure the kvm-70 did not have stalls and that kvm 73
certainly
has this problem.
Never tried 71 and I am not sure about 72 (haven't ran it for long
time and upgraded to 73)
Ok I
Kernel 2.6.27 + kvm-76 on the host really gives some performance boost here.
but:
When running 2.6.27 compiled with CONFIG_KVM_GUEST=y in the guest, the guest
won't start, lot's of segfaults (in the guest) especially udev initializations.
unset CONFIG_KVM_GUEST=y, then the guest runs fine
--
To
My guests do travel too. The host is vanilla 2.6.27.6 with kvm-79.
Right now I have a guest which looks like this:
# uname -a
Linux spaceball 2.6.27.6 #1 SMP Fri Nov 14 11:51:10 CET 2008 i686 QEMU
Virtual CPU version 0.9.1 AuthenticAMD GNU/Linux
# uptime
02:00:11 up 14663 days, 18:37, 5
The same guest did it again.
# uname -a
Linux spaceball 2.6.27.6 #1 SMP Fri Nov 14 11:51:10 CET 2008 i686 QEMU
Virtual CPU version 0.9.1 AuthenticAMD GNU/Linux
# date
Thu Dec 19 01:54:27 WET 1912
# uptime
01:54:29 up 14666 days, 21:17, 12 users, load average: 3.99, 3.97, 3.91
What can I do
I have a way to reproduce my instance of the problem easily now. I was
trying
to build a new kernel on my guest, and found that depmod hangs guests every
time.
In my case, I only have an amd processor - I don't have an intel
host to try it on, right now, but it happens on Ubuntu 8.04
Neither do I have access to an Intel box.
I have an AMD Athlon(tm) X2 Dual Core Processor BE-2300
on asus m2a vm with 6GB RAM.
The host is running 32-bit Gentoo with PAE. Guests are 32-bit
Gentoo (w/o PAE, tried with same hangs) using virt block and
virt net.
I suspect it's the load (CPU + IO)
Hi,
I have compile my kernel with make O=./HOST, and when building kvm with
./configure --kerneldir=/lib/modules/2.6.27.8/build/ it fails because
of the trailing /
This patch corrects it:
--- configure.orig 2008-12-08 16:42:05.0 +0100
+++ configure 2008-12-08 16:43:57.0
updated to kvm-80 and vanilla kernel 2.6.27.8.
This is still happening after a few hours on a idle host.
# uptime
01:19:43 up 8:02, 1 user, load average: 0.08, 0.03, 0.01
# vmstat 1
procs ---memory-- ---swap-- -io -system-- cpu
r b swpd free buff
It's usable; but not ported to newer kernel versions. I can't say when I'll
get around doing it. In the meanwhile if someone else is interested, drop me
a line.
Do you mean interested in porting to newer versions (kvm + kernel) or
interested
in to use pvdma?
If it's the latter, I am.
--
To
When trying to start X (and it loads qxl driver) the kvm process just crashes.
qemu-kvm 0.14
startup line
/usr/bin/kvm -name spaceball,process=spaceball -m 1024 -kernel
/boot/bzImage-2.6.37.2-guest -append root=/dev/vda ro -smp 1 -netdev
type=tap,id=spaceball0,script=kvm-ifup-brloc,vhost=on
Oops forgot to send this to the list too, here we go
That's a spice bug. In fact, there are a lot of
qemu_mutex_lock/unlock_iothread in that subsystem. I bet at least a few
of them can cause even more subtle problems.
Just tried spice 0.7.3 (was using 0.6.x) and still the same, should I
file
On Sun, Feb 27, 2011 at 8:03 PM, Alon Levy al...@redhat.com wrote:
On Sat, Feb 26, 2011 at 01:29:01PM +0100, Jan Kiszka wrote:
On 2011-02-26 12:43, xming wrote:
When trying to start X (and it loads qxl driver) the kvm process just
crashes.
This is fixed by Gerd's attached patch (taken
hi,
I am hitting this bug as well, using qemu-kvm-0.12.2 with the following command
/usr/bin/kvm -name pfsense,process=pfsense -m 256 -vnc
192.168.0.254:13 -smp 1 -hda /dev/volume01/G-pfsense -vga std
Option 'ipv4': Use 'on' or 'off'
Failed to parse yes for dummy.ipv4
inet_listen_opts:
On Wed, Feb 10, 2010 at 10:04 AM, Thomas Beinicke
thomas.beini...@fsd-web.de wrote:
On Wednesday 10 February 2010 09:30:57 xming wrote:
hi,
Hi,
I am hitting this bug as well, using qemu-kvm-0.12.2 with the following
command
/usr/bin/kvm -name pfsense,process=pfsense -m 256 -vnc
this to stable?
Thanks
xming
--
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
Hi,
I think I am hitting this, in a weird way :D. Running 0.12.90,
vhost_net and kernel 2.6.35.4, I have troubles to get dhcp clients to
work except an old dhcp client pump seems to work out of the box.
Below are the output of dhcpcd, isc's dhcp client and busybox' udhcpc.
My dhcp server is in a
Newer versions of dhclient should also be OK: they detect
that checksum is missing in the packet. Try it e.g. with
a recent fedora guest as a client.
I don't have fedora, but with the latest release (4.1.1-P1) on isc.org
it still behaves the same (see output at the bottom).
To solve the
24 matches
Mail list logo