Hi ALL I did it all partition. everything is cool. i installed centos too. i dont know how to assign ip for my centos let me know the same. xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 256 1 r----- 123.5 vm02 16 96 1 -b---- 12.2 Kaushal _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Just like you normally do. /etc/sysconfig/network and /etc/sysconfig/network-scripts/ifcfg-eth0 Or use dhcp and assign a mac address in the xen config file for vm02. Browse the list for some examples. Sjoerd de Heer S&R Solutions> -----Oorspronkelijk bericht----- > Van: xen-users-bounces@lists.xensource.com [mailto:xen-users- > bounces@lists.xensource.com] Namens Kaushal Shriyan > Verzonden: maandag 7 augustus 2006 14:43 > Aan: xen-users@lists.xensource.com > Onderwerp: [Xen-users] Assign IP''s > > Hi ALL > > I did it all partition. everything is cool. > i installed centos too. > i dont know how to assign ip for my centos let me know the same. > > xm list > Name ID Mem(MiB) VCPUs State Time(s) > Domain-0 0 256 1 r----- 123.5 > vm02 16 96 1 -b---- 12.2 > > Kaushal > > _______________________________________________ > 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
On 8/7/06, postmaster/info <info@sr-solutions.nl> wrote:> Just like you normally do. /etc/sysconfig/network and > /etc/sysconfig/network-scripts/ifcfg-eth0 Or use dhcp and assign a mac > address in the xen config file for vm02. Browse the list for some examples. > > Sjoerd de Heer > S&R Solutions > > > -----Oorspronkelijk bericht----- > > Van: xen-users-bounces@lists.xensource.com [mailto:xen-users- > > bounces@lists.xensource.com] Namens Kaushal Shriyan > > Verzonden: maandag 7 augustus 2006 14:43 > > Aan: xen-users@lists.xensource.com > > Onderwerp: [Xen-users] Assign IP''s > > > > Hi ALL > > > > I did it all partition. everything is cool. > > i installed centos too. > > i dont know how to assign ip for my centos let me know the same. > > > > xm list > > Name ID Mem(MiB) VCPUs State Time(s) > > Domain-0 0 256 1 r----- 123.5 > > vm02 16 96 1 -b---- 12.2 > > > > Kaushal > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > >Hi Sjoerd de Heer It didnot worked, can you point me to the exact steps Please Thanks and Regards Kaushal _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
What kind of error message did you get? And what did you try? Don''t forget to put a vif = ['' ''] statement in your xen config file else there won''t be a nic present in your domU. So please post your xen config file, lspci of domU and relevant parts of dmesg are welcome. Please check for typos I spend two days grumbling because I copied a typo from a not working example. Greetings, Sjoerd de Heer S&R Solutions> -----Oorspronkelijk bericht----- > Van: xen-users-bounces@lists.xensource.com [mailto:xen-users- > bounces@lists.xensource.com] Namens Kaushal Shriyan > Verzonden: maandag 7 augustus 2006 15:16 > Aan: xen-users@lists.xensource.com > Onderwerp: Re: [Xen-users] Assign IP''s > > On 8/7/06, postmaster/info <info@sr-solutions.nl> wrote: > > Just like you normally do. /etc/sysconfig/network and > > /etc/sysconfig/network-scripts/ifcfg-eth0 Or use dhcp and assign a mac > > address in the xen config file for vm02. Browse the list for some > examples. > > > > Sjoerd de Heer > > S&R Solutions > > > > > -----Oorspronkelijk bericht----- > > > Van: xen-users-bounces@lists.xensource.com [mailto:xen-users- > > > bounces@lists.xensource.com] Namens Kaushal Shriyan > > > Verzonden: maandag 7 augustus 2006 14:43 > > > Aan: xen-users@lists.xensource.com > > > Onderwerp: [Xen-users] Assign IP''s > > > > > > Hi ALL > > > > > > I did it all partition. everything is cool. > > > i installed centos too. > > > i dont know how to assign ip for my centos let me know the same. > > > > > > xm list > > > Name ID Mem(MiB) VCPUs State Time(s) > > > Domain-0 0 256 1 r----- 123.5 > > > vm02 16 96 1 -b---- 12.2 > > > > > > Kaushal > > > > > > _______________________________________________ > > > Xen-users mailing list > > > Xen-users@lists.xensource.com > > > http://lists.xensource.com/xen-users > > > > > Hi Sjoerd de Heer > > It didnot worked, can you point me to the exact steps Please > > Thanks and Regards > > Kaushal > > _______________________________________________ > 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
On 8/7/06, postmaster/info <info@sr-solutions.nl> wrote:> What kind of error message did you get? And what did you try? Don''t forget > to put a vif = ['' ''] statement in your xen config file else there won''t be a > nic present in your domU. So please post your xen config file, lspci of domU > and relevant parts of dmesg are welcome. Please check for typos I spend two > days grumbling because I copied a typo from a not working example. > > Greetings, > > Sjoerd de Heer > S&R Solutions > > > -----Oorspronkelijk bericht----- > > Van: xen-users-bounces@lists.xensource.com [mailto:xen-users- > > bounces@lists.xensource.com] Namens Kaushal Shriyan > > Verzonden: maandag 7 augustus 2006 15:16 > > Aan: xen-users@lists.xensource.com > > Onderwerp: Re: [Xen-users] Assign IP''s > > > > On 8/7/06, postmaster/info <info@sr-solutions.nl> wrote: > > > Just like you normally do. /etc/sysconfig/network and > > > /etc/sysconfig/network-scripts/ifcfg-eth0 Or use dhcp and assign a mac > > > address in the xen config file for vm02. Browse the list for some > > examples. > > > > > > Sjoerd de Heer > > > S&R Solutions > > > > > > > -----Oorspronkelijk bericht----- > > > > Van: xen-users-bounces@lists.xensource.com [mailto:xen-users- > > > > bounces@lists.xensource.com] Namens Kaushal Shriyan > > > > Verzonden: maandag 7 augustus 2006 14:43 > > > > Aan: xen-users@lists.xensource.com > > > > Onderwerp: [Xen-users] Assign IP''s > > > > > > > > Hi ALL > > > > > > > > I did it all partition. everything is cool. > > > > i installed centos too. > > > > i dont know how to assign ip for my centos let me know the same. > > > > > > > > xm list > > > > Name ID Mem(MiB) VCPUs State Time(s) > > > > Domain-0 0 256 1 r----- 123.5 > > > > vm02 16 96 1 -b---- 12.2 > > > > > > > > Kaushal > > > > > > > > _______________________________________________ > > > > Xen-users mailing list > > > > Xen-users@lists.xensource.com > > > > http://lists.xensource.com/xen-users > > > > > > > > Hi Sjoerd de Heer > > > > It didnot worked, can you point me to the exact steps Please > > > > Thanks and Regards > > > > Kaushal > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > >Hi Sjoerd de Heer How do i set vif in the xen config file [root@localhost etc]# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 256 1 r----- 34.2 vm02 2 96 1 -b---- 5.2 ifconfig eth0 Link encap:Ethernet HWaddr 00:16:76:08:17:55 inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::216:76ff:fe08:1755/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2444 errors:0 dropped:0 overruns:0 frame:0 TX packets:1755 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:403081 (393.6 KiB) TX bytes:159337 (155.6 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:34 errors:0 dropped:0 overruns:0 frame:0 TX packets:34 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:5034 (4.9 KiB) TX bytes:5034 (4.9 KiB) 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 MULTICAST MTU:1500 Metric:1 RX packets:2437 errors:0 dropped:0 overruns:0 frame:0 TX packets:1774 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:403748 (394.2 KiB) TX bytes:166515 (162.6 KiB) Interrupt:20 Base address:0xde00 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 MULTICAST MTU:1500 Metric:1 RX packets:1755 errors:0 dropped:0 overruns:0 frame:0 TX packets:2446 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:159337 (155.6 KiB) TX bytes:403249 (393.7 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 MULTICAST MTU:1500 Metric:1 RX packets:977 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:243833 (238.1 KiB) TX bytes:468 (468.0 b) CentOS release 4.3 (Final) Kernel 2.6.16-xen3_86.1_rhel4.1 on an i686 localhost login: root Password: Last login: Sun Aug 6 16:26:12 on tty1 -bash-3.00# ls -bash-3.00# ifconfig -bash-3.00# unable to add ip. Kaushal _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Also me I''m experiencing in a similar problem. I want that my virtual
machine get a static IP from outside. This is my cfg file:
xen:~# vi /etc/xen/vx1.cfg
kernel = ''/boot/vmlinuz-2.6.16-2-xen-686''
ramdisk = ''/boot/initrd.img-2.6.16-2-xen-686''
memory = 256
name = ''vx1''
root = ''/dev/sda1 ro''
disk = [ ''file:/vx/domains/vx1/disk.img,sda1,w'',
''file:/vx/domains/vx1/swap.img,sda2,w'' ]
# network
vif=[ '''' ]
dhcp="off"
ip="151.39.235.217"
netmask="255.255.255.192"
gateway="151.39.235.193"
hostname="vx1.sysman.iol.it"
extra="3"
xen:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:0E:0C:30:AA:BE
inet addr:151.39.235.216 Bcast:151.39.235.255 Mask:255.255.255.192
inet6 addr: fe80::20e:cff:fe30:aabe/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2576 errors:0 dropped:0 overruns:0 frame:0
TX packets:231 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:179952 (175.7 KiB) TX bytes:24496 (23.9 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:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 b) TX bytes:560 (560.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 MULTICAST MTU:1500 Metric:1
RX packets:2579 errors:0 dropped:0 overruns:0 frame:0
TX packets:245 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:191883 (187.3 KiB) TX bytes:26494 (25.8 KiB)
Base address:0x2040 Memory:fe6a0000-fe6c0000
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 MULTICAST MTU:1500 Metric:1
RX packets:231 errors:0 dropped:0 overruns:0 frame:0
TX packets:2581 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:24496 (23.9 KiB) TX bytes:180338 (176.1 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 MULTICAST MTU:1500 Metric:1
RX packets:2292 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:122371 (119.5 KiB) TX bytes:468 (468.0 b)
But domU does not start:
xen:~# xm create vx1.cfg -c
Using config file "/etc/xen/vx1.cfg".
Error: Device 2049 (vbd) could not be connected. Backend device not found.
In /var/log/xen-hotplug.log I''ve found:
interface vif1.0 does not exist!
xenstore-read: couldn''t read path backend/vbd/1/2049/node
xenstore-read: couldn''t read path backend/vbd/1/2050/node
xenstore-read: couldn''t read path backend/vbd/2/2049/node
xenstore-read: couldn''t read path backend/vbd/2/2050/node
xenstore-read: couldn''t read path backend/vbd/3/2049/node
xenstore-read: couldn''t read path backend/vbd/3/2050/node
xenstore-read: couldn''t read path backend/vbd/4/2049/node
xenstore-read: couldn''t read path backend/vbd/4/2050/node
And in /var/log/xend.log I got:
[2006-08-07 16:54:32 xend.XendDomainInfo] DEBUG (XendDomainInfo:877)
XendDomainInfo.handleShutdownWatch
[2006-08-07 16:54:32 xend] DEBUG (DevController:132) Waiting for devices vif.
[2006-08-07 16:54:32 xend] DEBUG (DevController:138) Waiting for 0.
[2006-08-07 16:54:32 xend] DEBUG (DevController:403)
hotplugStatusCallback /local/domain/0/backend/vif/4/0/hotplug-status.
[2006-08-07 16:54:32 xend] DEBUG (DevController:403)
hotplugStatusCallback /local/domain/0/backend/vif/4/0/hotplug-status.
[2006-08-07 16:54:32 xend] DEBUG (DevController:417) hotplugStatusCallback 1.
[2006-08-07 16:54:32 xend] DEBUG (DevController:132) Waiting for devices usb.
[2006-08-07 16:54:32 xend] DEBUG (DevController:132) Waiting for devices vbd.
[2006-08-07 16:54:32 xend] DEBUG (DevController:138) Waiting for 2049.
[2006-08-07 16:54:32 xend] DEBUG (DevController:403)
hotplugStatusCallback
/local/domain/0/backend/vbd/4/2049/hotplug-status.
[2006-08-07 16:54:32 xend] DEBUG (DevController:417) hotplugStatusCallback 2.
[2006-08-07 16:54:32 xend.XendDomainInfo] DEBUG (XendDomainInfo:1327)
XendDomainInfo.destroy: domid=4
[2006-08-07 16:54:32 xend.XendDomainInfo] DEBUG (XendDomainInfo:1335)
XendDomainInfo.destroyDomain(4)
Maybe can something be wrong in /etc/xen/xend-config.sxp ? Now is
uncommented only:
(network-script network-bridge)
(network-script network-dummy)
(vif-script vif-bridge)
Thanks
Stefano
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Try ''modprobe loop'' in domain 0 before trying to start your guest domains. On 8/7/06, Stefano Cislaghi <s.cislaghi@gmail.com> wrote:> Also me I''m experiencing in a similar problem. I want that my virtual > machine get a static IP from outside. This is my cfg file: > > xen:~# vi /etc/xen/vx1.cfg > > kernel = ''/boot/vmlinuz-2.6.16-2-xen-686'' > ramdisk = ''/boot/initrd.img-2.6.16-2-xen-686'' > memory = 256 > name = ''vx1'' > root = ''/dev/sda1 ro'' > disk = [ ''file:/vx/domains/vx1/disk.img,sda1,w'', > ''file:/vx/domains/vx1/swap.img,sda2,w'' ] > > # network > vif=[ '''' ] > dhcp="off" > ip="151.39.235.217" > netmask="255.255.255.192" > gateway="151.39.235.193" > hostname="vx1.sysman.iol.it" > > extra="3" > > > xen:~# ifconfig > eth0 Link encap:Ethernet HWaddr 00:0E:0C:30:AA:BE > inet addr:151.39.235.216 Bcast:151.39.235.255 Mask:255.255.255.192 > inet6 addr: fe80::20e:cff:fe30:aabe/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:2576 errors:0 dropped:0 overruns:0 frame:0 > TX packets:231 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:179952 (175.7 KiB) TX bytes:24496 (23.9 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:8 errors:0 dropped:0 overruns:0 frame:0 > TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:560 (560.0 b) TX bytes:560 (560.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 MULTICAST MTU:1500 Metric:1 > RX packets:2579 errors:0 dropped:0 overruns:0 frame:0 > TX packets:245 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:191883 (187.3 KiB) TX bytes:26494 (25.8 KiB) > Base address:0x2040 Memory:fe6a0000-fe6c0000 > > 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 MULTICAST MTU:1500 Metric:1 > RX packets:231 errors:0 dropped:0 overruns:0 frame:0 > TX packets:2581 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:24496 (23.9 KiB) TX bytes:180338 (176.1 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 MULTICAST MTU:1500 Metric:1 > RX packets:2292 errors:0 dropped:0 overruns:0 frame:0 > TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:122371 (119.5 KiB) TX bytes:468 (468.0 b) > > > > But domU does not start: > > xen:~# xm create vx1.cfg -c > Using config file "/etc/xen/vx1.cfg". > Error: Device 2049 (vbd) could not be connected. Backend device not found. > > In /var/log/xen-hotplug.log I''ve found: > > interface vif1.0 does not exist! > xenstore-read: couldn''t read path backend/vbd/1/2049/node > xenstore-read: couldn''t read path backend/vbd/1/2050/node > xenstore-read: couldn''t read path backend/vbd/2/2049/node > xenstore-read: couldn''t read path backend/vbd/2/2050/node > xenstore-read: couldn''t read path backend/vbd/3/2049/node > xenstore-read: couldn''t read path backend/vbd/3/2050/node > xenstore-read: couldn''t read path backend/vbd/4/2049/node > xenstore-read: couldn''t read path backend/vbd/4/2050/node > > And in /var/log/xend.log I got: > > [2006-08-07 16:54:32 xend.XendDomainInfo] DEBUG (XendDomainInfo:877) > XendDomainInfo.handleShutdownWatch > [2006-08-07 16:54:32 xend] DEBUG (DevController:132) Waiting for devices vif. > [2006-08-07 16:54:32 xend] DEBUG (DevController:138) Waiting for 0. > [2006-08-07 16:54:32 xend] DEBUG (DevController:403) > hotplugStatusCallback /local/domain/0/backend/vif/4/0/hotplug-status. > [2006-08-07 16:54:32 xend] DEBUG (DevController:403) > hotplugStatusCallback /local/domain/0/backend/vif/4/0/hotplug-status. > [2006-08-07 16:54:32 xend] DEBUG (DevController:417) hotplugStatusCallback 1. > [2006-08-07 16:54:32 xend] DEBUG (DevController:132) Waiting for devices usb. > [2006-08-07 16:54:32 xend] DEBUG (DevController:132) Waiting for devices vbd. > [2006-08-07 16:54:32 xend] DEBUG (DevController:138) Waiting for 2049. > [2006-08-07 16:54:32 xend] DEBUG (DevController:403) > hotplugStatusCallback > /local/domain/0/backend/vbd/4/2049/hotplug-status. > [2006-08-07 16:54:32 xend] DEBUG (DevController:417) hotplugStatusCallback 2. > [2006-08-07 16:54:32 xend.XendDomainInfo] DEBUG (XendDomainInfo:1327) > XendDomainInfo.destroy: domid=4 > [2006-08-07 16:54:32 xend.XendDomainInfo] DEBUG (XendDomainInfo:1335) > XendDomainInfo.destroyDomain(4) > > > > Maybe can something be wrong in /etc/xen/xend-config.sxp ? Now is > uncommented only: > (network-script network-bridge) > (network-script network-dummy) > (vif-script vif-bridge) > > > > Thanks > Stefano > > _______________________________________________ > 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
2006/8/7, Eric Peterson <srcfoo@gmail.com>:> Try ''modprobe loop'' in domain 0 before trying to start your guest domains.Yes, it''s working... now I''ll work on IP configuration. Thanks Stefano _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Just to add my two cents worth and experience from last night. Got my
Debian Sarge domU''s up and running for the first time.
Within dom0:-
# to allow me to have 32 domUs. Each one will use a two loopback devices.
rmmod loop && modprobe loop max_loop=64
# for each domU''s config file in /etc/xen/foo
# each one ghas a unique mac addy
vif = [ ''<mac address>'' ,
''bri=xenbr0'']
# set up your domU''s interface as required by your distro.
# I''m using sarge as domU
# /etc/{resolv.conf,hosts,hostname}, /etc/network/interfaces
That''s all well and good for Debian Sarge but *nothing* is happening
for CentOS domU''s. Anyone got examples of config files for
/etc/sysconfig/networking-scripts and
/etc/sysconfig/networking/devices ?
On 08/08/06, Stefano Cislaghi <s.cislaghi@gmail.com>
wrote:> 2006/8/7, Eric Peterson <srcfoo@gmail.com>:
> > Try ''modprobe loop'' in domain 0 before trying to
start your guest domains.
>
> Yes, it''s working... now I''ll work on IP configuration.
>
> Thanks
> Stefano
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
--
John Maclean - 07739 171 531
MSc (DIC)
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
2006/8/8, john maclean <jayeola@gmail.com>:> Just to add my two cents worth and experience from last night. Got my > Debian Sarge domU''s up and running for the first time. >For me problem is this: domU is running. I''m using bridged configuration. brctl show my bridge up. domU is 90.90.90.217 and dom0 is 90.90.90.216. dom0 can ping domU domU can ping dom0 dom0 can browse internet without problem. domU can ping an host in the same network and also can ping the gateway. A machine in the same network can ping and ssh to domU. domU cannot ping outside gateway and from outside there''s no way to ping or ssh to domU. This is very strange! in dom0 i have: xen:~# brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no peth0 vif0.0 vif5.0 xen:~# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-in vif5.0 Chain OUTPUT (policy ACCEPT) target prot opt source destination Configuration is: # network vif=[ '''' ] dhcp="off" ip="90.90.90.217" netmask="255.255.255.192" gateway="90.90.90.193" hostname="vx1.my.domain" extra="3" Routing on domU it''s ok... default GW is loaded. Any trick? Stefano _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ah, I used dhcp as my knowledge of networking is rather limited. Gave me no trouble at all and all of my domUs are pining ssh''ing and wget''ing away merrily. On 08/08/06, Stefano Cislaghi <s.cislaghi@gmail.com> wrote:> 2006/8/8, john maclean <jayeola@gmail.com>: > > Just to add my two cents worth and experience from last night. Got my > > Debian Sarge domU''s up and running for the first time. > > > > For me problem is this: > > domU is running. I''m using bridged configuration. brctl show my bridge > up. domU is 90.90.90.217 and dom0 is 90.90.90.216. > > dom0 can ping domU > domU can ping dom0 > dom0 can browse internet without problem. > domU can ping an host in the same network and also can ping the gateway. > A machine in the same network can ping and ssh to domU. > domU cannot ping outside gateway and from outside there''s no way to > ping or ssh to domU. > > This is very strange! > > > in dom0 i have: > > xen:~# brctl show > bridge name bridge id STP enabled interfaces > xenbr0 8000.feffffffffff no peth0 > vif0.0 > vif5.0 > xen:~# iptables -L > Chain INPUT (policy ACCEPT) > target prot opt source destination > > Chain FORWARD (policy ACCEPT) > target prot opt source destination > ACCEPT all -- anywhere anywhere PHYSDEV > match --physdev-in vif5.0 > > Chain OUTPUT (policy ACCEPT) > target prot opt source destination > > > Configuration is: > > # network > vif=[ '''' ] > dhcp="off" > ip="90.90.90.217" > netmask="255.255.255.192" > gateway="90.90.90.193" > hostname="vx1.my.domain" > > extra="3" > > > Routing on domU it''s ok... default GW is loaded. Any trick? > > > Stefano > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- John Maclean - 07739 171 531 MSc (DIC) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users