Xen users - Sep 2010 - DomU doesn''t boot after adding the vif.

Hi, I'm trying to run the xen with the NAT mode.
 
I referenced the
'http://wiki.kartbuilding.net/index.php/Xen_Networking#Routed_Networking_with_NAT_2'.
 
As shown the above link, I commented the 
 
(network-script network-bridge)
(vif-script vif-bridge),
 
and uncomment the 
 
(network-script network-nat)
(vif-script vif-nat)
 
in '/etc/xen/xend-config.sxp.
 
After rebooting the dom0, I configured the dom1.cfg to add the vif.
 
I inserted the 'vif = [ "ip=30.0.0.1" ] at the end of the
dom1.cfg.
 
When I run the dom1 using the virt-manager, the vncdisplay dosen't show the
POST screen.
 
It just shows the text 'Console is not yet active for guest' and the CPU
usage is 0%.
 
However the Memory usage shows 512MB which is configured when domain creating.
 
After deleting the 'vif = [ "ip=30.0.0.1" ]' in the dom1.cfg
and reruns the dom1, it works very well.
 
DId I wrong configure the dom1.cfg??
 
Thanks for reading.
 
PS) dom0: CentOS 5.5 + xen 3.1
 dom1: Ubuntu 8.04. LTS with HVM


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

2010/9/16 나제균 <archdoom@naver.com>
> Hi, I''m trying to run the xen with the NAT mode.
>
>
>
> I referenced the ''
>
http://wiki.kartbuilding.net/index.php/Xen_Networking#Routed_Networking_with_NAT_2
> ''.
>
>
I inserted the ''vif = [ "ip=30.0.0.1" ] at the end of the
dom1.cfg.
>
>
>
> When I run the dom1 using the virt-manager, the vncdisplay dosen''t
show the
> POST screen.
>
>
>
> It just shows the text ''Console is not yet active for
guest'' and the CPU
> usage is 0%.
>
>
Did you ask the wiki author about the problem?

>
>
> However the Memory usage shows 512MB which is configured when domain
> creating.
>
>
>
> After deleting the ''vif = [ "ip=30.0.0.1" ]'' in
the dom1.cfg and reruns the
> dom1, it works very well.
>
>
>
> DId I wrong configure the dom1.cfg??
>
>
Usually /var/log/xen/xend.log and /var/log/xen/dm-*.log will help determine
the problem.


> Thanks for reading.
>
>
>
> PS) dom0: CentOS 5.5 + xen 3.1
>
Is this the default packaged Xen?
If yes, and you only need one-way NAT (for domU to access outside network),
it''d be easier if you just use bridged networking and virbr0 bridge
(which
is created by default). Note that when creating domU config file manually,
you should specify a static MAC for domU.

-- 
Fajar


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

Some other blogs and sites also say that just input the IP address.
 
Therefore, I trusted that wiki and have no doubt.
 
Actually, the reason for using NAT is that I want to run the xorp (virtrual
router software) on the domU and dom0.
 
When I used the virbr0 and xenbr0, the routing protocol runned by xorp did not
find each other.
 
I tcpdumped all the interface on dom0, and thought that the bridge network did
somethig strange.
 
Also, the vifX.0 dose not send or receive any of the packets and acts like a
dummy.
 
So I configured the NAT mode and want the following situation.
 
---------------------------- --------------
| eth0 ----- vif1.0 ---|------|---eth0 |
---------------------------- --------------
 dom0+xorp dom1+xorp
 
As you mentioned, I inserted the static MAC address to the 'vif =[ ]'
after the IP address.
 
However, it still does not show the POST screen.
 
PS) The xen on CentOS is a default package.


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

2010/9/16 나제균 <archdoom@naver.com>
> Some other blogs and sites also say that just input the IP address.
>
>
>
> Therefore, I trusted that wiki and have no doubt.
>
>
Here''s an illustration. If you don''t put a static MAC address,
the MAC
address of domU will change every time. This will result in:
- dhcp server (if you''re using it) will assign new IP address each
time,
possibly leading to full lease making it unable to give out any more IP
address
- domU will possibly assign new interface name (eth1, eth2, etc) every time
(since it detects it as new interface due to different MAC address).

therefore while this may not be related to your problem, it''s
considered
best practice to set a static MAC address.

>
>
> Actually, the reason for using NAT is that I want to run the xorp (virtrual
> router software) on the domU and dom0.
>
>
>
> When I used the virbr0 and xenbr0, the routing protocol runned by xorp did
> not find each other.
>
>
>
> I tcpdumped all the interface on dom0, and thought that the bridge network
> did somethig strange.
>
>
>
> Also, the vifX.0 dose not send or receive any of the packets and acts
> like a dummy.
>
>
You''re grepping the worng interface. HVM domU by default send traffic
thru
tap* interface. The vif interface is only used:
- by PV domU
- by HVM domU, IF it has PV drivers.

virbr0 should be sufficent if you only need one way NAT (i.e. masquarade)
for domU. If you need something else, you can create your own bridge and
setup routing/NAT manually. It''s easier to manage that way.

-- 
Fajar


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