Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 54F08D8FF for ; Fri, 9 Nov 2012 03:20:18 +0000 (UTC) Received: (qmail 4085 invoked by uid 500); 9 Nov 2012 03:20:16 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 2780 invoked by uid 500); 9 Nov 2012 03:20:14 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 2734 invoked by uid 99); 9 Nov 2012 03:20:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Nov 2012 03:20:12 +0000 Date: Fri, 9 Nov 2012 03:20:12 +0000 (UTC) From: "Randy McAnally (JIRA)" To: cloudstack-dev@incubator.apache.org Message-ID: <1921424211.90094.1352431212601.JavaMail.jiratomcat@arcas> In-Reply-To: <1022463918.76331.1352232612521.JavaMail.jiratomcat@arcas> Subject: [jira] [Updated] (CLOUDSTACK-448) SSVM bootstrap failure on XenServer hosts with E3 CPU MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randy McAnally updated CLOUDSTACK-448: -------------------------------------- Comment: was deleted (was: Thank you for that patch, it looks like we have the same issue. We were able to get things going by manually hacking cloud-early-config in a similar way. I guess there are not many cloudstack users on modern CPU. ) > SSVM bootstrap failure on XenServer hosts with E3 CPU > ----------------------------------------------------- > > Key: CLOUDSTACK-448 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-448 > Project: CloudStack > Issue Type: Bug > Components: XenServer > Affects Versions: pre-4.0.0 > Environment: Cloudstack 3.0.2 + XenServer 6.0.2 on E3 CPU > Reporter: Randy McAnally > Priority: Blocker > Attachments: management-server.log.txt, screenshot-1.jpg, ssvm_cloud.log.txt, ssvm_console.txt, ssvm_dmesg.txt, ssvm_vm-param-list.txt > > > Cannot add XenServer 6.0.2 based hosts with E3 CPU. SSVM of any type fail to boostrap, ending up with incomplete network configuration and Cloudstack unable to ping it. Adding a host with any other type of previous generation CPU succeeds and SSVMs start properly (in this case X3450) . > Failing host: > [root@cl-ash-h1 ~]# xe host-cpu-info > cpu_count : 8 > vendor: GenuineIntel > speed: 3300.094 > modelname: Intel(R) Xeon(R) CPU E3-1230 V2 @ 3.30GHz > family: 6 > model: 58 > stepping: 9 > flags: fpu de tsc msr pae mce cx8 apic sep mtrr mca cmov pat clflush acpi mmx fxsr sse sse2 ss ht nx constant_tsc nonstop_tsc aperfmperf pni pclmulqdq vmx est ssse3 sse4_1 sse4_2 x2apic popcnt aes hypervisor ida arat tpr_shadow vnmi flexpriority ept vpid > features: 00000000-00000000-00000000-00000000 > features_after_reboot: 00000000-00000000-00000000-00000000 > physical_features: 00000000-00000000-00000000-00000000 > maskable: no > Working host: > [root@localhost ~]# xe host-cpu-info > cpu_count : 8 > vendor: GenuineIntel > speed: 2666.760 > modelname: Intel(R) Xeon(R) CPU X3450 @ 2.67GHz > family: 6 > model: 30 > stepping: 5 > flags: fpu de tsc msr pae mce cx8 apic sep mtrr mca cmov pat clflush acpi mmx fxsr sse sse2 ss ht nx constant_tsc nonstop_tsc aperfmperf pni vmx est ssse3 sse4_1 sse4_2 popcnt hypervisor ida tpr_shadow vnmi flexpriority ept vpid > features: 0098e3fd-bfebfbff-00000001-28100800 > features_after_reboot: 0098e3fd-bfebfbff-00000001-28100800 > physical_features: 0098e3fd-bfebfbff-00000001-28100800 > maskable: full -- 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