Hi,
>>>>Does it also work for para-virtualized DomUs?
>>If the device in question has a GLDv3 driver, then yes (but see
6592059, which means that it doesn't work for wireless NICs).
I tested this with a para-virtualized DomU and it works (see below).
But it's a little bit confusing that the dedicated adapter is still
visible in the Dom0 and that you can use ifconfig to reconfigure it
without getting an error. But the changes for the adapter in the Dom0
are only "cosmetic". Nevertheless snoop on the adapter in the Dom0 works.
regards
Bernd
# ### in the Dom0
#
bash-3.2# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu
8232 index 1
inet 127.0.0.1 netmask ff000000
bge0: flags=201004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4,CoS> mtu
1500 index 2
inet 192.168.1.6 netmask ffffff00 broadcast 192.168.1.255
ether 0:c0:9f:f4:6a:3c
iwi0: flags=201004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4,CoS> mtu
1500 index 3
inet 192.168.1.7 netmask ffffff00 broadcast 192.168.1.255
ether 0:15:0:45:d1:5f
bash-3.2# cat Solaris10_xen0707_test.phy
bootloader = "/usr/lib/xen/bin/pygrub"
name = "solaris_10_July_07"
memory = "368"
vcpus = "1"
disk = [
'file:/export/xen-images/Solaris10_xen0707/Solaris10_xen0707.raw,0,w' ]
root = "/dev/dsk/c0d0s0"
vif = [ 'bridge=bge0,mac=0:c0:9f:f4:6a:3c,script=vif-dedicated' ]
on_shutdown = 'destroy'
on_reboot = 'restart'
on_crash = 'destroy'
bash-3.2# xm create -c Solaris10_xen0707_test.phy
Using config file "./Solaris10_xen0707_test.phy".
Started domain solaris_10_July_07
# ### in the DomU
SunOS Release 5.11 Version xen-nv66-2007-06-24 32-bit
Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
WARNING: Found xen v3.0.4-1-xvm but need xen v3.0.4-1-sun
WARNING: The kernel may not function correctly
ip: joining multicasts failed (4) on xnf0 - will use link layer
broadcasts for multicast
Hostname: dhcppc1
dhcppc1 console login: root
Password:
Last login: Thu Nov 22 21:10:30 from localhost
Dec 11 20:07:35 dhcppc1 login: ROOT LOGIN /dev/console
Sun Microsystems Inc. SunOS 5.11 xen-nv66-2007-06-24 October 2007
# bash
bash-3.2# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu
8232 index 1
inet 127.0.0.1 netmask ff000000
> Does it also work for para-virtualized DomUs?
If the device in question has a GLDv3 driver, then yes (but see 6592059,
which means that it doesn't work for wireless NICs).
xnf0:
flags=201005843<UP,BROADCAST,RUNNING,MULTICAST,MULTI_BCAST,DHCP,IPv4,CoS>
mtu 1500 index 2
inet 192.168.1.6 netmask ffffff00 broadcast 192.168.1.255
ether 0:c0:9f:f4:6a:3c
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu
8252 index 1
inet6 ::1/128
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu
8252 index 1
inet6 ::1/128
bash-3.2#
# ### Dom0
# xm list
Name ID Mem VCPUs State
Time(s)
Domain-0 0 635 1 r----- 58.3
solaris_10_July_07 1 367 1 ------ 15.8
#
# It looksl like the network adapter used in the DomU is still visible
in the Dom0 and ifconfig commands
# for this adapter are possible but do not change the configuration of
the adapter.
# ifconfig bge0
bge0: flags=201004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4,CoS> mtu
1500 index 2
inet 192.168.1.6 netmask ffffff00 broadcast 192.168.1.255
ether 0:c0:9f:f4:6a:3c
bash-3.2# ifconfig bge0 down
bash-3.2# ifconfig bge0
bge0: flags=201000842<BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
inet 0.0.0.0 netmask 0
ether 0:c0:9f:f4:6a:3c
bash-3.2# ifconfig bge0 192.168.1.8
bash-3.2# ifconfig bge0
bge0: flags=201000842<BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
inet 192.168.1.8 netmask ffffff00 broadcast 192.168.1.255
ether 0:c0:9f:f4:6a:3c
bash-3.2# ping 192.168.1.8
^C
--
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
[email protected]
