cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-2823) SystemVMs start fail on CentOS 6.4
Date Thu, 11 Dec 2014 07:45:12 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14242289#comment-14242289
] 

ASF subversion and git services commented on CLOUDSTACK-2823:
-------------------------------------------------------------

Commit 4a7532ee65642b986b8cbf1034d482b94a76990c in cloudstack's branch refs/heads/4.4 from
Wei Zhou
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4a7532e ]

CLOUDSTACK-2823: pass cmdline info to system vms for 30 times

(cherry picked from commit 4eedfe53fcbab1d47b09eacaca1d803b67b6c4d2)
Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>

Conflicts:
	systemvm/patches/debian/config/etc/init.d/cloud-early-config


> SystemVMs start fail on CentOS 6.4
> ----------------------------------
>
>                 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: Wei Zhou
>            Priority: Blocker
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message