On Tue, Oct 29, 2013 at 06:18:05PM +0100, folkert wrote:
2. Get the system into the bad state and then do some deeper. Start
with outgoing ping, instrument guest driver and host vhost_net
functions to see what the drivers are doing, inspect the transmit
vring, etc.
2. Get the system into the bad state and then do some deeper. Start
with outgoing ping, instrument guest driver and host vhost_net
functions to see what the drivers are doing, inspect the transmit
vring, etc.
Update: have not gotten around to reboot the server for the new
Two approaches to get closer to the source of the problem:
1. Try the latest vanilla kernel on the host (Linux 3.10.5). This way
you can rule out fixed bugs in vhost_net or tap.
2. Get the system into the bad state and then do some deeper. Start
with outgoing ping,
On Mon, Aug 26, 2013 at 09:50:38PM +0200, folkert wrote:
2. Get the system into the bad state and then do some deeper. Start
with outgoing ping, instrument guest driver and host vhost_net
functions to see what the drivers are doing, inspect the transmit
vring, etc.
Okay, it's
Hi,
1. Try the latest vanilla kernel on the host (Linux 3.10.5). This way
you can rule out fixed bugs in vhost_net or tap.
For the last two weeks it went fine for a couple of days each time. This
evening was really bad again: uptimes of 5-10 minutes. This is with
3.11-rc4.
2. Get the
On Mon, Aug 05, 2013 at 10:59:45PM +0200, folkert wrote:
Two approaches to get closer to the source of the problem:
1. Try the latest vanilla kernel on the host (Linux 3.10.5). This way
you can rule out fixed bugs in vhost_net or tap.
2. Get the system into the bad state and then do
On Fri, Aug 02, 2013 at 08:06:58PM +0200, folkert wrote:
A couple of questions:
Please post the QEMU command-line from the host (ps aux | grep qemu).
I'll post them all:
- UMTS-clone: this one works fine since it was created a weak ago
- belle: this one was fine but suddenly also showed
If you do find something in dmesg that could be very helpful.
Ok it is down again: nothing in dmesg, neither on the guest or in the
host.
Based on this information it seems like a bug in the virtio_net guest
driver or vhost_net on the host. Actually there is one contradictory
piece of
Hi,
If the result is #2, check firewalls on host and guest. Also try the
following inside the guest: disable the network interface, rmmod
virtio_net, modprobe virtio_net again, and bring the network up.
I pinged, I sniffed, I updated the bug report (it also happens with
other guests now!).
On Fri, Aug 2, 2013 at 1:37 PM, folkert folk...@vanheusden.com wrote:
If the result is #2, check firewalls on host and guest. Also try the
following inside the guest: disable the network interface, rmmod
virtio_net, modprobe virtio_net again, and bring the network up.
I pinged, I sniffed, I
Hi Stefan,
I pinged, I sniffed, I updated the bug report (it also happens with
other guests now!).
And the bring down interfaces / rmmod / modprobe / ifup works!
So I think something is wrong with virtio_net!
What shall I do now?
I wrote a reply earlier today but it was
On Tue, Jul 30, 2013 at 10:45:20PM +0200, folkert wrote:
If you keep losing network connectivity you may have a MAC or IP address
conflict. The symptom is that network traffic is intermittent - for
example, ping might work but a full TCP connection does not.
I submitted a bug at bugzilla
On Tue, Jul 30, 2013 at 03:18:53AM +0200, folkert wrote:
The link at:
http://www.linux-kvm.org/page/FAQ#My_guest_network_is_stuck_what_should_I_do.3F
pointing to:
http://qemu-buch.de/cgi-bin/moin.cgi/QemuNetwork
is broken: it gives a Internal server error message.
Please someone point me
The link at:
http://www.linux-kvm.org/page/FAQ#My_guest_network_is_stuck_what_should_I_do.3F
pointing to:
http://qemu-buch.de/cgi-bin/moin.cgi/QemuNetwork
is broken: it gives a Internal server error message.
Please someone point me to the correct location as I'm struggeling with
a
If you keep losing network connectivity you may have a MAC or IP address
conflict. The symptom is that network traffic is intermittent - for
example, ping might work but a full TCP connection does not.
I submitted a bug at bugzilla a while ago which I updated today with new
findings:
Hi,
The link at:
http://www.linux-kvm.org/page/FAQ#My_guest_network_is_stuck_what_should_I_do.3F
pointing to:
http://qemu-buch.de/cgi-bin/moin.cgi/QemuNetwork
is broken: it gives a Internal server error message.
Please someone point me to the correct location as I'm struggeling with
a VM losing
16 matches
Mail list logo