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 5285AC430 for ; Thu, 19 Jul 2012 06:46:26 +0000 (UTC) Received: (qmail 95499 invoked by uid 500); 19 Jul 2012 06:46:26 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 95364 invoked by uid 500); 19 Jul 2012 06:46:25 -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 95334 invoked by uid 99); 19 Jul 2012 06:46:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jul 2012 06:46:24 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jason.bausewein@tier3.com designates 66.150.160.34 as permitted sender) Received: from [66.150.160.34] (HELO exchange.tier3.com) (66.150.160.34) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jul 2012 06:46:17 +0000 Received: from WA1T3NDAG01.t3n.dom ([169.254.1.201]) by WA1T3NDAG01.t3n.dom ([169.254.1.229]) with mapi id 14.02.0247.003; Wed, 18 Jul 2012 23:45:56 -0700 From: Jason Bausewein To: "cloudstack-dev@incubator.apache.org" Subject: RE: Review Request: CS-15588 Update systemvm support hypervisor type xen-hvm Thread-Topic: Review Request: CS-15588 Update systemvm support hypervisor type xen-hvm Thread-Index: AQHNYwaOxWzrX6znMEaKiW5rrrg7tJcsnP0AgAAZm4CAAGz+gIABFk2QgAAPliCAAPmT8IAAFxYwgAA0PiCAAAbYkIAAhqUg Date: Thu, 19 Jul 2012 06:45:55 +0000 Message-ID: <97A65BD83AD0814098231040F550DFC9A8BF39@WA1T3NDAG01.t3n.dom> References: <20120716171716.14837.32053@reviews.apache.org> <20120716184855.14836.32323@reviews.apache.org> <97A65BD83AD0814098231040F550DFC9A8BC62@WA1T3NDAG01.t3n.dom> <97A65BD83AD0814098231040F550DFC9A8BDB5@WA1T3NDAG01.t3n.dom> <97A65BD83AD0814098231040F550DFC9A8BE99@WA1T3NDAG01.t3n.dom> In-Reply-To: <97A65BD83AD0814098231040F550DFC9A8BE99@WA1T3NDAG01.t3n.dom> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [76.238.224.165] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 I tried VMware workstation 8.0.3 build-703057 on windows 7 and still gettin= g XenVMMXenVMM in the systemvm. Thanks for trying to figure it out. If you need any more info I'll be runn= ing this configuration for a while. -----Original Message----- From: Jason Bausewein [mailto:jason.bausewein@tier3.com]=20 Sent: Wednesday, July 18, 2012 2:45 PM To: cloudstack-dev@incubator.apache.org Subject: RE: Review Request: CS-15588 Update systemvm support hypervisor ty= pe xen-hvm I'll try installing xen on workstation 8 and see how it turns out. =20 -----Original Message----- From: Anthony Xu [mailto:Xuefei.Xu@citrix.com] Sent: Wednesday, July 18, 2012 2:36 PM To: Anthony Xu; cloudstack-dev@incubator.apache.org Subject: RE: Review Request: CS-15588 Update systemvm support hypervisor ty= pe xen-hvm Even in ESXi 5.0, Virt-what-cpuid-helper in systemvm and bom0 return VMwareVMware, Looks like the issue only happens in vmware fusion. Anthony > -----Original Message----- > From: Anthony Xu > Sent: Wednesday, July 18, 2012 11:23 AM > To: cloudstack-dev@incubator.apache.org > Subject: RE: Review Request: CS-15588 Update systemvm support=20 > hypervisor type xen-hvm >=20 > That's strange , I cannot reproduce this issue in vmware player 4.0.1=20 > build-528992( I'm using windows). >=20 > Virt-what-cpuid-helper in systemvm and bom0 return VMwareVMware, which=20 > is expected, because vmware player cannot distinguish dom0 and=20 > systemvm, they both are PV vm on XenServer. >=20 > Anthony >=20 >=20 >=20 > > -----Original Message----- > > From: Jason Bausewein [mailto:jason.bausewein@tier3.com] > > Sent: Wednesday, July 18, 2012 10:03 AM > > To: cloudstack-dev@incubator.apache.org > > Subject: RE: Review Request: CS-15588 Update systemvm support=20 > > hypervisor type xen-hvm > > > > Hi Anthony, > > > > 1. output of /usr/lib/virt-what/virt-what-cpuid-helper in systemvm=20 > > XenVMMXenVMM > > > > 2. copy virt-what-cpuid-helper to xenserver dom0, and execute virt-=20 > > what-cpuid-helper in dom0, post the result. > > VMwareVMware > > > > 3. systemvm information, execute below command in dom0 Xe vm-param-=20 > > list uuid=3D'uuid of systemvm' > > > > Rather large, so I attached to bug > > http://bugs.cloudstack.org/browse/CS-15588 > > > > 4. vmware player version. > > Fusion 4.1.3 (730298) for Mac > > > > -----Original Message----- > > From: Anthony Xu [mailto:Xuefei.Xu@citrix.com] > > Sent: Tuesday, July 17, 2012 6:54 PM > > To: cloudstack-dev@incubator.apache.org > > Subject: RE: Review Request: CS-15588 Update systemvm support=20 > > hypervisor type xen-hvm > > > > Hi Jason, > > > > Need more information. > > 1. output of /usr/lib/virt-what/virt-what-cpuid-helper in systemvm, 2. > > copy virt-what-cpuid-helper to xenserver dom0, and execute > > virt-what- cpuid-helper in dom0, post the result. > > 3. systemvm information, execute below command in dom0 > > Xe vm-param-list uuid=3D'uuid of systemvm' > > 4. vmware player version. > > > > > > - Anthony > > > > > -----Original Message----- > > > From: Jason Bausewein [mailto:jason.bausewein@tier3.com] > > > Sent: Tuesday, July 17, 2012 6:07 PM > > > To: cloudstack-dev@incubator.apache.org > > > Subject: RE: Review Request: CS-15588 Update systemvm support=20 > > > hypervisor type xen-hvm > > > > > > Hi All, > > > > > > I've been testing the last couple days with the updated systemvm, > and > > > the virtual router, storage, and console VMs appear to be > functioning > > > OK. > > > > > > I'm still not sure why the xen server is starting the system vm in=20 > > > full virtualization (HVM) instead of Para Virtualization (PV). > > > Possibly it's the only available mode when running nested VMs. > > > > > > http://wiki.xensource.com/xenwiki/XenOverview > > > > > > I'm no expert on virtualization types, does anybody see a problem > > with > > > the system vms running in HVM? > > > > > > Without the change to the cloud-early-config, the system vm fails > to > > > read the command line and assign the correct IP addresses. > > > > > > Jason > > > > > > -----Original Message----- > > > From: Sheng Yang [mailto:sheng@yasker.org] > > > Sent: Monday, July 16, 2012 6:19 PM > > > To: cloudstack-dev@incubator.apache.org > > > Subject: Fwd: Review Request: CS-15588 Update systemvm support=20 > > > hypervisor type xen-hvm > > > > > > Forward to mailing list. > > > > > > ---------- Forwarded message ---------- > > > From: Jason Bausewein > > > Date: Mon, Jul 16, 2012 at 11:48 AM > > > Subject: Re: Review Request: CS-15588 Update systemvm support=20 > > > hypervisor type xen-hvm > > > To: Sheng Yang > > > Cc: Jason Bausewein > > > > > > > > > This is an automatically generated e-mail. To reply, visit: > > > https://reviews.apache.org/r/5970/ > > > > > > On July 16th, 2012, 5:17 p.m., *Sheng Yang* wrote: > > > > > > I think there is something wrong with virt-what to show xen-hvm=20 > > > instead of xen-domU in nested virtualization, because I think as > long > > > as the systemvm is start by cloudstack, it should be pv guest(we=20 > > > specify so) rather than HVM guest. It would be possible if virt- > what > > > didn't consider the situation of nested virtualization. > > > > > > Or it's real xen-hvm guest in this case? Somehow unlikely... > > > > > > Probably what we need to fix is virt-what, or use some other way=20 > > > to detect the nested virtualization. > > > > > > On July 16th, 2012, 6:04 p.m., *Jason Bausewein* wrote: > > > > > > The script only uses the hypervisor type to load the boot params. > In > > > either case (nested or not) the boot params should be read from=20 > > > /proc/cmdline. > > > > > > I don't know much about the different types of xen guests, but the=20 > > > system vm appears to work fine under a xen-hvm guest. I have some=20 > > > instances running in a basic zone with security groups, and=20 > > > traffic > > is > > > filtered correctly to the instances. > > > > > > Is there anything I can check from xencenter/xenserver to tell if > its > > > really a hvm guest? > > > > > > On July 16th, 2012, 6:11 p.m., *Jason Bausewein* wrote: > > > > > > The console proxies are also working great to the instances and > > system > > > vms. > > > > > > The virt-what script appears to use the cpuid returned by virt- > what- > > > cpuid-helper. > > > > > > I attached output from cpuid running on the system vm if it helps. > > It > > > has a hypervisor_id of "XenVMMXenVMM", same what is returned by > virt- > > > what-cpuid-helper. > > > > > > > > > - Jason > > > > > > On July 16th, 2012, 6:42 p.m., Jason Bausewein wrote: > > > Review request for Sheng Yang. > > > By Jason Bausewein. > > > > > > *Updated July 16, 2012, 6:42 p.m.* Description > > > > > > When running Xen 6.0.2 under VMware Fusion 4 on Intel Core i7, the=20 > > > command /usr/sbin/virt-what returns xen-hvm instead of xen-dom0. > The > > > system VM cannot read the command line in this case, and will fail > to > > > bind IP addresses assigned via the command line. > > > > > > In the cloudstack UI, the system VMs will be stuck in the starting=20 > > > state. > > > > > > Testing > > > > > > Rebuilt system vm with change and it works perfectly. > > > > > > *Bugs: * CS-15588 > > > Diffs > > > > > > - patches/systemvm/debian/config/etc/init.d/cloud-early-config > > > (19f87c2) > > > > > > View Diff