What happen to the part where you create initial OS via debootstrap? Or we let user provide a VM and just run post?
Thanks ilya -----Original Message----- From: ASF subversion and git services (JIRA) [mailto:j...@apache.org] Sent: Thursday, February 07, 2013 5:51 PM To: cloudstack-dev@incubator.apache.org Subject: [jira] [Commented] (CLOUDSTACK-1066) Fix the scripts to generate systemvm template [ https://issues.apache.org/jira/browse/CLOUDSTACK-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574019#comment-13574019 ] ASF subversion and git services commented on CLOUDSTACK-1066: ------------------------------------------------------------- Commit 3dea9a7be578cd5116e02d66a39e2e61f8aedd9a in branch refs/heads/master from [~chiradeep] [ https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;h=3dea9a7 ] Summary: Remove superfluous chroot and change to use standard jre Detail: Since the script executes inside the running vm, the chroot is not necessary. Also the standard jre is used instead of sun jre. BUG-ID: CLOUDSTACK-1066 Signed-off-by: Chiradeep Vittal <chirad...@apache.org> 1360277071 -0800 > Fix the scripts to generate systemvm template > ---------------------------------------------- > > Key: CLOUDSTACK-1066 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1066 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Affects Versions: 4.0.0, 4.0.1 > Reporter: Sheng Yang > Fix For: 4.1.0 > > > The buildsystemvm.sh is broken. There is no way for CloudStack to generate an > new systemvm template now. And we're unable to add new feature which depends > on systemvm template change. We need to fix it in 4.1. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
