[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-users] domU HVM network problem
Sorry, I guess I forgot to elaborate on the rest of the setup to make it work. I modified vif-route because the default behavior is to set the eth0 ip address to the vif interface and I could never get that to work properly. Instead I assign the IP in the configuration file as you did, but I assign a network number address, not a host address. vif-route: dir=$(dirname "$0")
main_ip=$(dom0_ip) case "$command" in
if [ "${ip}" ] ; then
handle_iptable log debug "Successful vif-route $command for $vif."
Then in config I assign IP as "192.168.1.0". This is important because you will cause a conflict with the eth0 adapter inside the domU. In my domU I configure ifcfg-eth0 with IPADDRESS=192.168.1.2. AFTER the domU is started I assign IP address 192.168.1.1 to the tap/tun device created in dom0 for that domain. Here is where the problem with routing comes in. The tap/tun device created is not specific to the domU id in anyway, it depends in what order the domU's are created. If you have two HVM domains and each only one nic assigned, then the first one to be created will use device tap0 and the second one created will use tap1. I have not found a way to specify which tap device to create so I cannot assign the IP address for the tap device automatically on startup. Max Baro
-----Original Message-----
Hello, On Mar/08/2008, Max E. Baro wrote:
thank you! finally I have a NIC card! :-) I spent lot of time yesterday
Thank again! --
_______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |