[ldoms-discuss] LDOM Configurations

[Octave Orgeron]

Hi,

You only have to go back into configuration mode when you want to change something fundamental, like adding/remove a vsw. You should create a vsw for each physical nic on your box when you start configuring the control domain. You do not need to do that with vnet's or with vdsk-dev's or vdisks. However, in order for those virtual devices to show up or be removed in your guest domain, they will need to be rebooted. Currently, only VCPU resources can be dynamically reallocated.

Communications between the control and guest domains in your case is about networking. If you setup guest domains on a vsw that you do not have network access to in the control domain, meaning you didn't plumb an interface in the control domain on that vsw, it will fail. Nothing special or surprising there:)
 
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Octave J. Orgeron
Solaris Systems Engineer
http://www.opensolaris.org/os/community/sysadmin/
http://unixconsole.blogspot.com
unixconsole at yahoo.com
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

----- Original Message ----
From: Dan Gubber <dgubber at csc.com>
To: ldoms-discuss at opensolaris.org
Sent: Monday, October 29, 2007 12:10:44 PM
Subject: Re: [ldoms-discuss] LDOM Configurations


oorgoren,

Thank you for your quick reply, but I'm still left with the a few core
 issues in the model you indicated.

If a server is configured with, as an example, one vsw, let's say
 e1000g0 and a guest domain is actually installed, in order to create a new
 NIC connection, I would have to disrupt a production environment in
 order to add further "virtual" connectivity. I thought the whole premise to
 virtualization was the ability to dynamically reallocate resources
 when required.

Also, and I haven't tried this yet, but does this also apply to virtual
 disk services. IOW, if I present a new LUN from a RAID storage array
 such as SUN's or HDS's and I dynamically configure the LUN on the
 control domain, in order to present it to a guest domain, either an existing
 one or new one, would I have to reboot the control domain ?

Even with the fact that I would have to reboot the control domain, it
 appears that it's deeper then that. I actually have to remove and
 re-create the "initial" configuration in order for the changes to be applied.
 If this is true, and you have a fairly "defined" configuration, it
 seems impossible to want to deploy LDOM's due to the possible amount of
 work you would have to do just to add in additional resources ...

One more item.... the documentation seems to indicate that
 communication between the guest domains and control domain is disabled by default,
 and in order to configure them to communicate, you need to set vsw0 as
 an active network device on the control domain. What I found was even
 though the vsw0 entry was defined properly, and I renamed
 hostname.e1000g0 to hostname.vsw0 and rebooted, that after the reboot, that
 connection was no longer active OFF the server, ie, I was unable to communicate
 to remote systems via that device.

Also, if that device is not configured in this fashion ( leaving the
 control domain <-> guest domain communications disabled ) to what extent
 does this impact the guest domain ? Is this communication channel that
 get's created the means by which the guest domain communicates to the
 control domain for virtual services ? Or is it mearly a channel for
 networking ( ie, TCPIP ) communications between both?

Please let me know what I'm missing here
Regards,
Dan
--
This message was posted from opensolaris.org
_______________________________________________
ldoms-discuss mailing list
ldoms-discuss at opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss




__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com