Welcome to the Virtual Iron Forums!
Here you'll find information to help you get the maximum value from your Virtual Iron software.
Community |
Topic Title: Virtualization Manager Topic Summary: Using the Abort on Discover Created On: 12/17/2006 10:35 AM |
Linear : Threading : Single : Branch |
Topic Tools
|
12/17/2006 10:35 AM
|
|
I am using a practice setup, but I don't think this is the cause.
In the Manager, when performing a Discover (although I have nothing for it to discover), I let it try for a few minutes and then hit Abort. At that point, it seems to lock up as I can't click on anything or continue in the Manager. The practice Virtualization Manager seem to be within spec. 3Ghz P4, WinXP-Pro-SP2, plenty of drive space. It does have only 1GB of RAM though, not 2GB as the specs say it should have. Any thoughts on the appearent lockup when I hit Abort? |
|
|
|
12/17/2006 10:46 AM
|
|
It would help to have more RAM once you have a few VT/AMD V capable nodes to manage, again 2GB recommended. However, I don't think this is the cause of the problem you describe.
If you re-login to the Virtualization Manager user interface are you able to navigate the UI (go to Hardware view etc). Discover will scan a network (based upon the IP information you provided in the discover screen) looking nodes that have booted the VirtualizationServicesPartition. The size of the range you give this process will effect the amount of time discovery takes. A separate thread will do this walking so an Abort from the UI will have to alert this thread to stop the discovery. |
|
|
|
12/19/2006 09:05 AM
|
|
Thanks for the info
FYI - I tried again and just waited and it finished on its own. It did take a few minutes to finally come back to life. I just wasn't waiting long enough.
|
|
|
FORUMS
:
How-tos
:
General Q&A
:
Virtualization Manager
|
Topic Tools
|
FuseTalk Standard Edition - © 1999-2007 FuseTalk Inc. All rights reserved.
Copyright © 2003-2007 Virtual Iron Software, Inc. | Privacy Statement | Terms of Use | Site Map