Liam, Thanks for the responses first of all, I do appreciate it.
I still have a concern though as far as having to reboot the control domain. If in fact, the control domain is actually in control of the virtual device layer, and is merely acting as a "virtual presentor" of these devices to the guest domain layer, if you disrupt the virtual presentation of devices, you disrupt the guest domain. The only way this would not be the case, is if the control domain DOES NOT act as the "virtual presentor" and the control domain is simply used as a configuration manager. The saved configuration "define virtual device paths" at the firmware layer for use by the guest domains, thus making it possible to reboot the control domain without disrupting guest domain services. Is this what's really going on there ? Please let me know and thanks again! Regards, Daniel J. Gubber Sr System's Engineer CSC Consulting Group (781) 290-1334 CSC Consulting, Inc. Registered Office: 29 Sawyer Road, Waltham Massachusetts 02154, USA Registered in USA No: 042593545 ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
