cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-8933) SSVm and CPVM do not survive a reboot from API
Date Wed, 14 Oct 2015 06:00:10 GMT


ASF GitHub Bot commented on CLOUDSTACK-8933:

GitHub user bvbharatk opened a pull request:

    CLOUDSTACK-8933 SSVm and CPVM do not survive a reboot from API

    The issue is because we loop infinitely when we do not receive any cmdline data during
reboots. The current fix is to attempt one time to read the commadline data, the data is not
there we check if the cmdline is already populated. If is already there we continue with the
existing command line.
    This fix will work in case of reboots, but in case of stop and start if the cmdline changes
and we do not get it on first read we will end up using the old cmdline data instead of the
new one. I am not sure if the cmd data will change on start stop.  One way to fix this will
be to send some data in the cmdline on reboot to say that we can use the existing data in
the cmdline. I am not sure if this a good way to fix it.
    Please let me know if there is a better way to do this.

You can merge this pull request into a Git repository by running:

    $ git pull CLOUDSTACK-8933

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #930
commit 2fd8ab0b4852e792607b8ae4431d4537e98e6fea
Author: Bharat Kumar <>
Date:   2014-12-24T11:18:55Z

    CLOUDSTACK-8933 SSVm and CPVM do not survive a reboot from API


> SSVm and CPVM do not survive a reboot from API
> ----------------------------------------------
>                 Key: CLOUDSTACK-8933
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: SystemVM
>    Affects Versions: 4.6.0
>         Environment: KVM Advanced / Basic zone
>            Reporter: Remi Bergsma
>            Priority: Blocker
>             Fix For: 4.6.0
>         Attachments: Console screenshot.png, reboot.4.5.log, reboot.4.6.log
> These tests fail:
> -          integration.smoke.test_ssvm.TestSSVMs.test_07_reboot_ssvm
> -          integration.smoke.test_ssvm.TestSSVMs.test_08_reboot_cpvm
> Stopping works, then CloudStack successfully deploys a new one. Rebooting doesn’t work
as it doesn’t complete the boot sequence. Looking at the agent.log I noticed the systemvm
doesn’t get patched so it is probably waiting for that to happen.
> A successful start shows this:
> 2015-10-05 21:26:12,748 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-4:null)
Executing: /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/ -n v-1-VM
-p %template=domP%type=consoleproxy%host=
> 2015-10-05 21:26:12,777 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-4:null)
Execution is successful.
> The reboot doesn’t do this. When I hit reboot and run this command manually, it works:
> /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/ -n v-1-VM -p
> I basically copy/pasted the patch line from the stop/start and used it when rebooting.
Now everything works.
> We need to figure out why it doesn’t patch the system vms on reboot.

This message was sent by Atlassian JIRA

View raw message