January 2014 - Users - oVirt List Archives

[Users] Black VM Install Console
by David Li 22 Jan '14

22 Jan '14

Hi, My first time to install a VM on ovirt has encountered a problem. I tried to open up a console to continue the install process. But all I got is a blank window and a request to save a file which I did. The window remained blank and I couldn't see any activities. I went to the node itself and tried to see if I could use virsh tool to understand what's going on. But I was asked for a username and password to perform any actions. Any idea what I should do at this time? David

9 36

Re: [Users] Problem with python-cpopen dependency on f19 AIO stable
by Martijn Grendelman 22 Jan '14

22 Jan '14

I have the same issue on a CentOS node after updating it to 6.5: > Resolving Dependencies > --> Running transaction check > ---> Package python-cpopen.x86_64 0:1.2.3-4.el6 will be obsoleted > ---> Package vdsm-python-cpopen.x86_64 0:4.13.0-11.el6 will be obsoleting > --> Finished Dependency Resolution > > Dependencies Resolved > > ======================================================================================================================================================== > Package Arch Version Repository Size > ======================================================================================================================================================== > Installing: > vdsm-python-cpopen x86_64 4.13.0-11.el6 ovirt-stable 19 k > replacing python-cpopen.x86_64 1.2.3-4.el6 > > Transaction Summary > ======================================================================================================================================================== > Install 1 Package(s) > > Total download size: 19 k > Is this ok [y/N]: y On a subsequent run of 'yum update', python-cpopen will replace vdsm-python-cpopen, and so on. Cheers, Martijn. Vinzenz Feenstra schreef op 5-12-2013 8:34: > Forwading to vdsm-devel > > On 12/04/2013 08:59 AM, Gianluca Cecchi wrote: >> Hello, >> since yesterday evening I have this sort of dependency problem with updates >> >> yum update >> say >> >> Resolving Dependencies >> --> Running transaction check >> ---> Package python-cpopen.x86_64 0:1.2.3-4.fc19 will be obsoleting >> ---> Package vdsm-python-cpopen.x86_64 0:4.13.0-11.fc19 will be obsoleted >> --> Finished Dependency Resolution >> >> Dependencies Resolved >> >> ============================================================================================================================= >> Package Arch Version >> Repository Size >> ============================================================================================================================= >> Installing: >> python-cpopen x86_64 >> 1.2.3-4.fc19 updates 19 k >> replacing vdsm-python-cpopen.x86_64 4.13.0-11.fc19 >> >> Transaction Summary >> ============================================================================================================================= >> Install 1 Package >> >> If I go ahead and run yum update again I have: >> >> Dependencies Resolved >> >> ============================================================================================================================= >> Package Arch Version >> Repository Size >> ============================================================================================================================= >> Installing: >> vdsm-python-cpopen x86_64 >> 4.13.0-11.fc19 ovirt-stable 20 k >> replacing python-cpopen.x86_64 1.2.3-4.fc19 >> >> Transaction Summary >> ============================================================================================================================= >> Install 1 Package >> >> and so again in a loop.... >> >> Gianluca >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users > >

3 2

[Users] oVirt 3.3.3 Release Candidate is now available
by Sandro Bonazzola 22 Jan '14

22 Jan '14

The oVirt team is pleased to announce that the 3.3.3 Release Candidate is now available in ovirt-updates-testing [1]. Feel free to join us testing it[2] and verifying the bugzilla entries actually under verification [3]. Release notes for this update are available on the wiki [4]. A new oVirt Node build will be available soon as well. [1] http://resources.ovirt.org/releases/updates-testing [2] http://www.ovirt.org/Testing/Ovirt_3.3.3_testing [3] http://red.ht/KEesdK [4] http://www.ovirt.org/OVirt_3.3.3_release_notes -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[Users] Gluster volume snapshots feature UX feedback
by Malini Rao 22 Jan '14

22 Jan '14

Hi Shubendu, I saw your invite for your walkthrough on the feature - Gluster volume snapshots and also followed the feature link on the wiki and reviewed it. From the UX/ UI perspective, it looks good and I had only a couple of comments. The remove snapshot section seems to indicate an ability to delete multiple snapshots at once and I am not sure we support any batch actions as of now elsewhere in the tool. Ctrl+click is not supported on lists today I think. So, I wanted to find out if you were going to introduce this for your feature. If yes, then we should ensure all other grids are enabled with this multi-select capability. If not, we should refrain from introducing something just for this feature for the sake of consistency and across feature product cohesiveness. The other feedback I have is on the snapshot configuration dialog. It will be great if any units can be added to the right of the field because one is a number and the other is a percentage but the field labels are so similar sounding. The field labels with the dashes in between the words also make it look very homegrown and seems like we are exposing some internal labels to our users. Last but not least, since the terminology of 'snapshots' overlaps with VM snapshots, we should just ensure that no similar action does wildly different things although it seems like snapshotting here is much more simple. Hope this is helpful, Thanks Malini

2 1

[Users] Error when trying to create a new ISO storage domain
by Willard Dennis 21 Jan '14

21 Jan '14

--_84d40e63-2fba-48dd-8b16-7e7d22a9a18a_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all=2C I am trying to define a new ISO storage domain. I go to System > Storage=2C= click on the "New Domain" link=2C and fill in the requisite fields. "Domai= n Function / Storage Type" drop is set to "ISO / NFS"=2C and I verified tha= t I have the proper NFS path to the export on the NFS server I want to use.= However=2C when I click the "OK" button=2C I am getting the following popu= p: -----Error while executing action Add Storage Connection: Permission settin= gs on the specified path do not allow access to the storage.Verify permissi= on settings on the specified storage path.----- I have verified that I can manually mount the NFS filesystem on the host de= fined in the "Use Host" drop [as root]=2C and I have looked in /var/log/mes= sages (on the mounting host=2C as well as the NFS server=2C and do not see = any errors... Please not that the NFS export is a pre-existing share on the= NFS server=2C and does contain pre-existing data (ISOs=2C etc.) How can I debug this? = --_84d40e63-2fba-48dd-8b16-7e7d22a9a18a_ 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'>Hi all=2C<div><br></div><div>I a= m trying to define a new ISO storage domain. I go to System &gt=3B Storage= =2C click on the "New Domain" link=2C and fill in the requisite fields. "Do= main Function / Storage Type" drop is set to "ISO / NFS"=2C and I verified = that I have the proper NFS path to the export on the NFS server I want to u= se. However=2C when I click the "OK" button=2C I am getting the following p= opup:<br><div><br></div><div>-----</div><div><div>Error while executing act= ion Add Storage Connection: Permission settings on the specified path do no= t allow access to the storage.</div><div>Verify permission settings on the = specified storage path.</div></div></div><div>-----</div><div><br></div><di= v>I have verified that I can manually mount the NFS filesystem on the host = defined in the "Use Host" drop [as root]=2C and I have looked in /var/log/m= essages (on the mounting host=2C as well as the NFS server=2C and do not se= e any errors... Please not that the NFS export is a pre-existing share on t= he NFS server=2C and does contain pre-existing data (ISOs=2C etc.)</div><di= v><br></div><div>How can I debug this?</div> </div></body> </html>= --_84d40e63-2fba-48dd-8b16-7e7d22a9a18a_--

3 5

Re: [Users] Disk error
by Dafna Ron 21 Jan '14

21 Jan '14

since the error suggests that the disk is locked, and UI is reporting that it's not, it seems that the issue is with some table in the db which still has the disk marked as locked while the disk status is taken from a different table. Allon, any idea what table this can be? On 01/20/2014 11:21 AM, Koen Vanoppen wrote: > Status ok... > > > 2014/1/20 Dafna Ron <dron(a)redhat.com <mailto:dron@redhat.com>> > > and what is the snapshot/disk status in the UI? > > > > > On 01/20/2014 11:08 AM, Koen Vanoppen wrote: > > Error while executing action: > > KV-virt-v2v: > > * Cannot remove Snapshot. Disk KV-virt-v2v_Disk2 is being > moved or > copied. > * Cannot remove Snapshot. Disk LargeTemplate_Disk1 is being > moved or > copied. > > > > 2014/1/20 Koen Vanoppen <vanoppen.koen(a)gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>> > > > Yes, it did. Twice actually. But I already tried that one. > This is > the result: > > Error while executing action: > > KV-virt-v2v: > > * Cannot remove Snapshot. Disk KV-virt-v2v_Disk2 is > being moved > or copied. > * Cannot remove Snapshot. Disk LargeTemplate_Disk1 is being > moved or copied. > > > > > 2014/1/20 Dafna Ron <dron(a)redhat.com > <mailto:dron@redhat.com> <mailto:dron@redhat.com > <mailto:dron@redhat.com>>> > > > you said that you shut down the vm after you tried > migrating? > can you look at the vm in the UI and see if you have a > snapshot created during the migration? > if so, can you try to delete just the snapshot? > > > > > > On 01/20/2014 10:58 AM, Koen Vanoppen wrote: > > [root@soyuz ~]# lvs | grep > ff674bce-aa94-4b46-9f9d-d4182eab1e49 > Couldn't find device with uuid > Y5m0SH-HbWl-8PNL-fGkk-oXNF-WyQk-Snhncm. > ff674bce-aa94-4b46-9f9d-d4182eab1e49 > f8ddd1d1-5266-493b-879b-f79c128751e2 -wi-ao--- 50,00g > > Maybe it's already to another hypervisor or disk > domain? > If there is a *SAVE* way to remove these two disk, > tell > me. The data on it it's not THAT important. > > > > > 2014/1/20 Dafna Ron <dron(a)redhat.com > <mailto:dron@redhat.com> > <mailto:dron@redhat.com <mailto:dron@redhat.com>> > <mailto:dron@redhat.com <mailto:dron@redhat.com> > > <mailto:dron@redhat.com <mailto:dron@redhat.com>>>> > > > the disk ff674bce-aa94-4b46-9f9d-d4182eab1e49 > does not > exist in > the domain - which is the master domain > My guess that it has to do with the failed > migration. > > can you run lvs and grep for > ff674bce-aa94-4b46-9f9d-d4182eab1e49 > lets see where this disk is... > > > > > On 01/20/2014 10:44 AM, Koen Vanoppen wrote: > > [root@soyuz ~]# vdsClient -s 0 > getStorageDomainInfo > f8ddd1d1-5266-493b-879b-f79c128751e2 > uuid = > f8ddd1d1-5266-493b-879b-f79c128751e2 > vguuid = > i6QHH9-1fZR-HLcn-6Xuo-7jU7-66iu-iuzWfQ > lver = 13 > state = OK > version = 3 > role = Master > pool = > ['5849b030-626e-47cb-ad90-3ce782d831b3'] > spm_id = 1 > type = ISCSI > class = Data > master_ver = 1 > name = StoragePoolEva01 > > Thanx for the help! > > > 2014/1/20 Dafna Ron <dron(a)redhat.com > <mailto:dron@redhat.com> > <mailto:dron@redhat.com <mailto:dron@redhat.com>> > <mailto:dron@redhat.com <mailto:dron@redhat.com> > <mailto:dron@redhat.com <mailto:dron@redhat.com>>> > <mailto:dron@redhat.com > <mailto:dron@redhat.com> <mailto:dron@redhat.com > <mailto:dron@redhat.com>> > <mailto:dron@redhat.com <mailto:dron@redhat.com> > <mailto:dron@redhat.com <mailto:dron@redhat.com>>>>> > > > > can you please run: > > vdsClient -s 0 getStorageDomainInfo > f8ddd1d1-5266-493b-879b-f79c128751e2 > > > > On 01/20/2014 10:33 AM, Koen Vanoppen > wrote: > > [root@soyuz ~]# vdsClient -s 0 > getStorageDomainsList > f3fd055b-2764-44ed-9d77-81bd58984842 > 94de241c-bf5c-4630-9af3-7e31b902ae77 > f8ddd1d1-5266-493b-879b-f79c128751e2 > 50cf24a4-d1ef-4105-a9a5-b81d91339175 > 83b1867f-4aea-400e-9ce0-efbd5add4216 > > (soyuz=vdsmhost3) > > > 2014/1/20 Dafna Ron > <dron(a)redhat.com <mailto:dron@redhat.com> > <mailto:dron@redhat.com <mailto:dron@redhat.com>> > <mailto:dron@redhat.com > <mailto:dron@redhat.com> <mailto:dron@redhat.com > <mailto:dron@redhat.com>>> > <mailto:dron@redhat.com <mailto:dron@redhat.com> > <mailto:dron@redhat.com <mailto:dron@redhat.com>> > <mailto:dron@redhat.com > <mailto:dron@redhat.com> <mailto:dron@redhat.com > <mailto:dron@redhat.com>>>> > <mailto:dron@redhat.com > <mailto:dron@redhat.com> > <mailto:dron@redhat.com <mailto:dron@redhat.com>> > <mailto:dron@redhat.com <mailto:dron@redhat.com> > <mailto:dron@redhat.com <mailto:dron@redhat.com>>> > <mailto:dron@redhat.com > <mailto:dron@redhat.com> <mailto:dron@redhat.com > <mailto:dron@redhat.com>> > <mailto:dron@redhat.com <mailto:dron@redhat.com> > <mailto:dron@redhat.com <mailto:dron@redhat.com>>>>>> > > > > let's try to sift through :) > > can you run vdsClient -s 0 > getStorageDomainsList? > > > > > > On 01/20/2014 09:52 AM, Meital > Bourvine wrote: > > It seems that your setup is > completely messed > up. I > see the > following 3 errors all the > time (I > couldn't > actually > find the > live storage migration error, > since there are > too many > errors): > > Thread-118::ERROR::2014-01-20 > 07:59:17,066::sampling::355::vm.Vm::(collect) > vmId=`f8c6190c-b722-4fcd-af17-21572151fcef`::Stats > function > failed: <AdvancedStatsFunction > _highWrite at > 0x27b41b8> > Traceback (most recent > call last): > File > "/usr/share/vdsm/sampling.py", line > 351, in collect > statsFunction() > File > "/usr/share/vdsm/sampling.py", line 226, in > __call__ > retValue = > self._function(*args, **kwargs) > File > "/usr/share/vdsm/vm.py", > line 509, in > _highWrite > if not vmDrive.blockDev or > vmDrive.format > != 'cow': > AttributeError: 'Drive' > object has no > attribute 'format' > > PolicyEngine::DEBUG::2014-01-20 > > 07:59:17,198::libvirtconnection::108::libvirtconnection::(wrapper) > Unknown libvirterror: ecode: 8 > edom: 10 level: > 2 message: > invalid argument: cannot set > memory higher > than max memory > PolicyEngine::ERROR::2014-01-20 > 07:59:17,199::vm::4359::vm.Vm::(reportError) > vmId=`ce626f90-41c4-4417-9e53-bf4066ad062d`::Set new > balloon > target failed > Traceback (most recent > call last): > File > "/usr/share/vdsm/vm.py", > line 4371, in > setBalloonTarget > self._dom.setMemory(target) > File > "/usr/share/vdsm/vm.py", > line 835, in f > ret = attr(*args, > **kwargs) > File > > "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", > line > 76, in wrapper > ret = f(*args, **kwargs) > File > "/usr/lib64/python2.6/site-packages/libvirt.py", line > 1410, in setMemory > if ret == -1: raise > libvirtError > ('virDomainSetMemory() > failed', dom=self) > libvirtError: invalid > argument: > cannot set memory > higher than > max memory > > Thread-51::ERROR::2014-01-20 > 07:59:22,109::sampling::355::vm.Vm::(collect) > vmId=`493128c0-aba9-4b38-bf18-2778b910917f`::Stats > function > failed: <AdvancedStatsFunction > _highWrite at > 0x27b41b8> > Traceback (most recent > call last): > File > "/usr/share/vdsm/sampling.py", line > 351, in collect > statsFunction() > File > "/usr/share/vdsm/sampling.py", line 226, in > __call__ > retValue = > self._function(*args, **kwargs) > File > "/usr/share/vdsm/vm.py", > line 513, in > _highWrite > self._vm._dom.blockInfo(vmDrive.path, 0) > File > "/usr/share/vdsm/vm.py", > line 835, in f > ret = attr(*args, > **kwargs) > File > > "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", > line > 76, in wrapper > ret = f(*args, **kwargs) > File > "/usr/lib64/python2.6/site-packages/libvirt.py", line > 1797, in blockInfo > if ret is None: raise > libvirtError > ('virDomainGetBlockInfo() failed', dom=self) > libvirtError: invalid > argument: > invalid path > > /rhev/data-center/mnt/blockSD/f8ddd1d1-5266-493b-879b-f79c128751e2/images/b8da8541-9a0d-4c18-8aa8-50fc6225f18a/ff674bce-aa94-4b46-9f9d-d4182eab1e49 > not assigned to domain > > > > ------------------------------------------------------------------------ > > > > *From: *"Koen Vanoppen" > <vanoppen.koen(a)gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>>> > > <mailto:vanoppen.koen@gmail.com <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>>>>> > *To: *users(a)ovirt.org > <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>> > <mailto:users@ovirt.org > <mailto:users@ovirt.org> <mailto:users@ovirt.org > <mailto:users@ovirt.org>>> > <mailto:users@ovirt.org <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>> > <mailto:users@ovirt.org > <mailto:users@ovirt.org> <mailto:users@ovirt.org > <mailto:users@ovirt.org>>>> > <mailto:users@ovirt.org > <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>> > <mailto:users@ovirt.org <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>>> > <mailto:users@ovirt.org > <mailto:users@ovirt.org> <mailto:users@ovirt.org > <mailto:users@ovirt.org>> > <mailto:users@ovirt.org <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>>>>>, "Meital > > Bourvine" > <mbourvin(a)redhat.com <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>>> <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>> > > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>> > > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>>>>> > *Sent: *Monday, > January 20, > 2014 9:39:10 AM > *Subject: *Re: [Users] > Disk error > > > vdsm-4.13.0-11.el6.x86_64 > :-) > > > > 2014/1/20 Meital Bourvine > <mbourvin(a)redhat.com > <mailto:mbourvin@redhat.com> <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>> <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>>> > > <mailto:mbourvin@redhat.com <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>> <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>>>> > > <mailto:mbourvin@redhat.com <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>>> <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>>>>>> > > > > First of all, I > opened a > bug about 'Drive' > object has no > attribute 'format': > https://bugzilla.redhat.com/show_bug.cgi?id=1055437 > > Please send me the > output > of `rpm -q > vdsm` so I'll > update the > version in the bug. > > Also, it's better > to send > the logs to > the list > (and > not only > to me), so more people > will be able to > help > you debug it. > > ----- Original > Message ----- > > From: "Dafna Ron" > <dron(a)redhat.com <mailto:dron@redhat.com> > <mailto:dron@redhat.com <mailto:dron@redhat.com>> > <mailto:dron@redhat.com > <mailto:dron@redhat.com> <mailto:dron@redhat.com > <mailto:dron@redhat.com>>> > <mailto:dron@redhat.com > <mailto:dron@redhat.com> > <mailto:dron@redhat.com <mailto:dron@redhat.com>> > <mailto:dron@redhat.com <mailto:dron@redhat.com> > <mailto:dron@redhat.com <mailto:dron@redhat.com>>>> > <mailto:dron@redhat.com > <mailto:dron@redhat.com> > <mailto:dron@redhat.com <mailto:dron@redhat.com>> > <mailto:dron@redhat.com > <mailto:dron@redhat.com> <mailto:dron@redhat.com > <mailto:dron@redhat.com>>> > <mailto:dron@redhat.com <mailto:dron@redhat.com> > <mailto:dron@redhat.com <mailto:dron@redhat.com>> > <mailto:dron@redhat.com > <mailto:dron@redhat.com> <mailto:dron@redhat.com > <mailto:dron@redhat.com>>>>> > <mailto:dron@redhat.com > <mailto:dron@redhat.com> > <mailto:dron@redhat.com <mailto:dron@redhat.com>> > <mailto:dron@redhat.com <mailto:dron@redhat.com> > <mailto:dron@redhat.com <mailto:dron@redhat.com>>> > <mailto:dron@redhat.com > <mailto:dron@redhat.com> <mailto:dron@redhat.com > <mailto:dron@redhat.com>> > <mailto:dron@redhat.com <mailto:dron@redhat.com> > <mailto:dron@redhat.com <mailto:dron@redhat.com>>>> > <mailto:dron@redhat.com > <mailto:dron@redhat.com> > <mailto:dron@redhat.com <mailto:dron@redhat.com>> > <mailto:dron@redhat.com > <mailto:dron@redhat.com> <mailto:dron@redhat.com > <mailto:dron@redhat.com>>> > <mailto:dron@redhat.com <mailto:dron@redhat.com> > <mailto:dron@redhat.com <mailto:dron@redhat.com>> > <mailto:dron@redhat.com > <mailto:dron@redhat.com> <mailto:dron@redhat.com > <mailto:dron@redhat.com>>>>>>> > > > To: "Meital > Bourvine" > <mbourvin(a)redhat.com > <mailto:mbourvin@redhat.com> <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>> <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>>> > > <mailto:mbourvin@redhat.com <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>> <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>>>> > <mailto:mbourvin@redhat.com <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com <mailto:mbourvin@redhat.com>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>>> <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>>>>>> > > Cc: "Koen Vanoppen" > <vanoppen.koen(a)gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>>> > > <mailto:vanoppen.koen@gmail.com <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>>>> > <mailto:vanoppen.koen@gmail.com <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>>> > > <mailto:vanoppen.koen@gmail.com <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>>>>>>, users(a)ovirt.org > <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>> > <mailto:users@ovirt.org > <mailto:users@ovirt.org> <mailto:users@ovirt.org > <mailto:users@ovirt.org>>> > <mailto:users@ovirt.org > <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>> > <mailto:users@ovirt.org <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>>>> > <mailto:users@ovirt.org > <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>> > <mailto:users@ovirt.org > <mailto:users@ovirt.org> <mailto:users@ovirt.org > <mailto:users@ovirt.org>>> > <mailto:users@ovirt.org <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>> > <mailto:users@ovirt.org > <mailto:users@ovirt.org> <mailto:users@ovirt.org > <mailto:users@ovirt.org>>>>> > <mailto:users@ovirt.org <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>> > <mailto:users@ovirt.org > <mailto:users@ovirt.org> <mailto:users@ovirt.org > <mailto:users@ovirt.org>>> > <mailto:users@ovirt.org > <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>> > <mailto:users@ovirt.org <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>>>> > <mailto:users@ovirt.org > <mailto:users@ovirt.org> <mailto:users@ovirt.org > <mailto:users@ovirt.org>> > <mailto:users@ovirt.org <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>>> > <mailto:users@ovirt.org > <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>> > <mailto:users@ovirt.org <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>>>>>> > > > > Sent: Monday, > January > 20, 2014 > 8:49:32 AM > > Subject: Re: [Users] > Disk error > > > > from the errors > you are > getting, > disk status > in db > is locked. > > > > > > On 01/20/2014 > 08:38 AM, > Meital > Bourvine wrote: > > > Hi Koen, > > > > > > What is the > error that > you got > when live > storage > migration > failed? > > > Can you please > attach > vdsm.log and > engine.log > > > > > > *From: > *"Koen Vanoppen" > <vanoppen.koen(a)gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>>>> > <mailto:vanoppen.koen@gmail.com <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>>> > > > <mailto:vanoppen.koen@gmail.com <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>>>>>> > > > *To: > *users(a)ovirt.org <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>> > <mailto:users@ovirt.org > <mailto:users@ovirt.org> <mailto:users@ovirt.org > <mailto:users@ovirt.org>>> > <mailto:users@ovirt.org > <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>> > <mailto:users@ovirt.org <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>>>> > <mailto:users@ovirt.org > <mailto:users@ovirt.org> <mailto:users@ovirt.org > <mailto:users@ovirt.org>> > <mailto:users@ovirt.org <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>>> > <mailto:users@ovirt.org > <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>> > <mailto:users@ovirt.org <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>>>>> > <mailto:users@ovirt.org > <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>> > <mailto:users@ovirt.org > <mailto:users@ovirt.org> <mailto:users@ovirt.org > <mailto:users@ovirt.org>>> > <mailto:users@ovirt.org <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>> > <mailto:users@ovirt.org > <mailto:users@ovirt.org> <mailto:users@ovirt.org > <mailto:users@ovirt.org>>>> > <mailto:users@ovirt.org > <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>> > <mailto:users@ovirt.org <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>>> > <mailto:users@ovirt.org > <mailto:users@ovirt.org> <mailto:users@ovirt.org > <mailto:users@ovirt.org>> > <mailto:users@ovirt.org <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>>>>>> > > > > > *Sent: *Monday, > January 20, 2014 > 5:30:51 AM > > > *Subject: > *[Users] > Disk error > > > > > > Hi all! > > > > > > I got a kind > of a > strange > error in ovirt. > THere was a > problem with > > > a vm that was > complaining > about low disk > space. (in > terms of > > > storage > space of the > storage > center). > So I did > a live > migration of > > > the vm's > disk. This > failed, so > I did a > shutdown of the > vm, to see > > > if that > would help, > but now I > can't > get the VM > back up > again. > > > Neither can > I remove > the disk or > deactivate > the dis. > This is the > > > error: > > > Keep in mind > that > the vm is > down and > he had 2 > disks... > > > > > > While trying to > deactivate the > disk: > > > > > > Error while > executing action: > > > > > > KV-virt-v2v: > > > > > > * Cannot hot > unplug Virtual > Machine > Disk. Disk > KV-virt-v2v_Disk2 > > > is being > moved > or copied. > > > > > > > > > When I try > to simply > remove > the vm: > > > > > > Error while > executing action: > > > > > > KV-virt-v2v: > > > > > > * Cannot > remove > VM. Disk > KV-virt-v2v_Disk2 > is being > moved or copied. > > > * Cannot > remove > VM. Disk > LargeTemplate_Disk1 is > being moved or > > > copied. > > > > > > > > > Kind regards, > > > > > > Koen > > > > > > > _______________________________________________ > > > Users > mailing list > > > > Users(a)ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org > <mailto:Users@ovirt.org> <mailto:Users@ovirt.org > <mailto:Users@ovirt.org>>> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org > <mailto:Users@ovirt.org> <mailto:Users@ovirt.org > <mailto:Users@ovirt.org>>>> > <mailto:Users@ovirt.org > <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> > <mailto:Users@ovirt.org > <mailto:Users@ovirt.org> <mailto:Users@ovirt.org > <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>>>> > <mailto:Users@ovirt.org > <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org > <mailto:Users@ovirt.org> <mailto:Users@ovirt.org > <mailto:Users@ovirt.org>>> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org > <mailto:Users@ovirt.org> <mailto:Users@ovirt.org > <mailto:Users@ovirt.org>>>> > <mailto:Users@ovirt.org > <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> > <mailto:Users@ovirt.org > <mailto:Users@ovirt.org> <mailto:Users@ovirt.org > <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>>>>> > > > > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > > > > > > > > > _______________________________________________ > > > Users mailing list > > > > Users(a)ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org > <mailto:Users@ovirt.org> <mailto:Users@ovirt.org > <mailto:Users@ovirt.org>>> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org > <mailto:Users@ovirt.org> <mailto:Users@ovirt.org > <mailto:Users@ovirt.org>>>> > <mailto:Users@ovirt.org > <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> > <mailto:Users@ovirt.org > <mailto:Users@ovirt.org> <mailto:Users@ovirt.org > <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>>>> > <mailto:Users@ovirt.org > <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org > <mailto:Users@ovirt.org> <mailto:Users@ovirt.org > <mailto:Users@ovirt.org>>> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org > <mailto:Users@ovirt.org> <mailto:Users@ovirt.org > <mailto:Users@ovirt.org>>>> > <mailto:Users@ovirt.org > <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> > <mailto:Users@ovirt.org > <mailto:Users@ovirt.org> <mailto:Users@ovirt.org > <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>>>>> > > > > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > -- > > Dafna Ron > > > > > > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> > <mailto:Users@ovirt.org > <mailto:Users@ovirt.org> <mailto:Users@ovirt.org > <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>>> > <mailto:Users@ovirt.org > <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> > <mailto:Users@ovirt.org > <mailto:Users@ovirt.org> <mailto:Users@ovirt.org > <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>>>> > http://lists.ovirt.org/mailman/listinfo/users > > > > -- Dafna Ron > > > us > > -- Dafna Ron > > > > > -- Dafna Ron > > > > > -- Dafna Ron > > > > > > -- > Dafna Ron > > -- Dafna Ron

3 8

[Users] libvirt migration port configuration and virPortAllocator
by Gianluca Cecchi 21 Jan '14

21 Jan '14

Hello, following the bugzilla here: https://bugzilla.redhat.com/show_bug.cgi?id=1019053 we have " This is now fixed by v1.1.3-188-g0196845 and v1.1.3-189-ge3ef20d " Does this mean that f19 that has libvirt-1.0.5.8-1.fc19.x86_64 is out? Any time soon to update it? I see at http://libvirt.org/sources/ files such as libvirt-1.1.4-1.fc19.x86_64.rpm since beginning of November... any particular reason for no packages neither in updates-testing repo? Also, Fedora 20 has libvirt-1.1.3.2-1.fc20.x86_64.rpm Did it receive the patch update? I see nothing particular in its changelog... Thanks in advance, Gianluca

5 6

[Users] Change bootdisk from IDE to virtio
by Markus Stockhausen 21 Jan '14

21 Jan '14

------=_NextPartTM-000-e0e80aca-5ad6-4c75-8275-3036cde595fb Content-Type: multipart/alternative; boundary="_000_12EF8D94C6F8734FB2FF37B9FBEDD173585D887BEXCHANGEcollogi_" --_000_12EF8D94C6F8734FB2FF37B9FBEDD173585D887BEXCHANGEcollogi_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, i have a SLES 11 VM that was migrated into ovirt. I successfully changed all except the boot/root disk to virtio. Nevertheless I'm unable to do the same for the boot disk itself What I've done so far: - replace all /dev/sdx entries in fstab to /disk/by-uuid - replace all /dev/sdx entries in grub/menu.list to /disk/by-uuid - reboot the VM with these settings and IDE boot still active After switching the disk over to virtio the boot process hangs at SeaBIOS... Machine UUID ... iPXE ... Booting from Hard Disk ... Any ideas? Markus --_000_12EF8D94C6F8734FB2FF37B9FBEDD173585D887BEXCHANGEcollogi_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html dir=3D"ltr"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-= 1"> <style id=3D"owaParaStyle" type=3D"text/css">P {margin-top:0;margin-bottom:= 0;}</style> </head> <body ocsi=3D"0" fpstyle=3D"1"> <div style=3D"direction: ltr;font-family: Tahoma;color: #000000;font-size: = 10pt;">Hello,<br> <br> i have a SLES 11 VM that was migrated into ovirt. I successfully<br> changed all except the boot/root disk to virtio. Nevertheless I'm <br> unable to do the same for the boot disk itself<br> <br> What I've done so far:<br> <br> - replace all /dev/sdx entries in fstab to /disk/by-uuid<br> - replace all /dev/sdx entries in grub/menu.list to /disk/by-uuid<br> - reboot the VM with these settings and IDE boot still active<br> <br> After switching the disk over to virtio the boot process hangs at<br> <br> SeaBIOS...<br> Machine UUID ...<br> iPXE ...<br> Booting from Hard Disk ...<br> <br> Any ideas?<br> <br> Markus<br> </div> </body> </html> --_000_12EF8D94C6F8734FB2FF37B9FBEDD173585D887BEXCHANGEcollogi_-- ------=_NextPartTM-000-e0e80aca-5ad6-4c75-8275-3036cde595fb Content-Type: text/plain; name="InterScan_Disclaimer.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="InterScan_Disclaimer.txt" **************************************************************************** Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. Über das Internet versandte E-Mails können unter fremden Namen erstellt oder manipuliert werden. Deshalb ist diese als E-Mail verschickte Nachricht keine rechtsverbindliche Willenserklärung. Collogia Unternehmensberatung AG Ubierring 11 D-50678 Köln Vorstand: Kadir Akin Dr. Michael Höhnerbach Vorsitzender des Aufsichtsrates: Hans Kristian Langva Registergericht: Amtsgericht Köln Registernummer: HRB 52 497 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. e-mails sent over the internet may have been written under a wrong name or been manipulated. That is why this message sent as an e-mail is not a legally binding declaration of intention. Collogia Unternehmensberatung AG Ubierring 11 D-50678 Köln executive board: Kadir Akin Dr. Michael Höhnerbach President of the supervisory board: Hans Kristian Langva Registry office: district court Cologne Register number: HRB 52 497 **************************************************************************** ------=_NextPartTM-000-e0e80aca-5ad6-4c75-8275-3036cde595fb--

3 4

[Users] novnc console button/ticket via REST-API?
by Sven Kieske 21 Jan '14

21 Jan '14

Hi, we are quite impressed of the novnc console option to get access to the vms. however, we want to implement our own userportal. So is it possible to create the novnc ticket / open a vnc session with the vm event via REST-API? If yes how? If not, how could this be achieved? -- 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

3 8

[Users] Making v2v easier?
by Itamar Heim 21 Jan '14

21 Jan '14

I see a lot of threads about v2v pains (mostly from ESX?) I'm interested to see if we can make this simpler/easier. if you have experience with this, please describe the steps you are using (also the source platform), and how you would like to see this make simpler (I'm assuming that would start from somewhere in the webadmin probably). Thanks, Itamar

9 16