All of lore.kernel.org
 help / color / mirror / Atom feed
From: "W. Michael Petullo" <mike@flyn.org>
To: xen-devel@lists.xen.org
Subject: Windows guest networking with vif-nat
Date: Sun, 12 Feb 2017 21:17:44 -0500	[thread overview]
Message-ID: <20170213021744.GA23785@imp.flyn.org> (raw)

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=10.0.0.2/32,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?

-- 
Mike

:wq

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

                 reply	other threads:[~2017-02-13  2:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170213021744.GA23785@imp.flyn.org \
    --to=mike@flyn.org \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.