WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] nat does not work with hvm

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] nat does not work with hvm
From: Erdem Bayer <ebayer@xxxxxxxxxxxx>
Date: Wed, 25 Apr 2007 17:10:49 +0300
Delivery-date: Wed, 25 Apr 2007 07:08:51 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C2466939.5DAB%Keir.Fraser@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C2466939.5DAB%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.5.0.10 (X11/20070303)
Hi

Keir Fraser wrote On 14-04-2007 13:19:

Vif-nat isn't run in this case.

Well actually it is run in 3.0.4 (but not in the very latest xen-unstable
repository, so not in the forthcoming Xen 3.0.5). But it'll get run on the
wrong interface. The vif2.0, or whatever, interfaces aren't used by qemu.
qemu creates its own tap interface and the qemu-ifup script is executed to
configure that tap interface.

 -- Keir


In xen-unstable vif-nat scripts still runs with qemu-ifup script, when a hvm domain is booted. There are some problems with that. First of all, an un-needed vif interface is created and configured with the values from the hvm configuration file, and you can not write a qemu-ifup script that takes same info from config file. (for example you cannot configure the ip address of your tap interface because that ip is taken by vif interface, wrongly.)

Also I strongly believe that a qemu-ifdown script is needed. For example if you write some iptables rules in qemu-ifup, then these rules should be deleted from iptables when the domain goes down.

Please correct me if I am wrong. I think there should be only one network script per config, (ex: vif-nat, vif-bridge, etc) and that script should determine whether the domain is a hvm or a modified one and make necessary configuration accordingly. This way there is no need for seperate scripts for qemu and vif and when a qemu domain shuts down, it's settings can be de-configured properly. Or as an alternative there should be two script for each config (ex. vif-nat-qemu + vif-nat-other) and but only one of them should be executed.

So the question is: What is the plan about implementing other types of network scripts in qemu domains? Is this discussed or planned? If not I want to make the necessary changes. I figured that tools/ioemu/vl.c is responsible for creating a hvm domain and execute the correct network script. But I could not figure out what piece of code is responsible for calling the network script with necessary parameters when a modified guest boots. Also are these changes that I propose are acceptable (or reasonable at least)? I would appreciate if you share your knowledge and ideas about this matter.

Thanks
Erdem

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel