Thanks a lot. The problem was the compilation command. I was using mvn install
-Dnonoss maybe because i've read a lot of pages describing the build process
and I stopped on one that has worked the first time ;-)
Julien Garet
- Mail original -
De: Min Chen min.c...@citrix.com
Hello,
I am facing a problem I don't understand when I try to use the current master
with a vmware cluster.
When I create an instance for the first time, it does not download the template
to primary storage... But It works for the systemvms !
Here is what I see in the logs :
I've found something, I think. The template was refered in the
template_spool_ref with all NULL values.
Removing this entry make it trying to download the template. But it does not
complete due to errors :
013-03-01 13:48:27,559 DEBUG [cloud.storage.VolumeManagerImpl]
(Job-Executor-1:job-35)
This command is executed from SSVM, so you need to log into SSVM to find the
systemvm.log from /var/log/cloud to see what exception you got.
Thanks
-min
Sent from my iPhone
On Mar 1, 2013, at 4:58 AM, Julien Garet julien.ga...@inria.fr wrote:
I've found something, I think. The template
systemvm.log is not activated by default, documentation is missing on how to
activate it.
The main problem is linked to certificate validation
2013-03-01 21:15:40,157 ERROR
[storage.resource.VmwareSecondaryStorageResourceHandler]
(agentRequest-Handler-1:) Unexpected exception
That's strange, i've been using this branch. Do system VMs remain the same ? I
am using the burbank system VMs, are they still OK ?
Julien Garet
Le 2 mars 2013 à 00:14, Min Chen min.c...@citrix.com a écrit :
Yes, systemvm.log is not activated on master, I have enabled it on
vim51_win8
Are you talking about systemvm.iso or systemvm template? I am also using
Burbank system vm template for my testing. But systemvm.iso needs to be
rebuilt by running mvn clean install -P developer,systemvm -Dnonoss.
Remember to clear your previous systemvm-4.2.0-SNAPSHOT.iso from your
secondary
