- Users - oVirt List Archives

[Users] Make dependant on git
by Elias Abacioglu 09 Mar '12

09 Mar '12

Hi, I wanna create rpms from the source, latest stable tarball. [root@virtual ovirt-engine]# make rpm tar zcf ovirt-engine-3.0.0_0001.tar.gz `git ls-files` fatal: Not a git repository (or any of the parent directories): .git tar: Cowardly refusing to create an empty archive Try `tar --help' or `tar --usage' for more information. make: *** [ovirt-engine-3.0.0_0001.tar.gz] Error 2 [root@virtual ovirt-engine]# make srpm tar zcf ovirt-engine-3.0.0_0001.tar.gz `git ls-files` fatal: Not a git repository (or any of the parent directories): .git tar: Cowardly refusing to create an empty archive Try `tar --help' or `tar --usage' for more information. make: *** [ovirt-engine-3.0.0_0001.tar.gz] Error 2 Problem is I did not fetch ovirt git repo. Shouldn't tar populate the files it should tar in some other way perhaps? /Raboo

1 0

Re: [Users] Can I bypass VDSM?
by Andrew Cathrow 09 Mar '12

09 Mar '12

If you still want to use the ovirt-engine then this isn't an option, but if you want to handle all the management yourself than this will work. "Li, David" <LiD(a)cloudshield.com> wrote: Hi, Is it possible to bypass VDSM but use libvirt directly to manage ovirt node? David

1 0

[Users] having problem with a storage node
by Dominic Kaiser 08 Mar '12

08 Mar '12

I am using openfiler for my baremetal storage node. It is an NFS share all permissions are right. I currently have a master data node setup the same way and working fine. I was trying to use this data NFS as another storage node to create virtual disks on to run vms. I can attach fine and create disks fine but cannot run a vm. Here is the error: VM fs1 is down. Exit message internal error process exited while connecting to monitor: qemu-kvm: -drive file=/rhev/data-center/c10c25e0-526a-11e1-a5e4-87fa674ffb5d/60a1dff7-f112-433b-b49d-94a14b9ce3f1/images/cfecc532-9a2e-45f5-af71-190b8447c47d/100321d7-f575-4b3b-9af5-d25d765e779f,if=none,id=drive-virtio-disk0,format=raw,serial=f5-af71-190b8447c47d,cache=none,werror=stop,rerror=stop,aio=threads: could not open disk image /rhev/data-center/c10c25e0-526a-11e1-a5e4-87fa674ffb5d/60a1dff7-f112-433b-b49d-94a14b9ce3f1/images/cfecc532-9a2e-45f5-af71-190b8447c47d/100321d7-f575-4b3b-9af5-d25d765e779f: Permission denied . Again permissions are set fine vdsm owns them and can access and create disks just cannot run the vm. Thanks, -- Dominic Kaiser Greater Boston Vineyard Director of Operations cell: 617-230-1412 fax: 617-252-0238 email: dominic(a)bostonvineyard.org

1 0

[Users] missing iso files?
by Joe Pruett 08 Mar '12

08 Mar '12

the docs imply that the virtio and guest tools isos should be installed in the premade iso storage area, but nothing was setup on my install. furthermore the files that should be in /usr/share are not there either. is this something that isn't in ovirt, but only in rhev? or did something mess up in my install?

3 11

[Users] doc/ui mismatch for memory overcommit
by Joe Pruett 08 Mar '12

08 Mar '12

the docs say that server is 150% and desktop is 200%, but the ui has the opposite. it seems like server at 150% makes more sense. is it just the text in the ui that is wrong?

4 4

[Users] Data center is "non-responsive" after a reboot
by Terry Phelps 08 Mar '12

08 Mar '12

I have a pretty new ovirt/vsdm-combined installation on a Fedora 16 host. It was running okay, and then I applied a bunch of Fedora patches, and rebooted the box. Now, ovirt shows my data center as "non-responsive". What might be wrong? What can I look at to get more information?

3 2

[Users] proliant errors trying to install ovirt-node image
by Joe Pruett 07 Mar '12

07 Mar '12

i've already found the info on the list about the "global name 'disk' not defined" error and i've tried both an iso from the jenkins url listed, as well as creating my own git area using the 2.2.3 tagged code and making the one line change to fix that python error. but neither of those images work either. i get a generic "ovirt node hypervisor installation failed" message. i've poked around the log viewers and at the end i see it complaining that the gpt partition label has no bios bootable partition, but it isn't clear if that is really the issue. i'm wondering if there might be more cciss driver issues. i haven't dug into the source to figure out the root pw so i could more easily look at the log files or export them. can someone enlighten me with that more quickly than i can find it? what is the best procedure to follow to try and get to the bottom of issues like this? might i be better off installing a regular os and then installing the vdsm package?

4 10

[Users] "permission settings on the specified path do not allow access to the storage"
by Shu Ming 07 Mar '12

07 Mar '12

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" manually in the ovirt-engine host, also a new file can be created under the mounted directory with "touch xx". It looks to me that there is no permission problem when I access the remote nfs path manually. So does ovirt-engine enforce additional permission check beside the normal unix file permission check here? ---- [root@ovirt-engine-112 /]# vim /var/log/ovirt-engine/engine.log [root@ovirt-engine-112 /]# vim /var/log/ovirt-engine/engine.log 2012-03-06 00:38:51,165 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ValidateStorageServerConnectionVDSCommand] (http--0.0.0.0-8080-6) START, ValidateStorageServerConnectionVDSCommand(vdsId = 46a83d56-66d9-11e1-8004-5254009e821b, storagePoolId = 00000000-0000-0000-0000-000000000000, storageType = NFS, connectionList = [{ id: null, connection: xxx.xxx.xxx.110:/data };]), log id: 1899002d 2012-03-06 00:38:51,297 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ValidateStorageServerConnectionVDSCommand] (http--0.0.0.0-8080-6) FINISH, ValidateStorageServerConnectionVDSCommand, return: {00000000-0000-0000-0000-000000000000=469}, log id: 1899002d 2012-03-06 00:38:51,300 ERROR [org.ovirt.engine.core.bll.storage.NFSStorageHelper] (http--0.0.0.0-8080-6) The connection with details xxx.xxx.xxx.110:/data failed because of error code 469 and error message is: permission settings on the specified path do not allow access to the storage. verify permission settings on the specified storage path. 2012-03-06 00:38:51,300 WARN [org.ovirt.engine.core.bll.storage.AddStorageServerConnectionCommand] (http--0.0.0.0-8080-6) CanDoAction of action AddStorageServerConnection failed. Reasons:ACTION_TYPE_FAILED_STORAGE_CONNECTION 2012-03-06 00:38:51,425 INFO [org.ovirt.engine.core.bll.storage.RemoveStorageServerConnectionCommand] (http--0.0.0.0-8080-4) Running command: RemoveStorageServerConnectionCommand internal: false. Entities affected : ID: aaa00000-0000-0000-0000-123456789aaa Type: System -- Shu Ming<shuming(a)linux.vnet.ibm.com> IBM China Systems and Technology Laboratory

3 5

[Users] iSCSI dependancy
by Nathan Stratton 06 Mar '12

06 Mar '12

Is there any way to remove the iSCSI dependency? I am working to build a shared NFS root system with 40 boxes and am using only NFS. iSCSI requires remount-rootfs.service and that fails with read only root. -Nathan

2 1

[Users] SOLVED: New virtual disks will NOT reliably be placed where I specified
by Terry Phelps 06 Mar '12

06 Mar '12

On Thu, Mar 1, 2012 at 7:31 PM, Jeff Bailey <bailey(a)cs.kent.edu> wrote: > On 3/1/2012 7:13 PM, Itamar Heim wrote: > >> On 03/01/2012 06:02 PM, Terry Phelps wrote: >> >>> >>> 1. You said there's "not even support for creating a disk on the export >>> domain". But when I create a virtual disk, the "new virtual disk" window >>> that comes up has a field called "Storage Domain", and the dropdown box >>> shows both "data" and "export". >>> >> >> this looks like a bug. >> einav - can you see this as well? >> > > Could the storage domain have been accidentally created as another data > domain instead of an export domain? > > You're right. I must have not set the domain type to "admin". I re-created it as an export domain. 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?

2 1