On 03/06/2012 12:26 AM, Terry Phelps wrote:
When I created my VM's disks, before posing my original question, I did
specify which of my (accidentally) two data domain I wanted the disk to
go, but it did NOT go there. I presume that's a feature and not a bug,
right?
no. it would be a bug if
Hi,
My ovirt-engine was setup on a vm host with ip:xxx.xxx.xxx.112. And
I am trying to create a new domain with ovirt-engine UI by the
Storage-- New Domain. And the following error happened. However I
can mount the xxx.xxx.xxx.110:/data by mount -t nfs
xxx.xxx.xxx.110:/data /mnt
It seems that the problem came from the name of the data domain to be
created. I used data to be the name. Is data a reserved name for
the storage domain?
On 2012-3-6 17:30, Shu Ming wrote:
Hi,
My ovirt-engine was setup on a vm host with ip:xxx.xxx.xxx.112. And
I am trying to create a
Manually mount and touch with kvm:qemu user/group and see if success?
2012/3/6 Shu Ming shum...@linux.vnet.ibm.com:
It seems that the problem came from the name of the data domain to be
created. I used data to be the name. Is data a reserved name for the
storage domain?
On 2012-3-6 17:30,
The problem was resloved and It might come from the naming problem
using 'data' as domain name.
On 2012-3-6 22:55, Xiaofan wrote:
Manually mount and touch with kvm:qemu user/group and see if success?
2012/3/6 Shu Mingshum...@linux.vnet.ibm.com:
It seems that the problem came from the name of
On 03/07/2012 08:56 AM, Michael Pasternak wrote:
Hi David,
On 03/07/2012 12:08 AM, Li, David wrote:
Hi Michael,
Now I could create a host but couldn't delete it.
This is because you using not official release of the cli,
(you build cli rpm from the latest git right?!, you should use
6 matches
Mail list logo