Boris Derzhavets
2008-Feb-12 15:30 UTC
Attempt to configure SNV81 DomU with DHCP at F8 (32 bit) Dom0
I’ve placed F8 Dom0 box on DHCP bridge. Service “dnsmasq” behaves exactly the same way as on F8 Dom0 box with static IP :- It serves dhcp requests from RH DomUs and refuse to serve dhcp request from SNV76,78,81 DomUs . Any dhcp request from SNV DomU gets timed out. Regarding CentOS 5.1 Dom0 boxes, everything works just fine and doesn’t depend on network config for Dom0:- “dnsmasq” serves dhcp request from SNV76,78,81 with no delays I guess, if eth0 is configured as DHCP at Linux Dom0, to create SNV DomU with xnf0 configured as DHCP i need an entry into xend-config.sxp. (network-script 'network-bridge bridge=xenbr0 netdev=eth0') been read by xend daemon at boot up so that:- root@UbuntuGutsy:~# brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no vif0.0 peth0 It seems , that libvirtd daemon built in behavior at F8 Dom0 doesn't allow to do that and does allow to do that at CentOS 5.1 Dom0:- # chkconfig libvirtd off I cannot disable libvirtd on F8 to turn off virbr0 and work with old fashioned xen-bridge. External DHCP Server appears to be useless for me on Fedoras However, due to multiple MRJ's feedbacks i understand , that someting has been done incorrect. This message posted from opensolaris.org _______________________________________________ xen-discuss mailing list xen-discuss@opensolaris.org
Mark Johnson
2008-Feb-12 15:50 UTC
Re: Attempt to configure SNV81 DomU with DHCP at F8 (32 bit) Dom0
Boris Derzhavets wrote:> I’ve placed F8 Dom0 box on DHCP bridge. Service “dnsmasq” > behaves exactly the same way as on F8 Dom0 box with static IP :- > It serves dhcp requests from RH DomUs and refuse to serve dhcp request > from SNV76,78,81 DomUs . Any dhcp request from SNV DomU > gets timed out. > Regarding CentOS 5.1 Dom0 boxes, everything works just fine and doesn’t > depend on network config for Dom0:- > “dnsmasq” serves dhcp request from SNV76,78,81 with no delays > > I guess, if eth0 is configured as DHCP at Linux Dom0, to create SNV DomU > with xnf0 configured as DHCP i need an entry into xend-config.sxp. > > (network-script 'network-bridge bridge=xenbr0 netdev=eth0') > > been read by xend daemon at boot up so that:- > > root@UbuntuGutsy:~# brctl show > > bridge name bridge id STP enabled interfaces > xenbr0 8000.feffffffffff no vif0.0 > > peth0 > > It seems , that libvirtd daemon built in behavior at F8 Dom0 > doesn't allow to do that and does allow to do that at CentOS 5.1 Dom0:- > # chkconfig libvirtd off > I cannot disable libvirtd on F8 to turn off virbr0 and work with old fashioned > xen-bridge. External DHCP Server appears to be useless for me on Fedoras > However, due to multiple MRJ's feedbacks i understand , that someting > has been done incorrect.It could be that they recently change something in FC8? I haven't sync'd up recently. MRJ _______________________________________________ xen-discuss mailing list xen-discuss@opensolaris.org
Boris Derzhavets
2008-Feb-12 15:56 UTC
Re: Attempt to configure SNV81 DomU with DHCP at F8 (32 bit) Dom0
> It could be that they recently change something in > FC8? I haven''t sync''d > up recently.Does your statement mean, that you just turned into old fashioned xen-bridging , having libvirtd daemon (as well as virbr0 ) disabled on F8 ?> > > > MRJ > > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.orgThis message posted from opensolaris.org
Boris Derzhavets
2008-Feb-13 10:16 UTC
Re: Attempt to configure SNV81 DomU with DHCP at F8 (32 bit) Dom0
This thread follows up another one:- ********************************************************** Thread: Xen 3.1 Linux Dom0 (x86_64) & PYGRUB ********************************************************** http://www.opensolaris.org/jive/thread.jspa?threadID=45488&tstart=30 This message posted from opensolaris.org
Boris Derzhavets
2008-Feb-13 11:31 UTC
Re: Attempt to configure SNV81 DomU with DHCP at F8 (32 bit) Dom0
I believe the answer how to get access to DHCP Server having libvirtd up and running follows bellow (thanks Google) :- http://marc.info/?l=fedora-xen&m=119646437601158&w=2 Quote:- I have a bridge on VLAN 6 so I call it br6 you can use xenbr0 is you like. Mine mostly looks something like this after removing the VLAN trunk complication: # cat ifcfg-eth0 DEVICE=eth0 BOOTPROTO=none ONBOOT=yes BRIDGE=br6 # cat ifcfg-br6 DEVICE=br6 TYPE=Bridge BOOTPROTO=static ONBOOT=yes IPADDR=10.10.6.1 NETMASK=255.255.255.0 NETWORK=10.10.6.0 BROADCAST=10.10.6.255 Now your primary IP of your dom0 lives on the br6 interface. Your domU''s will be on the same VLAN and should see your DHCP server. Don''t forget to enable IP forwarding. # grep phys /etc/sysconfig/iptables -A FORWARD -m physdev --physdev-is-bridged -j ACCEPT # grep forward /etc/sysctl.conf # Controls IP packet forwarding net.ipv4.ip_forward = 1 p.s. use ''brctl show'' to see your bridges. This message posted from opensolaris.org
F7 Dom0 (64 bit) installed with static IP. /etc/xen/xend-config.sxp modified as follows:- # (network-script network-bridge) #### LAPTOP USERS ! ##### # For laptops, or machines where network interfaces come/go on-the-fly, # or are otherwise managed by NetworkManager, comment out the above line. # Then, uncomment the line below, and use libvirt''s virtual networking # capability which sets up a isolated bridge + NAT forwarding (network-script /bin/true) # service xend restart Both services libvirtd and dnsmasq are up and running. Interface virbr0 actived 192.168.122.1 SNV 81 installed with DHCP option on libvirtd (dnsmasq) network. In case when vif=['' ''] [root@fedora7xen vm]# brctl show bridge name bridge id STP enabled interfaces tmpbridge 8000.feffffffffff no vif5.0 virbr0 8000.000000000000 no and DHCP request to libvirtd''s network times out In case when vif=[''bridge = virbr0''] [root@fedora7xen vm]# brctl show bridge name bridge id STP enabled interfaces tmpbridge 8000.000000000000 no virbr0 8000.feffffffffff no vif6.0 DHCP request to libvirtd''s network succeseeded in 1-2 minutes Installation profile:- name = "Solaris81" vcpus = 1 memory = "1024" kernel = "/usr/lib/xen-solaris/unix-81" ramdisk = "/usr/lib/xen-solaris/x86.miniroot-81" extra = "/platform/i86xpv/kernel/amd64/unix - nowin -B install_media=cdrom" disk = [''file:/usr/lib/xen-solaris/snv81.iso,6:cdrom,r'',''phy:/dev/sdb7,0,w''] vif = [''bridge = virbr0''] on_shutdown = "destroy" on_reboot = "destroy" on_crash = "destroy" Runtime profile:- name = "Solaris81" vcpus = 1 memory = "1024" kernel = "/usr/lib/xen-solaris/unix-81" ramdisk = "/usr/lib/xen-solaris/x86.miniroot-81" extra = "/platform/i86xpv/kernel/amd64/unix" disk = [''phy:/dev/sdb7,0,w''] vif = [''bridge = virbr0''] root= "/dev/dsk/c0d0s0" on_shutdown = "destroy" on_reboot = "destroy" on_crash = "destroy" This message posted from opensolaris.org