Creating a service and I/O domain
I am attempting to create a service and I/O domain. I created the domain, gave this domain the e1000g1 network interface and setup a virtual switch from which other guest domains will get one network interface for network failover.
After that I bound the domain and started it and attempted to boot off of the net, but it does not see the network interface. The e1000g1 is connected to the network.
I have set up the control domain similar to the beginners guide and have jumpstarted a guest domain.
Here is the info on this service domain:
# ldm list-bindings service
Name:service
State: active
Flags: transition,vio service
OS:
Util:100%
Uptime: 22h 10m
Vcpu:4
vidpidutil strand
06100%100%
17100%100%
28100%100%
39100%100%
Mau:1
mau cpuset (4, 5, 6, 7)
Memory: 1G
real-addrphys-addrsize
0x48000000x848000001G
Vsw:secondary-vsw0
mac-addr=0:14:4f:fb:7:87
net-dev=e1000g1
mode=prog,promisc
Vds:secondary-vds0
Vcons: [via LDC:1]
service@primary-vcc0 [port:5001]
Vldcc: vldcc0 [Domain Services]
service: primary-vldc0 @ primary
[LDC: 0x0]
# ldm list-services service
Vsw:secondary-vsw0
mac-addr=0:14:4f:fb:7:87
net-dev=e1000g1
mode=prog,promisc
Vds:secondary-vds0
Thanks in advance for any help!
Kevin
[1440 byte] By [
vaka] at [2007-11-27 0:16:36]
# 1
First off the control domain is the first service domain by default. As a result, you can only setup a second service domain or one I/O domain. Remember that service domains virtualize networking and storage for guest domains. I/O domains do not service guest domains. One of your service domains has to be the control domain as well. There are two gotcha's in this area.
The first one is that there are only two PCI-E controllers on a T1K/T2K, this is what limits the number of service domains. When you configure a Split PCI-E configuration, where you have two service domains or one service domain and an I/O domain. This means that it will only have access to the devices on that PCI-E controller.
The second one is a bit more critical. There is only one SAS controller (either built onto the system board or as a PCI-X card). So you either have to boot off the net, the SAN, or an external storage device for your second service domain or I/O domain.
# 2
Okay, so what I hear you saying (virtually) is that to hand over control of a network interface, I need to hand over full control of a pci branch to the new service domain in order create a virtual switch and have it hand out interfaces to guest domains. Is that correct?
I just handed over the pci@7c0 pci branch to the service domain and I can now see network interfaces in OBP.
Also, I guess I do not understand the real difference between and I/O domain and a service domain. Could you please attempt to help me clarify that?
Thanks so much for your help! More of this is sinking in!
Kevin
vaka at 2007-7-11 22:04:46 >
