October 2012 - Users - oVirt List Archives

[Users] oVirt-engine and UserPortal "cluster"
by Brian Vetter 04 Oct '12

04 Oct '12

I've been scouring through the install notes and the architecture documents but didn't find my answer. Is there a way to "cluster" or replicate the userportal app or is it strictly a single instance? Any thoughts to the scale of a large VDI system with 10,000 desktops and their VMs and how that impacts the ovirt-engine and the user-portal app? I figure it has been discussed, but using the word cluster in a google search of the wiki results in a lot of hits, none of them that I saw that are to do with clustering the server, just the virtual machine nodes. Brian

3 3

[Users] new ovirt-engine-sdk features (form 3.1 till now)
by Michael Pasternak 04 Oct '12

04 Oct '12

- allow persistent_auth via localhost - make /filter header global rather than method driven #857018 - throw error when connecting to ssl site using http protocol - raise NoCertificatesError only when no ca_file specified - several rebases to include latest engine features -- Michael Pasternak RedHat, ENG-Virtualization R&D

1 0

[Users] new ovirt-engine-cli features (form 3.1 till now)
by Michael Pasternak 04 Oct '12

04 Oct '12

- support utf-8 encoding - do not log /connect command in history - disable /history while not connected - add username/password prompt/command-line functionality - history command does not support pipe redirection #854486 - valid UUIDs are treated as syntax error #854391 - Rename /delete command with /remove #855769 - Raise an error if identifier is not specified in /show command #855750 - remove --show-all option from /show command #855749 - rename "create" command with "add" #855773 - change NoCertificatesError message to ask only for ca_file - implement /filter flag - do not write to file i/o during script execution - shell does not exit when using /exit/ command in script -- Michael Pasternak RedHat, ENG-Virtualization R&D

1 0

[Users] Logical networks in 3.1 on CentOS 6.3
by Frank Soyer 04 Oct '12

04 Oct '12

Hi list, I'm testing oVirt on 3 hosts as a possible replacement for Proxmox. I've some trouble to understand the network part of the config (for beginning, I'll have some other questions about glusterfs later :)) and need some lights. The environment : - Engine host, no-virtualisation capability, one NIC eth0 - 2 nodes, virtualisation OK, 2 NICs eth0,eth1 - oVirt 3.1 on CentOS 6.3. The installation of engine/nodes was OK, no problem at all on the 3 nodes. The NIC eth0 on all hosts was manually bound on a bridge "ovirtmgmt", respectively on 10.0.0.1, .2, .3 ovirmgmt appears on the console as the management network, no problem, just a first question : it is marked as "VM network", and no way to change that. What if I want that this network to be dedicated on physical hosts only ? Second, I tried to create a logical network, call it "vmnetwork", linked it to datacenter and cluster. In the network interface configuration window on the hosts, I can link vmnetwork on eth0, but when validating an error occurs saying that eth0 is already linked to ovirmgmt. So I can't have management network and vm network on the same NIC , even on a virtual nic (tried with vlan=0 and vlan=10 on vmnetwork, same thing) ? Third, is this a bug when I come back to the configuration window, that the networks (for ovirmgmt and vmnetwork) return to "DHCP" ? If I forgot to re-check the static network, the host lose all it's network config and is declared non-responsive then rebooted..... Bad ! Thank you for helping me to understand. Frank

4 4

[Users] Question about network card order
by Kevin Maziere Aubry 03 Oct '12

03 Oct '12

Hello My first email on the mailing, I hope the first one of a longue serie. The email concerns a Network Card order issue for which I like to report a have your advises. I've made a template which contains 2 network cards, Each one bridge on different vlan network. When I create a VM from this template, the network card mac address assignation is random... so that by default my fedora assign eth0 to the smallest mac address, and so on for eth1/eth2 ... But no way to define network card order in template, so that sometime the smallest mac address is on eth0, sometime on eth1 (and in fact more often on eth1), sometime my VM works, sometime I have to destroy and recreate network interfaces. Is there a workaround or anything else ? Thanks Kévin -- Kevin Mazière Responsable Infrastructure Alter Way – Hosting 1 rue Royal - 227 Bureaux de la Colline 92213 Saint-Cloud Cedex Tél : +33 (0)1 41 16 38 41 Mob : +33 (0)7 62 55 57 05 http://www.alterway.fr

5 7

[Users] fw: Migrating ovirt-engine to new server
by Neil 03 Oct '12

03 Oct '12

Sorry to repost(kind of) but I'm really battling here and I need to get the VM's up and running again. I've given up on the idea of migrating the database across due to all sorts of problems encountered and I've instead done a completely NEW fresh ovirt-engine install and I've got one host added and running. How do I go about detaching my storage datacentre from my old ovirt-engine, and re-attaching it to my new ovirt-engine running on my new server? I'm running FC with multiple LUNS all assigned in one datacentre called "linux" and I can't detach it because it says "Cannot detach Storage Domain while VMs/Templates reside on it." My entire datacentre is in maintenance at the moment which consists of only 3 VM's(4TB's in total), my host only has a 16GB SDD in it, so exporting to a local NFS mount is not an option. Can I safely remove the VM's(as instructed above) by going to "VM's" and clicking remove and then will I be able to detach the datacentre and then re-attach it to the new ovirt-engine? Bearing in mind that I'm running a fresh install of ovirt-engine and I haven't copied the database across? Is it a matter of re-attaching the LUNS that are currently assigned because I can see the LUNS when I try and add a new FC storage domain, however the LUNS currently attached to the old ovirt-engine are greyed out and can't be selected. Any assistance is greatly appreciated. Thank you. Regards. Neil Wilson.

2 1

[Users] nested KVM
by Nathanaël Blanchet 03 Oct '12

03 Oct '12

Hello, I've tried many times to run a node as a guest in ovirt following http://wiki.ovirt.org/wiki/Vdsm_Developers#Running_Node_as_guest_-_Nested_K… . The result is that I'm able to register such a host in engine, but it is impossible to start any vm on it. If I boot on an ISO, I can see the first prompt and move between the items. But since I begin the installation I have a blank screen and the vm goes into pause mode in vit-manager. Then I have no way else than rebooting the hypervisor guest because it is impossible to resume. When I get logs on the real host, I can find this : arning : x86Decode:1306 : Preferred CPU model Westmere not allowed by hypervisor; closest supported model will be used Sep 25 17:11:59 khamsin libvirtd[23053]: 2012-09-25 15:11:59.384+0000: 23054: warning : x86Decode:1306 : Preferred CPU model Westmere not allowed by hypervisor; closest supported model will be used Sep 25 17:12:19 khamsin libvirtd[23053]: 2012-09-25 15:12:19.150+0000: 23055: warning : x86Decode:1306 : Preferred CPU model Westmere not allowed by hypervisor; closest supported model will be used Sep 25 17:45:48 khamsin libvirtd[23053]: 2012-09-25 15:45:48.342+0000: 23058: warning : x86Decode:1306 : Preferred CPU model Westmere not allowed by hypervisor; closest supported model will be used Sep 25 18:07:05 khamsin libvirtd[23053]: 2012-09-25 16:07:05.834+0000: 23058: warning : x86Decode:1306 : Preferred CPU model Nehalem not allowed by hypervisor; closest supported model will be used Sep 25 18:44:47 khamsin libvirtd[23053]: 2012-09-25 16:44:47.340+0000: 23057: warning : x86Decode:1306 : Preferred CPU model Penryn not allowed by hypervisor; closest supported model will be used As you can see, I have tried many cpu type for launching this guest hypervisor, but none of them is accepted by the hypervisor. Plus, I've modified each time the family type in the cluster tab, but it is the same. On the hist: #virsh capabilities gives <cpu> <arch>x86_64</arch> <model>Westmere</model> <vendor>Intel</vendor> Thanks for your help -- Nathanaël Blanchet Supervision réseau Pôle exploitation et maintenance Département des systèmes d'information 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

2 2

[Users] Setup Networks Screencast
by Muli Salem 03 Oct '12

03 Oct '12

Hi all, You are welcome to watch the newest screencast on the oVirt channel, about the 3.1 Setup Networks feature: http://www.youtube.com/watch?v=3EMrqQR-f3w&feature=plcp Regards, Muli

1 0

[Users] Migrating ovirt-engine to new server
by Neil 03 Oct '12

03 Oct '12

Hi guys, Please could someone assist me. I'm trying to migrate my ovirt-engine(3.1 but very early release) to latest 3.1 on new machine(both Centos 6.3 dreyou repo). After the intial engine-setup I can log into webadmin without a problem. I then imported my DB from the old server (psql -U postgres -d engine -w < /root/dump.sql) and start the ovirt-engine again, but now when try and browse to the webadmin I don't get anything at all, no web page displays at all, I'm guessing that there are lots of additional steps that I'm missing, so perhaps this is normal. I haven't attached any logs etc because I'm fairly certain that I'm missing some vital steps before I can actually log into my system using the new DB. I've changed the hostname of the machine -- previous name was node02.blabla.com and now it's backup.blabla.com does this matter? My guess is the certificates won't work with the DB now, is there any way to get around this, or should I rather just use the same hostname on the new server? I also haven't copied any physical files or configs across yet, which files/folders do I need? I'm using a FC SAN so I'm assuming I won't need to export my VM's, it should just be a matter of detaching my main storage domain and then re-attaching it on the new server? I see when I try and detach from the old server it says "can't export while there are Templates/VM's on the system" must I hit the remove button on each VM on the old system in order to detach and then attach to on the new system? (presume it will only remove the VM's from the old system and not actually delete the VM image?) I'm using no templates, so I'm assuming these don't need to be exported/imported? Sorry for all the questions, any help is greatly appreciated! Regards. Neil Wilson.

1 0

[Users] General challenges w/ Ovirt 3.1
by Hans Lellelid 02 Oct '12

02 Oct '12

Hi - I apologize in advance that this email is less about a specific problem and more a general inquiry as to the most recommended / likely-to-be-successful way path. I am on my third attempt to get an ovirt system up and running (using a collection of spare servers, that meet the requirements set out in the user guide). I'm looking to implement a viable evolution to the unscalable stove-piped ESXi servers (i.e. which are free). And while I'm happy to learn more about the underpinnings, I recognize that to really be a replacement for these VMWare solutions, this has to mostly "Just Work" -- and that's eventually why I've given up on previous occasions (after a couple days of work) and decided to revisit in 6 months. My basic server setup is: - oVirt Mgmt (engine) - oVirt HV1 (hypervisor node) - oVirt HV2 (hypervisor node) - oVirt Disk (NFS share) 1st attempt: I installed the latest stable Node image (2.5.1) on the HV1 and HV2 machines and re-installed the Mgmt server w/ Fedora 17 (64-bit) and all the latest stable engine packages. For the first time, Node installation and Engine setup all went flawlessly. But I could not mount the NFS shares. Upon deeper research, this appeared to be the bug mentioned about NFS; I was *sure* that the official stable Node image would have had a downgraded kernel, but apparently not :) I have no idea if there is an officially supported way to downgrade the kernel on the Node images; the warnings say that any changes will not persist, so I assume there is not. (I am frankly a little surprised that the official stable packages & ISO won't actually work to mount NFS shares, which is the recommended storage strategy and kinda critical to this thing!?) . FWIW, the oVirt Disk system is a CentOS 6.2 system. 2nd attempt: I re-installed the nodes as Fedora 17 boxes and downgraded the kernels to 3.4.6-2. Then I connected these from the Engine (specifying the root pw) and watched the logs while things installed. After reboot neither of the servers were reachable. Sitting in front of the console, I realized that networking was refusing to start; several errors printed to the console looked like: device-mapper: table: 253:??: multipath: error getting device (I don't remember exactly what was after the "253:") calling "multipath -ll" yielded no output, calling "multipath -r" re-issued the above errors Obviously the Engine did a lot of work there, setting up the bridge, etc. I did not spend a long time trying to untangle this. (In retrospect, I will go back and probably spend more time trying to track this down, but it's difficult since I lose network & have to stand at the console in the server room :)) 3rd attempt: I re-installed the nodes with Fedora 17 and attempted to install VDSM manually by RPM. Despite following the instructions to turn off ssl (ssl=false in /etc/vdsm/vdsm.conf), I am seeing SSL "unknown cert" errors from the python socket server with every attempt of the engine to talk to the node. I added the CA from the master into the /etc/pki/vdsm (since that was the commented-out path in the config file as the trust store) and added the server's cert here too, but have no idea what form these files should take to be respected by the python server -- or if they are respected at all. I couldn't find this documented anywhere, so I left the servers spewing logs for the weekend figuring that I'll either give up or try another strategy on Monday. So is there a general strategy that should get me to a working system here? I suspect that the Node image is not a good path, since it appears to be incompatible with NFS mounting. The Fedora-17-installed-by-engine sounds good, but there's a lot of magic there & it obviously completely broke my systems. Is that where I should focus my efforts? Should I ditch NFS storage and just try to get something working with local-only storage on the nodes? (Shared storage would be a primary motivation for moving to ovirt, though.) I am very excited for this to work for me someday. I think it has been frustrating to have such sparse (or outdated?) documentation and such fundamental problems/bugs/configuration challenges. I'm using pretty standard (Dell) commodity servers (SATA drives, simple RAID setups, etc.). Sorry for no log output, I can provide more of that when back at work on Monday, but this was more of a general inquiry on where I should plan to take this. Thanks in advance! Hans

3 7