[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Windows guest networking with vif-nat

  • To: xen-devel@xxxxxxxxxxxxx
  • From: "W. Michael Petullo" <mike@xxxxxxxx>
  • Date: Sun, 12 Feb 2017 21:17:44 -0500
  • Delivery-date: Mon, 13 Feb 2017 02:18:17 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

I recently tried to connect a Windows 7 HVM guest to my network using
vif-nat. For some reason, the setup does not work.  The DomU Windows
guest seems to recognize its virtual network interface (RTL8139C+),
but it can neither ping Dom0 nor beyond Dom0.

I have no problem with a similarly configured guest running Linux.

I am using xen-4.7.1-6.fc25.x86_64 on Fedora 25

The guest configuration is:

name      = "windows64"
memory    =  2048
vcpus     =  1
builder   = "hvm"
altp2mhvm =  1
vif       = [ "script=vif-nat,ip=,gatewaydev=wlp3s0" ]
disk      = [ "tap2:tapdisk:aio:/path/to/disk-windows64.img,xvda,w",
              "tap2:tapdisk:aio:/path/to/spare-vfat.img,xvdb,w" ]
serial    = "pty"
sdl       =  1

Switching to vif-bridge causes everything to work. I am a little suprised
by this, because I thought from the point of view of Xen both of these
configurations were rather similar; I thought the difference was in the
Dom0 network configuration. (Recall that my Linux guest works, so I do
not thing the problem is in my Dom0 network configuration/IP masquerade.)

The reason I prefer vif-nat is that it makes using my WiFi interface
easier. I have to go through some trouble to bridge vif/Ethernet to WiFi.

Might there be a bug in Xen or the vif-nat script? If there is a bug,
what else could I provide to help fix it?



Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.