Workaround is run "/etc/init.d/cloud-early-config start"
Att.
Marcelo
-Original Message-
From: Ivan Kudryavtsev
Sent: quinta-feira, 20 de setembro de 2018 13:46
To: users
Subject: Re: VR DHCP issue
Hello, in the past and in 4.9 too, I have met a bug like that with DHCP:
https://github
Hello, Daan, Rafael.
Ok, let's discover some points.
Rafael:
All the stuff is managed in Elasticsearch, clustered ES is supported as
well. As for now, value datatype is 'keyword' and doesn't fit well for
blobs. But, actually, there are no practical limitations except we don't
want press the CS se
sounds nice Ivan, Do you have a whitepaper on it? I strugle to see a clear
usecase for this plugin. maybe you have a casus or two!?!
On Wed, Sep 19, 2018 at 9:02 AM Ivan Kudryavtsev
wrote:
> Hello, community.
>
> We glad to announce a new Open Source plug-in for Apache CloudStack which
> helps t
Hello, in the past and in 4.9 too, I have met a bug like that with DHCP:
https://github.com/fgrehm/vagrant-lxc/issues/153
I have to apply that fix in our VRs to make it work always as expected.
чт, 20 сент. 2018 г., 22:52 Dag Sonstebo :
> Hi Allessandro,
>
> First of all have you tried to restar
Hi Allessandro,
First of all have you tried to restart the networks "with cleanup"
(alternatively just destroyed the VRs and let them recreate)?
Can you check the content of the following files on your problem VRs:
/etc/dhcphosts.txt
/etc/cloudstack/dhcpentry.json
Also look through the VR /var
Np, glad it helped :)
On Thu, 20 Sep 2018 at 16:40, Yordan Kostov
wrote:
> Hello Andrija,
>
> Your suggestion helped!
>
> There were issues with the system VMs getting IP address so I had to
> delete them from the hypervisor and after that I set UPDATE vm_instance SET
> removed=now() for the vm
Hi guys,
I'm experiencing an issue in our CS 4.9.
In fact, sonce a week ago, randomly some instances became unreachable.
After investigation we see that instances does not have IP address.
We tried to restart VR, restart instance, migrate both to another host, but
same issue.
So we configured the i
Hello Andrija,
Your suggestion helped!
There were issues with the system VMs getting IP address so I had to delete
them from the hypervisor and after that I set UPDATE vm_instance SET
removed=now() for the vms in the db to make them disappear in CD.
I did not know that ip relocation remained
Did you try disabling the zone first, delete ssvm and cpvm? Then try to
delete it...
Otherwise, you can check the DB, there is table named user_ip_address (from
top of my kind, not sure of name) and there you can check if any public IP
is assigned etc.
Best
Andrija
On Thu, Sep 20, 2018, 15:24 Yo
Dear all,
I am trying to remove a zone from Cloudstack.
Before I do that I went to delete the physical networks but I
get the error message (for the one that holds public vlan) : The Physical
Network is not deletable because there are public IP addresses allocated
Hello Rene
Even for VR's running on KVM, 256MB is really less. Thats why we offer
extra VR with 2 cores and 1GB RAM as another option so that customers can
use it instead of the default 256MB and 1 core.
On Tue, Sep 18, 2018 at 5:56 PM Rene Moser wrote:
> Hi
>
> While running test for a 4.11.1
Hello Ugo
You can change the display name of a vm through database or cloudmonkey
without stopping the vm. You need to change the name in two tables if you
are doing through database
Change display_name in "vm_instance" and "user_vm" tables. We did it for
our customers and didnt face any issue
O
Sooo... here is my experience:
if using correct VirtIO OS TYPE (set on template/VM) - i.e. ubuntu 14.04,
Centos 6.x or 7.x, Windows PV, other PV (but NOT centos 6.0 or 7.0 - these
"dot zero" versions are NOT virtio at least in ACS 4.8), then when VM is
STARTED FROM ACS (power on VM) - all drives s
ok, thx once more :)
On Wed, 19 Sep 2018 at 18:06, Rafael Weingärtner <
[email protected]> wrote:
> >
> > Btw, do you know what actually REALLY happens when you restart Network
> > (part of VPC), not the whole VPC - since I was not clear if this does
> > anything (and it takes 1-3 secon
It looks like I can just add
rootDiskController virtio
To the templates settings tab?
Can anyone confirm?
Thanks
Adam
-Original Message-
From: Ivan Kudryavtsev
Sent: 20 September 2018 10:20
To: users
Subject: Re: Disk controller type
** This mail originated from OUTSIDE the Oakfo
Controler depends on setyings, specified in template or os family used. So
Windows guests don't receive virtio for network and storagr, thus they can
be deployed without additional drivers.
чт, 20 сент. 2018 г., 16:19 Ivan Kudryavtsev :
> Rakesh, It doesn't work like that for CS as it uses statel
Rakesh, It doesn't work like that for CS as it uses stateless XML configs.
чт, 20 сент. 2018 г., 16:12 Rakesh Venkatesh :
> I think you can change the controller type in XML file of the VM but not
> sure if that works or not.
>
> virsh dumpxml
> virsh edit
> change the controller type, save and
I think you can change the controller type in XML file of the VM but not
sure if that works or not.
virsh dumpxml
virsh edit
change the controller type, save and start the vm again
On Thu, Sep 20, 2018 at 9:59 AM Adam Witwicki
wrote:
> Hello,
>
> I have a number of of instances using the wron
-0
A bug was found in the systemvmtemplate patching code and has been fixed in
this PR:
https://github.com/apache/cloudstack/pull/2855 (tests OK)
The above fix does not require new packages per se, but only a new
systemvmtemplate. Please continue testing RC1 this week so if we find any
addi
Hello,
I have a number of of instances using the wrong controller type (ATA) does
anyone know where this is set in the database so I can start them with the
VirtIO scsi controller?
Thanks
Adam
Disclaimer Notice:
This email has been sent by Oakford Technology Limited, while we have checked
20 matches
Mail list logo
