Re: [Users] Nic names : always start by eth0

Hi AFAIK This is more a CentOS- than an oVirt-issue. CentOS behaves identically on vSphere. If I remember correctly, this is due to the fact that the MAC-address of the virtual NIC has to change, when you create a VM from a template. CentOS however keeps the MAC address of the template and

Re: [Users] upgrade to latest master not working

Big thanks to all. I can have a deep breath eventually when I know it's not this patch set ( http://gerrit.ovirt.org/#/c/14605/) broke the master, we are glad to do something if there is any potential issue relevant with the patch sets we submitted. Best Regards, Dave Chen -Original

Re: [Users] Nic names : always start by eth0

gregoire.le...@retenodus.net wrote: I have an ovirt cluster which runs CentOS VM. I have a template to create VM. On this template, there are two interfaces, eth0 and eth1. When I create a VM using this template, the new interfaces are named eth2 and eth3. It can be pretty annoying and I would

Re: [Users] Nic names : always start by eth0

- Original Message - From: Itamar Heim ih...@redhat.com To: \René \Koch (ovido)\\ r.k...@ovido.at Cc: gregoire leroy gregoire.le...@retenodus.net, users@ovirt.org, Omer Frenkel ofren...@redhat.com, Michal Skrivanek mskri...@redhat.com, Greg Padgett gpadg...@redhat.com Sent:

Re: [Users] oVirt 3.3 SPICE console error 500

Dne 26.7.2013 16:24, Einav Cohen napsal(a): - Original Message - From: Itamar Heim ih...@redhat.com Sent: Friday, July 26, 2013 6:55:55 AM On 07/26/2013 01:07 PM, Tomas Jelinek wrote: Well, this is an error introduced by upgrading the GWT and it broke our serialization mechanism. There

[Users] oVirt 3.2.1 /F18 node vdsm issue

Hi, I just set up a vanilla oVirt 3.2.1 environment, containing oVirt engine 3.2.1 F18 based oVirt Engine Version: 3.2.1-1.fc18 F18 minimal node vdsm-4.10.3-10.fc18 libvirt-0.10.2.6-1.fc18 1.2.2 - 13.fc18 K ernel 3.9.11 - 200.fc18.x86_64 gluster-storage, replicated, EL6 glusterfs 3.4.0 F18

Re: [Users] oVirt 3.3 SPICE console error 500

On Jul 31, 2013, at 10:05 , Jakub Bittner j.bitt...@nbu.cz wrote: Dne 26.7.2013 16:24, Einav Cohen napsal(a): - Original Message - From: Itamar Heim ih...@redhat.com Sent: Friday, July 26, 2013 6:55:55 AM On 07/26/2013 01:07 PM, Tomas Jelinek wrote: Well, this is an error

Re: [Users] oVirt 3.2.1 /F18 node vdsm issue

On Wed, Jul 31, 2013 at 04:45:03AM -0400, Sven Knohsalla wrote: Hi, I just set up a vanilla oVirt 3.2.1 environment, containing oVirt engine 3.2.1 F18 based oVirt Engine Version: 3.2.1-1.fc18 F18 minimal node vdsm-4.10.3-10.fc18 libvirt-0.10.2.6-1.fc18 1.2.2 - 13.fc18 K ernel 3.9.11 -

Re: [Users] oVirt 3.3 SPICE console error 500

Dne 31.7.2013 13:30, Michal Skrivanek napsal(a): On Jul 31, 2013, at 10:05 , Jakub Bittner j.bitt...@nbu.cz wrote: Dne 26.7.2013 16:24, Einav Cohen napsal(a): - Original Message - From: Itamar Heim ih...@redhat.com Sent: Friday, July 26, 2013 6:55:55 AM On 07/26/2013 01:07 PM, Tomas

[Users] oVirt 3.2.1 adding NFS ISO/Export fails

Hi, did anybody run into the issue following issue under oVirt 3.2.1 + F18 based nodes ? -- NFS ISO/Export mount via webgui gives error message There is no storage domain under the specified path. Check event log for more details. (no advanced mount parameters given) Mounting NFS volume under

[Users] oVirt Weekly Meeting Minutes -- 2013-07-31

Minutes:http://ovirt.org/meetings/ovirt/2013/ovirt.2013-07-31-14.05.html Minutes (text): http://ovirt.org/meetings/ovirt/2013/ovirt.2013-07-31-14.05.txt Log: http://ovirt.org/meetings/ovirt/2013/ovirt.2013-07-31-14.05.log.html #ovirt: oVirt Weekly

Re: [Users] Fedora upgrading from 3.1 to 3.2

On 07/31/2013 05:10 PM, Karli Sjöberg wrote: Hey! Big news for me, I´ve managed to upgrade to 3.2, but sadly, now I can´t get it to log in with admin@internal mailto:admin@internal:( This is how I managed it: (After Fedora is up to 18) - Erase all of the 3.1-packages - Install the new

Re: [Users] Problem Creating oVirt Engine

I'm having difficulties copying files between the virtual machine and the host (Mac OS X) so here are the contents of the LOG files you requested, and them some others; just in case: ERROR_LOG [Wed Jul 24 15:43:22.461132 2013] [core:notice] [pid 1573] SELinux policy enabled; httpd running as

Re: [Users] Fedora upgrading from 3.1 to 3.2

- Original Message - From: Karli Sjöberg karli.sjob...@slu.se To: Alex Lourie alou...@redhat.com Cc: users@ovirt.org Sent: Wednesday, July 31, 2013 5:10:24 PM Subject: Re: [Users] Fedora upgrading from 3.1 to 3.2 Hey! Big news for me, I´ve managed to upgrade to 3.2, but sadly,

Re: [Users] Problem Creating oVirt Engine

- Original Message - From: Richie@HIP richiepiovane...@healthcareinfopartners.com To: Alon Bar-Lev alo...@redhat.com Cc: Itamar Heim ih...@redhat.com, users@ovirt.org Sent: Wednesday, July 31, 2013 9:00:11 PM Subject: Re: [Users] Problem Creating oVirt Engine I'm having

[Users] vdsm v4.12.0 dependencies for el6 hosts

vdsm v4.12.0 for engine 3.3 has some unsatisfied dependencies on el6 hosts: -- Finished Dependency Resolution Error: Package: vdsm-hook-sriov-4.12.0-10.el6.noarch (el6v-test) Requires: libvirt-daemon-driver-nodedev Error: Package: vdsm-4.12.0-10.el6.x86_64 (el6v-test)

Re: [Users] Problem Creating oVirt Engine

BTW - I installed oVirtEngine at a client's office using a VirtualBox VM. They are a large imaging center and have an Active Directory and DNS in place. I Stumbled upon ALL the same problems when using the default engine setup parameters (it hung upon restarting the HTTPd service). Just to

[Users] ovirt-hosted-engine CentOS

Hello, Is there anyway to install self hosted engine on CentOS 6.4? The package ovirt-hosted-engine isn't available in the el6-ovirt, CentOS ovirt-test repositories. Thanks, Haven ___ Users mailing list Users@ovirt.org

Re: [Users] Problem Creating oVirt Engine

On 08/01/2013 01:43 AM, Richie@HIP wrote: BTW - I installed oVirtEngine at a client's office using a VirtualBox VM. They are a large imaging center and have an Active Directory and DNS in place. I Stumbled upon ALL the same problems when using the default engine setup parameters (it hung upon