AlexanderKgr edited a comment on issue #5535:
URL: https://github.com/apache/cloudstack/issues/5535#issuecomment-930808503


   > @AlexanderKgr can you please share following details:
   > 
   > * Output of `cloudstack-sccs` on the management server
   > * cmk `list virtualmachines id=YOUR_VM_UUID` output for the VM before 
starting the second time
   > * After adding `TRACE` log level for `com.cloud.vm` in the 
`/usr/share/cloudstack-management/conf/log4j.xml` and restarting management 
server, complete logs for the start VM action (there are some logs in 
UserVmManagerImpl.java which tells what boot details are passed to the 
hypervisor plugin).
   > 
   > ```
   >    <category name="com.cloud.vm">
   >      <priority value="TRACE"/>
   >    </category>
   > ```
   > 
   > I've tested stop-starting VMs with both ISO and template multiple times 
but I'm not being able to reproduce this so if you can share above details it 
will be really helpful. Also, in a reply on previous ticket you mentioned that 
router boot because that is really weird. As per code systems VM should always 
be booting in BIOS.
   
   i will ask you some questions because it is the first time i am doing this.
   in my /usr/share/cloudstack-management/conf/log4j.xml i dont have value with 
category name com.cloud.vm but
   
![image](https://user-images.githubusercontent.com/25532758/135395493-b13f6ad0-9c38-4186-9ced-2fb642ab9c9f.png)
   
   i suppose it is the same or should i add a new category?
   
   also... what is it cloudstack-sccs? 
   
![image](https://user-images.githubusercontent.com/25532758/135395591-ad4e1a34-bd7a-4e41-b9a2-95f56f84ff41.png)
   
   and what is cmk?
   
![image](https://user-images.githubusercontent.com/25532758/135395667-808f8cef-6621-4649-996e-581b6e22da85.png)
   
   as server i am using Ubuntu server 18.04.6
   sorry for asking so much stuff and thank you for helping


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to