- Users - oVirt List Archives

[Users] SD Disk's Logical Volume not visible/activated on some nodes
by Boyan Tabakov 05 Mar '14

05 Mar '14

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --kNwttSRPs68koQxvdSI5KDEeiPmQG9f68 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello, I have ovirt 3.3 installed on on FC 19 hosts with vdsm 4.13.3-2.fc19. One of the hosts (host1) is engine + node + SPM and the other host2 is just a node. I have an iSCSI storage domain configured and accessible from both nodes. When creating a new disk in the SD, the underlying logical volume gets properly created (seen in vgdisplay output on host1), but doesn't seem to be automatically picked by host2. Consequently, when creating/booting a VM with the said disk attached, the VM fails to start on host2, because host2 can't see the LV. Similarly, if the VM is started on host1, it fails to migrate to host2. Extract from host2 log is in the end. The LV in question is 6b35673e-7062-4716-a6c8-d5bf72fe3280. As far as I could track quickly the vdsm code, there is only call to lvs and not to lvscan or lvchange so the host2 LVM doesn't fully refresh. The only workaround so far has been to restart VDSM on host2, which makes it refresh all LVM data properly. When is host2 supposed to pick up any newly created LVs in the SD VG? Any suggestions where the problem might be? Thanks! Thread-998::DEBUG::2014-02-18 14:49:15,399::BindingXMLRPC::965::vds::(wrapper) client [10.10.0.10]::call vmCreate with ({'acpiEnable': 'true', 'emulatedMachine': 'pc-1.0', 'tabletEnable': 'true', 'vmId': '4669e4ad-7b76-4531-a16b-2b85345593a3', 'memGuaranteedSize': 1024, 'spiceSslCipherSuite': 'DEFAULT', 'timeOffset': '0', 'cpuType': 'Penryn', 'custom': {}, 'smp': '1', 'vmType': 'kvm', 'memSize': 1024, 'smpCoresPerSocket': '1', 'vmName': 'testvm', 'nice': '0', 'smartcardEnable': 'false', 'keyboardLayout': 'en-us', 'kvmEnable': 'true', 'pitReinjection': 'false', 'transparentHugePages': 'true', 'devices': [{'device': 'cirrus', 'specParams': {'vram': '32768', 'heads': '1'}, 'type': 'video', 'deviceId': '9b769f44-db37-4e42-a343-408222e1422f'}, {'index': '2', 'iface': 'ide', 'specParams': {'path': ''}, 'readonly': 'true', 'deviceId': 'a61b291c-94de-4fd4-922e-1d51f4d2760d', 'path': '', 'device': 'cdrom', 'shared': 'false', 'type': 'disk'}, {'index': 0, 'iface': 'virtio', 'format': 'raw', 'bootOrder': '1', 'volumeID': '6b35673e-7062-4716-a6c8-d5bf72fe3280', 'imageID': '3738d400-a62e-4ded-b97f-1b4028e5f45b', 'specParams': {}, 'readonly': 'false', 'domainID': '3307f6fa-dd58-43db-ab23-b1fb299006c7', 'optional': 'false', 'deviceId': '3738d400-a62e-4ded-b97f-1b4028e5f45b', 'poolID': '61f15cc0-8bba-482d-8a81-cd636a581b58', 'device': 'disk', 'shared': 'false', 'propagateErrors': 'off', 'type': 'disk'}, {'device': 'memballoon', 'specParams': {'model': 'virtio'}, 'type': 'balloon', 'deviceId': '4e05c1d1-2ac3-4885-8c1d-92ccd1388f0d'}, {'device': 'scsi', 'specParams': {}, 'model': 'virtio-scsi', 'type': 'controller', 'deviceId': 'fa3c223a-0cfc-4adf-90bc-cb6073a4b212'}], 'spiceSecureChannels': 'smain,sinputs,scursor,splayback,srecord,sdisplay,susbredir,ssmartcard', 'display': 'vnc'},) {} flowID [20468793] Thread-998::INFO::2014-02-18 14:49:15,406::API::642::vds::(_getNetworkIp) network None: using 0 Thread-998::INFO::2014-02-18 14:49:15,406::clientIF::394::vds::(createVm) vmContainerLock acquired by vm 4669e4ad-7b76-4531-a16b-2b85345593a3 Thread-999::DEBUG::2014-02-18 14:49:15,409::vm::2091::vm.Vm::(_startUnderlyingVm) vmId=3D`4669e4ad-7b76-4531-a16b-2b85345593a3`::Start Thread-998::DEBUG::2014-02-18 14:49:15,409::clientIF::407::vds::(createVm) Total desktops after creation of 4669e4ad-7b76-4531-a16b-2b85345593a3 is 1 Thread-999::DEBUG::2014-02-18 14:49:15,409::vm::2095::vm.Vm::(_startUnderlyingVm) vmId=3D`4669e4ad-7b76-4531-a16b-2b85345593a3`::_ongoingCreations acquired= Thread-998::DEBUG::2014-02-18 14:49:15,410::BindingXMLRPC::972::vds::(wrapper) return vmCreate with {'status': {'message': 'Done', 'code': 0}, 'vmList': {'status': 'WaitForLaunch', 'acpiEnable': 'true', 'emulatedMachine': 'pc-1.0', 'tabletEnable': 'true', 'pid': '0', 'memGuaranteedSize': 1024, 'timeOffset': '0', 'keyboardLayout': 'en-us', 'displayPort': '-1', 'displaySecurePort': '-1', 'spiceSslCipherSuite': 'DEFAULT', 'cpuType': 'Penryn', 'smp': '1', 'clientIp': '', 'nicModel': 'rtl8139,pv', 'smartcardEnable': 'false', 'kvmEnable': 'true', 'pitReinjection': 'false', 'vmId': '4669e4ad-7b76-4531-a16b-2b85345593a3', 'transparentHugePages': 'true', 'devices': [{'device': 'cirrus', 'specParams': {'vram': '32768', 'heads': '1'}, 'type': 'video', 'deviceId': '9b769f44-db37-4e42-a343-408222e1422f'}, {'index': '2', 'iface': 'ide', 'specParams': {'path': ''}, 'readonly': 'true', 'deviceId': 'a61b291c-94de-4fd4-922e-1d51f4d2760d', 'path': '', 'device': 'cdrom', 'shared': 'false', 'type': 'disk'}, {'index': 0, 'iface': 'virtio', 'format': 'raw', 'bootOrder': '1', 'volumeID': '6b35673e-7062-4716-a6c8-d5bf72fe3280', 'imageID': '3738d400-a62e-4ded-b97f-1b4028e5f45b', 'specParams': {}, 'readonly': 'false', 'domainID': '3307f6fa-dd58-43db-ab23-b1fb299006c7', 'optional': 'false', 'deviceId': '3738d400-a62e-4ded-b97f-1b4028e5f45b', 'poolID': '61f15cc0-8bba-482d-8a81-cd636a581b58', 'device': 'disk', 'shared': 'false', 'propagateErrors': 'off', 'type': 'disk'}, {'device': 'memballoon', 'specParams': {'model': 'virtio'}, 'type': 'balloon', 'deviceId': '4e05c1d1-2ac3-4885-8c1d-92ccd1388f0d'}, {'device': 'scsi', 'specParams': {}, 'model': 'virtio-scsi', 'type': 'controller', 'deviceId': 'fa3c223a-0cfc-4adf-90bc-cb6073a4b212'}], 'custom': {}, 'vmType': 'kvm', 'memSize': 1024, 'displayIp': '0', 'spiceSecureChannels': 'smain,sinputs,scursor,splayback,srecord,sdisplay,susbredir,ssmartcard', 'smpCoresPerSocket': '1', 'vmName': 'testvm', 'display': 'vnc', 'nice': '0'}} Thread-999::INFO::2014-02-18 14:49:15,410::vm::2926::vm.Vm::(_run) vmId=3D`4669e4ad-7b76-4531-a16b-2b85345593a3`::VM wrapper has started Thread-999::DEBUG::2014-02-18 14:49:15,412::task::579::TaskManager.Task::(_updateState) Task=3D`07adf25e-b9fe-44d0-adf4-9159ac0f1f4d`::moving from state init -> state preparing Thread-999::INFO::2014-02-18 14:49:15,413::logUtils::44::dispatcher::(wrapper) Run and protect: getVolumeSize(sdUUID=3D'3307f6fa-dd58-43db-ab23-b1fb299006c7', spUUID=3D'61f15cc0-8bba-482d-8a81-cd636a581b58', imgUUID=3D'3738d400-a62e-4ded-b97f-1b4028e5f45b', volUUID=3D'6b35673e-7062-4716-a6c8-d5bf72fe3280', options=3DNone) Thread-999::DEBUG::2014-02-18 14:49:15,413::lvm::440::OperationMutex::(_reloadlvs) Operation 'lvm reload operation' got the operation mutex Thread-999::DEBUG::2014-02-18 14:49:15,413::lvm::309::Storage.Misc.excCmd::(cmd) '/usr/bin/sudo -n /sbin/lvm lvs --config " devices { preferred_names =3D [\\"^/dev/mapper/\\"] ignore_suspended_devices=3D1 write_cache_state=3D0 disable_after_error_count=3D3 obtain_device_list_from_udev=3D0 filter =3D= [ \'a|/dev/mapper/36090a098103b1821532d057a5a0120d4|/dev/mapper/36090a09810= bb99fefb2da57b94332027|\', \'r|.*|\' ] } global { locking_type=3D1 prioritise_write_locks=3D1 wait_for_locks=3D1 } backup { retain_min =3D 50 retain_days =3D 0 } " --noheadings --units b --nosuffix --separator | -o uuid,name,vg_name,attr,size,seg_start_pe,devices,tags 3307f6fa-dd58-43db-ab23-b1fb299006c7' (cwd None) Thread-999::DEBUG::2014-02-18 14:49:15,466::lvm::309::Storage.Misc.excCmd::(cmd) SUCCESS: <err> =3D '';= <rc> =3D 0 Thread-999::DEBUG::2014-02-18 14:49:15,481::lvm::475::Storage.LVM::(_reloadlvs) lvs reloaded Thread-999::DEBUG::2014-02-18 14:49:15,481::lvm::475::OperationMutex::(_reloadlvs) Operation 'lvm reload operation' released the operation mutex Thread-999::WARNING::2014-02-18 14:49:15,482::lvm::621::Storage.LVM::(getLv) lv: 6b35673e-7062-4716-a6c8-d5bf72fe3280 not found in lvs vg: 3307f6fa-dd58-43db-ab23-b1fb299006c7 response Thread-999::ERROR::2014-02-18 14:49:15,482::task::850::TaskManager.Task::(_setError) Task=3D`07adf25e-b9fe-44d0-adf4-9159ac0f1f4d`::Unexpected error Traceback (most recent call last): File "/usr/share/vdsm/storage/task.py", line 857, in _run return fn(*args, **kargs) File "/usr/share/vdsm/logUtils.py", line 45, in wrapper res =3D f(*args, **kwargs) File "/usr/share/vdsm/storage/hsm.py", line 3059, in getVolumeSize apparentsize =3D str(volClass.getVSize(dom, imgUUID, volUUID, bs=3D1)= ) File "/usr/share/vdsm/storage/blockVolume.py", line 111, in getVSize size =3D int(int(lvm.getLV(sdobj.sdUUID, volUUID).size) / bs) File "/usr/share/vdsm/storage/lvm.py", line 914, in getLV raise se.LogicalVolumeDoesNotExistError("%s/%s" % (vgName, lvName)) LogicalVolumeDoesNotExistError: Logical volume does not exist: ('3307f6fa-dd58-43db-ab23-b1fb299006c7/6b35673e-7062-4716-a6c8-d5bf72fe32= 80',) Thread-999::DEBUG::2014-02-18 14:49:15,485::task::869::TaskManager.Task::(_run) Task=3D`07adf25e-b9fe-44d0-adf4-9159ac0f1f4d`::Task._run: 07adf25e-b9fe-44d0-adf4-9159ac0f1f4d ('3307f6fa-dd58-43db-ab23-b1fb299006c7', '61f15cc0-8bba-482d-8a81-cd636a581b58', '3738d400-a62e-4ded-b97f-1b4028e5f45b', '6b35673e-7062-4716-a6c8-d5bf72fe3280') {} failed - stopping task Thread-999::DEBUG::2014-02-18 14:49:15,485::task::1194::TaskManager.Task::(stop) Task=3D`07adf25e-b9fe-44d0-adf4-9159ac0f1f4d`::stopping in state preparin= g (force False) Thread-999::DEBUG::2014-02-18 14:49:15,486::task::974::TaskManager.Task::(_decref) Task=3D`07adf25e-b9fe-44d0-adf4-9159ac0f1f4d`::ref 1 aborting True Thread-999::INFO::2014-02-18 14:49:15,486::task::1151::TaskManager.Task::(prepare) Task=3D`07adf25e-b9fe-44d0-adf4-9159ac0f1f4d`::aborting: Task is aborted:= 'Logical volume does not exist' - code 610 Thread-999::DEBUG::2014-02-18 14:49:15,486::task::1156::TaskManager.Task::(prepare) Task=3D`07adf25e-b9fe-44d0-adf4-9159ac0f1f4d`::Prepare: aborted: Logical volume does not exist Thread-999::DEBUG::2014-02-18 14:49:15,486::task::974::TaskManager.Task::(_decref) Task=3D`07adf25e-b9fe-44d0-adf4-9159ac0f1f4d`::ref 0 aborting True Thread-999::DEBUG::2014-02-18 14:49:15,486::task::909::TaskManager.Task::(_doAbort) Task=3D`07adf25e-b9fe-44d0-adf4-9159ac0f1f4d`::Task._doAbort: force False= Thread-999::DEBUG::2014-02-18 14:49:15,487::resourceManager::976::ResourceManager.Owner::(cancelAll) Owner.cancelAll requests {} Thread-999::DEBUG::2014-02-18 14:49:15,487::task::579::TaskManager.Task::(_updateState) Task=3D`07adf25e-b9fe-44d0-adf4-9159ac0f1f4d`::moving from state preparin= g -> state aborting Thread-999::DEBUG::2014-02-18 14:49:15,487::task::534::TaskManager.Task::(__state_aborting) Task=3D`07adf25e-b9fe-44d0-adf4-9159ac0f1f4d`::_aborting: recover policy = none Thread-999::DEBUG::2014-02-18 14:49:15,487::task::579::TaskManager.Task::(_updateState) Task=3D`07adf25e-b9fe-44d0-adf4-9159ac0f1f4d`::moving from state aborting= -> state failed Thread-999::DEBUG::2014-02-18 14:49:15,487::resourceManager::939::ResourceManager.Owner::(releaseAll) Owner.releaseAll requests {} resources {} Thread-999::DEBUG::2014-02-18 14:49:15,488::resourceManager::976::ResourceManager.Owner::(cancelAll) Owner.cancelAll requests {} Thread-999::ERROR::2014-02-18 14:49:15,488::dispatcher::67::Storage.Dispatcher.Protect::(run) {'status': {'message': "Logical volume does not exist: ('3307f6fa-dd58-43db-ab23-b1fb299006c7/6b35673e-7062-4716-a6c8-d5bf72fe32= 80',)", 'code': 610}} Thread-999::ERROR::2014-02-18 14:49:15,488::vm::1826::vm.Vm::(_normalizeVdsmImg) vmId=3D`4669e4ad-7b76-4531-a16b-2b85345593a3`::Unable to get volume size for 6b35673e-7062-4716-a6c8-d5bf72fe3280 Traceback (most recent call last): File "/usr/share/vdsm/vm.py", line 1822, in _normalizeVdsmImg drv['truesize'] =3D res['truesize'] KeyError: 'truesize' Thread-999::DEBUG::2014-02-18 14:49:15,489::vm::2112::vm.Vm::(_startUnderlyingVm) vmId=3D`4669e4ad-7b76-4531-a16b-2b85345593a3`::_ongoingCreations released= Thread-999::ERROR::2014-02-18 14:49:15,489::vm::2138::vm.Vm::(_startUnderlyingVm) vmId=3D`4669e4ad-7b76-4531-a16b-2b85345593a3`::The vm start process faile= d Traceback (most recent call last): File "/usr/share/vdsm/vm.py", line 2098, in _startUnderlyingVm self._run() File "/usr/share/vdsm/vm.py", line 2930, in _run devices =3D self.buildConfDevices() File "/usr/share/vdsm/vm.py", line 1935, in buildConfDevices self._normalizeVdsmImg(drv) File "/usr/share/vdsm/vm.py", line 1828, in _normalizeVdsmImg drv['volumeID']) RuntimeError: Volume 6b35673e-7062-4716-a6c8-d5bf72fe3280 is corrupted or missing Best regards, Boyan Tabakov --kNwttSRPs68koQxvdSI5KDEeiPmQG9f68 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlMDYX8ACgkQXOXFG4fgV77amACfdaldO8NlpTry88hrRrdH6eGk umQAoMNVB+zEV4gO+SunFLjuyq8J0pL0 =m0Qx -----END PGP SIGNATURE----- --kNwttSRPs68koQxvdSI5KDEeiPmQG9f68--

2 13

[Users] Ubuntu 13.04 cloud-init issue
by Tejesh M 05 Mar '14

05 Mar '14

Hi, I have deployed guest ubuntu 13.04 & installed cloud-init 0.7.2 on it. But it seems it has a bug setting Network address auto lo eth0 (this line is missing) iface eth0 inet *none* address 172.29.250.13 netmask 255.255.255.0 gateway 172.29.250.1 so it is not brining up the eth0 I tried this through API Kindly help for work around. -- Thanks & Regards Tejesh

2 1

[Users] oVirt 3.4 RC test day
by Doron Fediuck 05 Mar '14

05 Mar '14

Hi everyone, tomorrow we're planning the last test day for 3.4, based on the RC release. All the needed information can be found in the 3.4 test day wiki[1]. See you all tomorrow, Doron [1] http://www.ovirt.org/OVirt_3.4_Test_Day

1 0

[Users] Fwd: [Engine-devel] Tweaking backup/restore of engine
by Sven Kieske 05 Mar '14

05 Mar '14

Hi, forwarding this mail to the users list: Does somebody do engine(DB) backups and restores without the content of the audit_log table? This one can grow quite large if you are using REST like it's meant to be (stateless, so a single login/logout event for every REST-Call). This can quickly accumulate 100.000 events and more. Does anybody got any experience with restoring engine without these logs? I'm talking about disaster recovery, so I want just to backup the necessary data to make the engine run. -------- Original-Nachricht -------- Betreff: [Engine-devel] Tweaking backup/restore of engine Datum: Mon, 3 Mar 2014 16:25:39 +0000 Von: Sven Kieske <S.Kieske(a)mittwald.de> An: engine-devel(a)ovirt.org <engine-devel(a)ovirt.org> Hi, currently all events are stored in the table audit_log which all gets saved when you use the engine-backup shell script. the event log is full of these login lines (engine 3.3.2): 25652 fdfc627c-d875-11e0-90f0-83df133b58cc admin@internal 00000000-0000-0000-0000-000000000000 \N \N \N \N \N 2014-01-20 06:39:17.222+01 USER_VDC_LOGIN 30 0 User admin@internal logged in. f \N \N 00000000-0000-0000-0000-000000000000 \N \N \N \N 00000000-0000-0000-0000-000000000000 \N oVirt -1 30 f \N this makes the log and db grow very large when you use the REST-API to query ovirt for various data. Is this necessary for a working restore? It would be cool if we could tweak the engine-backup tool to just dump necessary tables so you don't have to restore events from the past no one is interested in. How does ovirt react, if I do not restore the content of the audit_log table? If this works (restore without audit_log) I would prefer to have this code upstream in ovirt git so I don't have to maintain my own backupscript. Would it be possible to extend the existing backupscript with a switch to not backup logs? Currently it's just "all" or "just db". I also recall that there shouldn't occur multiple login events any more since ovirt 3.3. but it still seems to be the case. I also do not understand how you would manage a stored authentication via REST as REST is stateless. I would appreciate any feedback or thoughts on this topic. -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen _______________________________________________ Engine-devel mailing list Engine-devel(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel

2 2

[Users] Snapshots
by Maurice James 05 Mar '14

05 Mar '14

--_c556482d-6a8d-4683-8a9b-3603583d82f1_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I attempted to create a snapshot and an alert came up saying that it failed= =2C but when I look at the snapshots tab for that specific VM=2C it says th= at the status is OK. Which should I believe? Ver 3.3.3-2.el6 = --_c556482d-6a8d-4683-8a9b-3603583d82f1_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html> <head> <style></style></head> <body class=3D'hmmessage'><div dir=3D'ltr'>I attempted to create a snapshot= and an alert came up saying that it failed=2C but when I look at the snaps= hots tab for that specific VM=2C it says that the status is OK. Which shoul= d I believe?<br><br>Ver&nbsp=3B <span style=3D"color: rgb(0=2C 0=2C 0)=3B f= ont-family: 'Arial Unicode MS'=2C Arial=2C sans-serif=3B font-size: small= =3B font-style: normal=3B font-variant: normal=3B font-weight: normal=3B le= tter-spacing: normal=3B line-height: normal=3B orphans: auto=3B text-align:= -webkit-center=3B text-indent: 0px=3B text-transform: none=3B white-space:= normal=3B widows: auto=3B word-spacing: 0px=3B -webkit-text-stroke-width: = 0px=3B background-color: rgb(255=2C 255=2C 255)=3B display: inline !importa= nt=3B float: none=3B">3.3.3-2.el6</span> </div></body> </html>= --_c556482d-6a8d-4683-8a9b-3603583d82f1_--

3 2

[Users] Importing Glance images as oVirt templates
by Oved Ourfalli 05 Mar '14

05 Mar '14

Hi all! In oVirt 3.4 we extended the integration with Glance, allowing to import Glance images as oVirt templates. We also added a public Glance repository to be used by oVirt deployments. A reference to this repository is automatically added in 3.4, so you'll see it in the UI by default, under the name "ovirt-image-repository". This repository currently contains only a small set of images, but we hope to extend it soon. The right way to use the Fedora and CentOS images that are there is to import them as templates, create VMs from them, and use cloud-init to configure them. I wrote a blog post on how to use it. Have a look at http://ovedou.blogspot.co.il/2014/03/importing-glance-images-as-ovirt.html Will be happy to hear your comments and answer your questions, Oved

1 0

[Users] View the Console using SPICE from Windows client
by Udaya Kiran P 05 Mar '14

05 Mar '14

---2097401939-1575330872-1393930284=:77562 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi All,=0A=0AI have successfully launched a VM on one of the Host (FC19 Hos= t). Console option for the VM is set to SPICE. However, I am not able to se= e the console after clicking on the console button in oVirt Engine.=0A=0AI = am accessing the oVirt Engine from a Windows 7 machine. I have tried with C= hrome, Firefox and IE.=0A=0APlease suggest.=0A=0AThank you.=0A=0ARegards,= =0AUdaya Kiran ---2097401939-1575330872-1393930284=:77562 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><body><div style=3D"color:#000; background-color:#fff; font-family:ti= mes new roman, new york, times, serif;font-size:10pt"><div>Hi All,</div><di= v><br></div><div style=3D"color: rgb(0, 0, 0); font-size: 13px; font-family= : 'times new roman', 'new york', times, serif; background-color: transparen= t; font-style: normal;">I have successfully launched a VM on one of the Hos= t (FC19 Host). Console option for the VM is set to SPICE. However, I am not= able to see the console after clicking on the console button in oVirt Engi= ne.</div><div style=3D"color: rgb(0, 0, 0); font-size: 13px; font-family: '= times new roman', 'new york', times, serif; background-color: transparent; = font-style: normal;"><br></div><div style=3D"color: rgb(0, 0, 0); font-size= : 13px; font-family: 'times new roman', 'new york', times, serif; backgroun= d-color: transparent; font-style: normal;">I am accessing the oVirt Engine = from a Windows 7 machine. I have tried with Chrome, Firefox and IE.</div><div style=3D"color: rgb(0, 0, 0); font-size: 13px; font-family: = 'times new roman', 'new york', times, serif; background-color: transparent;= font-style: normal;"><br></div><div style=3D"color: rgb(0, 0, 0); font-siz= e: 13px; font-family: 'times new roman', 'new york', times, serif; backgrou= nd-color: transparent; font-style: normal;">Please suggest.</div><div style= =3D"color: rgb(0, 0, 0); font-size: 13px; font-family: 'times new roman', '= new york', times, serif; background-color: transparent; font-style: normal;= "><br></div><div style=3D"color: rgb(0, 0, 0); font-size: 13px; font-family= : 'times new roman', 'new york', times, serif; background-color: transparen= t; font-style: normal;">Thank you.</div><div style=3D"color: rgb(0, 0, 0); = font-size: 13px; font-family: 'times new roman', 'new york', times, serif; = background-color: transparent; font-style: normal;"><br></div><div style=3D= "color: rgb(0, 0, 0); font-size: 13px; font-family: 'times new roman', 'new york', times, serif; background-color: transparent; font-style: normal;">R= egards,</div><div style=3D"color: rgb(0, 0, 0); font-size: 13px; font-famil= y: 'times new roman', 'new york', times, serif; background-color: transpare= nt; font-style: normal;">Udaya Kiran</div></div></body></html> ---2097401939-1575330872-1393930284=:77562--

4 4

[Users] SPICE causes migration failure?
by Ted Miller 05 Mar '14

05 Mar '14

I just got my Data Center running again, and am proceeding with some setup & testing. I created a VM (not doing anything useful) I clicked on the "Console" and had a SPICE console up (viewed in Win7). I had it printing the time on the screen once per second (while date;do sleep 1; done). I tried to migrate the VM to another host and got in the GUI: Migration started (VM: web1, Source: s1, Destination: s3, User: admin@internal). Migration failed due to Error: Fatal error during migration (VM: web1, Source: s1, Destination: s3). As I started the migration I happened to think "I wonder how they handle the SPICE console, since I think that is a link from the host to my machine, letting me see the VM's screen." After the failure, I tried shutting down the SPICE console, and found that the migration succeeded. I again opened SPICE and had a migration fail. Closed SPICE, migration failed. I can understand how migrating SPICE is a problem, but, at least could we give the victim of this condition a meaningful error message? I have seen a lot of questions about failed migrations (mostly due to attached CDs), but I have never seen this discussed. If I had not had that particular thought cross my brain at that particular time, I doubt that SPICE would have been where I went looking for a solution. If this is the first time this issue has been raised, I am willing to file a bug. Ted Miller Elkhart, IN, USA

3 3

Re: [Users] oVirt 3.5 planning
by Juan Pablo Lorier 05 Mar '14

05 Mar '14

Hi, I'm kind of out of date at this time, but I'd like to propose something that was meant for 3.4 and I don't know it it made into it; use any nfs share as either a iso or export so you can just copy into the share and then update in some way the db. Also, make export domain able to be shared among dcs as is iso domain, that is an rfe from long time ago and a useful one. Attaching and dettaching domains is both time consuming and boring. Also using tagged and untagged networks on top of the same nic. Everybody does that except for ovirt. I also like to say that tough I have a huge enthusiasm for ovirt's fast evolution, I think that you may need to slow down with adding new features until most of the rfes that have over a year are done, because other way it's kind of disappointing opening a rfe just to see it sleeping too much time. Don't take this wrong, I've been listened and helped by the team everytime I needed and I'm thankful for that. Regards,

2 2

[Users] [ANN] oVirt 3.4.0 Release Candidate is now available
by Sandro Bonazzola 04 Mar '14

04 Mar '14

The oVirt team is pleased to announce that the 3.4.0 Release Candidate is now available for testing. Release notes and information on the changes for this update are still being worked on and will be available soon on the wiki[1]. Please ensure to follow install instruction from release notes if you're going to test it. The existing repository ovirt-3.4.0-prerelease has been updated for delivering this release candidate and future refreshes until final release. An oVirt Node iso is already available, unchanged from third beta. You're welcome to join us testing this release candidate in next week test day [2] scheduled for 2014-03-06! [1] http://www.ovirt.org/OVirt_3.4.0_release_notes [2] http://www.ovirt.org/OVirt_3.4_Test_Day -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

6 7