[GitHub] [cloudstack-documentation] shwstppr commented on a change in pull request #53: [WIP - DO NOT MERGE] Constrained custom offerings update for 4.13
shwstppr commented on a change in pull request #53: [WIP - DO NOT MERGE] Constrained custom offerings update for 4.13 URL: https://github.com/apache/cloudstack-documentation/pull/53#discussion_r303733379 ## File path: source/adminguide/service_offerings.rst ## @@ -169,9 +162,13 @@ To create a new compute offering: system VM is running. Shared allocates from storage accessible via NFS. - - **Custom**: Custom compute offerings can be used in following + - **Provisioning type**: The type of disk that should be allocated. + Local + + + - **Compute Offering Type**: Custom compute offerings can be used in following cases: deploying a VM, changing the compute offering of a stopped - VM and running VMs, which is nothing but scaling up. + VM and running VMs. If the Custom field is checked, the end-user must fill in the Review comment: Can this be rephrased as there is no Custom checkbox field now This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-documentation] shwstppr commented on a change in pull request #53: [WIP - DO NOT MERGE] Constrained custom offerings update for 4.13
shwstppr commented on a change in pull request #53: [WIP - DO NOT MERGE] Constrained custom offerings update for 4.13 URL: https://github.com/apache/cloudstack-documentation/pull/53#discussion_r303734218 ## File path: source/adminguide/service_offerings.rst ## @@ -379,19 +379,27 @@ To create a new disk offering: Storage for the volume to be provisioned. If no such primary storage exists, allocation from the disk offering will fail.. - - **Public**: Indicate whether the service offering should be available - all domains or only some domains. Choose Yes to make it available - to all domains. Choose No to limit the scope to a subdomain; - CloudStack will then prompt for the subdomain's name. + - **Public**: Indicate whether the disk offering should be + available all domains or only some domains. Choose Yes to make it + available to all domains. Choose No to limit the scope to one or more + domains. When 'Public' is set to 'no' a multi-selection list box is + displayed. One or more domains can be selected from this list box. #. Click Add. +.. [2] These options are dependant on the capabilities of the hypervisor or the shared storage system which the VMs are on. + If the hypervisor or underlying storage don't support a particular capability in the offering, the setting will have no effect. + Modifying or Deleting a Service Offering -Service offerings cannot be changed once created. This applies to both -compute offerings and disk offerings. +Service offerings cannot be materially changed once created. This applies to +both compute offerings and disk offerings. However their name, description +and scope can be modified. To edit the name or description navigate to the +service offering's detail page and click on the edit icon |edit-icon.png|. +To alter the scope (zones and domains) that an offering is available in Review comment: Since zone specific offerings are referred here, will it be better to mention zone field in create section as well? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
Agent LB for CloudStack failed
Hello everyone
My kvm Agent LB on 4.11.2/4.11.3 failed. When the preferred managment node is
forced to power off, the agent will not immediately connect to the second
management node.After 15 minutes, the agent issues a "No route to host" error
and connects to the second management node.
management node:
acs-mn01,172.17.1.141
acs-mn02,172.17.1.142
mysql db node:
acs-db01
kvmm agent node:
test-ceph-node01
test-ceph-node02
test-ceph-node03
test-ceph-node04
global seting
host=172.17.1.142,172.17.1.141
indirect.agent.lb.algorithm=roundrobin
indirect.agent.lb.check.interval=60
Partial agnet logs:
2019-07-15 23:22:39,340 DEBUG [cloud.agent.Agent] (UgentTask-5:null) (logid:)
Sending ping: Seq 1-19: { Cmd , MgmtId: -1, via: 1, Ver : v1, Flags: 11,
[{"com.cloud.agent.api.PingRoutingWithNwGroupsCommand":{"newGroupStates":{},"_hostVmStateReport":{},"_gatewayAccessible":true,"_vnetAccessible":true,"hostType
":"Routing","hostId":1,"wait":0}}] }
2019-07-15 23:23:09,960 DEBUG [utils.nio.NioConnection]
(Agent-NioConnectionHandler-1:null) (logid:) Location 1: Socket
Socket[addr=/172.17.1.142,port=8250,localport= 34854] closed on read. Probably
-1 returned: No route to host
2019-07-15 23:23:09,960 DEBUG [utils.nio.NioConnection]
(Agent-NioConnectionHandler-1:null) (logid:) Closing socket
Socket[addr=/172.17.1.142,port=8250,localport=34854]
2019-07-15 23:23:09,961 DEBUG [cloud.agent.Agent] (Agent-Handler-4:null)
(logid:a4e4de49) Clearing watch list: 2
2019-07-15 23:23:09,962 INFO [cloud.agent.Agent] (Agent-Handler-4:null)
(logid:a4e4de49) Lost connection to host: 172.17.1.142. Attempting reconnection
while we still have 0 commands in Progress.
2019-07-15 23:23:09,963 INFO [utils.nio.NioClient] (Agent-Handler-4:null)
(logid:a4e4de49) NioClient connection closed
2019-07-15 23:23:09,964 INFO [cloud.agent.Agent] (Agent-Handler-4:null)
(logid:a4e4de49) Reconnecting to host:172.17.1.142
2019-07-15 23:23:09,964 INFO [utils.nio.NioClient] (Agent-Handler-4:null)
(logid:a4e4de49) Connecting to 172.17.1.142:8250
2019-07-15 23:23:12,972 ERROR [utils.nio.NioConnection] (Agent-Handler-4:null)
(logid:a4e4de49) Unable to initialize the threads.
java.net.NoRouteToHostException: No route to host
At sun.nio.ch.Net.connect0(Native Method)
At sun.nio.ch.Net.connect(Net.java:454)
At sun.nio.ch.Net.connect(Net.java:446)
At sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:648)
At com.cloud.utils.nio.NioClient.init(NioClient.java:56)
At com.cloud.utils.nio.NioConnection.start(NioConnection.java:95)
At com.cloud.agent.Agent.reconnect(Agent.java:517)
At com.cloud.agent.Agent$ServerHandler.doTask(Agent.java:1091)
At com.clo
[GitHub] [cloudstack-documentation] nvazquez commented on a change in pull request #53: [WIP - DO NOT MERGE] Constrained custom offerings update for 4.13
nvazquez commented on a change in pull request #53: [WIP - DO NOT MERGE] Constrained custom offerings update for 4.13 URL: https://github.com/apache/cloudstack-documentation/pull/53#discussion_r303564191 ## File path: source/adminguide/service_offerings.rst ## @@ -69,14 +77,20 @@ available offerings when they create a new VM. Based on the user’s selected offering, CloudStack emits usage records that can be integrated with billing systems. -Some characteristics of service offerings must be defined by the CloudStack -administrator, and others can be left undefined so that the end-user can -enter their own desired values. This is useful to reduce the number of -offerings the CloudStack administrator has to define. Instead of defining a -compute offering for every imaginable combination of values that a user +Compute offerings may be "fixed", "custom constrained" or "custom unconstrained". + +In fixed offering the Number of CPUs, Memory and CPU frequecy in each service +offerings are predefined by the CloudStack administrator, in custom unconstrained +offerings they are left undefined so that the end-user can enter their own desired +values when creating a guest instance. Since 4.13 custom constrained offerings have +been introduced to allow the end-user to enter the number of CPUs and memory +required within constraints set by the administrator. The constraints can be +different for different custom constrained offerings. This is useful to reduce +the number of offerings the CloudStack administrator has to define; Instead of +defining acompute offering for every imaginable combination of values that a user Review comment: Minor one: blankspace missing (acompute) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-documentation] ACSGitBot commented on issue #54: KVM direct downloads
ACSGitBot commented on issue #54: KVM direct downloads URL: https://github.com/apache/cloudstack-documentation/pull/54#issuecomment-511502754 Build finished. You can review it at: https://acs-www.shapeblue.com/docs/pr54 Build Log Output: No log errors found to report. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-documentation] PaulAngus commented on issue #54: KVM direct downloads
PaulAngus commented on issue #54: KVM direct downloads URL: https://github.com/apache/cloudstack-documentation/pull/54#issuecomment-511502131 requesting docbuild This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-documentation] ACSGitBot commented on issue #54: KVM direct downloads
ACSGitBot commented on issue #54: KVM direct downloads URL: https://github.com/apache/cloudstack-documentation/pull/54#issuecomment-511502190 Your request had been received, i'll go and build the documentation and check the output log for errors. This shouldn't take long. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-documentation] ACSGitBot commented on issue #53: [WIP - DO NOT MERGE] Constrained custom offerings update for 4.13
ACSGitBot commented on issue #53: [WIP - DO NOT MERGE] Constrained custom offerings update for 4.13 URL: https://github.com/apache/cloudstack-documentation/pull/53#issuecomment-511467765 Build finished. You can review it at: https://acs-www.shapeblue.com/docs/pr53 Build Log Output: No log errors found to report. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-documentation] nvazquez opened a new pull request #54: KVM direct downloads
nvazquez opened a new pull request #54: KVM direct downloads URL: https://github.com/apache/cloudstack-documentation/pull/54 Add documentation for direct downloads on KVM This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-documentation] PaulAngus commented on issue #53: [WIP - DO NOT MERGE] Constrained custom offerings update for 4.13
PaulAngus commented on issue #53: [WIP - DO NOT MERGE] Constrained custom offerings update for 4.13 URL: https://github.com/apache/cloudstack-documentation/pull/53#issuecomment-511467145 requesting docbuild This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-documentation] ACSGitBot commented on issue #53: [WIP - DO NOT MERGE] Constrained custom offerings update for 4.13
ACSGitBot commented on issue #53: [WIP - DO NOT MERGE] Constrained custom offerings update for 4.13 URL: https://github.com/apache/cloudstack-documentation/pull/53#issuecomment-511467176 Your request had been received, i'll go and build the documentation and check the output log for errors. This shouldn't take long. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-documentation] PaulAngus opened a new pull request #53: [WIP - DO NOT MERGE] Constrained custom offerings update for 4.13
PaulAngus opened a new pull request #53: [WIP - DO NOT MERGE] Constrained custom offerings update for 4.13 URL: https://github.com/apache/cloudstack-documentation/pull/53 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
Re: [ANNOUNCE] Sven Vogel has joined the PMC
Hi Guys, I am highly rally highly delighted to get an PMC. Nice to work with you all! Let’s bring Cloudstack together in the next level. Cheers Sven __ Sven Vogel Teamlead Platform EWERK RZ GmbH Brühl 24, D-04109 Leipzig P +49 341 42649 - 11 F +49 341 42649 - 18 s.vo...@ewerk.com www.ewerk.com Geschäftsführer: Dr. Erik Wende, Hendrik Schubert, Frank Richter Registergericht: Leipzig HRB 17023 Zertifiziert nach: ISO/IEC 27001:2013 DIN EN ISO 9001:2015 DIN ISO/IEC 2-1:2011 EWERK-Blog | LinkedIn | Xing | Twitter | Facebook Auskünfte und Angebote per Mail sind freibleibend und unverbindlich. Disclaimer Privacy: Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System. Vielen Dank. The contents of this e-mail (including any attachments) are confidential and may be legally privileged. If you are not the intended recipient of this e-mail, any disclosure, copying, distribution or use of its contents is strictly prohibited, and you should please notify the sender immediately and then delete it (including any attachments) from your system. Thank you. > Am 14.07.2019 um 23:59 schrieb Tutkowski, Mike : > > Congratulations, Sven! > > > From: Paul Angus > Sent: Saturday, July 13, 2019 9:44:47 AM > To: priv...@cloudstack.apache.org; dev@cloudstack.apache.org; > us...@cloudstack.apache.org > Subject: [ANNOUNCE] Sven Vogel has joined the PMC > > NetApp Security WARNING: This is an external email. Do not click links or > open attachments unless you recognize the sender and know the content is safe. > > > > > Fellow CloudStackers, > > > > It gives me great pleasure to say that Sven has been invited to join the > PMC and has gracefully accepted. > > > Please joining me in congratulating Sven! > > > > > Kind regards, > > > > Paul Angus > > CloudStack PMC
Re: [ANNOUNCE] Gabriel Beims Bräscher, Andrija Panic, Sven Vogel has joined the PMC
Congratulations, everyone!
Re: [ANNOUNCE] Apache CloudStack LTS Maintenance Release 4.11.3.0
Good work everybody! This release contains a few crucial fixes for us, so we're happy it's there! On Sat, 2019-07-13 at 16:52 +0100, Paul Angus wrote: > Announcing Apache CloudStack LTS Maintenance Release 4.11.30 > > > > The Apache CloudStack project is pleased to announce the release of > CloudStack 4.11.3.0 as part of its LTS 4.11.x releases. The > CloudStack > 4.11.3.0 release contains c. 50 fixes on top of the CloudStack > 4.11.2.0 > release. CloudStack LTS branches are supported for 20 months and will > receive updates for the first 14 months. For the final six months, > only > security updates are provided. > > > > Apache CloudStack is an integrated Infrastructure-as-a-Service (IaaS) > software platform allowing users to build feature-rich public and > private > cloud environments. CloudStack includes an intuitive user interface > and > rich API for managing the compute, networking, software, and storage > resources. The project became an Apache top level project in March, > 2013. > More information about Apache CloudStack can be found at: > > http://cloudstack.apache.org/ > > > > # Documentation > > > > The 4.11.3.0 release notes include a full list of issues fixed: > > http://docs.cloudstack.apache.org/en/4.11.3.0/releasenotes/fixed_issues.html > > > > > The CloudStack documentation includes upgrade instructions from > previous > versions of Apache CloudStack, and can be found at: > > http://docs.cloudstack.apache.org/en/4.11.3.0/upgrading/index.html > > > The official installation, administration and API documentation for > each of > the releases are available on our documentation page: > > http://docs.cloudstack.apache.org/ > > > > # Downloads > > > > The official source code for the 4.11.3.0 release can be downloaded > from > our downloads page: > > http://cloudstack.apache.org/downloads.html > > > > In addition to the official source code release, individual > contributors > have also made convenience binaries available on the Apache > CloudStack > download page, and can be found at: > > > http://download.cloudstack.org/ubuntu/dists/ > > http://download.cloudstack.org/centos/6/ > > http://download.cloudstack.org/centos/7/ > > http://www.shapeblue.com/packages/ > > > > Kind regards, > > > > Paul Angus
Re: Reg : qemu-kvm upgrade in KVM hypervisor agent
Looks like the logic here was designed to solve a different problem
// for KVM, only allow snapshot with memory when VM is in running state
if (userVmVo.getHypervisorType() == HypervisorType.KVM &&
userVmVo.getState() == State.Running && !snapshotMemory) {
throw new InvalidParameterValueException("KVM VM does not allow to
take a disk-only snapshot when VM is in running state");
}
Should probably be
userVmVo.getHypervisorType() == HypervisorType.KVM &&
userVmVo.getState() != State.Running && snapshotMemory
On Mon, Jul 15, 2019 at 12:21 PM Vladimir Melnik wrote:
> Yes, exactly. It's being thrown by qemu-img. You can try it and see the
> same. :-)
>
> On Mon, Jul 15, 2019 at 11:06:37AM +0200, Wei ZHOU wrote:
> > Hi Vladimir,
> >
> > The error should not be thrown by cloudstack I think.
> >
> > -Wei
> >
> > Vladimir Melnik 于2019年7月15日周一 上午10:59写道：
> > > I don't remember (I tried it about a half-year ago), but it was
> > > something regarding impossibility of touching a qcow2-file that is
> being
> > > opened by another process. :-(
> > > On Mon, Jul 15, 2019 at 10:25:19AM +0200, Wei ZHOU wrote:
> > > > Hi Vladimir,
> > > > What's the error message ?
> > > > You should be able to create a vm snapshot, then create volume
> snapshot
> > > > from vmsnapshot.
> > > > -Wei
> > > > Vladimir Melnik 于2019年7月15日周一 上午9:44写道：
> > > > > Hello,
> > > > > I tried to use qemu-kvm-ev with ACS 4.11.2 and have found out that
> it
> > > makes
> > > > > impossible to take a snapshot of a running instance's volume. :-(
> > > > > On Thu, Jun 13, 2019 at 07:16:24AM +, Pavan Kumar Aravapalli
> wrote:
> > > > > > Hello,
> > > > > > As part of KVM upgrade it's found that default package
> 'qemu-kvm' [
> > > > > which comes with OS distro] does not support machine chipset type
> > > 'q35'.
> > > > > And this support can be leveraged by installing 'qemu-kvm-ev'
> which is
> > > > > from centos-release-qemu-ev repo.
> > > > > > I saw some some old mail threads saying that they have
> integrated
> > > > > qemu-kvm-ev, but still in agent bundle rpm requirements [
> > >
> https://github.com/apache/cloudstack/blob/master/packaging/centos7/cloud.spec
> > > ]
> > > > > I found old 'qemu-kvm' only.
> > > > > > Can we leverage this package qemu-kvm-ev in agent rpm bundle?.
> Has
> > > > > anyone faced any issues in Cloud Stack after upgrading the package.
>
Re: Reg : qemu-kvm upgrade in KVM hypervisor agent
Yes, exactly. It's being thrown by qemu-img. You can try it and see the same. :-) On Mon, Jul 15, 2019 at 11:06:37AM +0200, Wei ZHOU wrote: > Hi Vladimir, > > The error should not be thrown by cloudstack I think. > > -Wei > > Vladimir Melnik 于2019年7月15日周一 上午10:59写道： > > I don't remember (I tried it about a half-year ago), but it was > > something regarding impossibility of touching a qcow2-file that is being > > opened by another process. :-( > > On Mon, Jul 15, 2019 at 10:25:19AM +0200, Wei ZHOU wrote: > > > Hi Vladimir, > > > What's the error message ? > > > You should be able to create a vm snapshot, then create volume snapshot > > > from vmsnapshot. > > > -Wei > > > Vladimir Melnik 于2019年7月15日周一 上午9:44写道： > > > > Hello, > > > > I tried to use qemu-kvm-ev with ACS 4.11.2 and have found out that it > > makes > > > > impossible to take a snapshot of a running instance's volume. :-( > > > > On Thu, Jun 13, 2019 at 07:16:24AM +, Pavan Kumar Aravapalli wrote: > > > > > Hello, > > > > > As part of KVM upgrade it's found that default package 'qemu-kvm' [ > > > > which comes with OS distro] does not support machine chipset type > > 'q35'. > > > > And this support can be leveraged by installing 'qemu-kvm-ev' which is > > > > from centos-release-qemu-ev repo. > > > > > I saw some some old mail threads saying that they have integrated > > > > qemu-kvm-ev, but still in agent bundle rpm requirements [ > > https://github.com/apache/cloudstack/blob/master/packaging/centos7/cloud.spec > > ] > > > > I found old 'qemu-kvm' only. > > > > > Can we leverage this package qemu-kvm-ev in agent rpm bundle?. Has > > > > anyone faced any issues in Cloud Stack after upgrading the package.
Re: Reg : qemu-kvm upgrade in KVM hypervisor agent
Looks like it does [image: Screen Shot 2019-07-15 at 12.20.22 PM.png] On Mon, Jul 15, 2019 at 12:07 PM Wei ZHOU wrote: > Hi Vladimir, > > The error should not be thrown by cloudstack I think. > > -Wei > > > Vladimir Melnik 于2019年7月15日周一 上午10:59写道： > > > I don't remember (I tried it about a half-year ago), but it was > > something regarding impossibility of touching a qcow2-file that is being > > opened by another process. :-( > > > > On Mon, Jul 15, 2019 at 10:25:19AM +0200, Wei ZHOU wrote: > > > Hi Vladimir, > > > > > > What's the error message ? > > > > > > You should be able to create a vm snapshot, then create volume snapshot > > > from vmsnapshot. > > > > > > -Wei > > > > > > Vladimir Melnik 于2019年7月15日周一 上午9:44写道： > > > > > > > Hello, > > > > > > > > I tried to use qemu-kvm-ev with ACS 4.11.2 and have found out that it > > makes > > > > impossible to take a snapshot of a running instance's volume. :-( > > > > > > > > On Thu, Jun 13, 2019 at 07:16:24AM +, Pavan Kumar Aravapalli > wrote: > > > > > Hello, > > > > > As part of KVM upgrade it's found that default package 'qemu-kvm' [ > > > > which comes with OS distro] does not support machine chipset type > > 'q35'. > > > > And this support can be leveraged by installing 'qemu-kvm-ev' which > is > > > > from centos-release-qemu-ev repo. > > > > > I saw some some old mail threads saying that they have integrated > > > > qemu-kvm-ev, but still in agent bundle rpm requirements [ > > > > > > > https://github.com/apache/cloudstack/blob/master/packaging/centos7/cloud.spec > > ] > > > > I found old 'qemu-kvm' only. > > > > > Can we leverage this package qemu-kvm-ev in agent rpm bundle?. Has > > > > anyone faced any issues in Cloud Stack after upgrading the package. > > > > > > >
Re: Reg : qemu-kvm upgrade in KVM hypervisor agent
Hi Vladimir, The error should not be thrown by cloudstack I think. -Wei Vladimir Melnik 于2019年7月15日周一 上午10:59写道： > I don't remember (I tried it about a half-year ago), but it was > something regarding impossibility of touching a qcow2-file that is being > opened by another process. :-( > > On Mon, Jul 15, 2019 at 10:25:19AM +0200, Wei ZHOU wrote: > > Hi Vladimir, > > > > What's the error message ? > > > > You should be able to create a vm snapshot, then create volume snapshot > > from vmsnapshot. > > > > -Wei > > > > Vladimir Melnik 于2019年7月15日周一 上午9:44写道： > > > > > Hello, > > > > > > I tried to use qemu-kvm-ev with ACS 4.11.2 and have found out that it > makes > > > impossible to take a snapshot of a running instance's volume. :-( > > > > > > On Thu, Jun 13, 2019 at 07:16:24AM +, Pavan Kumar Aravapalli wrote: > > > > Hello, > > > > As part of KVM upgrade it's found that default package 'qemu-kvm' [ > > > which comes with OS distro] does not support machine chipset type > 'q35'. > > > And this support can be leveraged by installing 'qemu-kvm-ev' which is > > > from centos-release-qemu-ev repo. > > > > I saw some some old mail threads saying that they have integrated > > > qemu-kvm-ev, but still in agent bundle rpm requirements [ > > > > https://github.com/apache/cloudstack/blob/master/packaging/centos7/cloud.spec > ] > > > I found old 'qemu-kvm' only. > > > > Can we leverage this package qemu-kvm-ev in agent rpm bundle?. Has > > > anyone faced any issues in Cloud Stack after upgrading the package. > > > >
Re: Reg : qemu-kvm upgrade in KVM hypervisor agent
I don't remember (I tried it about a half-year ago), but it was something regarding impossibility of touching a qcow2-file that is being opened by another process. :-( On Mon, Jul 15, 2019 at 10:25:19AM +0200, Wei ZHOU wrote: > Hi Vladimir, > > What's the error message ? > > You should be able to create a vm snapshot, then create volume snapshot > from vmsnapshot. > > -Wei > > Vladimir Melnik 于2019年7月15日周一 上午9:44写道： > > > Hello, > > > > I tried to use qemu-kvm-ev with ACS 4.11.2 and have found out that it makes > > impossible to take a snapshot of a running instance's volume. :-( > > > > On Thu, Jun 13, 2019 at 07:16:24AM +, Pavan Kumar Aravapalli wrote: > > > Hello, > > > As part of KVM upgrade it's found that default package 'qemu-kvm' [ > > which comes with OS distro] does not support machine chipset type 'q35'. > > And this support can be leveraged by installing 'qemu-kvm-ev' which is > > from centos-release-qemu-ev repo. > > > I saw some some old mail threads saying that they have integrated > > qemu-kvm-ev, but still in agent bundle rpm requirements [ > > https://github.com/apache/cloudstack/blob/master/packaging/centos7/cloud.spec] > > I found old 'qemu-kvm' only. > > > Can we leverage this package qemu-kvm-ev in agent rpm bundle?. Has > > anyone faced any issues in Cloud Stack after upgrading the package. > >
Re: Reg : qemu-kvm upgrade in KVM hypervisor agent
Hi Vladimir, What's the error message ? You should be able to create a vm snapshot, then create volume snapshot from vmsnapshot. -Wei Vladimir Melnik 于2019年7月15日周一 上午9:44写道： > Hello, > > I tried to use qemu-kvm-ev with ACS 4.11.2 and have found out that it makes > impossible to take a snapshot of a running instance's volume. :-( > > On Thu, Jun 13, 2019 at 07:16:24AM +, Pavan Kumar Aravapalli wrote: > > Hello, > > As part of KVM upgrade it's found that default package 'qemu-kvm' [ > which comes with OS distro] does not support machine chipset type 'q35'. > And this support can be leveraged by installing 'qemu-kvm-ev' which is > from centos-release-qemu-ev repo. > > I saw some some old mail threads saying that they have integrated > qemu-kvm-ev, but still in agent bundle rpm requirements [ > https://github.com/apache/cloudstack/blob/master/packaging/centos7/cloud.spec] > I found old 'qemu-kvm' only. > > Can we leverage this package qemu-kvm-ev in agent rpm bundle?. Has > anyone faced any issues in Cloud Stack after upgrading the package. >
Re: [ANNOUNCE] Apache CloudStack LTS Maintenance Release 4.11.3.0
Hello, By when will it available to us publicly to upgrade? Thanks On Mon, Jul 15, 2019 at 12:23 PM Vladimir Melnik wrote: > My congratulations to you, good people! Thank you for doing this great > job. > > I've upgraded yesterday, everything to keep working fine. > > The only thing that surprised me a little was the fact that one should > upgrade the system-VM image to upgrade a minor version. I think, it can > be a trap for people who tend to run "yum upgrade" on their servers > without diving into the details of each package marked for upgrading. > > I hope, no one will hurt due to that. :-) > > Again, thanks to everyone who contributes to this great project. You > totally rock! > > On Sat, Jul 13, 2019 at 04:52:12PM +0100, Paul Angus wrote: > > Announcing Apache CloudStack LTS Maintenance Release 4.11.30 >
Re: [ANNOUNCE] Apache CloudStack LTS Maintenance Release 4.11.3.0
My congratulations to you, good people! Thank you for doing this great job. I've upgraded yesterday, everything to keep working fine. The only thing that surprised me a little was the fact that one should upgrade the system-VM image to upgrade a minor version. I think, it can be a trap for people who tend to run "yum upgrade" on their servers without diving into the details of each package marked for upgrading. I hope, no one will hurt due to that. :-) Again, thanks to everyone who contributes to this great project. You totally rock! On Sat, Jul 13, 2019 at 04:52:12PM +0100, Paul Angus wrote: > Announcing Apache CloudStack LTS Maintenance Release 4.11.30
Re: Reg : qemu-kvm upgrade in KVM hypervisor agent
Hello, I tried to use qemu-kvm-ev with ACS 4.11.2 and have found out that it makes impossible to take a snapshot of a running instance's volume. :-( On Thu, Jun 13, 2019 at 07:16:24AM +, Pavan Kumar Aravapalli wrote: > Hello, > As part of KVM upgrade it's found that default package 'qemu-kvm' [ which > comes with OS distro] does not support machine chipset type 'q35'. And > this support can be leveraged by installing 'qemu-kvm-ev' which is from > centos-release-qemu-ev repo. > I saw some some old mail threads saying that they have integrated > qemu-kvm-ev, but still in agent bundle rpm requirements > [https://github.com/apache/cloudstack/blob/master/packaging/centos7/cloud.spec] > I found old 'qemu-kvm' only. > Can we leverage this package qemu-kvm-ev in agent rpm bundle?. Has anyone > faced any issues in Cloud Stack after upgrading the package.
