Hari,
Granularity of params and dynamic updates are two different issues. We
can file a enhance request for the dynamic updates and community can take
its development.
While granularity is what I think that is being considered currently.
On 14/04/13 11:22 AM, "Harikrishna Patnala"
wrote:
>Yes
Downloaded the vhd-util to my environment and had the same problem. I
Debugged this further by running the copy_vhd_from_secondarystorage.sh on
the XenServer. It looks like the copy_vhd_from_secondarystorage.sh is
looking for vhd-util in /opt/xensource/bin/ rather than /usr/bin/
I looked at this f
Yes Nitin, we need some listener kind of model but for the parameters that are
proposed may not need dynamic update (may be it needed for storage cleanup
interval).
Please correct me if I'm wrong. Can't we proceed normally for the doable
parameters.
-Harikrishna
On 11-Apr-2013, at 12:15 PM, Ni
That's weird...I have three local storages (one from DevCloud2 by default,
one from one ESXi host, and one from another ESXi host). I also have
several shared storages (iSCSI-based datastores that were configured in CS
as VMFS-based primary storages). I tagged the shared primary storage I
wanted
looks as though your zone is set to use shared storage, and youre only
providing local storage.
1. 2013-04-12 11:35:20,292 DEBUG [storage.allocator.
AbstractStoragePoolAllocator] (Job-Executor-11:job-11) Checking if
storage pool is suitable, name: devcloud Local Storage ,poolId: 200
2.
Now a new error shows:
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:432)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concu
Well you've got something trying to start, because you have vnet
interfaces. You need to look at your agent logs to see why the system VMS
refuse to start. If the power went out it could be corruption, the system
VMS may be waiting for you to fsck. It sounds like maybe the system was put
into produ
Greetings,
I'm have a terrible way to go, nothing I have done will start my cloud. None of
my system VM's will start, which in turn do not permit the regular OS VM's to
start. I suffered from first a power outage, then I manually rebooted my
server. Now, nothing is coming back online.
I was pr
This fixes an bug introduced in that commit.
I also want to point out that line 669 in ConfigurationServerImpl.java
traps exceptions thrown in development mode, hence this bug would not have
surfaced when ran in development mode. This 669 line appears to have been
committed months ago, removing it
I believe it was allowed because one can also create multiple NICs on the
same network while deploying a VM.
There may be people doing that to get multiple IPS auto-assigned to a VM.
On Apr 13, 2013 3:28 AM, "Saksham Srivastava"
wrote:
> Hi,
>
> Using addNicToVirtualMachine API user can add mul
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/10441/#review19121
---
Ship it!
Ship It!
- Milamber ASF
On April 13, 2013, 12:18 a.m.,
Hi,
Using addNicToVirtualMachine API user can add multiple NICs to a VM
I am also able to add multiple NICs to a VM on the same isolated guest network.
Is this a valid scenario??
If yes what could be the use case for the same?
Thanks,
Saksham
12 matches
Mail list logo
