[jira] [Commented] (CLOUDSTACK-2823) SystemVMs start fail on CentOS 6.4
[ 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 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)
[jira] [Commented] (CLOUDSTACK-2823) SystemVMs start fail on CentOS 6.4
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14242277#comment-14242277 ] ASF subversion and git services commented on CLOUDSTACK-2823: - Commit 9bfb8e571934f70d00a69c3aa58cf848d016afb9 in cloudstack's branch refs/heads/4.5 from Wei Zhou [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9bfb8e5 ] CLOUDSTACK-2823: pass cmdline info to system vms for 30 times (cherry picked from commit 4eedfe53fcbab1d47b09eacaca1d803b67b6c4d2) > 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)
[jira] [Commented] (CLOUDSTACK-2823) SystemVMs start fail on CentOS 6.4
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238039#comment-14238039 ] ASF subversion and git services commented on CLOUDSTACK-2823: - Commit 1e09494a4e6cc0aed0ecd1536d7806dbb88fb69d in cloudstack's branch refs/heads/4.3 from Wei Zhou [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1e09494 ] CLOUDSTACK-2823: pass cmdline info to system vms for 30 times (cherry picked from commit 4eedfe53fcbab1d47b09eacaca1d803b67b6c4d2) Signed-off-by: Rohit Yadav Conflicts: plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java 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)
[jira] [Commented] (CLOUDSTACK-2823) SystemVMs start fail on CentOS 6.4
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237945#comment-14237945 ] ASF subversion and git services commented on CLOUDSTACK-2823: - Commit 4eedfe53fcbab1d47b09eacaca1d803b67b6c4d2 in cloudstack's branch refs/heads/master from Wei Zhou [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4eedfe5 ] CLOUDSTACK-2823: pass cmdline info to system vms for 30 times > 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)
[jira] [Commented] (CLOUDSTACK-2823) SystemVMs start fail on CentOS 6.4
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237815#comment-14237815 ] Wei Zhou commented on CLOUDSTACK-2823: -- I reverted the commit 83656a6ea81ce9b85c2f480e576fd02d8a58c357 on master branch. > 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)
[jira] [Commented] (CLOUDSTACK-2823) SystemVMs start fail on CentOS 6.4
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14227538#comment-14227538 ] ASF subversion and git services commented on CLOUDSTACK-2823: - Commit 0a935a336ebf9dcc1c3b25a56f629bb9a217b56f in cloudstack's branch refs/heads/4.3 from [~dbierce] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0a935a3 ] CLOUDSTACK-2823: Loop through cmdline when patching routers Backported from https://reviews.apache.org/r/25585/diff which did not merge this fix on 4.3 branch. Occasionally the while loop can exit with no data (Probably recieving an EOF) before receiveing CMDline data from the certial port. Continue looping until cmdline is populated Signed-off-by: Rohit Yadav > 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)
[jira] [Commented] (CLOUDSTACK-2823) SystemVMs start fail on CentOS 6.4
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796469#comment-13796469 ] ASF subversion and git services commented on CLOUDSTACK-2823: - Commit 903d0c09200bda6928ef189623b8250319888609 in branch refs/heads/4.2 from [~mlsorensen] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=903d0c0 ] CLOUDSTACK-2823: This affects Ubuntu as well, since qemu version is 1.0.0 I don't think host kernel version has any bearing on it. Original code was tested with CentOS 6.3 and 6.4, but it seems to succeed or fail per-host, e.g. a fast host might work and a slow host might not. I was getting intermittent failures with ubuntu 12.04.3 prior to this patch. > 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.1#6144)
[jira] [Commented] (CLOUDSTACK-2823) SystemVMs start fail on CentOS 6.4
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796470#comment-13796470 ] ASF subversion and git services commented on CLOUDSTACK-2823: - Commit 3467c99e730af2949d4b6db3c3b953c9216f7a14 in branch refs/heads/master from [~mlsorensen] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3467c99 ] CLOUDSTACK-2823: This affects Ubuntu as well, since qemu version is 1.0.0 I don't think host kernel version has any bearing on it. Original code was tested with CentOS 6.3 and 6.4, but it seems to succeed or fail per-host, e.g. a fast host might work and a slow host might not. I was getting intermittent failures with ubuntu 12.04.3 prior to this patch. > 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.1#6144)
[jira] [Commented] (CLOUDSTACK-2823) SystemVMs start fail on CentOS 6.4
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708317#comment-13708317 ] ASF subversion and git services commented on CLOUDSTACK-2823: - Commit 564c30a0407886fea865ae93c67ed4cf00e2fdd8 in branch refs/heads/4.2 from [~weizhou] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=564c30a ] CLOUDSTACK-2823: move kernelVersion to global configuration in LibvirtComputingResource.java > 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 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
[jira] [Commented] (CLOUDSTACK-2823) SystemVMs start fail on CentOS 6.4
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708315#comment-13708315 ] ASF subversion and git services commented on CLOUDSTACK-2823: - Commit f89848b0db73d8c5a8795d0c90f45c05f45f5374 in branch refs/heads/master from [~weizhou] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f89848b ] CLOUDSTACK-2823: move kernelVersion to global configuration in LibvirtComputingResource.java > 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 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
[jira] [Commented] (CLOUDSTACK-2823) SystemVMs start fail on CentOS 6.4
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706759#comment-13706759 ] ASF subversion and git services commented on CLOUDSTACK-2823: - Commit 22c6df0ba25f1f1fd3cf489a29ed1f4f4097c89c in branch refs/heads/4.2 from [~weizhou] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=22c6df0 ] CLOUDSTACK-2823: try passCmdLine some times if kernel < 2.6.34 and qemu < 1.1.0 on hypervisor (for instance, CentOS 6.4) > 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 >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 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
[jira] [Commented] (CLOUDSTACK-2823) SystemVMs start fail on CentOS 6.4
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706760#comment-13706760 ] ASF subversion and git services commented on CLOUDSTACK-2823: - Commit dc9f7290e87c3a8270a68f4d06ec43b4521005ba in branch refs/heads/master from [~weizhou] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=dc9f729 ] CLOUDSTACK-2823: try passCmdLine some times if kernel < 2.6.34 and qemu < 1.1.0 on hypervisor (for instance, CentOS 6.4) > 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 >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 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
[jira] [Commented] (CLOUDSTACK-2823) SystemVMs start fail on CentOS 6.4
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706344#comment-13706344 ] edison su commented on CLOUDSTACK-2823: --- How about apply the patch you posted above, as a temporary workaround? > 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 >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 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
