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

[noc]

On 18-9-2013 23:08, SULLIVAN, Chris (WGK) wrote:
>
> Hi,
>
> I'm having network issues with a Windows Server 2008 R2 guest running 
> on an F19 host. The guest has a static configuration and is able to 
> ping itself and the host it is running on, however cannot ping the 
> gateway, any other hosts on the local network, or external hosts. A 
> RHEL 6.4 guest on the same host with a similar static configuration 
> works normally.
>
> Iptables/firewalld on the host are switched off and the network 
> definitions in the XML for each VM (Windows/RHEL) are the same. The 
> virtio network drivers are installed in the guest. The guest was 
> created from a Win 2008 R2 template, which was created from a VM 
> imported from oVirt 3.2. Software versions below.
>
Just to be sure, iptables/firewalld!=Windows Firewall. Is there a rule 
in the windows firewall to allow ping or is it disabled?

> Are there any manual configuration steps required on the host to 
> support Windows guests? Are there any particular diagnostic steps I 
> could take to try and narrow down the cause?
>
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.

> Versions:
>
> -oVirt 3.3.0-4
>
> -F19 3.10.11-200
>
> -QEMU 1.4.2-9
>
> -Libvirt 1.1.2-1
>
> -VDSM 4.12.1-2
>
> -virtio-win 0.1-52
>
>
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20130919/49b57d3b/attachment-0001.html>