[jira] [Reopened] (CLOUDSTACK-2823) SystemVMs start fail and have no HA

["Wei Zhou (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wei Zhou reopened CLOUDSTACK-2823:
----------------------------------

      Assignee: Marcus Sorensen

Marcus, 

Can you have a look at this? 

SystemVMs start fail on CentOS 6.4. 

I think it is because of the change from CS 4.1 to 4.2
In CS 4.1, we add an additional patchdisk to systemvm for setting in sytemvm startup.
In CS 4.2, you changed it to implement it thtough virtio-serial.

In http://www.linux-kvm.org/page/VMchannel_Requirements , it mentioned "The feature will be available in the next major QEMU release after 0.12." and "The corresponding kernel driver will be available in the Linux kernel 2.6.35 release. ".

But in latest CentOS (version 6.4) :
[root@cs-kvm015 agent]# uname -r
2.6.32-358.2.1.el6.x86_64

So I try to upgrade the host. I have upgraded libvirt to 0.10.2. But upgrade QEMU failed.

Have you ever tested on CentOS 6.4? Maybe we have to point out CS does not support CentOS 6.4, or keep the old way for lower OS version like CentOS 6.3/6.4.

What do you think about it ? Thanks.

-Wei


                
> SystemVMs start fail and have no HA
> -----------------------------------
>
>                 Key: CLOUDSTACK-2823
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2823
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.2.0
>         Environment: CentOS 6.4, KVM
> CloudStack master
>            Reporter: Wei Zhou
>            Assignee: Marcus Sorensen
>
> Host:
> [root@cs-kvm015 ~]# virsh version
> Compiled against library: libvirt 0.10.2
> Using library: libvirt 0.10.2
> Using API: QEMU 0.10.2
> Running hypervisor: QEMU 0.12.1
> Network:
> em0 -> cloudbr0 (Guest, Public), Guest: 172.16.61.0/24, Public: 10.11.11.0/24 (Can not connect outside)
> em1.103 -> cloudbr1 (Management, Storage) , IP: 192.168.103.*
> Issue descripion
> (1) SystemVMs (SSVM, CPVM) start fails , and have no IP (Public, guest, management)
> (2) After I destroyed SystemVM, no new SystemVM will be created automatically.
> This issue only exists on master branch
> Deploy 4.1 successfully, and SystemVms work well. 

--
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