Hi,
Is it possible that I can get the host to the pool with different amount of CPU?
*This is a Xen
Regards,
[firmalore]
De: Sanjeev Neelarapu [mailto:sanjeev.neelar...@accelerite.com]
Enviado el: Monday, June 13, 2016 11:47 PM
Para: users@cloudstack.apache.org
Asunto: RE: incluide host to
Thanks Kirk, will give it a try
Regards,
Timothy Lothering
On 14 Jun 2016 20:56, "Kirk Kosinski" wrote:
> Hi, you can configure the cores per socket on the template. I'm not sure
> if this works in CloudStack 4.3 but it should in 4.4 and newer. [1] It is
>
Hi, you can configure the cores per socket on the template. I'm not sure if
this works in CloudStack 4.3 but it should in 4.4 and newer. [1] It is
configured by adding a detail with cpu.corespersocket=# to the template. I'm
not sure if this is possible in the UI, so if not, try the
Hi, are you seeing this behavior with isolated or shared networks? I believe
that is the expected behavior for an isolated network, whereas for shared
networks the VLAN should be persistent.
Best regards,
kirk.kosin...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London
Hi All,
Our present environment is CS4.3.1 and XENSERVER 6.2.
In Cloud Stack we will create a separate VLAN ID for each Virtual machine.
While doing maintenance or if we reboot the router for any reasons, the VLAN ID
for the virtual machine changes.
My query is I want to keep the same VLAN ID
Hello Community,
We have found a very interesting issue with CPU allocation in ACS 4.3 and
VMware. When a Service Offering is configured, you can choose the number of
Cores and clock speed, which is simple enough. The problem comes in on HOW
the cores are assigned.
In VMware at least, each
Hello Community,
We have found a very interesting issue with CPU allocation in ACS 4.3 and
VMware. When a Service Offering is configured, you can choose the number of
Cores and clock speed, which is simple enough. The problem comes in on HOW
the cores are assigned.
In VMware at least, each
Stephan,
Thanks for your reply.
Yes, we run the storage network over the same bond. We are not using
the X540-AT2, we are using the X520-DA2. We are using SFP+, not RJ-45.
I'd rather use TwinAx cables or SFP+, as our switches are not RJ-45. So,
I'd prefer not to upgrade to those
Hi, Paul
Thank you for your e-mail.
And I will write the details of my networking.
Please wait for my e-mail.
(English is too difficult for me(^^))
Regards
>-Original Message-
>From: Remi Bergsma [mailto:rberg...@schubergphilis.com]
>Sent: Tuesday, June 14, 2016 4:27 PM
>To:
Hi,
I filed a bug for this a while back:
https://issues.apache.org/jira/browse/CLOUDSTACK-9227
If you have any further info, please add to the ticket - particularly if you
find a fix :)
Kind regards,
Paul Angus
paul.an...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden,
Hi,
XS 6.5 is built around CentOS 5 with a custom 3.10 Kernel. Using bonded
X540-AT2 NIC, I can't see any problems.
Depending on your network setup, your bond might be created and managed
by OVS instead of Kernel.
Just a guess, but OVS runs in userspace and could be affected by Dom0
RAM shortage
Hi Paul,
I don’t get it but that’s probably me :-) Never mind.
Regards,
Remi
On 13/06/16 16:00, "Paul Angus" wrote:
>Remi,
>
>I think asking for the details for Maruko San's networking in order to give
>him (hopefully) useful specific help covered that part.
>
12 matches
Mail list logo