Yes, that should all be specified in OVF, so it's hiden from template
registration form.
On Wed, 2 Jun 2021, 18:04 Corey, Mike, wrote:
> One area of change, not sure if it matters in my case, is that I can no
> longer specify the BIOS or EFI option of the instance/template.
>
> In the old UI,
One area of change, not sure if it matters in my case, is that I can no longer
specify the BIOS or EFI option of the instance/template.
In the old UI, when deploying an instance I could select the bios/efi in the
same window as controller and keyboard language etc. This option is NOT an
Oh i forgot: I am using 4.15.1 SNAPSHOT
Am 02.06.21 um 16:36 schrieb Udo Müller:
Hi guys,
next thing i stumple upon:
I have a VM which is setup from a windows categorized ISO and boottype
UEFI.
I can create and run the VM. But if i detach the ISO and want to
attach another one i get the
Hi guys,
next thing i stumple upon:
I have a VM which is setup from a windows categorized ISO and boottype UEFI.
I can create and run the VM. But if i detach the ISO and want to attach
another one i get the following error:
Dear all,
Is it possible to have one /24 network - for example
10.10.10.0/24 where it is divided into 2 shared networks as follow:
* Network A - 10.10.10.2-50 where 2 is Virtual router with DHCP for the ip
range mentioned
* Network B - 10.10.10.51-200 where 51 is
I saw that too - but that line regarding format is "ISO" for other deployments.
Example - I used an Ubuntu OVA from openvm and it deployed with the same
message...
You should acquire a new public ip for the isolated network. Then you can
configure firewall, portforwarder or loadbalancer on that ip.
You are not limited to use a single public ip in isolated network.
On Wed, Jun 2, 2021, 13:39 Jeremy Hansen wrote:
> I’m working through my initial setup of
There is no restriction about being on the same subnet but esxi management
ips should be reachable from management subnet of cloudstack (pod subnet).
AFAIK console proxy needs to reach esxi to proxy the vnc service as the vm
console to customer.
On Tue, Jun 1, 2021, 19:46 Daan Hoogland wrote:
Hi All,
I've created a 4.15.1.0 release, with the following artifacts up for a vote:
Git Branch and Commit SHA:
https://github.com/apache/cloudstack/tree/4.15.1.0-RC20210602T1429
Commit: aaac4b17099ba838a3f7b57400277ca9b23f98f5
Source release (checksums and signatures are available at the same
Isolated network = VR connected to both Public and Guest network (singe
network), plus 1 or more instances behind that VR, in that SINGLE network
VPC = VR (as above) + 1 or MORE networks, with instances in each network
If you want to really assign Public IP to your instances (old school VPS
style
I’m working through my initial setup of Cloudstack. I added a second vm host so
I could test live migration. Worked out the vlan kinks and that’s now working
great.
I launched a second guest and noticed it did not allocate a new public IP. My
expectation was that it would allocate another
Thank you Pearl!
Regards,
Jordan
-Original Message-
From: Pearl d'Silva
Sent: Wednesday, June 2, 2021 9:04 AM
To: users@cloudstack.apache.org
Subject: Re: "Bypass VLAN id/range overlap" argument missing?
[X] This message came from outside your organization
Hi Jordan,
The
Hi Jordan,
The 'bypassVlanOverlapCheck' parameter does exist in the createNetwork API, but
during API discovery the parameters sometimes get overwritten. This has been
addressed by https://github.com/apache/cloudstack/pull/4609 and will be
available as part of 4.15.1.
Thanks,
Pearl
13 matches
Mail list logo
