[
https://issues.apache.org/jira/browse/CLOUDSTACK-7143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143184#comment-14143184
]
ASF GitHub Bot commented on CLOUDSTACK-7143:
--------------------------------------------
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?
> Refactor systemvm build scripts to be easier to test
> ----------------------------------------------------
>
> Key: CLOUDSTACK-7143
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7143
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: SystemVM
> Reporter: Leo Simons
> Fix For: Future
>
>
> The veewee-wrapping build code could do with some love.
> E-mail thread:
> http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201407.mbox/%3C7A6CF878-7A28-4D4A-BCD2-0C264F8C90B7%40schubergphilis.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
