Github user bhaisaab commented on the pull request:
https://github.com/apache/cloudstack/pull/16#issuecomment-56371520
Hi Leo, I spent last few hours in debugging systemvms. I tested the built
systemvms from
http://jenkins.buildacloud.org/job/systemvm-refactor-CLOUDSTACK-7143/9/
on KVM using both master and 4.4 branch as my systemvms were unable to
connect to mgmt server.
At first, I was getting KVM clock error exceptions which I solved by
disabling it from agent.properties
(http://cjkz.wordpress.com/2014/08/08/apache-cloudstack-kvmclock-error/).
So after spending last few hours debugging them, I see the following from
VNC/KVM:
It looks like the disk is corrupt for some reason, so to test the image I
used the new KVM template to deploy a VM on another CloudStack deployment which
perfectly worked for me. So, I'm guessing something in the KVM iso/patching
process is messing with the systemvm. Now every time CloudStack tried to do HA
and re-deploys systemvms I get the above on my test environment.
Can you please try this at your end using KVM or Xen and let me know if it
works for you?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
