Re: [Users] oVirt 3.3/F19 - Windows guest unable to access network

Hi, Just following up on this issue. Turns out the network problems were being caused by the bond0 interface. The initial configuration was two NICs teamed as bond0, which was then bridged to the ovirtmgmt interface. With this configuration, RHEL guests could access the network normally but Windows guests (XP, 7, 2008 R2) could not. After deactivating the bond0 interface and bridging one of the NICs directly to the ovirtmgmt interface, both RHEL and Windows guests have fully functioning networks. I am not sure why exactly the bond0 interface was not working as intended. The initial configuration had the mode as balance-rr, is this known to cause problems? My intention was to have the mode as balance-alb however the bonding driver in F19 seems to completely ignore any BONDING_OPTS settings in the ifcfg-bond0 file. Attempts to change the bonding mode directly via /sys/class/net/bond0/bonding/mode repeatedly failed due to 'the bond having slaves', even after the bond had been taken down via ifconfig. I was not able to remove the bond0 definition either, even after removing the ifcfg-bond0 file and the modprobe.d alias. Is there a recommended/tested bonding configuration HOWTO for oVirt on F19? Joop: Responses as follows: - Windows firewall was disabled in each Windows VM - Changing the CPU setting and starting the VM directly on the host via QEMU (i.e. not through oVirt) did not seem to affect the behavior Thanks, Chris PLEASE CONSIDER THE ENVIRONMENT, DON'T PRINT THIS EMAIL UNLESS YOU REALLY NEED TO. This email and its attachments may contain information which is confidential and/or legally privileged. If you are not the intended recipient of this e-mail please notify the sender immediately by e-mail and delete this e-mail and its attachments from your computer and IT systems. You must not copy, re-transmit, use or disclose (other than to the sender) the existence or contents of this email or its attachments or permit anyone else to do so. ----------------------------- -----Original Message----- From: users-bounces(a)ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of users-request(a)ovirt.org Sent: Thursday, September 19, 2013 3:31 PM To: users(a)ovirt.org Subject: Users Digest, Vol 24, Issue 93 ------------------------------ Message: 3 Date: Thu, 19 Sep 2013 09:13:43 +0200 From: noc <noc(a)nieuwland.nl&gt; Cc: &quot;users(a)ovirt.org&quot; <users(a)ovirt.org&gt; Subject: Re: [Users] oVirt 3.3/F19 - Windows guest unable to access network Message-ID: <523AA427.2060605(a)nieuwland.nl&gt; Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" On 18-9-2013 23:08, SULLIVAN, Chris (WGK) wrote: Just to be sure, iptables/firewalld!=Windows Firewall. Is there a rule in the windows firewall to allow ping or is it disabled? Don't think so, just converted a Windows2008R2 datacenter guest from Vmware to oVirt and it ran, after adding virtio drivers or using e1000 and/or ide disks. Your problem looks like the problem Ren? had with his Solaris guest, its a recent thread. Turned out that setting -cpu Nehalem by ovirt caused networking in the Solaris guest to fail. Don't think this is your problem though since lots of people run Windows guest without problems. Regards, Joop