On 10/11/14 11:19 -0500, Ondřej Svoboda wrote:
Hi Adam,
there are some known issues, which depend on versions of software you are running.
If you are using EL7 (or Fedoras?) you may want to switch SELinux to permissive mode and
turn off NetworkManager (both are separate problems with bugs open for them [1, 2]). Then
give it another go. I think this could be your case. Please begin with NM, which is my
suspect.
If you are on EL6 you might be experiencing the traffic control (tc) utility or even the
kernel not supporting certain commands. I came to looking at this problem finally so I
might be able to sort it out (or ask Toni for help).
In the mean time, could you let us know what version of VDSM, selinux-policy and
NetworkManager you are running? Could you attach /var/log/vdsm/supervdsm.log and
/var/log/vdsm/vdsm.log? Does someting (NetworkManager!) in the journal seem fishy?
I spoke too soon :( Happened again on my box. Please see
https://bugzilla.redhat.com/show_bug.cgi?id=1162844 for a bug that I
created to track this. I've uploaded the vdsm.log and supervdsm.log
files too.
Thanks,
Ondra
[1]
https://bugzilla.redhat.com/show_bug.cgi?id=1138731 (I'll ask them for _working_
RPMs)
[2]
https://bugzilla.redhat.com/show_bug.cgi?id=1136843 (NetworkManager seems to touch
more than we want)
On 10.11.2014 15:34, Adam Litke wrote:
> I've been experiencing peculiar and annoying networking behavior on my
> oVirt development hosts and I'm hoping someone familiar with vdsm
> networking configuration can help me get to the bottom of it.
>
> My setup is two mini-Dells acting as virt hosts and ovirt engine
> running on my laptop. The dells get their network config from a
> cobbler instance running on my laptop which also provides PXE
> services.
>
> After freshly installing the dells, I get a nice, stable network
> connection. After installing vdsm, the connection seems to drop
> occasionally. I have visit the machine, log into the console, and
> execute 'dhclient ovirtmgmt'. This fixes the problem again for
> awhile.
>
> Does this sound like anything someone has seen before? What would be
> the best way to start debugging/diagnosing this issue? Thanks in
> advance for your responses.
--
Adam Litke