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-users

[Xen-users] Problems with services in DomU

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Problems with services in DomU
From: "Marcelo Solovey - Hardtotal" <msolovey@xxxxxxxxxxxxx>
Date: Mon, 23 Apr 2007 13:34:35 -0300
Delivery-date: Tue, 24 Apr 2007 10:04:53 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: Hardtotal
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AceFxUbrK6vkQm2vQtemw/Vp1D9JIw==

Hi, I’m new in Xen and I would like to make you a question about it. I have a Xen 3.0.3 recently installed and running (under debian etch), and everything is working flawlessly, except for one thing. I have transparent access to the outside world from the DomU’s and the Dom0, services like ftp, ssh, http, (i.e.: I can run apt-get without any problem), but I cannot access services from the outside world to the DomU, or the Dom0, (i.e.: Cannot access a DomU, or Dom0 via ssh, or http, or anything from an extrange network). I have a bridge configuration, because I have a whole /24 class for me, and an iptables-save from Dom0 drop this:

 

# Generated by iptables-save v1.3.6 on Mon Apr 23 10:17:20 2007

*filter

:INPUT ACCEPT [62:5584]

:FORWARD ACCEPT [8808:480067]

:OUTPUT ACCEPT [62:7029]

-A FORWARD -s xx.xx.xx.xx -m physdev  --physdev-in vif1.0 -j ACCEPT

-A FORWARD -p udp -m physdev  --physdev-in vif1.0 -m udp --sport 68 --dport 67 -j ACCEPT

COMMIT

# Completed on Mon Apr 23 10:17:20 2007

 

Also, when I start (turn on) the server, I must do an “/etc/init.d/networking restart”, because if I don’t do that, I’ll not be able to access any Dom0 or DomU service, not even from my internal network. When I restart the network, I can start any service I want (Only from my internal network)

 

My xen-config.spx looks like this:

 

(network-script network-bridge)

(vif-script vif-bridge)

(dom0-min-mem 196)

(dom0-cpus 1)

 

My DomU config:

 

kernel = "/boot/vmlinuz-2.6.18-4-xen-686"

memory = 512

name = "Jaguar_Virtual"

disk = ['file:/virtual/dom1/virtual1.img,sda1,w','file:/virtual/dom1/virtual1_swap.img’]

ramdisk = "/boot/initrd.img-2.6.18-4-xen-686"

root = "/dev/sda1 ro"

vif = [ 'ip=xx.xx.xx.xx' ]

 

ifconfig drop:

 

dummy0    Link encap:Ethernet  HWaddr 86:A7:93:58:2E:33

          inet addr:xx.xx.xx.xx  Bcast: oo.oo.oo.255  Mask:255.255.255.0

          inet6 addr: fe80::84a7:93ff:fe58:2e33/64 Scope:Link

          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:0 (0.0 b)  TX bytes:992 (992.0 b)

 

eth0      Link encap:Ethernet  HWaddr 00:14:5E:46:05:81

          inet addr:yy.yy.yy.yy Bcast:oo.oo.oo.255  Mask:255.255.255.0

          inet6 addr: fe80::214:5eff:fe46:581/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:1767 errors:0 dropped:0 overruns:0 frame:0

          TX packets:674 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:126732 (123.7 KiB)  TX bytes:99741 (97.4 KiB)

 

lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          inet6 addr: ::1/128 Scope:Host

          UP LOOPBACK RUNNING  MTU:16436  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

 

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF

          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link

          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1

          RX packets:5755 errors:0 dropped:0 overruns:0 frame:0

          TX packets:1875 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:433752 (423.5 KiB)  TX bytes:179515 (175.3 KiB)

          Interrupt:16

 

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF

          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link

          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1

          RX packets:683 errors:0 dropped:0 overruns:0 frame:0

          TX packets:6964 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:100335 (97.9 KiB)  TX bytes:469960 (458.9 KiB)

 

vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF

          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link

          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:6188 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:0 (0.0 b)  TX bytes:395730 (386.4 KiB)

 

xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF

          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link

          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1

          RX packets:656 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:30434 (29.7 KiB)  TX bytes:0 (0.0 b)

 

 

Any help will be highly appreciated! Thanks in advance…

 

Marcelo Solovey

 

 

 

 

 

 

 

 

 

 

 

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Problems with services in DomU, Marcelo Solovey - Hardtotal <=