[Users] Adding New oVirtNode Host 3.0.1 to the oVirt3.3

2013-10-21 Thread Udaya Kiran P
Hi everyone,

I don't find any options in the left menu of oVirtNode 3.0.1 to set the 
oVirtEngine related details  [which was there in oVirtNode2.6.1]. Please find 
attached the screenshot.

Please let me know how to add this new host into oVirt 3.3.

Thank you. 

Regards,
Udaya Kiranattachment: 3.0.1.png___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[Users] oVirtNode 3.0.1 - Invalid Installation Error

2013-10-21 Thread Udaya Kiran P
Hi everyone,

I was able to install oVirtNode 3.0.1 on a machine. 

When I tried installing the same setup on a different machine I am getting the 
error - Invalid Installation. Please reboot from media and reinstall. Please 
find attched the screenshot.

I tried rebooting but the error remains. Please suggest.


Thank You.

Regards,
Udaya Kiranattachment: 3.0.1_Error.png___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Adding New oVirtNode Host 3.0.1 to the oVirt3.3

2013-10-21 Thread Fabian Deutsch
Am Montag, den 21.10.2013, 14:48 +0800 schrieb Udaya Kiran P:

 I don't find any options in the left menu of oVirtNode 3.0.1 to set
 the oVirtEngine related details  [which was there in oVirtNode2.6.1].
 Please find attached the screenshot.

Hey Udaya,

you have probably downloaded the oVirt Node Base Image - which does not
contain the VDSM/oVirt Engine plugin.

The latest oVirt Node ISO with the VDSM plugin can be foun dhere:
http://resources.ovirt.org/releases/3.3-beta/iso/

This ISO has known problems and a new release is planned. For now you
cna use this draft build:
http://fedorapeople.org/~fabiand/node/ovirt-node-iso-3.0.1-1.0.201310020841draft.vdsm.el6.iso

Greetings
fabian

 Please let me know how to add this new host into oVirt 3.3.
 
 
 Thank you. 
 
 
 Regards,
 Udaya Kiran
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] oVirtNode 3.0.1 - Invalid Installation Error

2013-10-21 Thread Fabian Deutsch
Am Montag, den 21.10.2013, 14:57 +0800 schrieb Udaya Kiran P:

 I was able to install oVirtNode 3.0.1 on a machine. 
 
 
 When I tried installing the same setup on a different machine I am
 getting the error - Invalid Installation. Please reboot from media
 and reinstall. Please find attched the screenshot.

Hey Udaya,

this can happen when oVirt Node was previously installed on the machine
but did not completely removed.
Did you try to reinstall oVirt Node as suggested? (There is a reinstall
item in the grub menu right at boot).

Greetings
fabian

 
 
 I tried rebooting but the error remains. Please suggest.
 
 
 
 
 Thank You.
 
 
 Regards,
 Udaya Kiran
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Permission denied on disk image file !!

2013-10-21 Thread Anil Dhingra
hi

Permission issue is resolved after changing on openfiler NFS share
permission  .but still on every reboot we need to set below values manually
Any idea how to make it perm

setsebool -P virt_use_sanlock=on
setsebool -P virt_use_nfs=on


On Wed, Oct 16, 2013 at 8:24 AM, Itamar Heim ih...@redhat.com wrote:

 On 10/15/2013 11:05 AM, Anil Dhingra wrote:

 Hi Guys
 Any know issue why we are not able to start VM due to permission issue
 on disk image file .. as per docs ownership should be vdsm:kvm  byt not
 sure why its showing below
 used - both  ovirt-node-iso-3.0.1-1.0.1.**vdsm.el6 
 ovirt-node-iso-3.0.1-1.0.2.**vdsm.el6  same issue  [ using NFS Domain ]
 VM n0001vdap is down. Exit message: internal error process exited while
 connecting to monitor: qemu-kvm: -drive
 file=/rhev/data-center/**d09d8a3e-8ab4-42fc-84ec-**
 86f307d144a0/1a04e13a-0ed4-**40d6-a153-f7091c65d916/images/**
 44e3fc9b-0382-4c11-b00c-**35bd74032e9a/34542412-ed50-**
 4350-8867-0d7d5f8127fd,if=**none,id=drive-virtio-disk0,**
 format=raw,serial=44e3fc9b-**0382-4c11-b00c-35bd74032e9a,**
 cache=none,werror=stop,rerror=**stop,aio=threads:
 *could not open *disk image
 */rhev/data-center*/d09d8a3e-**8ab4-42fc-84ec-86f307d144a0/**
 1a04e13a-0ed4-40d6-a153-**f7091c65d916/*images*/**
 44e3fc9b-0382-4c11-b00c-**35bd74032e9a/34542412-ed50-**
 4350-8867-0d7d5f8127fd:
 *Permission denied*


 [root@node1 44e3fc9b-0382-4c11-b00c-**35bd74032e9a]# ls -lh
 total 1.1M
 -rw-rw+ 1 *vdsm 96* 6.0G 2013-10-15 05:47
 34542412-ed50-4350-8867-**0d7d5f8127fd
 -rw-rw+ 1 *vdsm 96* 1.0M 2013-10-15 05:47
 34542412-ed50-4350-8867-**0d7d5f8127fd.lease
 -rw-rw-rw-+ 1 *vdsm 96*  268 2013-10-15 05:47

 34542412-ed50-4350-8867-**0d7d5f8127fd.meta
 As it doesn't allow us o change permissions any alternate way for this
 ?or do I need to manually set permissions in */etc/libvirt/qemu.conf*
 alos ther is no such *group *with*96* .. so from where it picks this

 config .
 Another question is related to SELINUX config change for below 2
 parameters to recover from error *internal error Failed to open socket
 to sanlock daemon: Permission denied* I saw some where this is fixed

 but not sure why it appears  VDSM should take care of this auto
 setsebool -P virt_use_sanlock=on
 setsebool -P virt_use_nfs=on


 __**_
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/**mailman/listinfo/usershttp://lists.ovirt.org/mailman/listinfo/users


 have you tried:
 http://www.ovirt.org/wiki/**Troubleshooting_NFS_Storage_**Issueshttp://www.ovirt.org/wiki/Troubleshooting_NFS_Storage_Issues

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Permission denied on disk image file !!

2013-10-21 Thread Itamar Heim

On 10/21/2013 08:44 AM, Anil Dhingra wrote:

hi
Permission issue is resolved after changing on openfiler NFS share
permission  .but still on every reboot we need to set below values manually
Any idea how to make it perm
setsebool -P virt_use_sanlock=on
setsebool -P virt_use_nfs=on


On Wed, Oct 16, 2013 at 8:24 AM, Itamar Heim ih...@redhat.com
mailto:ih...@redhat.com wrote:

On 10/15/2013 11:05 AM, Anil Dhingra wrote:

Hi Guys
Any know issue why we are not able to start VM due to permission
issue
on disk image file .. as per docs ownership should be vdsm:kvm
  byt not
sure why its showing below
used - both  ovirt-node-iso-3.0.1-1.0.1.__vdsm.el6 
ovirt-node-iso-3.0.1-1.0.2.__vdsm.el6  same issue  [ using NFS
Domain ]
VM n0001vdap is down. Exit message: internal error process
exited while
connecting to monitor: qemu-kvm: -drive

file=/rhev/data-center/__d09d8a3e-8ab4-42fc-84ec-__86f307d144a0/1a04e13a-0ed4-__40d6-a153-f7091c65d916/images/__44e3fc9b-0382-4c11-b00c-__35bd74032e9a/34542412-ed50-__4350-8867-0d7d5f8127fd,if=__none,id=drive-virtio-disk0,__format=raw,serial=44e3fc9b-__0382-4c11-b00c-35bd74032e9a,__cache=none,werror=stop,rerror=__stop,aio=threads:
*could not open *disk image

*/rhev/data-center*/d09d8a3e-__8ab4-42fc-84ec-86f307d144a0/__1a04e13a-0ed4-40d6-a153-__f7091c65d916/*images*/__44e3fc9b-0382-4c11-b00c-__35bd74032e9a/34542412-ed50-__4350-8867-0d7d5f8127fd:
*Permission denied*


[root@node1 44e3fc9b-0382-4c11-b00c-__35bd74032e9a]# ls -lh
total 1.1M
-rw-rw+ 1 *vdsm 96* 6.0G 2013-10-15 05:47
34542412-ed50-4350-8867-__0d7d5f8127fd
-rw-rw+ 1 *vdsm 96* 1.0M 2013-10-15 05:47
34542412-ed50-4350-8867-__0d7d5f8127fd.lease
-rw-rw-rw-+ 1 *vdsm 96*  268 2013-10-15 05:47

34542412-ed50-4350-8867-__0d7d5f8127fd.meta
As it doesn't allow us o change permissions any alternate way
for this
?or do I need to manually set permissions in
*/etc/libvirt/qemu.conf*
alos ther is no such *group *with*96* .. so from where it
picks this

config .
Another question is related to SELINUX config change for below 2
parameters to recover from error *internal error Failed to open
socket
to sanlock daemon: Permission denied* I saw some where this is
fixed

but not sure why it appears  VDSM should take care of this auto
setsebool -P virt_use_sanlock=on
setsebool -P virt_use_nfs=on


_
Users mailing list
Users@ovirt.org mailto:Users@ovirt.org
http://lists.ovirt.org/__mailman/listinfo/users
http://lists.ovirt.org/mailman/listinfo/users


have you tried:
http://www.ovirt.org/wiki/__Troubleshooting_NFS_Storage___Issues
http://www.ovirt.org/wiki/Troubleshooting_NFS_Storage_Issues




ovirt node? fedora? .el6?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Permission denied on disk image file !!

2013-10-21 Thread Anil Dhingra
currentely using ovirt-node-iso-3.0.1-1.0.1.vdsm.el6.iso

also tied on  ovirt-node-iso-3.0.1-1.0.2.vdsm.el6   draft version
ovirt-node-iso-3.0.1-1.0.201310020841draft.vdsm.el6.iso posed by fabian
deutsch





On Mon, Oct 21, 2013 at 3:46 PM, Itamar Heim ih...@redhat.com wrote:

 On 10/21/2013 08:44 AM, Anil Dhingra wrote:

 hi
 Permission issue is resolved after changing on openfiler NFS share
 permission  .but still on every reboot we need to set below values
 manually
 Any idea how to make it perm
 setsebool -P virt_use_sanlock=on
 setsebool -P virt_use_nfs=on


 On Wed, Oct 16, 2013 at 8:24 AM, Itamar Heim ih...@redhat.com
 mailto:ih...@redhat.com wrote:

 On 10/15/2013 11:05 AM, Anil Dhingra wrote:

 Hi Guys
 Any know issue why we are not able to start VM due to permission
 issue
 on disk image file .. as per docs ownership should be vdsm:kvm
   byt not
 sure why its showing below
 used - both  ovirt-node-iso-3.0.1-1.0.1.__**vdsm.el6 
 ovirt-node-iso-3.0.1-1.0.2.__**vdsm.el6  same issue  [ using NFS

 Domain ]
 VM n0001vdap is down. Exit message: internal error process
 exited while
 connecting to monitor: qemu-kvm: -drive
 file=/rhev/data-center/__**d09d8a3e-8ab4-42fc-84ec-__**
 86f307d144a0/1a04e13a-0ed4-__**40d6-a153-f7091c65d916/images/**
 __44e3fc9b-0382-4c11-b00c-__**35bd74032e9a/34542412-ed50-__**
 4350-8867-0d7d5f8127fd,if=__**none,id=drive-virtio-disk0,__**
 format=raw,serial=44e3fc9b-__**0382-4c11-b00c-35bd74032e9a,__**
 cache=none,werror=stop,rerror=**__stop,aio=threads:

 *could not open *disk image
 */rhev/data-center*/d09d8a3e-_**_8ab4-42fc-84ec-86f307d144a0/_**
 _1a04e13a-0ed4-40d6-a153-__**f7091c65d916/*images*/__**
 44e3fc9b-0382-4c11-b00c-__**35bd74032e9a/34542412-ed50-__**
 4350-8867-0d7d5f8127fd:
 *Permission denied*


 [root@node1 44e3fc9b-0382-4c11-b00c-__**35bd74032e9a]# ls -lh

 total 1.1M
 -rw-rw+ 1 *vdsm 96* 6.0G 2013-10-15 05:47
 34542412-ed50-4350-8867-__**0d7d5f8127fd

 -rw-rw+ 1 *vdsm 96* 1.0M 2013-10-15 05:47
 34542412-ed50-4350-8867-__**0d7d5f8127fd.lease

 -rw-rw-rw-+ 1 *vdsm 96*  268 2013-10-15 05:47

 34542412-ed50-4350-8867-__**0d7d5f8127fd.meta

 As it doesn't allow us o change permissions any alternate way
 for this
 ?or do I need to manually set permissions in
 */etc/libvirt/qemu.conf*
 alos ther is no such *group *with*96* .. so from where it
 picks this

 config .
 Another question is related to SELINUX config change for below 2
 parameters to recover from error *internal error Failed to open
 socket
 to sanlock daemon: Permission denied* I saw some where this is
 fixed

 but not sure why it appears  VDSM should take care of this auto
 setsebool -P virt_use_sanlock=on
 setsebool -P virt_use_nfs=on


 __**___
 Users mailing list
 Users@ovirt.org mailto:Users@ovirt.org
 
 http://lists.ovirt.org/__**mailman/listinfo/usershttp://lists.ovirt.org/__mailman/listinfo/users

 
 http://lists.ovirt.org/**mailman/listinfo/usershttp://lists.ovirt.org/mailman/listinfo/users
 


 have you tried:
 
 http://www.ovirt.org/wiki/__**Troubleshooting_NFS_Storage___**Issueshttp://www.ovirt.org/wiki/__Troubleshooting_NFS_Storage___Issues
 
 http://www.ovirt.org/wiki/**Troubleshooting_NFS_Storage_**Issueshttp://www.ovirt.org/wiki/Troubleshooting_NFS_Storage_Issues
 



 ovirt node? fedora? .el6?

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[Users] Host Error

2013-10-21 Thread Neil
Hi guys,

We had a power failure over the weekend, and when powering everything
back on, one of the hosts gives the following error when trying to
re-activate it.

Host ovirt02.blabla.co.za running without virtualization hardware acceleration

I've checked in the machine's bios and the VT options are still
enabled, I've reset the PC's bios and then confirmed all the CPU
features were enabled as a precaution and yet I still get the same
error.

Could this be an ovirt/vdsm issue or is it more likely a hardware issue?

These are my versions...

vdsm-cli-4.10.3-10.el6.centos.alt.noarch
vdsm-4.10.3-10.el6.centos.alt.x86_64
vdsm-xmlrpc-4.10.3-10.el6.centos.alt.noarch
vdsm-hook-nestedvt-4.10.3-10.el6.centos.alt.noarch
vdsm-python-4.10.3-10.el6.centos.alt.x86_64

ovirt-engine-genericapi-3.2.1-1.41.el6.noarch
ovirt-engine-dbscripts-3.2.1-1.41.el6.noarch
ovirt-engine-tools-3.2.1-1.41.el6.noarch
ovirt-engine-sdk-3.2.0.9-1.el6.noarch
ovirt-engine-restapi-3.2.1-1.41.el6.noarch
ovirt-host-deploy-1.1.0-0.0.master.el6.noarch
ovirt-log-collector-3.2.0-1.el6.noarch
ovirt-engine-backend-3.2.1-1.41.el6.noarch
ovirt-image-uploader-3.2.0-1.el6.noarch
ovirt-engine-userportal-3.2.1-1.41.el6.noarch
ovirt-engine-jbossas711-1-0.x86_64
ovirt-engine-setup-3.2.1-1.41.el6.noarch
ovirt-host-deploy-java-1.1.0-0.0.master.el6.noarch
ovirt-iso-uploader-3.2.0-1.el6.noarch
ovirt-engine-3.2.1-1.41.el6.noarch
ovirt-engine-cli-3.2.0.10-1.el6.noarch
ovirt-engine-webadmin-portal-3.2.1-1.41.el6.noarch

Any help is appreciated.

Thanks.

Regards.

Neil Wilson
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Host Error

2013-10-21 Thread Dan Kenigsberg
On Mon, Oct 21, 2013 at 10:57:12AM +0200, Neil wrote:
 Hi guys,
 
 We had a power failure over the weekend, and when powering everything
 back on, one of the hosts gives the following error when trying to
 re-activate it.
 
 Host ovirt02.blabla.co.za running without virtualization hardware 
 acceleration
 
 I've checked in the machine's bios and the VT options are still
 enabled, I've reset the PC's bios and then confirmed all the CPU
 features were enabled as a precaution and yet I still get the same
 error.
 
 Could this be an ovirt/vdsm issue or is it more likely a hardware issue?
 
 These are my versions...
 
 vdsm-cli-4.10.3-10.el6.centos.alt.noarch
 vdsm-4.10.3-10.el6.centos.alt.x86_64
 vdsm-xmlrpc-4.10.3-10.el6.centos.alt.noarch
 vdsm-hook-nestedvt-4.10.3-10.el6.centos.alt.noarch
 vdsm-python-4.10.3-10.el6.centos.alt.x86_64
 
 ovirt-engine-genericapi-3.2.1-1.41.el6.noarch
 ovirt-engine-dbscripts-3.2.1-1.41.el6.noarch
 ovirt-engine-tools-3.2.1-1.41.el6.noarch
 ovirt-engine-sdk-3.2.0.9-1.el6.noarch
 ovirt-engine-restapi-3.2.1-1.41.el6.noarch
 ovirt-host-deploy-1.1.0-0.0.master.el6.noarch
 ovirt-log-collector-3.2.0-1.el6.noarch
 ovirt-engine-backend-3.2.1-1.41.el6.noarch
 ovirt-image-uploader-3.2.0-1.el6.noarch
 ovirt-engine-userportal-3.2.1-1.41.el6.noarch
 ovirt-engine-jbossas711-1-0.x86_64
 ovirt-engine-setup-3.2.1-1.41.el6.noarch
 ovirt-host-deploy-java-1.1.0-0.0.master.el6.noarch
 ovirt-iso-uploader-3.2.0-1.el6.noarch
 ovirt-engine-3.2.1-1.41.el6.noarch
 ovirt-engine-cli-3.2.0.10-1.el6.noarch
 ovirt-engine-webadmin-portal-3.2.1-1.41.el6.noarch
 
 Any help is appreciated.

What does `virsh -r capabilities` report when run on that host?
And `lsmod | grep kvm` ?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] oVirt October Updates

2013-10-21 Thread Vijay Bellur

On 10/19/2013 10:44 AM, Gianluca Cecchi wrote:

On Wed, Oct 16, 2013 at 1:01 PM, Itamar Heim wrote:

Hope to meet many next week in LinuxCon Europe/KVM Forum/oVirt conference in
Edinburgh


Unfortunately not me ;-(



- LINBIT published High-Availability oVirt-Cluster with
   iSCSI-Storage[9]




[9] note: link requires registeration:
http://www.linbit.com/en/company/news/333-high-available-virtualization-at-a-most-reasonable-price
the pdf is:
http://www.linbit.com/en/downloads/tech-guides?download=68:high-availability-ovirt-cluster-with-iscsi-storage


About 3 years ago I successfully tested plain Qemu/KVM with two nodes
and drbd dual-primary with live migration on Fedora, so I know it
works very well.
I think the LINBIT guide gives many suggestions, one of them is in
particular just another way to have a High Available oVirt Engine for
example, that is a hot topic lately
Deep attention is to be put in fencing mechanism though, as always it
is in general when talking about drbd, pacemaker, oVirt.
I don't know it quite well, but the drbd proxy feature (closed source
and not free) could also be then an option for DR in small
environments

I'm going to experiment the solution of the paper (possibly using
clusterlabs.org repo for cluster and so using corosync instead of
heartbeat).
To compare in small environments where two nodes are ok, in my opinion
glusterfs is far away from robust at the moment: with 3.4.1 on fedora
19 I cannot put a host in maintenance and get back a workable node
after normal reboot.


Are you referring to the absence of self-healing after maintenance? 
Please see below as to why this should not happen. If there's a 
reproducible test case, it would be good to track this bug at:


https://bugzilla.redhat.com/enter_bug.cgi?product=GlusterFS


Didn't find any safe way for a node in distributed-replicated two
nodes config to leave the cluster and get it back without becoming
crazy to manual solve the brick differences generated in the mean
time. And this was with only one VM running .
Possibly I have to dig more in this, but I didn't find great resources
for it. Any tips/links are welcome


The following commands might help:

1. gluster volume heal volname  - perform a fast index based self-heal

2. gluster volume heal volname full - perform a full self-heal if 1. 
does not work.


3. gluster volume heal volname info - provide information about 
files/directories that were healed recently.


Neither of 1. or 2. would be required in normal operational course as 
the proactive self-healing feature in glusterfs takes care of healing 
after a node comes online.




I would like to have oVirt more conscious about it and have sort of
capability to solve itself the misalignments generated on gluster
backend during mainteneance of a node.
At the moment it seems to me it only shows volumes are ok in the sense
of started, but they could be very different...
For example another tab with details about heal info; something like
the output of the command

gluster volume heal $VOLUME info

and/or

gluster volume heal $VOLUME info split-brain


Yes, we are looking to build this for monitoring replicated gluster volumes.

- Vijay


so that if one finds 0 entries, he/she is calm and at the same doesn't
risk to be erroneously calm in the other scenario...

just my opinion.

Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Permission denied on disk image file !!

2013-10-21 Thread Fabian Deutsch
Am Montag, den 21.10.2013, 15:44 +0800 schrieb Anil Dhingra:
 hi
  
 Permission issue is resolved after changing on openfiler NFS share
 permission  .but still on every reboot we need to set below values
 manually
 Any idea how to make it perm 
  
 setsebool -P virt_use_sanlock=on
 setsebool -P virt_use_nfs=on

Hum ... That's interesting.
We actually set both of them to on during the installation of the
ovirt-node selinux package:
/usr/sbin/setsebool -P allow_execstack=0 \
   virt_use_nfs=1 \
   virt_use_sanlock=1 \
   sanlock_use_nfs=1

What does 
getsebool virt_use_sanlock virt_use_nfs

say?

- fabian

 
 On Wed, Oct 16, 2013 at 8:24 AM, Itamar Heim ih...@redhat.com wrote:
 On 10/15/2013 11:05 AM, Anil Dhingra wrote:
 
 Hi Guys
 Any know issue why we are not able to start VM due to
 permission issue
 on disk image file .. as per docs ownership should be
 vdsm:kvm  byt not
 sure why its showing below
 used - both  ovirt-node-iso-3.0.1-1.0.1.vdsm.el6 
 ovirt-node-iso-3.0.1-1.0.2.vdsm.el6  same issue
  [ using NFS Domain ]
 VM n0001vdap is down. Exit message: internal error
 process exited while
 connecting to monitor: qemu-kvm: -drive
 
 file=/rhev/data-center/d09d8a3e-8ab4-42fc-84ec-86f307d144a0/1a04e13a-0ed4-40d6-a153-f7091c65d916/images/44e3fc9b-0382-4c11-b00c-35bd74032e9a/34542412-ed50-4350-8867-0d7d5f8127fd,if=none,id=drive-virtio-disk0,format=raw,serial=44e3fc9b-0382-4c11-b00c-35bd74032e9a,cache=none,werror=stop,rerror=stop,aio=threads:
 
 *could not open *disk image
 
 */rhev/data-center*/d09d8a3e-8ab4-42fc-84ec-86f307d144a0/1a04e13a-0ed4-40d6-a153-f7091c65d916/*images*/44e3fc9b-0382-4c11-b00c-35bd74032e9a/34542412-ed50-4350-8867-0d7d5f8127fd:
 *Permission denied*
 
 
 [root@node1 44e3fc9b-0382-4c11-b00c-35bd74032e9a]# ls
 -lh
 total 1.1M
 
 -rw-rw+ 1 *vdsm 96* 6.0G 2013-10-15 05:47
 34542412-ed50-4350-8867-0d7d5f8127fd
 -rw-rw+ 1 *vdsm 96* 1.0M 2013-10-15 05:47
 34542412-ed50-4350-8867-0d7d5f8127fd.lease
 -rw-rw-rw-+ 1 *vdsm 96*  268 2013-10-15 05:47
 
 34542412-ed50-4350-8867-0d7d5f8127fd.meta
 As it doesn't allow us o change permissions any
 alternate way for this
 
 ?or do I need to manually set permissions in
 */etc/libvirt/qemu.conf*
 alos ther is no such *group *with*96* .. so from
 where it picks this
 
 config .
 Another question is related to SELINUX config change
 for below 2
 
 parameters to recover from error *internal error
 Failed to open socket
 to sanlock daemon: Permission denied* I saw some
 where this is fixed
 
 but not sure why it appears  VDSM should take care of
 this auto
 setsebool -P virt_use_sanlock=on
 setsebool -P virt_use_nfs=on
 
 
 
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users
 
 
 have you tried:
 http://www.ovirt.org/wiki/Troubleshooting_NFS_Storage_Issues
 
 
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Permission denied on disk image file !!

2013-10-21 Thread Anil Dhingra
*below is the output after reboot .. also after reboot we need to restart
sanlock daemon manually every time else no spm selection  hosts keep on
contending  fails*
**
*[root@node1-3-3 ~]# getsebool -a | egrep -i 'nfs|sanlock'*
allow_ftpd_use_nfs -- off
cobbler_use_nfs -- off
git_system_use_nfs -- off
httpd_use_nfs -- off
qemu_use_nfs -- on
rsync_use_nfs -- off
samba_share_nfs -- off
sanlock_use_fusefs -- off
sanlock_use_nfs -- off
sanlock_use_samba -- off
sge_use_nfs -- off
use_nfs_home_dirs -- on
*virt_use_nfs -- off
virt_use_sanlock -- off*
xen_use_nfs -- off
*[root@node1-3-3 ~]# getsebool -a | egrep -i allow_execstack*
allow_execstack -- on
[root@node1-3-3 ~]#


On Mon, Oct 21, 2013 at 7:16 PM, Fabian Deutsch fabi...@redhat.com wrote:

 Am Montag, den 21.10.2013, 15:44 +0800 schrieb Anil Dhingra:
  hi
 
  Permission issue is resolved after changing on openfiler NFS share
  permission  .but still on every reboot we need to set below values
  manually
  Any idea how to make it perm
 
  setsebool -P virt_use_sanlock=on
  setsebool -P virt_use_nfs=on

 Hum ... That's interesting.
 We actually set both of them to on during the installation of the
 ovirt-node selinux package:
 /usr/sbin/setsebool -P allow_execstack=0 \
virt_use_nfs=1 \
virt_use_sanlock=1 \
sanlock_use_nfs=1

 What does
 getsebool virt_use_sanlock virt_use_nfs

 say?

 - fabian

 
  On Wed, Oct 16, 2013 at 8:24 AM, Itamar Heim ih...@redhat.com wrote:
  On 10/15/2013 11:05 AM, Anil Dhingra wrote:
 
  Hi Guys
  Any know issue why we are not able to start VM due to
  permission issue
  on disk image file .. as per docs ownership should be
  vdsm:kvm  byt not
  sure why its showing below
  used - both  ovirt-node-iso-3.0.1-1.0.1.vdsm.el6 
  ovirt-node-iso-3.0.1-1.0.2.vdsm.el6  same issue
   [ using NFS Domain ]
  VM n0001vdap is down. Exit message: internal error
  process exited while
  connecting to monitor: qemu-kvm: -drive
 
 file=/rhev/data-center/d09d8a3e-8ab4-42fc-84ec-86f307d144a0/1a04e13a-0ed4-40d6-a153-f7091c65d916/images/44e3fc9b-0382-4c11-b00c-35bd74032e9a/34542412-ed50-4350-8867-0d7d5f8127fd,if=none,id=drive-virtio-disk0,format=raw,serial=44e3fc9b-0382-4c11-b00c-35bd74032e9a,cache=none,werror=stop,rerror=stop,aio=threads:
 
  *could not open *disk image
 
 */rhev/data-center*/d09d8a3e-8ab4-42fc-84ec-86f307d144a0/1a04e13a-0ed4-40d6-a153-f7091c65d916/*images*/44e3fc9b-0382-4c11-b00c-35bd74032e9a/34542412-ed50-4350-8867-0d7d5f8127fd:
  *Permission denied*
 
 
  [root@node1 44e3fc9b-0382-4c11-b00c-35bd74032e9a]# ls
  -lh
  total 1.1M
 
  -rw-rw+ 1 *vdsm 96* 6.0G 2013-10-15 05:47
  34542412-ed50-4350-8867-0d7d5f8127fd
  -rw-rw+ 1 *vdsm 96* 1.0M 2013-10-15 05:47
  34542412-ed50-4350-8867-0d7d5f8127fd.lease
  -rw-rw-rw-+ 1 *vdsm 96*  268 2013-10-15 05:47
 
  34542412-ed50-4350-8867-0d7d5f8127fd.meta
  As it doesn't allow us o change permissions any
  alternate way for this
 
  ?or do I need to manually set permissions in
  */etc/libvirt/qemu.conf*
  alos ther is no such *group *with*96* .. so from
  where it picks this
 
  config .
  Another question is related to SELINUX config change
  for below 2
 
  parameters to recover from error *internal error
  Failed to open socket
  to sanlock daemon: Permission denied* I saw some
  where this is fixed
 
  but not sure why it appears  VDSM should take care of
  this auto
  setsebool -P virt_use_sanlock=on
  setsebool -P virt_use_nfs=on
 
 
 
  ___
  Users mailing list
  Users@ovirt.org
  http://lists.ovirt.org/mailman/listinfo/users
 
 
  have you tried:
  http://www.ovirt.org/wiki/Troubleshooting_NFS_Storage_Issues
 
 
  ___
  Users mailing list
  Users@ovirt.org
  http://lists.ovirt.org/mailman/listinfo/users



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Permission denied on disk image file !!

2013-10-21 Thread Fabian Deutsch
Am Montag, den 21.10.2013, 20:21 +0800 schrieb Anil Dhingra:
  
 below is the output after reboot .. also after reboot we need to
 restart sanlock daemon manually every time else no spm selection 
 hosts keep on contending  fails

Do you know what the problem of the sanlock daemon is, so why it needs
to be restarted?

 [root@node1-3-3 ~]# getsebool -a | egrep -i 'nfs|sanlock'
 allow_ftpd_use_nfs -- off
 cobbler_use_nfs -- off
 git_system_use_nfs -- off
 httpd_use_nfs -- off
 qemu_use_nfs -- on
 rsync_use_nfs -- off
 samba_share_nfs -- off
 sanlock_use_fusefs -- off
 sanlock_use_nfs -- off
 sanlock_use_samba -- off
 sge_use_nfs -- off
 use_nfs_home_dirs -- on
 virt_use_nfs -- off
 virt_use_sanlock -- off
 xen_use_nfs -- off
 [root@node1-3-3 ~]# getsebool -a | egrep -i allow_execstack
 allow_execstack -- on
 [root@node1-3-3 ~]#

Seems like it was changed. Is maybe VDSM changing it?

Greetings
fabian


 
 On Mon, Oct 21, 2013 at 7:16 PM, Fabian Deutsch fabi...@redhat.com
 wrote:
 Am Montag, den 21.10.2013, 15:44 +0800 schrieb Anil Dhingra:
  hi
 
  Permission issue is resolved after changing on openfiler NFS
 share
  permission  .but still on every reboot we need to set below
 values
  manually
  Any idea how to make it perm
 
  setsebool -P virt_use_sanlock=on
  setsebool -P virt_use_nfs=on
 
 
 Hum ... That's interesting.
 We actually set both of them to on during the installation of
 the
 ovirt-node selinux package:
 /usr/sbin/setsebool -P allow_execstack=0 \
virt_use_nfs=1 \
virt_use_sanlock=1 \
sanlock_use_nfs=1
 
 What does
 getsebool virt_use_sanlock virt_use_nfs
 
 say?
 
 - fabian
 
 
  On Wed, Oct 16, 2013 at 8:24 AM, Itamar Heim
 ih...@redhat.com wrote:
  On 10/15/2013 11:05 AM, Anil Dhingra wrote:
 
  Hi Guys
  Any know issue why we are not able to start
 VM due to
  permission issue
  on disk image file .. as per docs ownership
 should be
  vdsm:kvm  byt not
  sure why its showing below
  used - both
  ovirt-node-iso-3.0.1-1.0.1.vdsm.el6 
  ovirt-node-iso-3.0.1-1.0.2.vdsm.el6  same
 issue
   [ using NFS Domain ]
  VM n0001vdap is down. Exit message: internal
 error
  process exited while
  connecting to monitor: qemu-kvm: -drive
 
 
 file=/rhev/data-center/d09d8a3e-8ab4-42fc-84ec-86f307d144a0/1a04e13a-0ed4-40d6-a153-f7091c65d916/images/44e3fc9b-0382-4c11-b00c-35bd74032e9a/34542412-ed50-4350-8867-0d7d5f8127fd,if=none,id=drive-virtio-disk0,format=raw,serial=44e3fc9b-0382-4c11-b00c-35bd74032e9a,cache=none,werror=stop,rerror=stop,aio=threads:
 
  *could not open *disk image
 
 
 */rhev/data-center*/d09d8a3e-8ab4-42fc-84ec-86f307d144a0/1a04e13a-0ed4-40d6-a153-f7091c65d916/*images*/44e3fc9b-0382-4c11-b00c-35bd74032e9a/34542412-ed50-4350-8867-0d7d5f8127fd:
  *Permission denied*
 
 
  [root@node1
 44e3fc9b-0382-4c11-b00c-35bd74032e9a]# ls
  -lh
  total 1.1M
 
  -rw-rw+ 1 *vdsm 96* 6.0G 2013-10-15
 05:47
  34542412-ed50-4350-8867-0d7d5f8127fd
  -rw-rw+ 1 *vdsm 96* 1.0M 2013-10-15
 05:47
  34542412-ed50-4350-8867-0d7d5f8127fd.lease
  -rw-rw-rw-+ 1 *vdsm 96*  268 2013-10-15
 05:47
 
  34542412-ed50-4350-8867-0d7d5f8127fd.meta
  As it doesn't allow us o change permissions
 any
  alternate way for this
 
  ?or do I need to manually set permissions in
  */etc/libvirt/qemu.conf*
  alos ther is no such *group *with*96* ..
 so from
  where it picks this
 
  config .
  Another question is related to SELINUX
 config change
  for below 2
 
  parameters to recover from error *internal
 error
  Failed to open socket
  to sanlock daemon: Permission denied* I saw
 some
  where this is fixed
 
   

[Users] Unable to install oVirt Node 3.0.1: Exception: RunTimeError('Failed to partition/format')

2013-10-21 Thread Edgars M.
Hi

I am trying to install oVirt Node
(ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19.iso) on DELL R805 server, but every
time install fails with Exception: RunTimeError('Failed to
partition/format'). I also tried ovirt-node-iso-3.0.1-1.0.2.vdsm.el6.iso
version and the same error occures. I tried different partition sizes and I
always make sure that partitions dont exceed the total disk space. I
browsed log fails and could not find anything relevant. I am really out of
ideas...

Any advise?

Thanks
Edgars
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Unable to install oVirt Node 3.0.1: Exception: RunTimeError('Failed to partition/format')

2013-10-21 Thread Gabi C
Hello!

Had same problem on IBM xSeries  3650. Aparently was an RAID problem (Serve
RID in my case). I had to wipe the disk, recreate the  array an wait until
it was OK and only after that I manage to install.


On Mon, Oct 21, 2013 at 3:45 PM, Edgars M. edgars.maz...@gmail.com wrote:

 Hi

 I am trying to install oVirt Node
 (ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19.iso) on DELL R805 server, but every
 time install fails with Exception: RunTimeError('Failed to
 partition/format'). I also tried ovirt-node-iso-3.0.1-1.0.2.vdsm.el6.iso
 version and the same error occures. I tried different partition sizes and I
 always make sure that partitions dont exceed the total disk space. I
 browsed log fails and could not find anything relevant. I am really out of
 ideas...

 Any advise?

 Thanks
 Edgars

 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Host Error

2013-10-21 Thread Dan Kenigsberg
On Mon, Oct 21, 2013 at 12:50:29PM +0200, Neil wrote:
 Hi Dan,
 
 Thanks, below are the results.
 
 [root@ovirt02 ~]# virsh -r capabilities
 capabilities
 
   host
 uuid6d0aa20e-c6c2-410d-b3c5-3c87af15dd7c/uuid
 cpu
   archx86_64/arch
   modelHaswell/model
   vendorIntel/vendor
   topology sockets='1' cores='4' threads='2'/
   feature name='abm'/
   feature name='pdpe1gb'/
   feature name='rdrand'/
   feature name='f16c'/
   feature name='osxsave'/
   feature name='pdcm'/
   feature name='xtpr'/
   feature name='tm2'/
   feature name='est'/
   feature name='smx'/
   feature name='vmx'/
   feature name='ds_cpl'/
   feature name='monitor'/
   feature name='dtes64'/
   feature name='pbe'/
   feature name='tm'/
   feature name='ht'/
   feature name='ss'/
   feature name='acpi'/
   feature name='ds'/
   feature name='vme'/
 /cpu
 power_management
   suspend_mem/
   suspend_disk/
 /power_management
 migration_features
   live/
   uri_transports
 uri_transporttcp/uri_transport
   /uri_transports
 /migration_features
 topology
   cells num='1'
 cell id='0'
   cpus num='8'
 cpu id='0' socket_id='0' core_id='0' siblings='0,4'/
 cpu id='1' socket_id='0' core_id='1' siblings='1,5'/
 cpu id='2' socket_id='0' core_id='2' siblings='2,6'/
 cpu id='3' socket_id='0' core_id='3' siblings='3,7'/
 cpu id='4' socket_id='0' core_id='0' siblings='0,4'/
 cpu id='5' socket_id='0' core_id='1' siblings='1,5'/
 cpu id='6' socket_id='0' core_id='2' siblings='2,6'/
 cpu id='7' socket_id='0' core_id='3' siblings='3,7'/
   /cpus
 /cell
   /cells
 /topology
 secmodel
   modelselinux/model
   doi0/doi
 /secmodel
 secmodel
   modeldac/model
   doi0/doi
 /secmodel
   /host
 
   guest
 os_typehvm/os_type
 arch name='i686'
   wordsize32/wordsize
   emulator/usr/libexec/qemu-kvm/emulator
   machinerhel6.4.0/machine
   machine canonical='rhel6.4.0'pc/machine
   machinerhel6.3.0/machine
   machinerhel6.2.0/machine
   machinerhel6.1.0/machine
   machinerhel6.0.0/machine
   machinerhel5.5.0/machine
   machinerhel5.4.4/machine
   machinerhel5.4.0/machine
   domain type='qemu'
   /domain
 /arch
 features
   cpuselection/
   deviceboot/
   acpi default='on' toggle='yes'/
   apic default='on' toggle='no'/
   pae/
   nonpae/
 /features
   /guest
 
   guest
 os_typehvm/os_type
 arch name='x86_64'
   wordsize64/wordsize
   emulator/usr/libexec/qemu-kvm/emulator
   machinerhel6.4.0/machine
   machine canonical='rhel6.4.0'pc/machine
   machinerhel6.3.0/machine
   machinerhel6.2.0/machine
   machinerhel6.1.0/machine
   machinerhel6.0.0/machine
   machinerhel5.5.0/machine
   machinerhel5.4.4/machine
   machinerhel5.4.0/machine
   domain type='qemu'
   /domain
 /arch
 features
   cpuselection/
   deviceboot/
   acpi default='on' toggle='yes'/
   apic default='on' toggle='no'/
 /features
   /guest
 
 /capabilities

seems fine to me.

 
 
 [root@ovirt02 ~]# lsmod | grep kvm
 kvm   317504  0

I'd expect kvm_intel here, too. Could you manually modprobe it and
retry?

Another thing that I should have asked for is the output of
getVdsCapabilities in your vdsm.log.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Permission denied on disk image file !!

2013-10-21 Thread Anil Dhingra
Now sure what's wrong with  sanlock daemon  ..what I am expecting is .. as
Iam not using any FENCINGshutdown everything [ ovirt manager / node /
AD server / Storage ] bfr leaving office
so may be sanlock is not able to clean leases,  failed co-ordination  as
both nodes in cluster goes down at same time .


so may be after boot up it need sanlock restart to clean something pending
bfr last shutdown or manual fencing requires ?? not sure my understanding
is correct here .. coz  sanlock used to kill any process
 holding a resource lease within the lockspace and release the it
automatically  .. but will it work without FENCEING .



On Mon, Oct 21, 2013 at 8:34 PM, Fabian Deutsch fabi...@redhat.com wrote:

 Am Montag, den 21.10.2013, 20:21 +0800 schrieb Anil Dhingra:
 
  below is the output after reboot .. also after reboot we need to
  restart sanlock daemon manually every time else no spm selection 
  hosts keep on contending  fails

 Do you know what the problem of the sanlock daemon is, so why it needs
 to be restarted?

  [root@node1-3-3 ~]# getsebool -a | egrep -i 'nfs|sanlock'
  allow_ftpd_use_nfs -- off
  cobbler_use_nfs -- off
  git_system_use_nfs -- off
  httpd_use_nfs -- off
  qemu_use_nfs -- on
  rsync_use_nfs -- off
  samba_share_nfs -- off
  sanlock_use_fusefs -- off
  sanlock_use_nfs -- off
  sanlock_use_samba -- off
  sge_use_nfs -- off
  use_nfs_home_dirs -- on
  virt_use_nfs -- off
  virt_use_sanlock -- off
  xen_use_nfs -- off
  [root@node1-3-3 ~]# getsebool -a | egrep -i allow_execstack
  allow_execstack -- on
  [root@node1-3-3 ~]#

 Seems like it was changed. Is maybe VDSM changing it?

 Greetings
 fabian


 
  On Mon, Oct 21, 2013 at 7:16 PM, Fabian Deutsch fabi...@redhat.com
  wrote:
  Am Montag, den 21.10.2013, 15:44 +0800 schrieb Anil Dhingra:
   hi
  
   Permission issue is resolved after changing on openfiler NFS
  share
   permission  .but still on every reboot we need to set below
  values
   manually
   Any idea how to make it perm
  
   setsebool -P virt_use_sanlock=on
   setsebool -P virt_use_nfs=on
 
 
  Hum ... That's interesting.
  We actually set both of them to on during the installation of
  the
  ovirt-node selinux package:
  /usr/sbin/setsebool -P allow_execstack=0 \
 virt_use_nfs=1 \
 virt_use_sanlock=1 \
 sanlock_use_nfs=1
 
  What does
  getsebool virt_use_sanlock virt_use_nfs
 
  say?
 
  - fabian
 
  
   On Wed, Oct 16, 2013 at 8:24 AM, Itamar Heim
  ih...@redhat.com wrote:
   On 10/15/2013 11:05 AM, Anil Dhingra wrote:
  
   Hi Guys
   Any know issue why we are not able to start
  VM due to
   permission issue
   on disk image file .. as per docs ownership
  should be
   vdsm:kvm  byt not
   sure why its showing below
   used - both
   ovirt-node-iso-3.0.1-1.0.1.vdsm.el6 
   ovirt-node-iso-3.0.1-1.0.2.vdsm.el6  same
  issue
[ using NFS Domain ]
   VM n0001vdap is down. Exit message: internal
  error
   process exited while
   connecting to monitor: qemu-kvm: -drive
  
 
 file=/rhev/data-center/d09d8a3e-8ab4-42fc-84ec-86f307d144a0/1a04e13a-0ed4-40d6-a153-f7091c65d916/images/44e3fc9b-0382-4c11-b00c-35bd74032e9a/34542412-ed50-4350-8867-0d7d5f8127fd,if=none,id=drive-virtio-disk0,format=raw,serial=44e3fc9b-0382-4c11-b00c-35bd74032e9a,cache=none,werror=stop,rerror=stop,aio=threads:
  
   *could not open *disk image
  
 
 */rhev/data-center*/d09d8a3e-8ab4-42fc-84ec-86f307d144a0/1a04e13a-0ed4-40d6-a153-f7091c65d916/*images*/44e3fc9b-0382-4c11-b00c-35bd74032e9a/34542412-ed50-4350-8867-0d7d5f8127fd:
   *Permission denied*
  
  
   [root@node1
  44e3fc9b-0382-4c11-b00c-35bd74032e9a]# ls
   -lh
   total 1.1M
  
   -rw-rw+ 1 *vdsm 96* 6.0G 2013-10-15
  05:47
   34542412-ed50-4350-8867-0d7d5f8127fd
   -rw-rw+ 1 *vdsm 96* 1.0M 2013-10-15
  05:47
   34542412-ed50-4350-8867-0d7d5f8127fd.lease
   -rw-rw-rw-+ 1 *vdsm 96*  268 2013-10-15
  05:47
  
   34542412-ed50-4350-8867-0d7d5f8127fd.meta
   As it doesn't allow us o change permissions
  any

Re: [Users] Host Error

2013-10-21 Thread Alon Bar-Lev


- Original Message -
 From: Neil nwilson...@gmail.com
 To: Dan Kenigsberg dan...@redhat.com
 Cc: users@ovirt.org
 Sent: Monday, October 21, 2013 5:20:41 PM
 Subject: Re: [Users] Host Error
 
 Okay, below is the modprobe and attached is the capabilities from the
 vdsm.log
 
 modprobe kvm_intel
 FATAL: Error inserting kvm_intel
 (/lib/modules/2.6.32-358.23.2.el6.x86_64/kernel/arch/x86/kvm/kvm-intel.ko):
 Unknown symbol in module, or unknown parameter (see dmesg)
 
 According to this message, I should see something in dmesg, but I
 don't see anything when I run the modprobe.
 
 If I search through my dmesg I do see this though kvm_intel: Unknown
 parameter `nested'

Do you have anything special at /etc/modprobe.d?
Have you complied the kernel manually?

 
 Please shout if you need anything else though.
 
 Thank so much.
 
 Regards.
 
 Neil Wilson.
 
 
 
 On Mon, Oct 21, 2013 at 3:22 PM, Dan Kenigsberg dan...@redhat.com wrote:
  On Mon, Oct 21, 2013 at 12:50:29PM +0200, Neil wrote:
  Hi Dan,
 
  Thanks, below are the results.
 
  [root@ovirt02 ~]# virsh -r capabilities
  capabilities
 
host
  uuid6d0aa20e-c6c2-410d-b3c5-3c87af15dd7c/uuid
  cpu
archx86_64/arch
modelHaswell/model
vendorIntel/vendor
topology sockets='1' cores='4' threads='2'/
feature name='abm'/
feature name='pdpe1gb'/
feature name='rdrand'/
feature name='f16c'/
feature name='osxsave'/
feature name='pdcm'/
feature name='xtpr'/
feature name='tm2'/
feature name='est'/
feature name='smx'/
feature name='vmx'/
feature name='ds_cpl'/
feature name='monitor'/
feature name='dtes64'/
feature name='pbe'/
feature name='tm'/
feature name='ht'/
feature name='ss'/
feature name='acpi'/
feature name='ds'/
feature name='vme'/
  /cpu
  power_management
suspend_mem/
suspend_disk/
  /power_management
  migration_features
live/
uri_transports
  uri_transporttcp/uri_transport
/uri_transports
  /migration_features
  topology
cells num='1'
  cell id='0'
cpus num='8'
  cpu id='0' socket_id='0' core_id='0' siblings='0,4'/
  cpu id='1' socket_id='0' core_id='1' siblings='1,5'/
  cpu id='2' socket_id='0' core_id='2' siblings='2,6'/
  cpu id='3' socket_id='0' core_id='3' siblings='3,7'/
  cpu id='4' socket_id='0' core_id='0' siblings='0,4'/
  cpu id='5' socket_id='0' core_id='1' siblings='1,5'/
  cpu id='6' socket_id='0' core_id='2' siblings='2,6'/
  cpu id='7' socket_id='0' core_id='3' siblings='3,7'/
/cpus
  /cell
/cells
  /topology
  secmodel
modelselinux/model
doi0/doi
  /secmodel
  secmodel
modeldac/model
doi0/doi
  /secmodel
/host
 
guest
  os_typehvm/os_type
  arch name='i686'
wordsize32/wordsize
emulator/usr/libexec/qemu-kvm/emulator
machinerhel6.4.0/machine
machine canonical='rhel6.4.0'pc/machine
machinerhel6.3.0/machine
machinerhel6.2.0/machine
machinerhel6.1.0/machine
machinerhel6.0.0/machine
machinerhel5.5.0/machine
machinerhel5.4.4/machine
machinerhel5.4.0/machine
domain type='qemu'
/domain
  /arch
  features
cpuselection/
deviceboot/
acpi default='on' toggle='yes'/
apic default='on' toggle='no'/
pae/
nonpae/
  /features
/guest
 
guest
  os_typehvm/os_type
  arch name='x86_64'
wordsize64/wordsize
emulator/usr/libexec/qemu-kvm/emulator
machinerhel6.4.0/machine
machine canonical='rhel6.4.0'pc/machine
machinerhel6.3.0/machine
machinerhel6.2.0/machine
machinerhel6.1.0/machine
machinerhel6.0.0/machine
machinerhel5.5.0/machine
machinerhel5.4.4/machine
machinerhel5.4.0/machine
domain type='qemu'
/domain
  /arch
  features
cpuselection/
deviceboot/
acpi default='on' toggle='yes'/
apic default='on' toggle='no'/
  /features
/guest
 
  /capabilities
 
  seems fine to me.
 
 
 
  [root@ovirt02 ~]# lsmod | grep kvm
  kvm   317504  0
 
  I'd expect kvm_intel here, too. Could you manually modprobe it and
  retry?
 
  Another thing that I should have asked for is the output of
  getVdsCapabilities in your vdsm.log.
 
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users
 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Host Error

2013-10-21 Thread Neil
Okay, below is the modprobe and attached is the capabilities from the vdsm.log

modprobe kvm_intel
FATAL: Error inserting kvm_intel
(/lib/modules/2.6.32-358.23.2.el6.x86_64/kernel/arch/x86/kvm/kvm-intel.ko):
Unknown symbol in module, or unknown parameter (see dmesg)

According to this message, I should see something in dmesg, but I
don't see anything when I run the modprobe.

If I search through my dmesg I do see this though kvm_intel: Unknown
parameter `nested'

Please shout if you need anything else though.

Thank so much.

Regards.

Neil Wilson.



On Mon, Oct 21, 2013 at 3:22 PM, Dan Kenigsberg dan...@redhat.com wrote:
 On Mon, Oct 21, 2013 at 12:50:29PM +0200, Neil wrote:
 Hi Dan,

 Thanks, below are the results.

 [root@ovirt02 ~]# virsh -r capabilities
 capabilities

   host
 uuid6d0aa20e-c6c2-410d-b3c5-3c87af15dd7c/uuid
 cpu
   archx86_64/arch
   modelHaswell/model
   vendorIntel/vendor
   topology sockets='1' cores='4' threads='2'/
   feature name='abm'/
   feature name='pdpe1gb'/
   feature name='rdrand'/
   feature name='f16c'/
   feature name='osxsave'/
   feature name='pdcm'/
   feature name='xtpr'/
   feature name='tm2'/
   feature name='est'/
   feature name='smx'/
   feature name='vmx'/
   feature name='ds_cpl'/
   feature name='monitor'/
   feature name='dtes64'/
   feature name='pbe'/
   feature name='tm'/
   feature name='ht'/
   feature name='ss'/
   feature name='acpi'/
   feature name='ds'/
   feature name='vme'/
 /cpu
 power_management
   suspend_mem/
   suspend_disk/
 /power_management
 migration_features
   live/
   uri_transports
 uri_transporttcp/uri_transport
   /uri_transports
 /migration_features
 topology
   cells num='1'
 cell id='0'
   cpus num='8'
 cpu id='0' socket_id='0' core_id='0' siblings='0,4'/
 cpu id='1' socket_id='0' core_id='1' siblings='1,5'/
 cpu id='2' socket_id='0' core_id='2' siblings='2,6'/
 cpu id='3' socket_id='0' core_id='3' siblings='3,7'/
 cpu id='4' socket_id='0' core_id='0' siblings='0,4'/
 cpu id='5' socket_id='0' core_id='1' siblings='1,5'/
 cpu id='6' socket_id='0' core_id='2' siblings='2,6'/
 cpu id='7' socket_id='0' core_id='3' siblings='3,7'/
   /cpus
 /cell
   /cells
 /topology
 secmodel
   modelselinux/model
   doi0/doi
 /secmodel
 secmodel
   modeldac/model
   doi0/doi
 /secmodel
   /host

   guest
 os_typehvm/os_type
 arch name='i686'
   wordsize32/wordsize
   emulator/usr/libexec/qemu-kvm/emulator
   machinerhel6.4.0/machine
   machine canonical='rhel6.4.0'pc/machine
   machinerhel6.3.0/machine
   machinerhel6.2.0/machine
   machinerhel6.1.0/machine
   machinerhel6.0.0/machine
   machinerhel5.5.0/machine
   machinerhel5.4.4/machine
   machinerhel5.4.0/machine
   domain type='qemu'
   /domain
 /arch
 features
   cpuselection/
   deviceboot/
   acpi default='on' toggle='yes'/
   apic default='on' toggle='no'/
   pae/
   nonpae/
 /features
   /guest

   guest
 os_typehvm/os_type
 arch name='x86_64'
   wordsize64/wordsize
   emulator/usr/libexec/qemu-kvm/emulator
   machinerhel6.4.0/machine
   machine canonical='rhel6.4.0'pc/machine
   machinerhel6.3.0/machine
   machinerhel6.2.0/machine
   machinerhel6.1.0/machine
   machinerhel6.0.0/machine
   machinerhel5.5.0/machine
   machinerhel5.4.4/machine
   machinerhel5.4.0/machine
   domain type='qemu'
   /domain
 /arch
 features
   cpuselection/
   deviceboot/
   acpi default='on' toggle='yes'/
   apic default='on' toggle='no'/
 /features
   /guest

 /capabilities

 seems fine to me.



 [root@ovirt02 ~]# lsmod | grep kvm
 kvm   317504  0

 I'd expect kvm_intel here, too. Could you manually modprobe it and
 retry?

 Another thing that I should have asked for is the output of
 getVdsCapabilities in your vdsm.log.
Thread-191::DEBUG::2013-10-21 16:10:00,134::BindingXMLRPC::913::vds::(wrapper) 
client [192.168.0.9]::call getCapabilities with () {}
Thread-191::DEBUG::2013-10-21 16:10:00,175::BindingXMLRPC::920::vds::(wrapper) 
return getCapabilities with {'status': {'message': 'Done', 'code': 0}, 'info': 
{'HBAInventory': {'iSCSI': [{'InitiatorName': 
'iqn.1994-05.com.redhat:b35c161775fc'}], 'FC': []}, 'packages2': {'kernel': 
{'release': '358.23.2.el6.x86_64', 'buildtime': 1381941432.0, 'version': 
'2.6.32'}, 'spice-server': {'release': '12.el6_4.3', 'buildtime': 1378241755L, 
'version': '0.12.0'}, 'vdsm': {'release': '10.el6.centos.alt', 'buildtime': 
1363869298L, 'version': '4.10.3'}, 'qemu-kvm': {'release': '2.355.0.1.el6_4.9', 
'buildtime': 1380718456L, 'version': 

Re: [Users] Host Error

2013-10-21 Thread Neil
Thanks guys,

Your questions lead me to the fact that another technician had
installed vdsm-hook-nestedvt to try and get nested virtualization on
a VM working a while back. I have removed the hook and restarted and
this resolved the issue.

Thanks once again, much appreciated.

Regards.

Neil Wilson.


On Mon, Oct 21, 2013 at 4:25 PM, Alon Bar-Lev alo...@redhat.com wrote:


 - Original Message -
 From: Neil nwilson...@gmail.com
 To: Dan Kenigsberg dan...@redhat.com
 Cc: users@ovirt.org
 Sent: Monday, October 21, 2013 5:20:41 PM
 Subject: Re: [Users] Host Error

 Okay, below is the modprobe and attached is the capabilities from the
 vdsm.log

 modprobe kvm_intel
 FATAL: Error inserting kvm_intel
 (/lib/modules/2.6.32-358.23.2.el6.x86_64/kernel/arch/x86/kvm/kvm-intel.ko):
 Unknown symbol in module, or unknown parameter (see dmesg)

 According to this message, I should see something in dmesg, but I
 don't see anything when I run the modprobe.

 If I search through my dmesg I do see this though kvm_intel: Unknown
 parameter `nested'

 Do you have anything special at /etc/modprobe.d?
 Have you complied the kernel manually?


 Please shout if you need anything else though.

 Thank so much.

 Regards.

 Neil Wilson.



 On Mon, Oct 21, 2013 at 3:22 PM, Dan Kenigsberg dan...@redhat.com wrote:
  On Mon, Oct 21, 2013 at 12:50:29PM +0200, Neil wrote:
  Hi Dan,
 
  Thanks, below are the results.
 
  [root@ovirt02 ~]# virsh -r capabilities
  capabilities
 
host
  uuid6d0aa20e-c6c2-410d-b3c5-3c87af15dd7c/uuid
  cpu
archx86_64/arch
modelHaswell/model
vendorIntel/vendor
topology sockets='1' cores='4' threads='2'/
feature name='abm'/
feature name='pdpe1gb'/
feature name='rdrand'/
feature name='f16c'/
feature name='osxsave'/
feature name='pdcm'/
feature name='xtpr'/
feature name='tm2'/
feature name='est'/
feature name='smx'/
feature name='vmx'/
feature name='ds_cpl'/
feature name='monitor'/
feature name='dtes64'/
feature name='pbe'/
feature name='tm'/
feature name='ht'/
feature name='ss'/
feature name='acpi'/
feature name='ds'/
feature name='vme'/
  /cpu
  power_management
suspend_mem/
suspend_disk/
  /power_management
  migration_features
live/
uri_transports
  uri_transporttcp/uri_transport
/uri_transports
  /migration_features
  topology
cells num='1'
  cell id='0'
cpus num='8'
  cpu id='0' socket_id='0' core_id='0' siblings='0,4'/
  cpu id='1' socket_id='0' core_id='1' siblings='1,5'/
  cpu id='2' socket_id='0' core_id='2' siblings='2,6'/
  cpu id='3' socket_id='0' core_id='3' siblings='3,7'/
  cpu id='4' socket_id='0' core_id='0' siblings='0,4'/
  cpu id='5' socket_id='0' core_id='1' siblings='1,5'/
  cpu id='6' socket_id='0' core_id='2' siblings='2,6'/
  cpu id='7' socket_id='0' core_id='3' siblings='3,7'/
/cpus
  /cell
/cells
  /topology
  secmodel
modelselinux/model
doi0/doi
  /secmodel
  secmodel
modeldac/model
doi0/doi
  /secmodel
/host
 
guest
  os_typehvm/os_type
  arch name='i686'
wordsize32/wordsize
emulator/usr/libexec/qemu-kvm/emulator
machinerhel6.4.0/machine
machine canonical='rhel6.4.0'pc/machine
machinerhel6.3.0/machine
machinerhel6.2.0/machine
machinerhel6.1.0/machine
machinerhel6.0.0/machine
machinerhel5.5.0/machine
machinerhel5.4.4/machine
machinerhel5.4.0/machine
domain type='qemu'
/domain
  /arch
  features
cpuselection/
deviceboot/
acpi default='on' toggle='yes'/
apic default='on' toggle='no'/
pae/
nonpae/
  /features
/guest
 
guest
  os_typehvm/os_type
  arch name='x86_64'
wordsize64/wordsize
emulator/usr/libexec/qemu-kvm/emulator
machinerhel6.4.0/machine
machine canonical='rhel6.4.0'pc/machine
machinerhel6.3.0/machine
machinerhel6.2.0/machine
machinerhel6.1.0/machine
machinerhel6.0.0/machine
machinerhel5.5.0/machine
machinerhel5.4.4/machine
machinerhel5.4.0/machine
domain type='qemu'
/domain
  /arch
  features
cpuselection/
deviceboot/
acpi default='on' toggle='yes'/
apic default='on' toggle='no'/
  /features
/guest
 
  /capabilities
 
  seems fine to me.
 
 
 
  [root@ovirt02 ~]# lsmod | grep kvm
  kvm   317504  0
 
  I'd expect kvm_intel here, too. Could you manually modprobe it and
  retry?
 
  Another thing that I should have asked for is the 

Re: [Users] Change main datastore's IP address

2013-10-21 Thread emi...@gmail.com
Thank you very much!

Regards!


2013/10/21 Yedidyah Bar David d...@redhat.com

 - Original Message -
  From: Itamar Heim ih...@redhat.com
  To: emi...@gmail.com, Yedidyah Bar David d...@redhat.com
  Cc: users@ovirt.org
  Sent: Monday, October 21, 2013 7:23:44 AM
  Subject: Re: [Users] Change main datastore's IP address
 
  On 10/18/2013 06:12 PM, emi...@gmail.com wrote:
   Hi, I'm using oVirt 3.2 and I need to change the IP address of the main
   datastore of a cluster. Through the UI I'm not able to do it. How could
   I do this?
  
 

 IIRC, if you only change the IP address and not the hostname, the engine
 does not care. You'll naturally have to take care of keeping network access
 working (firewalling etc), might need to reboot the engine and/or hosts. I
 didn't try that.

  i don't recall the steps for 3.2, but worth mentioning that in 3.3 this
  should work via:
 
  http://gerrit.ovirt.org/17408
  http://www.ovirt.org/Changing_Engine_Hostname
 
  It provides a script
  /usr/share/ovirt-engine/setup/bin/ovirt-engine-rename which allows
  changing the engine's hostname.

 Indeed. And this script is only needed when changing the hostname, not
 the IP address.

 
  It's otopi-based. This means, among other things, that it looks similar
  to the new engine-setup/cleanup, and provides similar logging, options,
 etc.
 
  Options specific to it:
  --newname=newname
 
  An example run, which does everything in batch and does not ask
  questions, if possible:
  /usr/share/ovirt-engine/setup/bin/ovirt-engine-rename
  --newname=ovirte1n.home.local
  --otopi-environment=OSETUP_RENAME/forceIgnoreAIAInCA=bool:'True'
  OVESETUP_CORE/engineStop=bool:'True'
  OSETUP_RENAME/confirmForceOverwrite=bool:'False'
 
  didi - i think above example should be added to the wiki feature page?

 Added to the link above. It has no feature page, as in something under
 ovirt.org/Features with the format of the pages there.

 Also removed DRAFT and a few other minor changes, as what's there is
 basically correct.
 --
 Didi

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] oVirt 3.3.1 Beta now available

2013-10-21 Thread Jason Brooks


- Original Message -
 From: Jason Brooks jbro...@redhat.com
 To: users users@ovirt.org
 Sent: Saturday, October 19, 2013 11:57:38 AM
 Subject: Re: [Users] oVirt 3.3.1 Beta now available
 
 Some further 3.3.1 beta tests:
 
 Since I wasn't able to upgrade from 3.3.0.1 (seems related to
bz1005533)
 I did a fresh install of 3.3.1 beta on F19 -- an AIO install. That
 worked fine, but I wasn't able to add an additional host, and tried
with
 F19 and CentOS 6.4. In both cases, engine complained of:
 java.io.IOException: Unexpected connection termination

Bit of an update:

Adding a host to an F19 engine fails because of
https://bugzilla.redhat.com/show_bug.cgi?id=1021273 and you can work
around it with yum downgrade apache-sshd.

There's no problem adding a new host to a CentOS-based engine. On that
test, I simply forgot to install the ovirt-release package, which pulls
in tar, and the absence of tar is what caused the Unexpected connection
termination.


 
 I tried installing an 3.3.1 AIO on CentOS 6.4 but hit a dependency
 issue:
 
 Error: Package: vdsm-4.13.0-2.gitbae164c.el6.x86_64 (ovirt-beta)
Requires: selinux-policy-targeted = 3.7.19-213
Installed:
selinux-policy-targeted-3.7.19-195.el6_4.12.noarch
 (@updates)
 
 I did a clean install of a non-AIO engine on CentOS 6.4, but wasn't
able
 to add a host due to the selinux issue  (w/ CentOS) and the
Unexpected
 connection termination (w/ F19).
 
 So, so far, F19 AIO w/ no additional hosts is the only 3.3.1 config
I've
 managed to get working.
 
 Jason
 
 
 
 On Fri, 2013-10-18 at 13:48 -0700, Jason Brooks wrote:
  I hit a bump upgrading from 3.3.0.1:
  
  2013-10-18 16:38:14 DEBUG otopi.plugins.ovirt_engine_setup.db.schema
  plugin.execute:446 execute-output:
  ['/usr/share/ovirt-engine/dbscripts/upgrade.sh', '-s', 'localhost',
  '-p', '5432', '-u', 'engine', '-d', 'engine', '-l',
  '/var/log/ovirt-engine/setup/ovirt-engine-setup-20131018163438.log',
  '-g'] stderr:
  psql:create_views.sql:400: ERROR:  column
vm_templates.single_qxl_pci
  does not exist
  LINE 18:vm_templates.single_qxl_pci as single_qxl_pci,
  ^
  
  2013-10-18 16:38:14 DEBUG otopi.context context._executeMethod:137
  method exception
  Traceback (most recent call last):
File /usr/lib/python2.7/site-packages/otopi/context.py, line
127, in
  _executeMethod
  method['method']()
File
 
/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/db/schema.py,
  line 261, in _miscUpgrade
  osetupcons.DBEnv.PGPASS_FILE
File /usr/lib/python2.7/site-packages/otopi/plugin.py, line 451,
in
  execute
  command=args[0],
  RuntimeError: Command '/usr/share/ovirt-engine/dbscripts/upgrade.sh'
  failed to execute
  2013-10-18 16:38:14 ERROR otopi.context context._executeMethod:146
  Failed to execute stage 'Misc configuration': Command
  '/usr/share/ovirt-engine/dbscripts/upgrade.sh' failed to execute
  
  
  
  - Original Message -
   From: Mike Burns mbu...@redhat.com
   To: annou...@ovirt.org, users users@ovirt.org
   Sent: Friday, October 18, 2013 4:03:38 AM
   Subject: [Users] oVirt 3.3.1 Beta now available
   
   The oVirt team is pleased to announce that the 3.3.1 Release is
now
   available in beta.
   
   Release notes for this update are still being worked on, but
information
   on the changes can be found on the wiki[1].
   
   A new oVirt Node build will be available soon as well.
   
   Mike
   
   
   [1] http://www.ovirt.org/OVirt_3.3.1_release_notes
   ___
   Users mailing list
   Users@ovirt.org
   http://lists.ovirt.org/mailman/listinfo/users
   
  
  
  ___
  Users mailing list
  Users@ovirt.org
  http://lists.ovirt.org/mailman/listinfo/users
 
 
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users
 


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Unable to install oVirt Node 3.0.1: Exception: RunTimeError('Failed to partition/format')

2013-10-21 Thread Joey Boggs

On 10/21/2013 08:59 AM, Gabi C wrote:

Hello!

Had same problem on IBM xSeries  3650. Aparently was an RAID problem 
(Serve RID in my case). I had to wipe the disk, recreate the  array an 
wait until it was OK and only after that I manage to install.



On Mon, Oct 21, 2013 at 3:45 PM, Edgars M. edgars.maz...@gmail.com 
mailto:edgars.maz...@gmail.com wrote:


Hi

I am trying to install oVirt Node
(ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19.iso) on DELL R805 server,
but every time install fails with Exception: RunTimeError('Failed
to partition/format'). I also
tried ovirt-node-iso-3.0.1-1.0.2.vdsm.el6.iso version and the same
error occures. I tried different partition sizes and I always make
sure that partitions dont exceed the total disk space. I browsed
log fails and could not find anything relevant. I am really out of
ideas...

Any advise?

Thanks
Edgars

___
Users mailing list
Users@ovirt.org mailto:Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users




___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



Once it fails, press F2 to drop to shell. /tmp/ovirt.log 
/var/log/ovirt.log and /var/log/ovirt-node.log will have the debug 
messages in it. Paste those in here if you can.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[Users] oVirt translations on Transifex

2013-10-21 Thread Marcelo Barbosa
We have several Fedora related projects[1] using transifex as
translation platform. I myself have been using transifex for some
time, but searching for oVirt, I noticed it isn't there. Actually it
is on Zanata platform.
I'm wondering if we could take advantage of the big transifex
subscribed user base and get oVirt in line with main fedora projects
by migrating oVirt translations to transifex. Not sure if we have
discussed this matter before. Anyway, I'm able to help with migration
(if needed) and further help with oVirt translations.

Could you guys share your thoughts?

[1]
- Libvirt: https://fedora.transifex.com/projects/p/libvirt/
- Virt-manager: https://www.transifex.com/projects/p/virt-manager/
- Fedora : https://fedora.transifex.com/projects/p/fedora/
- Spacewalk : https://fedora.transifex.com/projects/p/spacewalk/
- FreeIPA : https://fedora.transifex.com/projects/p/freeipa/

Best Regards.

Marcelo Barbosa
Fedora Project Packager/Ambassador
fireman...@fedoraproject.org
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[Users] HTTPD error

2013-10-21 Thread Zhang, Hongyi
Hello,



I tried to setup ovirt engine on a fedora 18 machine, but I got the following 
error:



$engine-setup

[...]

Installing:

Configuring oVirt Engine... [ DONE ]

Configuring JVM...  [ DONE ]

Creating CA...  [ DONE ]

Updating ovirt-engine service...[ DONE ]

Setting Database Configuration...   [ DONE ]

Setting Database Security...[ DONE ]

Creating Database...[ DONE ]

Updating the Default Data Center Storage Type...[ DONE ]

Editing oVirt Engine Configuration...   [ DONE ]

Editing Postgresql Configuration... [ DONE ]

Configuring Firewall... [ DONE ]

Starting ovirt-engine Service...[ DONE ]

Configuring HTTPD... [ ERROR ]

Failed to enable SELinux boolean

Would someone help me to fix this problem?

Thanks a lot!
Hongyi

--

My machine uses:
$ uname -a
Linux localhost 3.10.10-100.fc18.x86_64 #1 SMP Thu Sep 5 17:47:01 EDT 2013 
x86_64 x86_64 x86_64 GNU/Linux

$ getenforce
Disabled

Here is the trace in the log:

2013-10-21 17:12:02::DEBUG::engine-setup::960::root:: Creating firewalld 
configuration
2013-10-21 17:12:02::DEBUG::setup_sequences::59::root:: running _startEngine
2013-10-21 17:12:02::DEBUG::engine-setup::1732::root:: using chkconfig to 
enable engine to load on system startup.
2013-10-21 17:12:02::DEBUG::common_utils::434::root:: Executing command -- 
'/sbin/chkconfig ovirt-engine on'
2013-10-21 17:12:02::DEBUG::common_utils::472::root:: output =
2013-10-21 17:12:02::DEBUG::common_utils::473::root:: stderr = Note: Forwarding 
request to 'systemctl enable ovirt-engine.service'.

2013-10-21 17:12:02::DEBUG::common_utils::474::root:: retcode = 0
2013-10-21 17:12:02::DEBUG::common_utils::1261::root:: stopping ovirt-engine
2013-10-21 17:12:02::DEBUG::common_utils::1298::root:: executing action 
ovirt-engine on service stop
2013-10-21 17:12:02::DEBUG::common_utils::434::root:: Executing command -- 
'/sbin/service ovirt-engine stop'
2013-10-21 17:12:02::DEBUG::common_utils::472::root:: output =
2013-10-21 17:12:02::DEBUG::common_utils::473::root:: stderr = Redirecting to 
/bin/systemctl stop  ovirt-engine.service

2013-10-21 17:12:02::DEBUG::common_utils::474::root:: retcode = 0
2013-10-21 17:12:02::DEBUG::common_utils::1251::root:: starting ovirt-engine
2013-10-21 17:12:02::DEBUG::common_utils::1298::root:: executing action 
ovirt-engine on service start
2013-10-21 17:12:02::DEBUG::common_utils::434::root:: Executing command -- 
'/sbin/service ovirt-engine start'
2013-10-21 17:12:02::DEBUG::common_utils::472::root:: output =
2013-10-21 17:12:02::DEBUG::common_utils::473::root:: stderr = Redirecting to 
/bin/systemctl start  ovirt-engine.service

2013-10-21 17:12:02::DEBUG::common_utils::474::root:: retcode = 0
2013-10-21 17:12:02::DEBUG::setup_sequences::59::root:: running 
_configureSelinuxBoolean
2013-10-21 17:12:02::DEBUG::engine-setup::722::root:: Enable 
httpd_can_network_connect boolean
2013-10-21 17:12:02::DEBUG::common_utils::434::root:: Executing command -- 
'/usr/sbin/semanage boolean --modify --on httpd_can_network_connect'
2013-10-21 17:12:16::DEBUG::common_utils::472::root:: output =
2013-10-21 17:12:16::DEBUG::common_utils::473::root:: stderr = 
libsemanage.semanage_commit_sandbox: Error while renaming 
/etc/selinux/targeted/modules/active to /etc/selinux/targeted/modules/previous. 
(Invalid cross-device link).
/usr/sbin/semanage: Could not commit semanage transaction

2013-10-21 17:12:16::DEBUG::common_utils::474::root:: retcode = 1
2013-10-21 17:12:16::DEBUG::setup_sequences::62::root:: Traceback (most recent 
call last):
  File /usr/share/ovirt-engine/scripts/setup_sequences.py, line 60, in run
function()
  File /usr/bin/engine-setup, line 730, in _configureSelinuxBoolean
out, rc = utils.execCmd(cmdList=cmd, failOnError=True, 
msg=output_messages.ERR_FAILED_UPDATING_SELINUX_BOOLEAN)
  File /usr/share/ovirt-engine/scripts/common_utils.py, line 477, in execCmd
raise Exception(msg)
Exception: Failed to enable SELinux boolean

2013-10-21 17:12:16::DEBUG::engine-setup::1973::root:: *** The following params 
were used as user input:
2013-10-21 17:12:16::DEBUG::engine-setup::1978::root:: override-httpd-config: 
yes
2013-10-21 17:12:16::DEBUG::engine-setup::1978::root:: http-port: 80
2013-10-21 17:12:16::DEBUG::engine-setup::1978::root:: https-port: 443
2013-10-21 17:12:16::DEBUG::engine-setup::1978::root:: random-passwords: no
2013-10-21 17:12:16::DEBUG::engine-setup::1978::root:: mac-range: 
00:1A:4A:10:7C:00-00:1A:4A:10:7C:FF
2013-10-21 17:12:16::DEBUG::engine-setup::1978::root:: host-fqdn: engine.wrs.com
2013-10-21 17:12:16::DEBUG::engine-setup::1978::root:: auth-pass: 

Re: [Users] Unable to install oVirt Node 3.0.1: Exception: RunTimeError('Failed to partition/format')

2013-10-21 Thread Edgars M.
Hi, thanks for your replies..

As suggested by Gabi C, I destroyed RAID on my RAID controller, re-created
it and after that it worked.

Thanks again.


On Mon, Oct 21, 2013 at 10:45 PM, Joey Boggs jbo...@redhat.com wrote:

  On 10/21/2013 08:59 AM, Gabi C wrote:

  Hello!

  Had same problem on IBM xSeries  3650. Aparently was an RAID problem
 (Serve RID in my case). I had to wipe the disk, recreate the  array an wait
 until it was OK and only after that I manage to install.


 On Mon, Oct 21, 2013 at 3:45 PM, Edgars M. edgars.maz...@gmail.comwrote:

 Hi

  I am trying to install oVirt Node
 (ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19.iso) on DELL R805 server, but every
 time install fails with Exception: RunTimeError('Failed to
 partition/format'). I also tried ovirt-node-iso-3.0.1-1.0.2.vdsm.el6.iso
 version and the same error occures. I tried different partition sizes and I
 always make sure that partitions dont exceed the total disk space. I
 browsed log fails and could not find anything relevant. I am really out of
 ideas...

  Any advise?

  Thanks
  Edgars

 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users




 ___
 Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users



 Once it fails, press F2 to drop to shell. /tmp/ovirt.log
 /var/log/ovirt.log and /var/log/ovirt-node.log will have the debug messages
 in it. Paste those in here if you can.

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] HTTPD error

2013-10-21 Thread Itamar Heim

On 10/21/2013 10:25 PM, Zhang, Hongyi wrote:

Hello,

I tried to setup ovirt engine on a fedora 18 machine, but I got the
following error:

$engine-setup

[…]

Installing:

Configuring oVirt Engine... [ DONE ]

Configuring JVM...  [ DONE ]

Creating CA...  [ DONE ]

Updating ovirt-engine service...[ DONE ]

Setting Database Configuration...   [ DONE ]

Setting Database Security...[ DONE ]

Creating Database...[ DONE ]

Updating the Default Data Center Storage Type...[ DONE ]

Editing oVirt Engine Configuration...   [ DONE ]

Editing Postgresql Configuration... [ DONE ]

Configuring Firewall... [ DONE ]

Starting ovirt-engine Service...[ DONE ]

Configuring HTTPD... [ ERROR ]

Failed to enable SELinux boolean

Would someone help me to fix this problem?

Thanks a lot!

Hongyi

--

My machine uses:

$ uname -a

Linux localhost 3.10.10-100.fc18.x86_64 #1 SMP Thu Sep 5 17:47:01 EDT
2013 x86_64 x86_64 x86_64 GNU/Linux

$ getenforce

Disabled

*Here is the trace in the log:*

2013-10-21 17:12:02::DEBUG::engine-setup::960::root:: Creating firewalld
configuration

2013-10-21 17:12:02::DEBUG::setup_sequences::59::root:: running _startEngine

2013-10-21 17:12:02::DEBUG::engine-setup::1732::root:: using chkconfig
to enable engine to load on system startup.

2013-10-21 17:12:02::DEBUG::common_utils::434::root:: Executing command
-- '/sbin/chkconfig ovirt-engine on'

2013-10-21 17:12:02::DEBUG::common_utils::472::root:: output =

2013-10-21 17:12:02::DEBUG::common_utils::473::root:: stderr = Note:
Forwarding request to 'systemctl enable ovirt-engine.service'.

2013-10-21 17:12:02::DEBUG::common_utils::474::root:: retcode = 0

2013-10-21 17:12:02::DEBUG::common_utils::1261::root:: stopping ovirt-engine

2013-10-21 17:12:02::DEBUG::common_utils::1298::root:: executing action
ovirt-engine on service stop

2013-10-21 17:12:02::DEBUG::common_utils::434::root:: Executing command
-- '/sbin/service ovirt-engine stop'

2013-10-21 17:12:02::DEBUG::common_utils::472::root:: output =

2013-10-21 17:12:02::DEBUG::common_utils::473::root:: stderr =
Redirecting to /bin/systemctl stop  ovirt-engine.service

2013-10-21 17:12:02::DEBUG::common_utils::474::root:: retcode = 0

2013-10-21 17:12:02::DEBUG::common_utils::1251::root:: starting ovirt-engine

2013-10-21 17:12:02::DEBUG::common_utils::1298::root:: executing action
ovirt-engine on service start

2013-10-21 17:12:02::DEBUG::common_utils::434::root:: Executing command
-- '/sbin/service ovirt-engine start'

2013-10-21 17:12:02::DEBUG::common_utils::472::root:: output =

2013-10-21 17:12:02::DEBUG::common_utils::473::root:: stderr =
Redirecting to /bin/systemctl start  ovirt-engine.service

2013-10-21 17:12:02::DEBUG::common_utils::474::root:: retcode = 0

2013-10-21 17:12:02::DEBUG::setup_sequences::59::root:: running
_configureSelinuxBoolean

2013-10-21 17:12:02::DEBUG::engine-setup::722::root:: Enable
httpd_can_network_connect boolean

2013-10-21 17:12:02::DEBUG::common_utils::434::root:: Executing command
-- '/usr/sbin/semanage boolean --modify --on httpd_can_network_connect'

2013-10-21 17:12:16::DEBUG::common_utils::472::root:: output =

2013-10-21 17:12:16::DEBUG::common_utils::473::root:: stderr =
libsemanage.semanage_commit_sandbox: Error while renaming
/etc/selinux/targeted/modules/active to
/etc/selinux/targeted/modules/previous. (Invalid cross-device link).

/usr/sbin/semanage: Could not commit semanage transaction

2013-10-21 17:12:16::DEBUG::common_utils::474::root:: retcode = 1

2013-10-21 17:12:16::DEBUG::setup_sequences::62::root:: Traceback (most
recent call last):

File /usr/share/ovirt-engine/scripts/setup_sequences.py, line 60, in run

 function()

   File /usr/bin/engine-setup, line 730, in _configureSelinuxBoolean

 out, rc = utils.execCmd(cmdList=cmd, failOnError=True,
msg=output_messages.ERR_FAILED_UPDATING_SELINUX_BOOLEAN)

   File /usr/share/ovirt-engine/scripts/common_utils.py, line 477, in
execCmd

 raise Exception(msg)

Exception: Failed to enable SELinux boolean

2013-10-21 17:12:16::DEBUG::engine-setup::1973::root:: *** The following
params were used as user input:

2013-10-21 17:12:16::DEBUG::engine-setup::1978::root::
override-httpd-config: yes

2013-10-21 17:12:16::DEBUG::engine-setup::1978::root:: http-port: 80

2013-10-21 17:12:16::DEBUG::engine-setup::1978::root:: https-port: 443

2013-10-21 17:12:16::DEBUG::engine-setup::1978::root:: random-passwords: no

2013-10-21 17:12:16::DEBUG::engine-setup::1978::root:: mac-range:
00:1A:4A:10:7C:00-00:1A:4A:10:7C:FF

2013-10-21 17:12:16::DEBUG::engine-setup::1978::root:: host-fqdn:
engine.wrs.com

2013-10-21 

Re: [Users] Host Error

2013-10-21 Thread Itamar Heim

On 10/21/2013 03:39 PM, Neil wrote:

Thanks guys,

Your questions lead me to the fact that another technician had
installed vdsm-hook-nestedvt to try and get nested virtualization on
a VM working a while back. I have removed the hook and restarted and
this resolved the issue.

Thanks once again, much appreciated.


danken - shouldn't the hook (if in rpm form) require a kernel which 
actually supports nested, to not be installed on .el6, etc.?




Regards.

Neil Wilson.


On Mon, Oct 21, 2013 at 4:25 PM, Alon Bar-Lev alo...@redhat.com wrote:



- Original Message -

From: Neil nwilson...@gmail.com
To: Dan Kenigsberg dan...@redhat.com
Cc: users@ovirt.org
Sent: Monday, October 21, 2013 5:20:41 PM
Subject: Re: [Users] Host Error

Okay, below is the modprobe and attached is the capabilities from the
vdsm.log

modprobe kvm_intel
FATAL: Error inserting kvm_intel
(/lib/modules/2.6.32-358.23.2.el6.x86_64/kernel/arch/x86/kvm/kvm-intel.ko):
Unknown symbol in module, or unknown parameter (see dmesg)

According to this message, I should see something in dmesg, but I
don't see anything when I run the modprobe.

If I search through my dmesg I do see this though kvm_intel: Unknown
parameter `nested'


Do you have anything special at /etc/modprobe.d?
Have you complied the kernel manually?



Please shout if you need anything else though.

Thank so much.

Regards.

Neil Wilson.



On Mon, Oct 21, 2013 at 3:22 PM, Dan Kenigsberg dan...@redhat.com wrote:

On Mon, Oct 21, 2013 at 12:50:29PM +0200, Neil wrote:

Hi Dan,

Thanks, below are the results.

[root@ovirt02 ~]# virsh -r capabilities
capabilities

   host
 uuid6d0aa20e-c6c2-410d-b3c5-3c87af15dd7c/uuid
 cpu
   archx86_64/arch
   modelHaswell/model
   vendorIntel/vendor
   topology sockets='1' cores='4' threads='2'/
   feature name='abm'/
   feature name='pdpe1gb'/
   feature name='rdrand'/
   feature name='f16c'/
   feature name='osxsave'/
   feature name='pdcm'/
   feature name='xtpr'/
   feature name='tm2'/
   feature name='est'/
   feature name='smx'/
   feature name='vmx'/
   feature name='ds_cpl'/
   feature name='monitor'/
   feature name='dtes64'/
   feature name='pbe'/
   feature name='tm'/
   feature name='ht'/
   feature name='ss'/
   feature name='acpi'/
   feature name='ds'/
   feature name='vme'/
 /cpu
 power_management
   suspend_mem/
   suspend_disk/
 /power_management
 migration_features
   live/
   uri_transports
 uri_transporttcp/uri_transport
   /uri_transports
 /migration_features
 topology
   cells num='1'
 cell id='0'
   cpus num='8'
 cpu id='0' socket_id='0' core_id='0' siblings='0,4'/
 cpu id='1' socket_id='0' core_id='1' siblings='1,5'/
 cpu id='2' socket_id='0' core_id='2' siblings='2,6'/
 cpu id='3' socket_id='0' core_id='3' siblings='3,7'/
 cpu id='4' socket_id='0' core_id='0' siblings='0,4'/
 cpu id='5' socket_id='0' core_id='1' siblings='1,5'/
 cpu id='6' socket_id='0' core_id='2' siblings='2,6'/
 cpu id='7' socket_id='0' core_id='3' siblings='3,7'/
   /cpus
 /cell
   /cells
 /topology
 secmodel
   modelselinux/model
   doi0/doi
 /secmodel
 secmodel
   modeldac/model
   doi0/doi
 /secmodel
   /host

   guest
 os_typehvm/os_type
 arch name='i686'
   wordsize32/wordsize
   emulator/usr/libexec/qemu-kvm/emulator
   machinerhel6.4.0/machine
   machine canonical='rhel6.4.0'pc/machine
   machinerhel6.3.0/machine
   machinerhel6.2.0/machine
   machinerhel6.1.0/machine
   machinerhel6.0.0/machine
   machinerhel5.5.0/machine
   machinerhel5.4.4/machine
   machinerhel5.4.0/machine
   domain type='qemu'
   /domain
 /arch
 features
   cpuselection/
   deviceboot/
   acpi default='on' toggle='yes'/
   apic default='on' toggle='no'/
   pae/
   nonpae/
 /features
   /guest

   guest
 os_typehvm/os_type
 arch name='x86_64'
   wordsize64/wordsize
   emulator/usr/libexec/qemu-kvm/emulator
   machinerhel6.4.0/machine
   machine canonical='rhel6.4.0'pc/machine
   machinerhel6.3.0/machine
   machinerhel6.2.0/machine
   machinerhel6.1.0/machine
   machinerhel6.0.0/machine
   machinerhel5.5.0/machine
   machinerhel5.4.4/machine
   machinerhel5.4.0/machine
   domain type='qemu'
   /domain
 /arch
 features
   cpuselection/
   deviceboot/
   acpi default='on' toggle='yes'/
   apic default='on' toggle='no'/
 /features
   /guest

/capabilities


seems fine to me.




[root@ovirt02 ~]# lsmod | grep kvm
kvm   317504  0


I'd expect kvm_intel here, too. Could you manually modprobe it and
retry?

Another thing that I should have asked for is