Hi! I am trying to install Xen 3.0 on a athlon machine running Centos 4.1 with 1 gb of ram. I used the rhel install script from xensource, modified it to setup xen on the machine. Now in between the installation, the script ran out with an error of not able to update grub.conf. I made manual entries inside grub.conf and rebooted inside the xen kernel. The entries i made inside grub.conf are as follows: title Xen (3.0) root (hd1,0) kernel /boot/xen-3.gz com1=115200,8n1 dom0_mem=262144 module /boot/vmlinuz-2.6-xen root=LABEL=/ ro maxcpus=1 console=tty1 console=ttyS0,115200n8 module /boot/initrd-2.6-xen.img Now after the installation and successful bootup inside xen kernel, i wanted to create a new domain, while looking in the examples i found that there should be 2 kernels, one for dom0 and other for the rest of the guest domains. However the installation script from xensource installed on one kernel. Now can anyone please tell me how should i proceed ? How do i get a kernel for the other guest domains ? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I downloaded centos 4.2 image from xen-get and used its config to create a new domain. Here is the cfg kernel = "/boot/vmlinuz-2.6-xen" memory = 128 name = "centos.4-2" nics = 1 dhcp = "dhcp" disk = [''file:/root/xen/centos/centos.4-2.img,sda1,w'', ''file:/root/xen/centos/centos.swap,sda2,w''] root = "/dev/sda1 ro" The kernel is the same kernel which is booting the machine. Now when i run xm create /etc/xen/centos.402.xen.cfg, i get the following: Using config file "/etc/xen/centos.4-2.xen.cfg". Error: Device 2049 (vbd) could not be connected. Backend device not found. Any help would be really appreciated. On 12/29/05, Anand <xen.mails@gmail.com> wrote:> > Hi! > > I am trying to install Xen 3.0 on a athlon machine running Centos 4.1 with > 1 gb of ram. > > I used the rhel install script from xensource, modified it to setup xen on > the machine. Now in between the installation, the script ran out with an > error of not able to update grub.conf. I made manual entries inside > grub.conf and rebooted inside the xen kernel. The entries i made inside > grub.conf are as follows: > > title Xen (3.0) > root (hd1,0) > kernel /boot/xen-3.gz com1=115200,8n1 dom0_mem=262144 > module /boot/vmlinuz-2.6-xen root=LABEL=/ ro maxcpus=1 console=tty1 > console=ttyS0,115200n8 > module /boot/initrd-2.6-xen.img > > Now after the installation and successful bootup inside xen kernel, i > wanted to create a new domain, while looking in the examples i found that > there should be 2 kernels, one for dom0 and other for the rest of the guest > domains. However the installation script from xensource installed on one > kernel. Now can anyone please tell me how should i proceed ? How do i get a > kernel for the other guest domains ? >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ok i finally got domain1 working with the centos image. It was a stupid typo. Now i modified the cfg file so i can supply the ip, netmask, gateway and hostname to the image. Here is the modified cfg file: kernel = "/boot/vmlinuz-2.6-xen" memory = 128 name = "centos.4-2" nics = 1 ip="192.168.1.230" netmask="255.255.255.0" gateway="192.168.1.1" hostname="xentest1" extra="selinux=0" #dhcp = "dhcp" disk = [''file:/root/xen/centos.4-2.img,sda1,w'', ''file:/root/xen/centos.swap,sda2,w''] root = "/dev/sda1 ro" However even with the above entries inside the cfg file, the image once booted up doesn''t take the ip address, gateway and hostname settings. Can anyone please tell me what i am missing here ? Any help would be appreciated. On 12/29/05, Anand <xen.mails@gmail.com> wrote:> > I downloaded centos 4.2 image from xen-get and used its config to create a > new domain. > > Here is the cfg > > kernel = "/boot/vmlinuz-2.6-xen" > memory = 128 > name = "centos.4-2" > nics = 1 > dhcp = "dhcp" > disk = [''file:/root/xen/centos/centos.4-2.img,sda1,w'', > ''file:/root/xen/centos/centos.swap,sda2,w''] > root = "/dev/sda1 ro" > > The kernel is the same kernel which is booting the machine. > > Now when i run xm create /etc/xen/centos.402.xen.cfg, i get the following: > > Using config file "/etc/xen/centos.4-2.xen.cfg". > Error: Device 2049 (vbd) could not be connected. Backend device not found. > > > Any help would be really appreciated. >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Dear Fernando, Thanks for the reply. The reason why i am interested in those directives because we want to deploy several domains in an automated fashion. Everytime doing network config inside each domain will be time consuming hence i thought these directives could be used to do the configuration part. Any other ideas on how this can be automated ? On 12/29/05, Fernando Maior <fernando.souto.maior@gmail.com> wrote:> > On 12/29/05, Anand <xen.mails@gmail.com> wrote: > > Ok i finally got domain1 working with the centos image. It was a stupid > > typo. > > > > Now i modified the cfg file so i can supply the ip, netmask, gateway and > > hostname to the image. Here is the modified cfg file: > > > > kernel = "/boot/vmlinuz- 2.6-xen" > > memory = 128 > > name = "centos.4-2" > > nics = 1 > > ip="192.168.1.230" > > netmask="255.255.255.0" > > gateway=" 192.168.1.1" > > hostname="xentest1" > > extra="selinux=0" > > #dhcp = "dhcp" > > disk = [''file:/root/xen/centos.4-2.img,sda1,w'', > > ''file:/root/xen/centos.swap,sda2,w''] > > root = "/dev/sda1 ro" > > Hi Anand, > > Just do not use the directives "ip", "netmask", "gateway" and "hostname" > at all. Try configuring network inside your domain. It runs. It is > logically > correct. It is easy. Remember, the domain do not know how to configure > every network interface, if you do not tell him. > > I have not proof on that, but I believe those directives are for the > network > interface OUT of the domain, not IN the domain. So, the domain remains > without any configuration for an interface. > > Last but not least, try understand Xen as a real network with real hosts, > configure your host as they were real ones. > > -- > Bye, > Fernando Maior > LPIC/1(31908) > LinuxCounter(391325) >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Dear Fernando, Thank you for your suggestion. Really appreciate it. I will do that. Also i would want to calculate the network traffic on the interfaces of these domains, any clues on that ? On 12/29/05, Fernando Maior <fernando.souto.maior@gmail.com> wrote:> > Anand, > > Just try the same mechanisms you would use if real hosts. DHCP. Configure > your installation image to get ip address/netmasks/gateways from DHCP, > configure a dhcp server in dom0, set the mac address of each vif in the > domX config files, put the mac associated to an ip number and other info > in dhcpd.conf, start dhcpd and boot your domX. Do not forget to set dhcpd > to listen in every interface! > > And do not use those directives anymore. > > -- > Bye, > Fernando Maior > LPIC/1(31908) > LinuxCounter(391325) >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Dear Fernando, I thought about mrtg and snmp however each time i stop and start a domain, its ID and thus the corresponding network interface name from ifconfig changes, then how can one find out the exact network utilisation of a domain ? I tried to get a constant ID number each time a domain is restarted, however i failed. Any clues ? On 12/30/05, Fernando Maior <fernando.souto.maior@gmail.com> wrote:> > Anand, > > May be a good idea to use mrtg. Mrtg uses SNMP for getting info from > network interfaces and display it to your browser in graphics. Ask Google > about mrtg, may be it should be exactly what you want. > > On 12/29/05, Anand <xen.mails@gmail.com> wrote: > > Dear Fernando, > > > > Thank you for your suggestion. Really appreciate it. I will do that. > > > > Also i would want to calculate the network traffic on the interfaces of > > these domains, any clues on that ? > > > > On 12/29/05, Fernando Maior <fernando.souto.maior@gmail.com> wrote: > > > Anand, > > > > > > Just try the same mechanisms you would use if real hosts. DHCP. > Configure > > > your installation image to get ip address/netmasks/gateways from DHCP, > > > configure a dhcp server in dom0, set the mac address of each vif in > the > > > domX config files, put the mac associated to an ip number and other > info > > > in dhcpd.conf, start dhcpd and boot your domX. Do not forget to set > dhcpd > > > to listen in every interface! > > > > > > And do not use those directives anymore. > > > > > > -- > > > Bye, > > > Fernando Maior > > > LPIC/1(31908) > > > LinuxCounter(391325) > > > > > > > > > > -- > Bye, > Fernando Maior > LPIC/1(31908) > LinuxCounter(391325) >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Dear Fernando, I wanted to use something which doesn''t force me to run anything inside the domX. And how will i get information from the bridges ? Thanks again for all the help. On 12/30/05, Fernando Maior <fernando.souto.maior@gmail.com> wrote:> > > Anand, > > SNMP runs in a client/server fashion. The client (mrtg) should run in > dom0. > And each domX should run the server (snmpd). So, snmpd is queried by > mrtg and ALWAYS tell mrtg about the SAME ethernet interfaces: eth0, > eth1, eth2, ethX. > > I did not understand why you need to control ID numbers or anything else > in dom0 that way, it is NOT necessary. But, if you want to grab > information > from within dom0, try grabbing from the bridges, instead of the > interfaces. > > -- > Bye, > Fernando Maior > LPIC/1(31908) > LinuxCounter(391325) >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Dec 30, 2005 at 06:00:11PM +0530, Anand wrote:> I wanted to use something which doesn''t force me to run anything > inside the domX. > And how will i get information from the bridges ?You can measure the bandwidth use of the vif interfaces in dom0, either by parsing /proc/net/devices periodically or by polling SNMP. As you noted the vif name will change every time a domain is restarted. In Xen 2.x you can use the vifname config directive to hardcode vif names per domain. You can also do this in 3.0 if you use a snapshot of -unstable that has this functionality (apologies, I do not know exactly when it was (re)added). Finally you could also use iptables in dom0 and the physdev module to add rules for traffic going in/out particular vifs, and poll its counters to measure bandwidth. Regards, Andy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Dear Andy, Thanks for the reply.>As you noted the vif name will change every time a domain is >restarted. In Xen 2.x you can use the vifname config directive to >hardcode vif names per domain. You can also do this in 3.0 if you >use a snapshot of -unstable that has this functionality (apologies, >I do not know exactly when it was (re)added).Thanks, thats indeed excellent news. May i ask is the snapshot stable enough to use on the production box (sorry if it sounds a stupid question to you). I am using 3.0 stable rpm from xensource on centos 4.1 right now.>You can measure the bandwidth use of the vif interfaces in dom0, >either by parsing /proc/net/devices periodically or by polling SNMP.This will give the problem of the vifname changing everytime and hence loosing track of the vif to whom the bandwidth should be accounted to.>Finally you could also use iptables in dom0 and the physdev module >to add rules for traffic going in/out particular vifs, and poll its >counters to measure bandwidth.Is it possible for you to direct me to some examples ? It will really help. regards, Anand _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Dec 30, 2005 at 08:23:42PM +0530, Anand wrote:> > Dear Andy, > Thanks for the reply. > >As you noted the vif name will change every time a domain is > >restarted. In Xen 2.x you can use the vifname config directive to > >hardcode vif names per domain. You can also do this in 3.0 if you > >use a snapshot of -unstable that has this functionality (apologies, > >I do not know exactly when it was (re)added). > Thanks, thats indeed excellent news. May i ask is the snapshot stable > enough to use on the production box (sorry if it sounds a stupid > question to you). I am using 3.0 stable rpm from xensource on centos > 4.1 right now.I can''t advise on this I''m afraid as I''m not using it heavily in production. It works nicely in the latest 2.x which is what I''m running in production.> >You can measure the bandwidth use of the vif interfaces in dom0, > >either by parsing /proc/net/devices periodically or by polling SNMP. > This will give the problem of the vifname changing everytime and hence > loosing track of the vif to whom the bandwidth should be accounted to.Yes you do need to use vifname for this to work.> >Finally you could also use iptables in dom0 and the physdev module > >to add rules for traffic going in/out particular vifs, and poll its > >counters to measure bandwidth. > Is it possible for you to direct me to some examples ? It will really > help.This too requires static vif names. Off the top of my head: iptables -N accounting_in iptables -N accounting_out iptables -A FORWARD -m physdev --physdev-out vif+ -j accounting_in iptables -A FORWARD -m physdev --physdev-in vif+ -j accounting_out iptables -A accounting_in -m physdev --physdev-out vif-foo+ -j RETURN iptables -A accounting_out -m physdev --physdev-in vif-foo+ -j RETURN The above iptables commands check all forwarded traffic to see if it came from/to a vif, if they do they are checked to see if they specifically went through an interface name matching "vif-foo*". You can then use iptables -v --list accounting_in iptables -v --list accounting_out to view the packet and byte counters for those tables. Note this matches only IP traffic. You''ll need to use ip6tables to match IPv6. Without static vif names you could add rules to the bridge interface and try to match only things going to or coming from the IP addresses that you have assigned but that seems even more hackish to me.. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Dear Andy, Thanks for all the help. I will try it out. On 12/30/05, Andy Smith <andy@strugglers.net> wrote:> > On Fri, Dec 30, 2005 at 08:23:42PM +0530, Anand wrote: > > > > Dear Andy, > > Thanks for the reply. > > >As you noted the vif name will change every time a domain is > > >restarted. In Xen 2.x you can use the vifname config directive to > > >hardcode vif names per domain. You can also do this in 3.0 if you > > >use a snapshot of -unstable that has this functionality (apologies, > > >I do not know exactly when it was (re)added). > > Thanks, thats indeed excellent news. May i ask is the snapshot stable > > enough to use on the production box (sorry if it sounds a stupid > > question to you). I am using 3.0 stable rpm from xensource on centos > > 4.1 right now. > > I can''t advise on this I''m afraid as I''m not using it heavily in > production. > > It works nicely in the latest 2.x which is what I''m running in > production. > > > >You can measure the bandwidth use of the vif interfaces in dom0, > > >either by parsing /proc/net/devices periodically or by polling SNMP. > > This will give the problem of the vifname changing everytime and > hence > > loosing track of the vif to whom the bandwidth should be accounted > to. > > Yes you do need to use vifname for this to work. > > > >Finally you could also use iptables in dom0 and the physdev module > > >to add rules for traffic going in/out particular vifs, and poll its > > >counters to measure bandwidth. > > Is it possible for you to direct me to some examples ? It will really > > help. > > This too requires static vif names. Off the top of my head: > > iptables -N accounting_in > iptables -N accounting_out > > iptables -A FORWARD -m physdev --physdev-out vif+ -j accounting_in > iptables -A FORWARD -m physdev --physdev-in vif+ -j accounting_out > > iptables -A accounting_in -m physdev --physdev-out vif-foo+ -j RETURN > iptables -A accounting_out -m physdev --physdev-in vif-foo+ -j RETURN > > The above iptables commands check all forwarded traffic to see if it > came from/to a vif, if they do they are checked to see if they > specifically went through an interface name matching "vif-foo*". > You can then use > > iptables -v --list accounting_in > iptables -v --list accounting_out > > to view the packet and byte counters for those tables. > > Note this matches only IP traffic. You''ll need to use ip6tables to > match IPv6. > > Without static vif names you could add rules to the bridge interface > and try to match only things going to or coming from the IP > addresses that you have assigned but that seems even more hackish to > me.. > > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.1 (GNU/Linux) > > iD8DBQFDtU7SIJm2TL8VSQsRAtBrAKDW6fAWiPi3DoMD3hG2375VEBoONQCgpTvA > poJ7lh1XIbW7dwT/PhuLqh0> =xw9q > -----END PGP SIGNATURE----- > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Dear Fernando, Thanks for the information. I looked at the vif-bridge file however confused on how to proceed. First as Andy pointed out the foremost point would be to get a constant vifname everytime the domain starts up only then any bandwidth calculation could work. Looks like i need to get my hands on someone who knows more on this and perhaps help me achieve this since i am unable to work on it much :(( On 12/30/05, Fernando Maior <fernando.souto.maior@gmail.com> wrote:> > On 12/30/05, Anand <xen.mails@gmail.com> wrote: > > Dear Andy, > > > > Thanks for all the help. I will try it out. > > > > > > On 12/30/05, Andy Smith <andy@strugglers.net> wrote: > > > > > > On Fri, Dec 30, 2005 at 08:23:42PM +0530, Anand wrote: > > > > > > > > Dear Andy, > > > > Thanks for the reply. > > > > >As you noted the vif name will change every time a domain is > > > > >restarted. In Xen 2.x you can use the vifname config directive > to > > > > >hardcode vif names per domain. You can also do this in 3.0 if > you > > > > >use a snapshot of -unstable that has this functionality > (apologies, > > > > >I do not know exactly when it was (re)added). > > > > Thanks, thats indeed excellent news. May i ask is the snapshot > stable > > > > enough to use on the production box (sorry if it sounds a stupid > > > > question to you). I am using 3.0 stable rpm from xensource on > centos > > > > 4.1 right now. > > > > > > I can''t advise on this I''m afraid as I''m not using it heavily in > > > production. > > > > > > It works nicely in the latest 2.x which is what I''m running in > > > production. > > > > > > > >You can measure the bandwidth use of the vif interfaces in dom0, > > > > >either by parsing /proc/net/devices periodically or by polling > SNMP. > > > > This will give the problem of the vifname changing everytime and > > hence > > > > loosing track of the vif to whom the bandwidth should be > accounted > > to. > > > > > > Yes you do need to use vifname for this to work. > > > > > > > >Finally you could also use iptables in dom0 and the physdev > module > > > > >to add rules for traffic going in/out particular vifs, and poll > its > > > > >counters to measure bandwidth. > > > > Is it possible for you to direct me to some examples ? It will > really > > > > help. > > > > > > This too requires static vif names. Off the top of my head: > > > > > > iptables -N accounting_in > > > iptables -N accounting_out > > > > > > iptables -A FORWARD -m physdev --physdev-out vif+ -j accounting_in > > > iptables -A FORWARD -m physdev --physdev-in vif+ -j accounting_out > > > > > > iptables -A accounting_in -m physdev --physdev-out vif-foo+ -j RETURN > > > iptables -A accounting_out -m physdev --physdev-in vif-foo+ -j RETURN > > > > > > The above iptables commands check all forwarded traffic to see if it > > > came from/to a vif, if they do they are checked to see if they > > > specifically went through an interface name matching "vif-foo*". > > > You can then use > > > > > > iptables -v --list accounting_in > > > iptables -v --list accounting_out > > > > > > to view the packet and byte counters for those tables. > > > > > > Note this matches only IP traffic. You''ll need to use ip6tables to > > > match IPv6. > > > > > > Without static vif names you could add rules to the bridge interface > > > and try to match only things going to or coming from the IP > > > addresses that you have assigned but that seems even more hackish to > > > me.. > > > > > > > > > > > > -----BEGIN PGP SIGNATURE----- > > > Version: GnuPG v1.4.1 (GNU/Linux) > > > > > > > > iD8DBQFDtU7SIJm2TL8VSQsRAtBrAKDW6fAWiPi3DoMD3hG2375VEBoONQCgpTvA > > > poJ7lh1XIbW7dwT/PhuLqh0> > > =xw9q > > > -----END PGP SIGNATURE----- > > > > > > > > > _______________________________________________ > > > Xen-users mailing list > > > Xen-users@lists.xensource.com > > > http://lists.xensource.com/xen-users > > > > > > > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > > > > Anand, > > You can tweak /etc/xen/scripts/vif-bridges in order to include the > iptables {add|delete} rules when the domain is started/shutdown. > > -- > Bye, > Fernando Maior > LPIC/1(31908) > LinuxCounter(391325) >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 12/30/05, Anand <xen.mails@gmail.com> wrote:> Dear Fernando, > > Thanks for the information. > > I looked at the vif-bridge file however confused on how to proceed. First as > Andy pointed out the foremost point would be to get a constant vifname > everytime the domain starts up only then any bandwidth calculation could > work. > > Looks like i need to get my hands on someone who knows more on this and > perhaps help me achieve this since i am unable to work on it much :(( > > On 12/30/05, Fernando Maior <fernando.souto.maior@gmail.com> wrote: > > On 12/30/05, Anand <xen.mails@gmail.com> wrote: > > > Dear Andy, > > > > > > Thanks for all the help. I will try it out. > > > > > > > > > On 12/30/05, Andy Smith < andy@strugglers.net> wrote: > > > > > > > > On Fri, Dec 30, 2005 at 08:23:42PM +0530, Anand wrote: > > > > > > > > > > Dear Andy, > > > > > Thanks for the reply. > > > > > >As you noted the vif name will change every time a domain is > > > > > >restarted. In Xen 2.x you can use the vifname config directive > to > > > > > >hardcode vif names per domain. You can also do this in 3.0 if > you > > > > > >use a snapshot of -unstable that has this functionality > (apologies, > > > > > >I do not know exactly when it was (re)added). > > > > > Thanks, thats indeed excellent news. May i ask is the snapshot > stable > > > > > enough to use on the production box (sorry if it sounds a stupid > > > > > question to you). I am using 3.0 stable rpm from xensource on > centos > > > > > 4.1 right now. > > > > > > > > I can''t advise on this I''m afraid as I''m not using it heavily in > > > > production. > > > > > > > > It works nicely in the latest 2.x which is what I''m running in > > > > production. > > > > > > > > > >You can measure the bandwidth use of the vif interfaces in dom0, > > > > > >either by parsing /proc/net/devices periodically or by polling > SNMP. > > > > > This will give the problem of the vifname changing everytime and > > > hence > > > > > loosing track of the vif to whom the bandwidth should be > accounted > > > to. > > > > > > > > Yes you do need to use vifname for this to work. > > > > > > > > > >Finally you could also use iptables in dom0 and the physdev > module > > > > > >to add rules for traffic going in/out particular vifs, and poll > its > > > > > >counters to measure bandwidth. > > > > > Is it possible for you to direct me to some examples ? It will > really > > > > > help. > > > > > > > > This too requires static vif names. Off the top of my head: > > > > > > > > iptables -N accounting_in > > > > iptables -N accounting_out > > > > > > > > iptables -A FORWARD -m physdev --physdev-out vif+ -j accounting_in > > > > iptables -A FORWARD -m physdev --physdev-in vif+ -j accounting_out > > > > > > > > iptables -A accounting_in -m physdev --physdev-out vif-foo+ -j RETURN > > > > iptables -A accounting_out -m physdev --physdev-in vif-foo+ -j RETURN > > > > > > > > The above iptables commands check all forwarded traffic to see if it > > > > came from/to a vif, if they do they are checked to see if they > > > > specifically went through an interface name matching "vif-foo*". > > > > You can then use > > > > > > > > iptables -v --list accounting_in > > > > iptables -v --list accounting_out > > > > > > > > to view the packet and byte counters for those tables. > > > > > > > > Note this matches only IP traffic. You''ll need to use ip6tables to > > > > match IPv6. > > > > > > > > Without static vif names you could add rules to the bridge interface > > > > and try to match only things going to or coming from the IP > > > > addresses that you have assigned but that seems even more hackish to > > > > me.. > > > > > > > > > > > > > > > > -----BEGIN PGP SIGNATURE----- > > > > Version: GnuPG v1.4.1 (GNU/Linux) > > > > > > > > > > > > iD8DBQFDtU7SIJm2TL8VSQsRAtBrAKDW6fAWiPi3DoMD3hG2375VEBoONQCgpTvA > > > > poJ7lh1XIbW7dwT/PhuLqh0> > > > =xw9q > > > > -----END PGP SIGNATURE----- > > > > > > > > > > > > _______________________________________________ > > > > Xen-users mailing list > > > > Xen-users@lists.xensource.com > > > > http://lists.xensource.com/xen-users > > > > > > > > > > > > > > > > > _______________________________________________ > > > Xen-users mailing list > > > Xen-users@lists.xensource.com > > > http://lists.xensource.com/xen-users > > > > > > > > > > Anand, > > > > You can tweak /etc/xen/scripts/vif-bridges in order to include the > > iptables {add|delete} rules when the domain is started/shutdown. > > > > -- > > Bye, > > Fernando Maior > > LPIC/1(31908) > > LinuxCounter(391325) > > > >Anand, I just started and then shutdown a domain. Rules on iptables were created, but NOT deleted. Should be some problem running the shutdown scripts, take care about them! -- Bye, Fernando Maior LPIC/1(31908) LinuxCounter(391325) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks for the valuable information. I am also trying to work my way out in it. On 1/2/06, Fernando Maior <fernando.souto.maior@gmail.com> wrote:> > I just started and then shutdown a domain. Rules on iptables were > created, but NOT deleted. Should be some problem running the > shutdown scripts, take care about them! >regards, Anand _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users