Users
Threads by month
- ----- 2025 -----
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- 10 participants
- 19138 discussions
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
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
------=_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
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
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
------_=_NextPart_001_01CF0D11.E17769E3
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello,
I am evaluating oVirt as a replacement/alternative to VMware deployments =
we typically do. I have installed and all-in-one setup on a test box =
(which itself used to be an ESXi server), but it only has one NIC. I =
trying to duplicate our typical configuration we do in VMware, which is =
this:
1.) we create several "port groups" on the vSwitch, each assigned a =
VLAN ID, such as:
- VLAN001 (VLAN ID: 1)
- VLAN002 (VLAN ID: 2)
- VLAN009 (VLAN ID: 9)
- VLAN010 (VLAN ID: 10)
- VLAN200 (VLAN ID: 200)
- TRUNK (VLAN ID: 4095 - in VMware-world, VLAN ID "4095" is "all =
VLANS" and basically just passes the VLANs through to whatever is =
attached to the port group for the VM to handle)
2.) We assign VMs to port groups appropriate for the VLAN they are =
part of.
3.) The only VM that has a NIC assigned to the "TRUNK" port group is =
the firewall (which is Linux), and we create VLAN interfaces on it =
(i.e., "eth1.1", "eth1.2", "eth1.10", "eth1.200"). The firewall VM acts =
as the router between the various VLANs.
To replicate the above in oVirt, I created logical networks for each =
VLAN, and assigned the appropriate VLAN ID. It seems oVirt/KVM does not =
have an equivalent for VMware's VLAN ID of "4095", so after some =
searching around, so for the "TRUNK" network, I left it with no VLAN =
assigned. Because i cannot add VLAN and non-VLAN networks to the same =
physical NIC, after some searching around, it looks like I may have to =
utilise two NICS: one for the VLAN networks and one for the "TRUNK" =
network.
Because, at this point, I am not yet concerned with making the test VMs =
I will be setting up be accessible from outside the virtual lab =
environment (i.e., everything will communicate within my oVirt =
server/network for now), I am trying to make use of "dummy" interfaces, =
but I am not sure the best way to make use of this. I am able to create =
the dummy* interfaces and have them show up in oVirt, but I am not sure =
of how they should be setup. Here is what I am *thinking* should be =
done, but want to make sure it is correct before getting too deep:
- I will use the physical NIC for management, therefore the =
"ovirtmgmt" bridge with eth0 assigned to it will remain as-is
- Create two dummy interfaces: "dummy0" and "dummy1"
- Create a new bridge, "ovirtvm" and assign "dummy0" and "dummy1" to =
it
- Attach the VLAN-enabled networks to "dummy0"
- Attach the "TRUNK" network to "dummy1"
Would the above be the way to go about this? The one thing I am not =
sure of is whether or not having no VLAN assigned (on the "TRUNK" =
network) accomplishes the same this as the "VLAN ID 4095" in VMware: =
will oVirt/KVM just pass the traffic through for the VM attached to it =
to deal with?
Thanks for reading this far, and I appreciate any help you might be able =
to lend in the above.
-Alan
------_=_NextPart_001_01CF0D11.E17769E3
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7654.12">
<TITLE>Networking questions (LONG)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=3D2>Hello,<BR>
<BR>
I am evaluating oVirt as a replacement/alternative to VMware deployments =
we typically do. I have installed and all-in-one setup on a test =
box (which itself used to be an ESXi server), but it only has one =
NIC. I trying to duplicate our typical configuration we do in =
VMware, which is this:<BR>
<BR>
1.) we create several "port groups" on the vSwitch, =
each assigned a VLAN ID, such as:<BR>
<BR>
- VLAN001 (VLAN ID: 1)<BR>
- VLAN002 (VLAN ID: 2)<BR>
- VLAN009 (VLAN ID: 9)<BR>
- VLAN010 (VLAN ID: 10)<BR>
- VLAN200 (VLAN ID: 200)<BR>
- TRUNK (VLAN ID: 4095 - in VMware-world, =
VLAN ID "4095" is "all VLANS" and basically just =
passes the VLANs through to whatever is attached to the port group for =
the VM to handle)<BR>
<BR>
2.) We assign VMs to port groups appropriate for the VLAN they =
are part of.<BR>
3.) The only VM that has a NIC assigned to the "TRUNK" =
port group is the firewall (which is Linux), and we create VLAN =
interfaces on it (i.e., "eth1.1", "eth1.2", =
"eth1.10", "eth1.200"). The firewall VM acts =
as the router between the various VLANs.<BR>
<BR>
To replicate the above in oVirt, I created logical networks for each =
VLAN, and assigned the appropriate VLAN ID. It seems oVirt/KVM =
does not have an equivalent for VMware's VLAN ID of "4095", so =
after some searching around, so for the "TRUNK" network, I =
left it with no VLAN assigned. Because i cannot add VLAN and =
non-VLAN networks to the same physical NIC, after some searching around, =
it looks like I may have to utilise two NICS: one for the VLAN networks =
and one for the "TRUNK" network.<BR>
<BR>
Because, at this point, I am not yet concerned with making the test VMs =
I will be setting up be accessible from outside the virtual lab =
environment (i.e., everything will communicate within my oVirt =
server/network for now), I am trying to make use of "dummy" =
interfaces, but I am not sure the best way to make use of this. I =
am able to create the dummy* interfaces and have them show up in oVirt, =
but I am not sure of how they should be setup. Here is what I am =
*thinking* should be done, but want to make sure it is correct before =
getting too deep:<BR>
<BR>
- I will use the physical NIC for management, therefore the =
"ovirtmgmt" bridge with eth0 assigned to it will remain =
as-is<BR>
- Create two dummy interfaces: "dummy0" and =
"dummy1"<BR>
- Create a new bridge, "ovirtvm" and assign =
"dummy0" and "dummy1" to it<BR>
- Attach the VLAN-enabled networks to "dummy0"<BR>
- Attach the "TRUNK" network to "dummy1"<BR>
<BR>
Would the above be the way to go about this? The one thing I am =
not sure of is whether or not having no VLAN assigned (on the =
"TRUNK" network) accomplishes the same this as the "VLAN =
ID 4095" in VMware: will oVirt/KVM just pass the traffic through =
for the VM attached to it to deal with?<BR>
<BR>
Thanks for reading this far, and I appreciate any help you might be able =
to lend in the above.<BR>
<BR>
-Alan<BR>
</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01CF0D11.E17769E3--
7
14
Hello,
Do you guys know of a script that I could use to backup VMs automatically
but creating the lower downtime? I modified a bit the 'virt-backup.pl'
script by Daniel Berteaud <daniel(a)firewall-services.com> so it
authenticates against Ovirt as shown below:
Sys::Virt::CRED_AUTHNAME,
Sys::Virt::CRED_PASSPHRASE,
However, wondering if I could get advice from you as to which tool or
script will do this job better. Thanks
--Rizzo
1
0
------=_Part_4459753_822472212.1390304404609
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
The following is a new meeting request:
Subject: Feature Review: Gluster Volume Snapshot
Organizer: "Shubhendu Tripathi" <shtripat(a)redhat.com>
Location: "Vijayanagara - BLR" <vijayanagara-blr(a)redhat.com>
Resources: "Vijayanagara - BLR" <vijayanagara-blr(a)redhat.com>
Time: Monday, January 27, 2014, 6:30:00 PM - 7:30:00 PM GMT +05:30 Chennai, Kolkata, Mumbai, New Delhi
Invitees: arch(a)ovirt.org; users(a)ovirt.org
*~*~*~*~*~*~*~*~*~*
Hi,
In this talk I intend to present a short overview of the feature Gluster Volume Snapshots in oVirt.
BlueJeans session details:
https://bluejeans.com/298626980/6439/browser
WIKI Page:
http://www.ovirt.org/Features/GlusterVolumeSnapshots
Call bridge details:
Would be shared separately.
Thanks and Regards,
Shubhendu Tripathi
------=_Part_4459753_822472212.1390304404609
Content-Type: text/calendar; charset=utf-8; method=REQUEST; name=meeting.ics
Content-Transfer-Encoding: 7bit
BEGIN:VCALENDAR
PRODID:Zimbra-Calendar-Provider
VERSION:2.0
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:Asia/Kolkata
BEGIN:STANDARD
DTSTART:16010101T000000
TZOFFSETTO:+0530
TZOFFSETFROM:+0530
TZNAME:IST
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:3440764a-ef38-4491-a023-f369dcfe9a18
SUMMARY:Feature Review: Gluster Volume Snapshot
LOCATION:"Vijayanagara - BLR" <vijayanagara-blr(a)redhat.com>
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:arch@ov
irt.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:users@o
virt.org
ATTENDEE;CN=Vijayanagara - BLR;CUTYPE=RESOURCE;ROLE=NON-PARTICIPANT;PARTSTAT
=NEEDS-ACTION;RSVP=TRUE:mailto:vijayanagara-blr@redhat.com
ORGANIZER;CN=Shubhendu Tripathi:mailto:shtripat@redhat.com
DTSTART;TZID="Asia/Kolkata":20140127T183000
DTEND;TZID="Asia/Kolkata":20140127T193000
STATUS:CONFIRMED
CLASS:PUBLIC
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
TRANSP:OPAQUE
LAST-MODIFIED:20140121T114004Z
DTSTAMP:20140121T114004Z
SEQUENCE:0
DESCRIPTION:The following is a new meeting request:\n\nSubject: Feature Revi
ew: Gluster Volume Snapshot \nOrganizer: "Shubhendu Tripathi" <shtripat@redh
at.com> \n\nLocation: "Vijayanagara - BLR" <vijayanagara-blr(a)redhat.com> \nR
esources: "Vijayanagara - BLR" <vijayanagara-blr(a)redhat.com> \nTime: Monday\
, January 27\, 2014\, 6:30:00 PM - 7:30:00 PM GMT +05:30 Chennai\, Kolkata\,
Mumbai\, New Delhi\n \nInvitees: arch(a)ovirt.org\; users(a)ovirt.org \n\n\n*~*
~*~*~*~*~*~*~*~*\n\nHi\,\n\nIn this talk I intend to present a short overvie
w of the feature Gluster Volume Snapshots in oVirt.\n\nBlueJeans session det
ails:\nhttps://bluejeans.com/298626980/6439/browser\n\nWIKI Page:\nhttp://ww
w.ovirt.org/Features/GlusterVolumeSnapshots\n\nCall bridge details:\nWould b
e shared separately.\n\nThanks and Regards\,\nShubhendu Tripathi
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER;RELATED=START:-PT5M
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR
------=_Part_4459753_822472212.1390304404609--
1
0
[Users] Feature Review: Gluster Volume Snapshots
by Shubhendu Tripathi via Blue Jeans Network 21 Jan '14
by Shubhendu Tripathi via Blue Jeans Network 21 Jan '14
21 Jan '14
------=_Part_219_383193853.1390304209777
Content-Type: multipart/related;
boundary="----=_Part_220_35630018.1390304209777"
------=_Part_220_35630018.1390304209777
Content-Type: multipart/alternative;
boundary="----=_Part_221_1833258660.1390304209778"
------=_Part_221_1833258660.1390304209778
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Shubhendu Ram Tripathi (shtripat(a)redhat.com) has invited you to a video meeting.
Meeting Title:
Feature Review: Gluster Volume Snapshots
Meeting Time:
Monday January 27, 2014 6:30 p.m. IST / 1 hr
************************************************
To join or start the meeting, go to:
https://bluejeans.com/298626980/6439?g=ovzwk4ttibxxm2lsoqxg64th
No Computer or Internet Connection?
Join via phone:
1) Dial-in phone number: +1 408 740 7256 or +1 888 240 2560 (US or Canada only) (http://bluejeans.com/numbers)
2) Enter Conference ID: 298626980
3) Enter Participant PIN: 6439
Join via room system:
1) Dial-in IP: 199.48.152.152 or bjn.vc
2) Enter Meeting ID: 298626980
3) Enter Participant passcode: 6439
************************************************
First time joining a Blue Jeans Video Meeting?
http://bluejeans.com/faq#connecting
************************************************
Want to test your video connection?
http://bluejeans.com/111
************************************************
Blue Jeans Network 2012
------=_Part_221_1833258660.1390304209778
Content-Type: text/html;charset="utf-8"
Content-Transfer-Encoding: 7bit
<table width="100%">
<tr bgcolor="#d8d8d8">
<td align="center">
<table width="600px" bgcolor="#FFFFFF" style="margin-top:20px;padding:0px 50px 10px 50px;margin-bottom:20px;text-align:left;">
<tr>
<td style="padding-right:10px;padding-bottom:20px;">
<a href="http://bluejeans.com">
<img src="https://static.bluejeans.com/z1/static/images/bjn/BlueJeans_Logo.png" alt="Blue Jeans" style="border:none;">
</a>
</td>
</tr>
<tr>
<td style="font-size: 20px;color: #333333; padding-bottom:30px;">
<a href="mailto:shtripat@redhat.com">Shubhendu Ram Tripathi</a> has invited you to a video meeting.
</td>
</tr>
<tr>
<td style="padding-top:10px; font-size: 16px;">
<span style="color:#666666; padding-right: 20px;">Meeting Title: </span>Feature Review: Gluster Volume Snapshots
</td>
</tr>
<tr>
<td style="padding-top:10px; padding-bottom: 10px; font-size: 16px;">
<span style="color:#666666; padding-right: 15px;">Meeting Time:</span>
Monday January 27, 2014 • 6:30 p.m. IST / 1 hr
</td>
</tr>
<tr>
<td style="padding-top:40px; padding-bottom: 40px;">
<table cellpadding="0" cellspacing="0" border="0">
<tbody>
<tr>
<td height="30" bgcolor="#FEFEFE"></td>
<td width="200" height="50" bgcolor="#2588AD" align="center" valign="middle">
<a href="https://bluejeans.com/298626980/6439?g=ovzwk4ttibxxm2lsoqxg64th" style="font-family:Helvetica, sans-serif;font-size:17px;color:#FFFFFF;font-weight:bold;text-decoration:none" target="_blank">
Join Meeting
</a>
</td>
<td height="30" bgcolor="#FEFEFE"></td>
</tr>
</tbody>
</table>
</td>
</tr>
<tr>
<td>
<hr size="1" noshade="noshade" style="line-height:1px;border-color:#cccccc;">
</td>
</tr>
<tr>
<td style="padding-top:10px; padding-bottom:10px;">
<b><span style="color:#333333">No Computer or Internet Connection?</span></b><br>
<br>
Join via phone:<br>
1)
<a href="tel:+1 408 740 7256,#298626980#,6439#">Direct-dial with my iPhone</a> or <br>
Dial-in phone number: +1 408 740 7256 or +1 888 240 2560 (US or Canada only) (<a href="http://bluejeans.com/numbers">all</a>)<br>
2) Enter Conference ID: 298626980<br>
3) Enter Participant PIN: 6439 <br>
<br>
Join via room system:<br>
1) Dial-in IP: 199.48.152.152 or bjn.vc<br>
2) Enter Meeting ID: 298626980<br>
3) Enter Participant passcode: 6439 <br>
<br>
</td>
</tr>
<tr>
<td>
<hr size="1" noshade="noshade" style="line-height:1px;border-color:#cccccc;">
</td>
</tr>
<tr>
<td style="padding-top:10px;padding-bottom: 10px;">
<span style="color:#666666">First time joining a Blue Jeans Video Meeting?</span><br>
<a href="http://bluejeans.com/faq#connecting">http://bluejeans.com/faq#connecting</a>
</td>
</tr>
<tr>
<td>
<hr size="1" noshade="noshade" style="line-height:1px;border-color:#cccccc;">
</td>
</tr>
<tr>
<td style="padding-top:10px;padding-bottom: 10px;">
<span style="color:#666666">Want to test your video connection?</span><br>
<a href="http://bluejeans.com/111">http://bluejeans.com/111</a>
</td>
</tr>
<tr>
<td style="line-height:1px;color:#CCCCCC;">
<hr size="1" noshade="noshade" style="line-height:1px;color:#CCCCCC;border-color:#CCCCCC;">
</td>
</tr>
<tr>
<td style="font-size:11px;text-align:left">
<p align="center">©Blue Jeans Network 2013</p>
</td>
</tr>
</table>
</td>
</tr>
</table>
------=_Part_221_1833258660.1390304209778
Content-Type: text/calendar; method=REQUEST; charset="utf-8"
Content-Transfer-Encoding: 7bit
BEGIN:VCALENDAR
VERSION:2.0
METHOD:REQUEST
PRODID:-//PYVOBJECT//NONSGML Version 1//EN
BEGIN:VTIMEZONE
TZID:Asia/Kolkata
TZURL:http://tzurl.org/zoneinfo-outlook/Asia/Kolkata
X-LIC-LOCATION:Asia/Kolkata
BEGIN:STANDARD
TZOFFSETFROM:+0530
TZOFFSETTO:+0530
TZNAME:IST
DTSTART:19700101T000000
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:0H44B_sN0PzTAnM2@H6D3JmW4G7v71tX
DTSTART;TZID=Asia/Kolkata:20140127T183000
DTEND;TZID=Asia/Kolkata:20140127T193000
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP
=TRUE:mailto:users@ovirt.org
CREATED:20140121T113648Z
DESCRIPTION:\nShubhendu Ram Tripathi (shtripat(a)redhat.com) has invited you
to a video meeting.\n\n\n\n**********************************************
**\n\nTo join or start the meeting\, go to:\nhttps://bluejeans.com/2986269
80/6439?g=ovzwk4ttibxxm2lsoqxg64th\n\n\nNo Computer or Internet Connection
?\n\nJoin via phone:\n1) Dial-in phone number: +1 408 740 7256 or +1 888 2
40 2560 (US or Canada only) (http://bluejeans.com/numbers)\n2) Enter Conf
erence ID: 298626980\n3) Enter Participant PIN: 6439\n\nJoin via room syst
em:\n1) Dial-in IP: 199.48.152.152 or bjn.vc\n2) Enter Meeting ID: 2986269
80\n3) Enter Participant passcode: 6439\n\n*******************************
*****************\n\nFirst time joining a Blue Jeans Video Meeting?\nhttp:
//bluejeans.com/faq#connecting\n\n****************************************
********\n\nWant to test your video connection?\nhttp://bluejeans.com/111\
n\n************************************************\n\nBlue Jeans Network
2012\n
DTSTAMP:20140121T113649Z
LAST-MODIFIED:20140121T113648Z
LOCATION:
ORGANIZER:mailto:shtripat@redhat.com
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Feature Review: Gluster Volume Snapshots
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR
------=_Part_221_1833258660.1390304209778--
------=_Part_220_35630018.1390304209777--
------=_Part_219_383193853.1390304209777
Content-Type: application/ics; name=invite.ics
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename=invite.ics
BEGIN:VCALENDAR
VERSION:2.0
METHOD:REQUEST
PRODID:-//PYVOBJECT//NONSGML Version 1//EN
BEGIN:VTIMEZONE
TZID:Asia/Kolkata
TZURL:http://tzurl.org/zoneinfo-outlook/Asia/Kolkata
X-LIC-LOCATION:Asia/Kolkata
BEGIN:STANDARD
TZOFFSETFROM:+0530
TZOFFSETTO:+0530
TZNAME:IST
DTSTART:19700101T000000
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:0H44B_sN0PzTAnM2@H6D3JmW4G7v71tX
DTSTART;TZID=Asia/Kolkata:20140127T183000
DTEND;TZID=Asia/Kolkata:20140127T193000
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP
=TRUE:mailto:users@ovirt.org
CREATED:20140121T113648Z
DESCRIPTION:\nShubhendu Ram Tripathi (shtripat(a)redhat.com) has invited you
to a video meeting.\n\n\n\n**********************************************
**\n\nTo join or start the meeting\, go to:\nhttps://bluejeans.com/2986269
80/6439?g=ovzwk4ttibxxm2lsoqxg64th\n\n\nNo Computer or Internet Connection
?\n\nJoin via phone:\n1) Dial-in phone number: +1 408 740 7256 or +1 888 2
40 2560 (US or Canada only) (http://bluejeans.com/numbers)\n2) Enter Conf
erence ID: 298626980\n3) Enter Participant PIN: 6439\n\nJoin via room syst
em:\n1) Dial-in IP: 199.48.152.152 or bjn.vc\n2) Enter Meeting ID: 2986269
80\n3) Enter Participant passcode: 6439\n\n*******************************
*****************\n\nFirst time joining a Blue Jeans Video Meeting?\nhttp:
//bluejeans.com/faq#connecting\n\n****************************************
********\n\nWant to test your video connection?\nhttp://bluejeans.com/111\
n\n************************************************\n\nBlue Jeans Network
2012\n
DTSTAMP:20140121T113649Z
LAST-MODIFIED:20140121T113648Z
LOCATION:
ORGANIZER:mailto:shtripat@redhat.com
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Feature Review: Gluster Volume Snapshots
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR
------=_Part_219_383193853.1390304209777--
1
0
This is a cryptographically signed message in MIME format.
--------------ms040006030805040301050402
Content-Type: multipart/mixed;
boundary="------------020709050106010805030505"
This is a multi-part message in MIME format.
--------------020709050106010805030505
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: quoted-printable
Hello,
I'm just curious and I didn't try it already. I'm using FC storage (Dell =
MD3620f) with some logical disks on it. I should be able online increase =
virtual disk capacity using storage management (I have some free=20
capacity on disk group).
Is there any way to on-line extend volume group used for vm's images=20
storage and don't break anything?
I just found this hint by Eduardo from list
1. Shutdown all VMs
2. Manually connect iscsi on the SPM host
3. Run pvresize on the LUN
4. Put the domain in maintenance
5. Activate the domains
Is it possible to do this on-line without shutting down all vms? If not, =
it could be really nice feature for oncoming releases.
Thanks in advance
Jiri
--------------020709050106010805030505
Content-Type: text/x-vcard; charset=utf-8;
name="jiri_slezka.vcf"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="jiri_slezka.vcf"
begin:vcard
fn;quoted-printable:Ing. Ji=3DC5=3D99=3DC3=3DAD Sl=3DC3=3DA9=3DC5=3DBEka
n;quoted-printable;quoted-printable:Sl=3DC3=3DA9=3DC5=3DBEka;Ji=3DC5=3D99=
=3DC3=3DAD
org;quoted-printable;quoted-printable:Slezsk=3DC3=3DA1 univerzita v Opav=3D=
C4=3D9B;Centrum informa=3DC4=3D8Dn=3DC3=3DADch technologi=3DC3=3DAD
adr;quoted-printable;quoted-printable:Na Rybn=3DC3=3DAD=3DC4=3D8Dku 1;;CI=
T, Slezsk=3DC3=3DA1 univerzita v Opav=3DC4=3D9B;Opava;;74601;Czech Republ=
ic
email;internet:jiri.slezka@slu.cz
title;quoted-printable:Spr=3DC3=3DA1vce s=3DC3=3DADt=3DC4=3D9B a aplikac=3D=
C3=3DAD
tel;work:+420 553 684 696
x-mozilla-html:FALSE
url:http://www.slu.cz
version:2.1
end:vcard
--------------020709050106010805030505--
--------------ms040006030805040301050402
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: Elektronicky podpis S/MIME
MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJZjCC
BJswggODoAMCAQICEFVyFjoambpWOjuqgDsl/VswDQYJKoZIhvcNAQEFBQAwOzELMAkGA1UE
BhMCTkwxDzANBgNVBAoTBlRFUkVOQTEbMBkGA1UEAxMSVEVSRU5BIFBlcnNvbmFsIENBMB4X
DTEyMTEyNzAwMDAwMFoXDTE0MTEyNzIzNTk1OVowZTELMAkGA1UEBhMCQ1oxJTAjBgNVBAoM
HFNsZXpza8OhIHVuaXZlcnppdGEgdiBPcGF2xJsxGDAWBgNVBAMMD0ppxZnDrSBTbMOpxb5r
YTEVMBMGCSqGSIb3DQEJAhYGc2xlemthMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAtbqepY7nJ2kyAZxv/HS4tUEyXDh2ovWpQEI3triEqomfGE0aOqkHB0j/z2Oq0IeC+U91
TIpAoTPP+7fYR5rpcTfWPOW745RW4rJ6lj57Y+ZSqY0ID9vHe2nBxSnY2mWGIg///MWSbWrX
Pbsxoemn6rb5ZP/1W9oPbkdTI3omEsdX2JlLbjYG3tcwxMvvQUMz3XEXMPz/Vi4SsG+1N49X
C+Qw/KI9tYoUqVDZPTQhS4S/zu/ediv2ZH7MwIWo23lhkFU83fDtrpgwsrjIgfHNqIhak0Ly
EuiQlxQGrvBplO29S1odQlJBIOpNQU99DElbtNRb1O3LFAUw4dTjMe7ObwIDAQABo4IBbzCC
AWswHwYDVR0jBBgwFoAUY01DWhlIP8RGwQK6v+4O5YK3ZqYwHQYDVR0OBBYEFGLVBIcIvL2c
hB6HdEbdqflwgrTTMA4GA1UdDwEB/wQEAwIFoDAMBgNVHRMBAf8EAjAAMB0GA1UdJQQWMBQG
CCsGAQUFBwMEBggrBgEFBQcDAjAYBgNVHSAEETAPMA0GCysGAQQBsjEBAgIdMD8GA1UdHwQ4
MDYwNKAyoDCGLmh0dHA6Ly9jcmwudGNzLnRlcmVuYS5vcmcvVEVSRU5BUGVyc29uYWxDQS5j
cmwwcgYIKwYBBQUHAQEEZjBkMDoGCCsGAQUFBzAChi5odHRwOi8vY3J0LnRjcy50ZXJlbmEu
b3JnL1RFUkVOQVBlcnNvbmFsQ0EuY3J0MCYGCCsGAQUFBzABhhpodHRwOi8vb2NzcC50Y3Mu
dGVyZW5hLm9yZzAdBgNVHREEFjAUgRJqaXJpLnNsZXprYUBzbHUuY3owDQYJKoZIhvcNAQEF
BQADggEBAAXIoOnvYifhjAyW1oALfQSl8UemLGYSXiOsoosWx/2yG2/WlULU1lyqOkqztden
dQdt5JZ1Y91HFWRmGGyq+a5kZseYRcpRxEKhJtLngrA24arcvouC/1Wev0RO4d0CKQa/wuC5
yfXIqhn60XJh51mHtbZ4k0jY+U/eNhTWns2Q0NZbR+u3SMrQRa31Df0wmMJvnZkd7cqKF3ur
543ojxAlIVDEUanWPndyljm4ZlAUxmwfmYTd0fRbCl+pDNG+gJnXQO6uvt/yoKNxAaBBFwh0
zmj8k6dCrcpeOKXw+T2mqjSO+6SQBQugGeOSxZA8gZ7rUtf6oNnIZwfxyqoHTVQwggTDMIID
q6ADAgECAhBz/lf637jFCIF7Zrlr8C3vMA0GCSqGSIb3DQEBBQUAMIGuMQswCQYDVQQGEwJV
UzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUg
VVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2
MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWls
MB4XDTA5MDUxODAwMDAwMFoXDTI4MTIzMTIzNTk1OVowOzELMAkGA1UEBhMCTkwxDzANBgNV
BAoTBlRFUkVOQTEbMBkGA1UEAxMSVEVSRU5BIFBlcnNvbmFsIENBMIIBIjANBgkqhkiG9w0B
AQEFAAOCAQ8AMIIBCgKCAQEAyBXZ9TNqI6GQDc+7BUTDqx9KNYUaIYWgT/jwQOJKQ5v+W7Gw
v7RX3HWAQUtkGvbbT2+P0CVFNfnqy0r6+9rT7UWIEZQ25MyoDe/FPTftFnvjwpWeWDN/Ivv4
/+zmvtuuCmUlIofab4SLRuhAhig/v1YI4krpg6LpIvst+rYoH5HBw3H7U8ArTqQMoW6dVe3s
4SSHOgjiDRzkxE3Qyyf6hGTm0ZedViRbk7spLkPiQWo94kpl/JpfWoaHvIfHeYCWmVHGkA9k
kZl9EN2sLAMq4Xhk/s49TvQrUBFL0VjUmwPwf/U7U7BTQ/vFL8QEKRo6rNdV6dEOldE7MX94
T64pLQIDAQABo4IBTTCCAUkwHwYDVR0jBBgwFoAUiYJnfcSdJnAAS7RQSHzePa4Ebn0wHQYD
VR0OBBYEFGNNQ1oZSD/ERsECur/uDuWCt2amMA4GA1UdDwEB/wQEAwIBBjASBgNVHRMBAf8E
CDAGAQH/AgEAMBgGA1UdIAQRMA8wDQYLKwYBBAGyMQECAh0wWAYDVR0fBFEwTzBNoEugSYZH
aHR0cDovL2NybC51c2VydHJ1c3QuY29tL1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0aGVudGlj
YXRpb25hbmRFbWFpbC5jcmwwbwYIKwYBBQUHAQEEYzBhMDgGCCsGAQUFBzAChixodHRwOi8v
Y3J0LnVzZXJ0cnVzdC5jb20vVVROQUFBQ2xpZW50X0NBLmNydDAlBggrBgEFBQcwAYYZaHR0
cDovL29jc3AudXNlcnRydXN0LmNvbTANBgkqhkiG9w0BAQUFAAOCAQEABiupUy8T3Fw5FsyG
n15Me3L77I1Vil6aCv9TTHb0Bj1Qz1fwos+vmYyq/qAZdj6ZAzL6dYM4irtrmqUME7LUG3bm
lC5nmFnjkWwCkJqcyGBLVavKiFqNK+VplQMH0dQO/CQiLlmxY6Rf7dkjcuSczjpcbB9PqQDJ
Hf76f0Utti6E3Q8noFkYTtV2JUX0mSZ522+fI/dDuysPBKOBJiy3ezX5PXdfQCHmfx2lllq9
0MsWOmy7YYuK/QQ5RArLLOHLzi4QmBrb4JPtSWRkCCCft6NQ8KLdyrTGfAw9514V3CeG5Do7
UloXq6kGUyudCXNkHAHD/TDShwNv5BUDejlfaDGCAwcwggMDAgEBME8wOzELMAkGA1UEBhMC
TkwxDzANBgNVBAoTBlRFUkVOQTEbMBkGA1UEAxMSVEVSRU5BIFBlcnNvbmFsIENBAhBVchY6
Gpm6Vjo7qoA7Jf1bMAkGBSsOAwIaBQCgggGNMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEw
HAYJKoZIhvcNAQkFMQ8XDTE0MDEyMDE0NTczNFowIwYJKoZIhvcNAQkEMRYEFIoX/VPcdTJX
x6m4sGEQH5qjDOoTMF4GCSsGAQQBgjcQBDFRME8wOzELMAkGA1UEBhMCTkwxDzANBgNVBAoT
BlRFUkVOQTEbMBkGA1UEAxMSVEVSRU5BIFBlcnNvbmFsIENBAhBVchY6Gpm6Vjo7qoA7Jf1b
MGAGCyqGSIb3DQEJEAILMVGgTzA7MQswCQYDVQQGEwJOTDEPMA0GA1UEChMGVEVSRU5BMRsw
GQYDVQQDExJURVJFTkEgUGVyc29uYWwgQ0ECEFVyFjoambpWOjuqgDsl/VswbAYJKoZIhvcN
AQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3
DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDANBgkqhkiG
9w0BAQEFAASCAQARkLOM+mziP6jxoSER0vGkhRFTJ+UJuIDelhhfv908fbf7Qz0m2iNltpBU
EfkTYKtIUOo1ZZdUTioGNTHriIcAE9+cqxIEsPwg4QpcImrJUTJPOQ6yhx+4BZ+bAopGaRJy
qEN5/xGflbjpk83BragPNE3Cq+0H/msq2RUbfWK+7kEyQGVYigaXzUrxn3VJ4/BaIQTNOg13
esW/R+sJcvh6oIil5/TN7pxuSKj/NkwfpuYzPlr35Izzdjo88GFrwIF0NwkjXGqWD2ZwLmKh
29t0+G7P1MLazz4+yPY+q19bXv60lg9+rv7jq5xM1640CtRMpllbYWzEN6h2B5HfclbAAAAA
AAAA
--------------ms040006030805040301050402--
3
3
Hello there
Seem to be going in a problem again. I had installed oVirt node on my
server and was running the engine on another machine. Now I had to change
the engine machine since that was just a test PC so I got rid of the engine
machine. Installed the engine on another machine and now i'm trying to add
the node to it. It goes on all well until it reaches the 'termination'
stage and then it gives an error "Installation failed. Network error during
communication with the host."
PS
SELinux/ebtables is off on both machines.
A little help would be great.
Regards
Nauman Abbas
Assistant System Administrator (LMS),
Room No. A-207, SEECS,
National University of Sciences & Technology,
+ 92 321 5359946
4
5
21 Jan '14
Hello,
any feedback about VoIP softswitches on virtual servers?
I found this positive whitepaper on VMware web site but it seems
mostly related to Class5 softswitches (intended for work with
end-users):
http://www.vmware.com/files/pdf/techpaper/voip-perf-vsphere5.pdf
I would like to know about real experiences and Class4 softswitches
too (used for transit VoIP traffic between carriers).
Thanks in advance,
Gianluca
3
2
--_000_16669B246DBC4D4EB043E6B646D51CEA2231D8mbx025w1ca8exch02_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
I have a disk image (i.e. a file) that I want to register as a disk using t=
he REST API.
The REST API works with existing disks, but does the API work with disk ima=
ges?
--_000_16669B246DBC4D4EB043E6B646D51CEA2231D8mbx025w1ca8exch02_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I have a disk image (i.e. a file) that I want to reg=
ister as a disk using the REST API.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">The REST API works with existing disks, but does the=
API work with disk images?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>
--_000_16669B246DBC4D4EB043E6B646D51CEA2231D8mbx025w1ca8exch02_--
3
11
20 Jan '14
--=-0VuymFCw5CMiaFLyxpM6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Hey,
as many of you have noticed there wasn't any well working oVirt Node ISO
around for oVirt 3.3.
To get this ball rolling again I've put together a draft image of ALPHA
quality. It contains many fixes some of us have been working on over the
last weeks.
- Source & ISO -
To not drown Jenkins in a hell-of-a-patch-queue I've pushed the patches to
https://github.com/fabiand/ovirt-node/tree/teamsync
The ISO built from that patchset can be found here:
http://fedorapeople.org/~fabiand/node/3.0.4/ovirt-node-iso-3.0.3-0.999.2014=
01170926draft.vdsm.el6.iso
Please test this draft image and provide feedback on how it works for
you.
If you encounter problems - and you probably will - please take a look
here on how to debug them:
http://www.ovirt.org/Node_Troubleshooting
- Important Notes -
SELinux: Boot this alpha image with enforcing=3D0 to log potential
denials, but not block the calls. To fix those denials permanently
please attach your /var/log/audit/audit.log to a bug in bugzilla.
Known problems:
- Exception is raised after registration to Engine
- Many bond devices are show on network page
- Denials appear in /var/log/audit/audit.log
And don't hesitate to reach out to us if you want to get more involved
with Node.
- fabian
--=-0VuymFCw5CMiaFLyxpM6
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
iQIcBAABAgAGBQJS2Q8IAAoJEC9+uOgSHVGUE4cP/05i7nAgZVXJGhErZeZQlpkn
eP6ot4cCRS4MDDOjfkrK54TNvs+CrKMefsvDv4B8NzfnaDHrVjyCFI2+8Yfhj/0/
so/csLBWy1A0LR5tHv4RQBov8Dz74zgMjZxMeGIMuQcQekSmghONK8vQsfpGOtys
xytG84MXRTQjrkJt5Wc7V1AKxkH7lHGH21g+IDesnSVUQouA/Zu/x/4A0o/mx/R+
VJow7lNR/PMlMe8fzjFNUrlFYjA0olFGFaeVXfphVjhnIIN2dJABVpb6hXfU25Uy
6rwjr45eS8gL81JjMEm3XwD215WxdlmzVawcVmqcKcrBu7U+eKxFZFYSe4HD7Nnf
E4Aw3A5mSK76WFjLyaKwczXl1DyWNdTp1yIPDtX8H5lG2rJpUe23o2yMlqn3IZ5u
JjBRjg5EwgHfucxpRRUwdh8tnYIzgp6ejhvgwbY8X8kYwXqSd8Td5mZvM8GBEdif
noXrJImIYoU08Q/0acjiOpZ710wqEvPhmL15okXj+3+WFp53aMUdUY8F2amSBj+a
ik+Zzpiq0SXTthuAatOUxdTX+Sp0kraV5moV6qBYxXX80wGLg2qzhNA4xZ0vqkc2
ipQOuyceGWCaSziklngY86DNNWzhkaOAyCyTmXDMokSthAITI4LVgsuWIvy2A8Z1
JSMjEl7msdgH/t3OFrjO
=oLBg
-----END PGP SIGNATURE-----
--=-0VuymFCw5CMiaFLyxpM6--
2
6
------=_NextPartTM-000-dd723cdf-6ccb-4b19-9baf-8b262252573c
Content-Type: multipart/alternative;
boundary="_000_12EF8D94C6F8734FB2FF37B9FBEDD173585D3007EXCHANGEcollogi_"
--_000_12EF8D94C6F8734FB2FF37B9FBEDD173585D3007EXCHANGEcollogi_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello,
we are currently encountering the above error during virt-v2v
migration. There was an older post about it here:
http://lists.ovirt.org/pipermail/users/2013-December/018379.html
The answers suggest that this is already fixed upstream
and that you only need virt-v2v for OS disks. Could someone,
explain
- how to migrate only the OS disk and to dd the data disks.
- if there exist any offical patches to fix the bug.
Thanks in advance.
Markus
--_000_12EF8D94C6F8734FB2FF37B9FBEDD173585D3007EXCHANGEcollogi_
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>
we are currently encountering the above error during virt-v2v<br>
migration. There was an older post about it here: <br>
http://lists.ovirt.org/pipermail/users/2013-December/018379.html<br>
<br>
The answers suggest that this is already fixed upstream<br>
and that you only need virt-v2v for OS disks. Could someone,<br>
explain<br>
<br>
- how to migrate only the OS disk and to dd the data disks.<br>
- if there exist any offical patches to fix the bug. <br>
<br>
Thanks in advance.<br>
<br>
Markus<br>
</div>
</body>
</html>
--_000_12EF8D94C6F8734FB2FF37B9FBEDD173585D3007EXCHANGEcollogi_--
------=_NextPartTM-000-dd723cdf-6ccb-4b19-9baf-8b262252573c
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-dd723cdf-6ccb-4b19-9baf-8b262252573c--
3
3
Hi,
is it possible to get the vm events via any API/CLI?
I'm talking about the "events" tab which you can select
in webadmin when you selected a vm.
If this is possible, how can we get the data?
We could even write a vdsm hook, if necessary, but
would of course prefer REST-API.
Thanks.
--
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
4
9
--_000_D86C48DF8800164BBE50B87623F7AC9548080D6Eln2wio001devtra_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
I have a problem where VM network profiles are lost when editing a host. E.=
G.
* VM is running fine on the correct network. Network Interfaces tab=
shows "nic1" and "Network Name" shows the correct network profile.
* I shutdown the VM then right click and Edit.
* The General settings for the node shows "nic1 <Empty>". If I then=
edit config, something like increasing memory or changing CPU cores then c=
lick on OK, the VM configuration is saved without a network profile.
* When I boot the VM I cannot connect to it.
* I then have to edit the node again configure back in the correct =
network profile.
Does anyone know if this is a known issue? If not, any suggestions as to ho=
w I correct this so that the original network profile definition is retaine=
d after an edit?
Many thanks,
Simon
--_000_D86C48DF8800164BBE50B87623F7AC9548080D6Eln2wio001devtra_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1503741428;
mso-list-type:hybrid;
mso-list-template-ids:-1164301930 134807553 134807555 134807557 134807553 =
134807555 134807557 134807553 134807555 134807557;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New","serif";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New","serif";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New","serif";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I have a problem where VM network profiles are lost =
when editing a host. E.G.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span style=3D"font-family:Symbol"><span styl=
e=3D"mso-list:Ignore">·<span style=3D"font:7.0pt "Times New Rom=
an"">
</span></span></span><![endif]>VM is running fine on the correct network. N=
etwork Interfaces tab shows “nic1” and “Network Name̶=
1; shows the correct network profile.<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span style=3D"font-family:Symbol"><span styl=
e=3D"mso-list:Ignore">·<span style=3D"font:7.0pt "Times New Rom=
an"">
</span></span></span><![endif]>I shutdown the VM then right click and Edit.=
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span style=3D"font-family:Symbol"><span styl=
e=3D"mso-list:Ignore">·<span style=3D"font:7.0pt "Times New Rom=
an"">
</span></span></span><![endif]>The General settings for the node shows R=
20;nic1 <Empty>”. If I then edit config, something like increas=
ing memory or changing CPU cores then click on OK, the VM configuration is =
saved without a network profile.<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span style=3D"font-family:Symbol"><span styl=
e=3D"mso-list:Ignore">·<span style=3D"font:7.0pt "Times New Rom=
an"">
</span></span></span><![endif]>When I boot the VM I cannot connect to it.<o=
:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span style=3D"font-family:Symbol"><span styl=
e=3D"mso-list:Ignore">·<span style=3D"font:7.0pt "Times New Rom=
an"">
</span></span></span><![endif]>I then have to edit the node again configure=
back in the correct network profile.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">Does anyone know if this is a known issue? If not, a=
ny suggestions as to how I correct this so that the original network profil=
e definition is retained after an edit?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">Many thanks,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">Simon<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>
--_000_D86C48DF8800164BBE50B87623F7AC9548080D6Eln2wio001devtra_--
4
11
Hi
I am experiencing issues with manual VM migration. VM fails to migrate to
other node in the same Cluster. Here are some relevant engine.log entries:
ERROR [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo]
(DefaultQuartzScheduler_Worker-73) Rerun vm
a31cfd62-26fc-4396-8a83-1aed68c7fd39. Called from vds novmnode1
ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand]
(pool-6-thread-49) Failed in MigrateStatusVDS method
ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand]
(pool-6-thread-49) Error code migrateErr and error message
VDSGenericException: VDSErrorException: Failed to MigrateStatusVDS, error =
Fatal error during migration
ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand]
(pool-6-thread-49) Command MigrateStatusVDS execution failed. Exception:
VDSErrorException: VDSGenericException: VDSErrorException: Failed to
MigrateStatusVDS, error = Fatal error during migration
Both Engine and Node are running CentOS 6.5 x64. oVirt Engine Version:
3.3.2-1.el6. VDSM version 4.13.2-1. I restarted engine and vdsm, that did
not help.
Also in vdsm log file I see the following errors related to the same VM ID:
Thread-27::ERROR::2014-01-17 16:37:06,271::sampling::355::vm.Vm::(collect)
vmId=`a31cfd62-26fc-4396-8a83-1aed68c7fd39`::Stats function failed:
<AdvancedStatsFunction _highWrite at 0x26efb58>
Any hints?
BR
Edgars
5
20
Hi,
Now that I finally stepped through and have a working hosted engine setup
(after opening numerous BZs)..
How do I modify network configuration (eg. assign new VLANs to hosts), when
I attempt to modify a network it gives the error:
Error while executing action Setup Networks: Network is currently being used
Is there a recommended way to set up these extra networks, or must all of
these be not managed by the engine?
Thanks,
Andrew
3
7
---------- Forwarded message ----------
From: Koen Vanoppen <vanoppen.koen(a)gmail.com>
Date: 2014/1/20
Subject: Re: [Users] Disk error
To: dron(a)redhat.com
Status ok...
2014/1/20 Dafna Ron <dron(a)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(a)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>>
>>
>>
>> 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>>>
>>
>>
>> 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>>>>
>>
>>
>>
>> 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>>>>>
>>
>>
>>
>> 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>>>>>
>> *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>>>>, "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>>>>>
>> *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>>>>>>
>>
>>
>>
>> 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>>>>>>
>>
>> > 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(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>>>>>>
>> > 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(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>>>>>>, 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>>>>>
>>
>>
>> > 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(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>>>>>>
>> > > *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>>>>>
>>
>>
>> > > *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>>>>>
>>
>>
>> > >
>> 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>>>>>
>>
>>
>> > >
>> 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>>>>
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>>
>> -- Dafna Ron
>>
>>
>> us
>>
>> -- Dafna Ron
>>
>>
>>
>>
>> -- Dafna Ron
>>
>>
>>
>>
>> -- Dafna Ron
>>
>>
>>
>>
>
> --
> Dafna Ron
>
1
0
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>
> 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>
>
>> 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>>
>>>
>>>
>>> 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>>>
>>>
>>>
>>>
>>> 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>>>>
>>>
>>>
>>>
>>> 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>>>>
>>> *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>>>, "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>>>>
>>> *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>>>>>
>>>
>>>
>>>
>>> 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>>>>>
>>> > 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>>>>>
>>> > 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>>>>>, 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>>>>
>>>
>>>
>>> > 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>>>>>
>>> > > *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>>>>
>>>
>>>
>>> > > *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>>>>
>>>
>>>
>>> > >
>>> 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>>>>
>>>
>>>
>>> > >
>>> 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>>>
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>>>
>>> -- Dafna Ron
>>>
>>>
>>> us
>>>
>>> -- Dafna Ron
>>>
>>>
>>>
>>>
>>> -- Dafna Ron
>>>
>>>
>>>
>>
>> --
>> Dafna Ron
>>
>
>
2
1
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>>
>
> 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>>>
>
>
> 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>>>>
>
>
>
> 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>>>>
> *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>>>, "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>>>>
> *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>>>>>
>
>
>
> 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>>>>>
> > 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>>>>>
> > 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>>>>>, 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>>>>
>
> > 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>>>>>
> > > *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>>>>
>
>
> > > *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>>>>
>
>
> > >
> 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>>>>
>
>
> > >
> 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>>>
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
> -- Dafna Ron
>
>
> us
>
> -- Dafna Ron
>
>
>
>
> --
> Dafna Ron
>
>
--
Dafna Ron
1
0
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>>
>
> 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>>>
>
>
> 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>>>
> *To: *users(a)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>>>
> *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>>>>
>
>
>
> 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>>>>
> > 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>>>>
> > 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>>>>, 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>>>
>
> > 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>>>>
> > > *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>>>
>
>
> > > *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>>>
>
>
> > > 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>>>
>
>
> > > 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>>
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
> -- Dafna Ron
>
>
> us
>
> --
> Dafna Ron
>
>
--
Dafna Ron
1
0
20 Jan '14
Hi,
I'm seeing this weird error on my host which runs the hosted-engine, it
only recently showed up and put the host into 'Non Operational' :
Gluster command [Non interactive user] failed on server HV01.
ovirt-engine.log
http://www.fpaste.org/69949/90213863/
Current running VMs continue to run. Has anyone seen this before?
Thanks,
Andrew
2
2
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>>
>
> 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>>
> *To: *users(a)ovirt.org <mailto:users@ovirt.org>, "Meital
> Bourvine" <mbourvin(a)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>>>
>
>
> 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>>>
> > To: "Meital Bourvine" <mbourvin(a)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>>>, users(a)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>>>
> > > *To: *users(a)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>>
>
> > > 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>>
>
> > > http://lists.ovirt.org/mailman/listinfo/users
> >
> >
> > --
> > Dafna Ron
> >
>
>
>
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org <mailto:Users@ovirt.org>
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
> --
> Dafna Ron
>
>
us
--
Dafna Ron
1
0