bash-3.2# dladm show-link
LINK CLASS MTU STATE OVER
elxl0 phys 1500 unknown --
bash-3.2# svccfg -s xend listprop|grep default-nic
config/default-nic astring elxl0
Prepare to install:-
bash-3.2# ls -l
total 24021968
-rw-r--r-- 1 root root 3876421632 Apr 5 14:21 f8.iso
-rw-r--r-- 1 root root 4442685440 Apr 5 13:59 RHEL51.iso
-rw-r--r-- 1 root root 3974103040 Apr 4 12:02 snv85.iso
bash-3.2# lofiadm -a /export/home/isos/RHEL51.iso
/dev/lofi/1
bash-3.2# mount -o ro -F hsfs /dev/lofi/1 /mnt
bash-3.2# share -F nfs /mnt
********************
Run virt-install:-
********************
bash-3.2# virt-install -n CentOS51 -r 512 --vcpus=1 --nographics --os-type=linux
\
-p -f /dev/zvol/dsk/vmpool/snv85-disk -l nfs:192.168.1.41:/mnt -d
Starting install...
libvir: Xen Daemon error : GET operation failed:
Sat, 05 Apr 2008 14:46:34 DEBUG Preparing mount at
/var/lib/xen/virtinstmnt.-UNNat
Sat, 05 Apr 2008 14:46:34 DEBUG Acquiring file from
/var/lib/xen/virtinstmnt.-UNNat/Fedora
Sat, 05 Apr 2008 14:46:34 DEBUG Cannot find file Fedora
Sat, 05 Apr 2008 14:46:34 DEBUG Acquiring file from
/var/lib/xen/virtinstmnt.-UNNat/Server
Sat, 05 Apr 2008 14:46:34 DEBUG Cannot find file Server
Sat, 05 Apr 2008 14:46:34 DEBUG Acquiring file from
/var/lib/xen/virtinstmnt.-UNNat/RedHat
Sat, 05 Apr 2008 14:46:34 DEBUG Cannot find file RedHat
Sat, 05 Apr 2008 14:46:34 DEBUG Acquiring file from
/var/lib/xen/virtinstmnt.-UNNat/CentOS
Sat, 05 Apr 2008 14:46:34 DEBUG Found a directory
Sat, 05 Apr 2008 14:46:34 DEBUG Detected a CentOS distro
Sat, 05 Apr 2008 14:46:34 DEBUG Acquiring file from
/var/lib/xen/virtinstmnt.-UNNat/images/xen/vmlinuz
Sat, 05 Apr 2008 14:48:04 DEBUG Saved file to
/var/lib/xen/virtinst-vmlinuz.g6ZzaX
Sat, 05 Apr 2008 14:48:04 DEBUG Acquiring file from
/var/lib/xen/virtinstmnt.-UNNat/images/xen/initrd.img
Sat, 05 Apr 2008 14:48:04 DEBUG Saved file to
/var/lib/xen/virtinst-initrd.img.3f7zza
Sat, 05 Apr 2008 14:48:04 DEBUG Cleaning up mount at
/var/lib/xen/virtinstmnt.-UNNat
libvir: Xen Daemon error : GET operation failed:
Sat, 05 Apr 2008 14:48:04 DEBUG Creating guest from ''<domain
type=''xen''>
<name>CentOS51</name>
<currentMemory>524288</currentMemory>
<memory>524288</memory>
<uuid>0bc0af1a-7359-903e-1fcf-745172cd3942</uuid>
<os>
<type>linux</type>
<kernel>/var/lib/xen/virtinst-vmlinuz.g6ZzaX</kernel>
<initrd>/var/lib/xen/virtinst-initrd.img.3f7zza</initrd>
<cmdline> method=nfs:192.168.1.41:/mnt</cmdline>
</os>
<on_poweroff>destroy</on_poweroff>
<on_reboot>destroy</on_reboot>
<on_crash>destroy</on_crash>
<vcpu>1</vcpu>
<devices>
<disk type=''block''
device=''disk''>
<source
dev=''/dev/zvol/dsk/vmpool/snv85-disk''/>
<target dev=''xvda''/>
</disk>
<interface type=''bridge''>
<source bridge=''''/>
<mac address=''00:16:3e:02:63:ff''/>
</interface>
</devices>
</domain>
''
libvir: Xen Daemon error : POST operation failed: (xend.err ''Device 0
(vif) could not be connected. Backend device not found.'')
Sat, 05 Apr 2008 14:48:07 DEBUG Removing /var/lib/xen/virtinst-vmlinuz.g6ZzaX
Sat, 05 Apr 2008 14:48:07 DEBUG Removing
/var/lib/xen/virtinst-initrd.img.3f7zza
Traceback (most recent call last):
File "/usr/bin/virt-install", line 657, in ?
main()
File "/usr/bin/virt-install", line 606, in main
dom = guest.start_install(conscb,progresscb)
File
"/export/builds/xvm_85/proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py",
line 638, in start_install
File
"/export/builds/xvm_85/proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py",
line 655, in _do_install
File "/usr/lib/python2.4/vendor-packages/libvirt.py", line 585, in
createLinux
if ret is None:raise libvirtError(''virDomainCreateLinux()
failed'', conn=self)
libvirt.libvirtError: virDomainCreateLinux() failed POST operation failed:
(xend.err ''Device 0 (vif) could not be connected. Backend device not
found.'')
bash-3.2#
This message posted from opensolaris.org
> libvir: Xen Daemon error : POST operation failed: (xend.err ''Device > 0 (vif) could not be connected. Backend device not found.'')I think that is your elxl0 card not having a GLDv3 driver On my build 81 system (where I''m using e1000g for my centOS install) root@frank / $ dladm show-link e1000g0 type: non-vlan mtu: 1500 device: e1000g0 rge0 type: non-vlan mtu: 1500 device: rge0 elxl0 type: legacy mtu: 1500 device: elxl0 Please note: apparently the format of dvladm command has changed in 85 see: http://www.opensolaris.org/jive/thread.jspa?messageID=217732&tstart=0 try dladm show-phys according to linked post. (can''t test as havn''t had time to go to build 81 yet) (this is in response to your comment at http://jameslegg.blogspot.com/2008/02/centos-5-dom0-out-of-thin-air.html) -- Cheers James (I havn''t had time to move on from 81 recently so can''t test) On 5 Apr 2008, at 19:57, Boris Derzhavets wrote:> bash-3.2# dladm show-link > LINK CLASS MTU STATE OVER > elxl0 phys 1500 unknown -- > bash-3.2# svccfg -s xend listprop|grep default-nic > config/default-nic astring elxl0 > Prepare to install:- > bash-3.2# ls -l > total 24021968 > -rw-r--r-- 1 root root 3876421632 Apr 5 14:21 f8.iso > -rw-r--r-- 1 root root 4442685440 Apr 5 13:59 RHEL51.iso > -rw-r--r-- 1 root root 3974103040 Apr 4 12:02 snv85.iso > bash-3.2# lofiadm -a /export/home/isos/RHEL51.iso > /dev/lofi/1 > bash-3.2# mount -o ro -F hsfs /dev/lofi/1 /mnt > bash-3.2# share -F nfs /mnt > ******************** > Run virt-install:- > ******************** > > bash-3.2# virt-install -n CentOS51 -r 512 --vcpus=1 --nographics -- > os-type=linux \ > -p -f /dev/zvol/dsk/vmpool/snv85-disk -l nfs:192.168.1.41:/mnt -d > > Starting install... > > libvir: Xen Daemon error : GET operation failed: > > Sat, 05 Apr 2008 14:46:34 DEBUG Preparing mount at /var/lib/xen/ > virtinstmnt.-UNNat > > Sat, 05 Apr 2008 14:46:34 DEBUG Acquiring file from /var/lib/xen/ > virtinstmnt.-UNNat/Fedora > > Sat, 05 Apr 2008 14:46:34 DEBUG Cannot find file Fedora > > Sat, 05 Apr 2008 14:46:34 DEBUG Acquiring file from /var/lib/xen/ > virtinstmnt.-UNNat/Server > > Sat, 05 Apr 2008 14:46:34 DEBUG Cannot find file Server > > Sat, 05 Apr 2008 14:46:34 DEBUG Acquiring file from /var/lib/xen/ > virtinstmnt.-UNNat/RedHat > > Sat, 05 Apr 2008 14:46:34 DEBUG Cannot find file RedHat > > Sat, 05 Apr 2008 14:46:34 DEBUG Acquiring file from /var/lib/xen/ > virtinstmnt.-UNNat/CentOS > > Sat, 05 Apr 2008 14:46:34 DEBUG Found a directory > > Sat, 05 Apr 2008 14:46:34 DEBUG Detected a CentOS distro > > Sat, 05 Apr 2008 14:46:34 DEBUG Acquiring file from /var/lib/xen/ > virtinstmnt.-UNNat/images/xen/vmlinuz > > Sat, 05 Apr 2008 14:48:04 DEBUG Saved file to /var/lib/xen/ > virtinst-vmlinuz.g6ZzaX > > Sat, 05 Apr 2008 14:48:04 DEBUG Acquiring file from /var/lib/xen/ > virtinstmnt.-UNNat/images/xen/initrd.img > > Sat, 05 Apr 2008 14:48:04 DEBUG Saved file to /var/lib/xen/ > virtinst-initrd.img.3f7zza > > Sat, 05 Apr 2008 14:48:04 DEBUG Cleaning up mount at /var/lib/xen/ > virtinstmnt.-UNNat > > libvir: Xen Daemon error : GET operation failed: > > Sat, 05 Apr 2008 14:48:04 DEBUG Creating guest from ''<domain > type=''xen''> > > <name>CentOS51</name> > > <currentMemory>524288</currentMemory> > > <memory>524288</memory> > > <uuid>0bc0af1a-7359-903e-1fcf-745172cd3942</uuid> > > <os> > > <type>linux</type> > > <kernel>/var/lib/xen/virtinst-vmlinuz.g6ZzaX</kernel> > > <initrd>/var/lib/xen/virtinst-initrd.img.3f7zza</ > initrd> > > <cmdline> method=nfs:192.168.1.41:/mnt</cmdline> > > </os> > > <on_poweroff>destroy</on_poweroff> > > <on_reboot>destroy</on_reboot> > > <on_crash>destroy</on_crash> > > <vcpu>1</vcpu> > > <devices> > > <disk type=''block'' device=''disk''> > > <source dev=''/dev/zvol/dsk/vmpool/snv85-disk''/> > > <target dev=''xvda''/> > > </disk> > > > > <interface type=''bridge''> > > <source bridge=''''/> > > <mac address=''00:16:3e:02:63:ff''/> > > </interface> > > > > > > </devices> > > </domain> > > '' > > libvir: Xen Daemon error : POST operation failed: (xend.err ''Device > 0 (vif) could not be connected. Backend device not found.'') > > Sat, 05 Apr 2008 14:48:07 DEBUG Removing /var/lib/xen/virtinst- > vmlinuz.g6ZzaX > > Sat, 05 Apr 2008 14:48:07 DEBUG Removing /var/lib/xen/virtinst- > initrd.img.3f7zza > > Traceback (most recent call last): > > File "/usr/bin/virt-install", line 657, in ? > > main() > > File "/usr/bin/virt-install", line 606, in main > > dom = guest.start_install(conscb,progresscb) > > File "/export/builds/xvm_85/proto/install/usr/lib/python2.4/site- > packages/virtinst/Guest.py", line 638, in start_install > > File "/export/builds/xvm_85/proto/install/usr/lib/python2.4/site- > packages/virtinst/Guest.py", line 655, in _do_install > > File "/usr/lib/python2.4/vendor-packages/libvirt.py", line 585, in > createLinux > > if ret is None:raise libvirtError(''virDomainCreateLinux() > failed'', conn=self) > > libvirt.libvirtError: virDomainCreateLinux() failed POST operation > failed: (xend.err ''Device 0 (vif) could not be connected. Backend > device not found.'') > > bash-3.2# > > > This message posted from opensolaris.org > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
Boris Derzhavets
2008-Apr-06 05:31 UTC
Re: Failure to install CentOS 5.1 DomU at SNV85 Dom0
You are right. Install runs fine on another system with "rge0". Thank you. Boris This message posted from opensolaris.org
Boris Derzhavets
2008-Apr-06 07:55 UTC
Re: Failure to install CentOS 5.1 DomU at SNV85 Dom0
Runtime snapshot attached. This message posted from opensolaris.org
ssh connection from DomU to SNV 85 Dom0 has been established. Several reports have been run at Dom0 and "xm list -l RHEL51PVM" , in particular. One question is still up:- SNV Dom0 is connected to ADSL modem , acting as DHCP Bridge. Ethernet interface "rge0", connecting Dom0 to modem, is default NIC for xend. I can ping modem and ISP''s DNS servers from Linux DomU, however i don''t have access to internet (firewall disabled, ip-forwarding is up on DomU and Dom0). Browser is " Looking up .." for ever. It never happened to me on Linux Dom0s This message posted from opensolaris.org
As you have connectivity from within the CentOS DomU to the solaris Host I suspect you have NAT/routing issues. At a guess you need to add a default route on your DomU but you don''t quite provide enough info to say for sure. If you can contact any other hosts on your network from the CentOS DomU then I would say it is almost definitely a route issue and not related to the fact that the machine is virtualised. netstat -rn on the CentOS domU will help. On 6 Apr 2008, at 14:54, Boris Derzhavets wrote:> ssh connection from DomU to SNV 85 Dom0 has been established. > Several reports have been run at Dom0 and "xm list -l RHEL51PVM" , > in particular. > One question is still up:- > SNV Dom0 is connected to ADSL modem , acting as DHCP Bridge. > Ethernet interface "rge0", connecting Dom0 to modem, is default NIC > for xend. > I can ping modem and ISP''s DNS servers from Linux DomU, however > i don''t have access to internet (firewall disabled, ip-forwarding is > up > on DomU and Dom0). > Browser is " Looking up .." for ever. > It never happened to me on Linux Dom0s > > > This message posted from > opensolaris > .org > < > R2.png><R3.png><R4.png>_______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
Bernd Schemmer
2008-Apr-06 18:39 UTC
Re: Internet access from CentOS 5.1 DomU at SNV85 Dom0
Hi, did you already check that it''s not the old checksum problem again? e.g. execute ethtool -K eth0 tx off in the Linux DomU? regards Bernd Boris Derzhavets wrote:> ssh connection from DomU to SNV 85 Dom0 has been established. > Several reports have been run at Dom0 and "xm list -l RHEL51PVM" , > in particular. > One question is still up:- > SNV Dom0 is connected to ADSL modem , acting as DHCP Bridge. > Ethernet interface "rge0", connecting Dom0 to modem, is default NIC > for xend. > I can ping modem and ISP''s DNS servers from Linux DomU, however > i don''t have access to internet (firewall disabled, ip-forwarding is up > on DomU and Dom0). > Browser is " Looking up .." for ever. > It never happened to me on Linux Dom0s > > > This message posted from opensolaris.org > > ------------------------------------------------------------------------ > > > ------------------------------------------------------------------------ > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------ > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org-- Bernd Schemmer, Frankfurt am Main, Germany http://home.arcor.de/bnsmb/index.html M s temprano que tarde el mundo cambiar . Fidel Castro
Bernd Markgraf
2008-Apr-06 18:50 UTC
Re: Internet access from CentOS 5.1 DomU at SNV85 Dom0
On Sun, 2008-04-06 at 20:39 +0200, Bernd Schemmer wrote:> Hi, > > did you already check that it''s not the old checksum problem again? > > e.g. > > execute > > ethtool -K eth0 tx off > > in the Linux DomU?I bet it is. I''ve seen the same problem in a Fedora 8 domU. I colud ping the host system and all boxes on the same subnet. All real data (name service, ssh etc) just didn''t work . Bernd
Boris Derzhavets
2008-Apr-06 19:06 UTC
Re: Failure to install CentOS 5.1 DomU at SNV85 Dom0
> > libvir: Xen Daemon error : POST operation failed: > (xend.err ''Device > > 0 (vif) could not be connected. Backend device not > > see: > http://www.opensolaris.org/jive/thread.jspa?messageID> 217732&tstart=0 > > try dladm show-phys according to linked post. (can''t > test as havn''t > had time to go to build 81 yet) > found.'') > > > I think that is your elxl0 card not having a GLDv3 > driver > > On my build 81 system (where I''m using e1000g for my > centOS install) > > root@frank / $ dladm show-link > e1000g0 type: non-vlan mtu: 1500 device: e1000g0 > rge0 type: non-vlan mtu: 1500 device: rge0 > elxl0 type: legacy mtu: 1500 device: elxl0 > > Please note: apparently the format of dvadm command > has changed in 85:-Yes, that is right at SNV85 Dom0:- bash-3.2# dladm show-dev LINK STATE SPEED DUPLEX elxl0 unknown 0Mb half bash-3.2# dladm show-link LINK CLASS MTU STATE OVER elxl0 phys 1500 unknown --> > (this is in response to your comment at > http://jameslegg.blogspot.com/2008/02/centos-5-dom0-ou > t-of-thin-air.html) > > -- > Cheers > JamesThis message posted from opensolaris.org
Bernd Schemmer
2008-Apr-06 20:46 UTC
Re: Internet access from CentOS 5.1 DomU at SNV85 Dom0
Looks like -- I just installed a Solaris snv_85 DomU in a Solaris snv_85 Dom0 and I had to disable the checksum offload to get working network connection. Bernd Bernd Markgraf wrote:> On Sun, 2008-04-06 at 20:39 +0200, Bernd Schemmer wrote: > >> Hi, >> >> did you already check that it''s not the old checksum problem again? >> >> e.g. >> >> execute >> >> ethtool -K eth0 tx off >> >> in the Linux DomU? >> > I bet it is. I''ve seen the same problem in a Fedora 8 domU. I colud ping > the host system and all boxes on the same subnet. All real data (name > service, ssh etc) just didn''t work . > > Bernd > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org > >-- Bernd Schemmer, Frankfurt am Main, Germany http://home.arcor.de/bnsmb/index.html M s temprano que tarde el mundo cambiar . Fidel Castro
Boris Derzhavets
2008-Apr-07 05:22 UTC
Re: Internet access from CentOS 5.1 DomU at SNV85 Dom0
Communications between Linux DomU and SNV 85 Dom0 are fine.
Including vncviewer 192.168.1.27 :1 at Dom0
Looks like routing issue.
*******************************************************************
SNV85 Dom0 - 192.168.1.35 (dhcp)
Current SNV 85 box - 192.168.1.37 (dhcp)
Linux DomU at SNV85 Dom0 - 192.168.1.27 (static)
*******************************************************************
DomU is pingable from current SNV 85 box and can ping current SNV 85 box.
However from current box (192.168.1.37) :-
bash-3.2# hostname
Solaris85X312
bash-3.2# ssh root@192.167.1.27
. . . . . . . . . . . (** hangs **)
#xhost +
access control disabled, clients can connect from any host
bash-3.2# ping 192.168.1.27
192.168.1.27 is alive
bash-3.2# vncviewer 192.168.1.27:1
VNC Viewer Free Edition 4.1.2 for X - built Mar 3 2008 20:21:29
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Mon Apr 7 01:09:47 2008
CConn: connected to host 192.168.1.27 port 5901 (** hangs **)
^C
Mon Apr 7 01:10:02 2008
main: CleanupSignalHandler called
*****************************************************
SSH connection to Dom0 from current box
*****************************************************
bash-3.2# ssh boris@192.168.1.35
Password:
Last login: Mon Apr 7 06:05:37 2008 from 192.168.1.37
Sun Microsystems Inc. SunOS 5.11 snv_85 January 2008
-bash-3.2$ hostname
solaris85
-bash-3.2$ export DISPLAY=192.168.1.37:0.0
-bash-3.2$ vncviewer 192.168.1.27:1
VNC Viewer Free Edition 4.1.2 for X - built Mar 3 2008 20:21:29
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
vncviewer: unable to open display "192.168.1.37:0.0"
-bash-3.2$ vncviewer 192.168.1.27:1
VNC Viewer Free Edition 4.1.2 for X - built Mar 3 2008 20:21:29
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
vncviewer: unable to open display "192.168.1.37:0.0"
**************************************************
Attempt to connect to DomU from Dom0
**************************************************
-bash-3.2$ ssh root@192.168.1.27
The authenticity of host ''192.168.1.27 (192.168.1.27)''
can''t be established.
RSA key fingerprint is 30:35:a1:ee:dc:13:c8:ef:02:4e:b6:92:20:e0:e7:5d.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added ''192.168.1.27'' (RSA) to the list of
known hosts.
root@192.168.1.27''s password:
Last login: Mon Apr 7 01:14:14 2008 from 192.168.1.35
[root@RHL51PVM ~]# uname -a
Linux RHL51PVM 2.6.18-53.el5xen #1 SMP Mon Nov 12 02:46:57 EST 2007 x86_64
x86_64 x86_64 GNU/Linux
[root@RHL51PVM ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
20G 4.2G 15G 23% /
/dev/xvda1 99M 13M 81M 14% /boot
tmpfs 512M 0 512M 0% /dev/shm
[root@RHL51PVM ~]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:3E:72:F0:C1
inet addr:192.168.1.27 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::216:3eff:fe72:f0c1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3019 errors:0 dropped:0 overruns:0 frame:0
TX packets:5638 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:180728 (176.4 KiB) TX bytes:6108131 (5.8 MiB)
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)
[root@RHL51PVM ~]# ping 192.168.1.37
PING 192.168.1.37 (192.168.1.37) 56(84) bytes of data.
64 bytes from 192.168.1.37: icmp_seq=1 ttl=255 time=1.97 ms
64 bytes from 192.168.1.37: icmp_seq=2 ttl=255 time=0.164 ms
64 bytes from 192.168.1.37: icmp_seq=3 ttl=255 time=0.163 ms
64 bytes from 192.168.1.37: icmp_seq=4 ttl=255 time=0.159 ms
--- 192.168.1.37 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3001ms
rtt min/avg/max/mdev = 0.159/0.616/1.979/0.786 ms
This message posted from opensolaris.org
Boris Derzhavets
2008-Apr-07 05:41 UTC
Re: Internet access from CentOS 5.1 DomU at SNV85 Dom0
SNV85 DomU at SNV85 Dom0 works fine through my experience. This message posted from opensolaris.org
Boris Derzhavets
2008-Apr-07 07:54 UTC
Re: Internet access from CentOS 5.1 DomU at SNV85 Dom0
> > On Sun, 2008-04-06 at 20:39 +0200, Bernd Schemmer > wrote: > > Hi, > > > > did you already check that it''s not the old > checksum problem again? > > > > e.g. > > > > execute > > > > ethtool -K eth0 tx off > > > > in the Linux DomU? > I bet it is. I''ve seen the same problem in a Fedora 8 > domU. I colud ping > the host system and all boxes on the same subnet. All > real data (name > service, ssh etc) just didn''t work .Through my experience:- *************************************************************************************** If you installed dnsmasq service and all members of Virtualization group properly. Daemons libvirtd & dnsmasq (as DHCP server) will provide bridging and NAT forwarding from F8 Dom0 to any DomU (SNV85,F8,..) on subnet 192.168.122.1 (netmask 255.255.255.0) perfectly. Phyton profiles of DomUs should have entry:- vif=[''bridge=virbr0''] Othewise F8 install along with Xen has to run on box connected to DHCP Bridge.Finally "brctl show" will provide you two bridges. Entry like vif=['' ''] will use xen bridge based on ethernet interface connected Physical DHCP Bridge Device and will put DomU on the same subnet with Dom0 with old fashion xen bridging implemented. Tuning /etc/xen/xend-conf.sxp is different for case one and case two. RHEL 5.1 behaves same way and installs service "dnsmasq" automatically. **************************************************************************************> > Bernd > ______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.orgThis message posted from opensolaris.org
Boris Derzhavets
2008-Apr-07 08:33 UTC
Re: Internet access from CentOS 5.1 DomU at SNV85 Dom0
SNV85 DomU running at F8 (RHEL 5.1) Dom0 , been placed on DHCP Bridge from ISP, goes to Internet right away. Either woks fine throgh remote Proxy Server on the same LAN. Oracle 10g database been installed on such kind of SNV85 DomU is visible across the LAN perfectly. This message posted from opensolaris.org
Boris Derzhavets
2008-Apr-08 06:38 UTC
Re: Internet access from CentOS 5.1 DomU at SNV85 Dom0
> As you have connectivity from within the CentOS DomU > to the solaris > Host I suspect you have NAT/routing issues. > > At a guess you need to add a default route on your > DomU but you don''t > quite provide enough info to say for sure. > > If you can contact any other hosts on your network > from the CentOS > DomU then I would say it is almost definitely a route > issue and not > related to the fact that the machine is virtualised. > > netstat -rn on the CentOS domU will help.Sorry, i found solution for LAN issues :- At Linux DomU run:- # route add -net 192.168.1.0 netmask 255.255.255.0 gw 192.168.1.35 where 192.168.1.35 IP-address of SNV85 Dom0. Still no luck with internet access. [root@RHL51pvm ~]# netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.1.0 192.168.1.35 255.255.255.0 UG 0 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 Actually, first line has been added This message posted from opensolaris.org
Boris Derzhavets
2008-Jul-17 09:09 UTC
Re: Internet access from CentOS 5.1 DomU at SNV85 Dom0
Thank you , it worked and works fine. This message posted from opensolaris.org
Boris Derzhavets
2008-Jul-22 18:32 UTC
Re: Internet access from CentOS 5.1 DomU at SNV85 Dom0
> > Looks like -- I just installed a Solaris snv_85 DomU > in a Solaris snv_85 > Dom0 and I had to disable the checksum offload to get > working network > connection.In my case it''s not xnf->xnb issue . 1. If default-nic="rtls0" then Solaris snv_93 DomU at Solaris snv_93 Dom0 network connection is fine. 2. If default-nic="rge0" then Solaris snv_93 DomU at Solaris snv_93 Dom0 requires to disable the checksum offload at DomU to get working network connection. Through my experience the cause might be broken network driver at Dom0 ( like "rge")> > Bernd > > > Bernd Markgraf wrote: > > On Sun, 2008-04-06 at 20:39 +0200, Bernd Schemmer > wrote: > > > >> Hi, > >> > >> did you already check that it''s not the old > checksum problem again? > >> > >> e.g. > >> > >> execute > >> > >> ethtool -K eth0 tx off > >> > >> in the Linux DomU? > >> > > I bet it is. I''ve seen the same problem in a Fedora > 8 domU. I colud ping > > the host system and all boxes on the same subnet. > All real data (name > > service, ssh etc) just didn''t work . > > > > Bernd > > > > _______________________________________________ > > xen-discuss mailing list > > xen-discuss@opensolaris.org > > > > > > > -- > Bernd Schemmer, Frankfurt am Main, Germany > http://home.arcor.de/bnsmb/index.html > > M s temprano que tarde el mundo cambiar . > Fidel Castro > ________________________ > xen-discuss mailing list > xen-discuss@opensolaris.orgThis message posted from opensolaris.org