hello Andy, thank you very much for your replay, in fact I want to explain for you the slowness case that we experience it is at starting windows and shutdown it once I switch the VM on it take about 15 minutes to see the win3003 starting logo and in shutdown it shutdown fast until you see a blue screen after that it take about half hour to switch off.
once the windows started it is work normal and I can say it fast in working the issue is in starting and ending the windows. yesterday I did what you asked but i didn't get any important log or even see any boot logs. dose i need to make some tuning for KVM which i installed it in fedora Linux 6.6 also i tried install Ubuntu using the KVM also i experience the same problem. thank you Tariq On Thu, May 1, 2014 at 11:39 AM, Andy Kurth <[email protected]> wrote: > Sorry for the delay, been on vacation. It looks like the security > policies are being successfully applied so the previous problem appears to > be solved. > > The capture process attempted to reboot the VM in order to delete the > pagefile to save space. The VM never responded to ping after the reboot. > Something is misconfigured regarding the VM or VM host's networking. Log > into the VM and check ipconfig. Does the VM have a private IP address? > Can you now ping it and SSH in from the management node? > > You mentioned slowness in a previous message. If the VM currently has a > private IP address and the networking currently looks OK, it's possible > that the VM took over 5 minutes to reboot and the capture process timed > out. If this is the case you'll need to figure out the reason for the > slowness. Try rebooting the VM. Where does it seem to hang -- shutting > down or coming back up? If it is slow coming back up, disable the GUI boot > option so you can see where the boot sequence hangs: > -Run msconfig.exe > -Select the Boot tab > -Check "No GUI boot" > -Check "Boot log" > -Check "OS boot information" > -Save the changes > > Also, clear the System event log just prior to rebooting the computer, > then reboot it. Watch the screen while it reboots to see if there is a > long pause where nothing is happening. What is displayed during the pause > and immediately afterwards? After it boots, look at the system event log > and see if there is a long gap between timestamps where the delay occurred. > What event log messages are generated before and after the delay? > > The VM only has 1GB of RAM. This should be sufficient but you could also > try to increase it. > > > On Wed, Apr 30, 2014 at 12:05 AM, zvclproject zvclproject < > [email protected]> wrote: > >> hello, >> >> i fixed the ssh in the flake and still i can't capture the image due to >> the reboot failed in flake, please your advises >> please find the attaches file >> >> thank you >> >> >> On Tue, Apr 29, 2014 at 10:27 AM, Aaron Peeler <[email protected]>wrote: >> >>> The node flake is not accessible via ssh. >>> >>> Look for the first WARNING flag in the log file. >>> >>> The management node vcld process needs to log into the node via ssh >>> using PKI. >>> >>> Make sure ssh logins work first, then set the state of the request in >>> the db from maintenance to image. This restarts the imaging process, >>> watch the log file for any additional errors. >>> >>> Aaron >>> >>> >>> On Mon, Apr 28, 2014 at 11:13 PM, zvclproject zvclproject >>> <[email protected]> wrote: >>> > hello Andy, >>> > >>> > i have deleted all the database record and then i re added all the >>> nodes but >>> > still i experience error in capturing the image, please find the >>> attachment >>> > that show your the logs >>> > >>> > >>> > please your help, >>> > >>> > thank you very much >>> > >>> >>> >>> >>> -- >>> Aaron Peeler >>> Program Manager >>> Virtual Computing Lab >>> NC State University >>> >>> All electronic mail messages in connection with State business which >>> are sent to or received by this account are subject to the NC Public >>> Records Law and may be disclosed to third parties. >>> >> >> >
