[ovirt-users] Re: Request for feedback about "Overview of Networking in oVirt"

2020-08-12 Thread thomas
One of the many cases where nested virtualization would be quite handy for 
testing...

If only it worked with oVirt on top of oVirt...
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/DWNBTCB7KF2MYQUYCQCYSUVV74LVB4ZG/


[ovirt-users] Re: Support for Shared SAS storage

2020-08-12 Thread thomas

> 
> Since 4.4 is the last feature release, this will never change even if it is 
> not
> documented.
> 
> Nir
Hi Nir,
could you please clarfiy: What does "last feature release" mean here: Is oVirt 
being feature frozen in preparation to something more drastic?
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/FKGE2VELIU3XBTWDC65CRETNCOTGEDWJ/


[ovirt-users] Re: Is the udev settling issue more wide spread? Getting failed 'qemu-img -convert' also while copying disks between data and vmstore domains

2020-08-12 Thread Nir Soffer
On Wed, Aug 12, 2020 at 2:25 AM  wrote:

> While trying to diagnose an issue with a set of VMs that get stopped for
> I/O problems at startup, I try to deal with the fact that their boot disks
> cause this issue, no matter where I connect them. They might have been the
> first disks I ever tried to sparsify and I was afraid that might have
> messed them up. The images are for a nested oVirt deployment and they
> worked just fine, before I shut down those VMs...
>
> So I first tried to hook them as secondary disks to another VM to have a
> look, but that just cause the other VM to stop at boot.
>
> Also tried downloading, exporting, and plain copying the disks to no
> avail, OVA exports on the entire VM fail again (fix is in!).
>
> So to make sure copying disks between volumes *generally* work, I tried
> copying a disk from a working (but stopped) VM from 'vmstore' to 'data' on
> my 3nHCI farm, but that failed, too!
>
> Plenty of space all around, but all disks are using thin/sparse/VDO on SSD
> underneath.
>
> Before I open a bug, I'd like to have some feedback if this is a standard
> QA test, this is happening to you etc.
>
> Still on oVirt 4.3.11 with pack_ova.py patched to wait for the udev
> settle,
>
> This is from the engine.log on the hosted-engine:
>
> 2020-08-12 00:04:15,870+02 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] EVENT_ID:
> VDS_BROKER_COMMAND_FAILURE(10,802), VDSM gem2 command
> HSMGetAllTasksStatusesVDS failed: low level Image copy failed: ("Command
> ['/usr/bin/qemu-img', 'convert', '-p', '-t', 'none', '-T', 'none', '-f',
> 'raw', 
> u'/rhev/data-center/mnt/glusterSD/192.168.0.91:_vmstore/9d1b8774-c5dc-46a8-bfa2-6a6db5851195/images/aca27b96-7215-476f-b793-fb0396543a2e/311f853c-e9cc-4b9e-8a00-5885ec7adf14',
> '-O', 'raw', 
> u'/rhev/data-center/mnt/glusterSD/192.168.0.91:_data/32129b5f-d47c-495b-a282-7eae1079257e/images/f6a08d2a-4ddb-42da-88e6-4f92a38b9c95/e0d00d46-61a1-4d8c-8cb4-2e5f1683d7f5']
> failed with rc=1 out='' err=bytearray(b'qemu-img: error while reading
> sector 131072: Transport endpoint is not connected\\nqemu-img: error while
> reading sector 135168: Transport endpoint is not connected\\nqemu-img:
> error while reading sector 139264: Transport
>   endpoint is not connected\\nqemu-img: error while reading sector 143360:
> Transport endpoint is not connected\\nqemu-img: error while reading sector
> 147456: Transport endpoint is not connected\\nqemu-img: error while reading
> sector 151552: Transport endpoint is not connected\\n')",)
>
> and this is from the vdsm.log on the gem2 node:
> Error: Command ['/usr/bin/qemu-img', 'convert', '-p', '-t', 'none', '-T',
> 'none', '-f', 'raw', 
> u'/rhev/data-center/mnt/glusterSD/192.168.0.91:_vmstore/9d1b8774-c5dc-46a8-bfa2-6a6db5851195/images/aca27b96-7215-476f-b793-fb0396543a2e/311f853c-e9cc-4b9e-8a00-5885ec7adf14',
> '-O', 'raw', 
> u'/rhev/data-center/mnt/glusterSD/192.168.0.91:_data/32129b5f-d47c-495b-a282-7eae1079257e/images/f6a08d2a-4ddb-42da-88e6-4f92a38b9c95/e0d00d46-61a1-4d8c-8cb4-2e5f1683d7f5']
> failed with rc=1 out='' err=bytearray(b'qemu-img: error while reading
> sector 131072: Transport endpoint is not connected\nqemu-img: error while
> reading sector 135168: Transport endpoint is not connected\nqemu-img: error
> while reading sector 139264: Transport endpoint is not connected\nqemu-img:
> error while reading sector 143360: Transport endpoint is not
> connected\nqemu-img: error while reading sector 147456: Transport endpoint
> is not connected\nqemu-img: error while reading sector 151552: Transport
> endpoint is not connected\n')
> 2020-08-12 00:03:15,428+0200 ERROR (tasks/7) [storage.Image] Unexpected
> error (image:849)
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/image.py", line 837,
> in copyCollapsed
> raise se.CopyImageError(str(e))
> CopyImageError: low level Image copy failed: ("Command
> ['/usr/bin/qemu-img', 'convert', '-p', '-t', 'none', '-T', 'none', '-f',
> 'raw', 
> u'/rhev/data-center/mnt/glusterSD/192.168.0.91:_vmstore/9d1b8774-c5dc-46a8-bfa2-6a6db5851195/images/aca27b96-7215-476f-b793-fb0396543a2e/311f853c-e9cc-4b9e-8a00-5885ec7adf14',
> '-O', 'raw', 
> u'/rhev/data-center/mnt/glusterSD/192.168.0.91:_data/32129b5f-d47c-495b-a282-7eae1079257e/images/f6a08d2a-4ddb-42da-88e6-4f92a38b9c95/e0d00d46-61a1-4d8c-8cb4-2e5f1683d7f5']
> failed with rc=1 out='' err=bytearray(b'qemu-img: error while reading
> sector 131072: Transport endpoint is not connected\\nqemu-img: error while
> reading sector 135168: Transport endpoint is not connected\\nqemu-img:
> error while reading sector 139264: Transport endpoint is not
> connected\\nqemu-img: error while reading sector 143360: Transport endpoint
> is not connected\\nqemu-img: error while reading sector 147456: Transport
> endpoint is not connected\\nqemu-img: error while reading sector 151552: T
>  ransport endpoint is not 

[ovirt-users] Re: Support for Shared SAS storage

2020-08-12 Thread Nir Soffer
On Wed, Aug 12, 2020 at 9:46 AM Lao Dh  wrote:

> Update for all. The deployment finally detect the SAS collected storage.
> After manual compile the driver for the RAID control PCI card.
> Nir is correct. FC detect anything that is not "NFS, iSCSI". As this time
> it also detect a local connected SATA SSD.
>

You should blacklist this local device, see the instructions in
/etc/multipath.conf.


> 2020年8月10日月曜日 1:55:37 GMT+8、Nir Soffer が書いたメール:
>
>
> On Sat, Aug 8, 2020 at 6:56 AM Jeff Bailey  wrote:
> >
> > I haven't tried with 4.4 but shared SAS works just fine with 4.3 (and
> has for many, many years).  You simply treat it as Fibre Channel.  If your
> LUNs aren't showing up I'd make sure they're being claimed as multipath
> devices.  You want them to be.  After that, just make sure they're
> sufficiently wiped so they don't look like they're in use.
>
> Correct. FC in oVirt means actually not "iSCSI". Any device - including
> local
> devices - that multipath expose, and is not iSCSI is considered as FC.
>
> This is not officially supported and not documented anywhere. I learned
> about it only we tried to deploy strict multipath blacklist allowing
> only "iscsi"
> or "fc" transport, and found that it broke users' setups with sas other
> esoteric
> storage.
>
> Since 4.4 is the last feature release, this will never change even if it
> is not
> documented.
>
> Nir
>
> > On 8/7/2020 10:49 PM, Lao Dh via Users wrote:
> >
> > Wow. That's sound bad. Then what storage type you choose at last (with
> your SAS connected storage)? VMware vSphere support DAS. Red Hat should do
> something.
> >
> > 2020年8月8日土曜日 4:06:34 GMT+8、Vinícius Ferrão via Users  >が書いたメール:
> >
> >
> > No, there’s no support for direct attached shared SAS storage on
> oVirt/RHV.
> >
> > Fibre Channel is a different thing that oVirt/RHV supports.
> >
> > > On 7 Aug 2020, at 08:52, hkexdong--- via Users 
> wrote:
> > >
> > > Hello Vinícius,
> > > Do you able to connect the SAS external storage?
> > > Now I've the problem during host engine setup. Select Fibre Channel
> and end up show "No LUNS found".
> > > ___
> > > Users mailing list -- users@ovirt.org
> > > To unsubscribe send an email to users-le...@ovirt.org
> > > Privacy Statement: https://www.ovirt.org/privacy-policy.html
> > > oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> > > List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/RDPLKGIRN5ZGIEPWGOKMGNFZNMCEN5RC/
> >
> >
> > ___
> > Users mailing list -- users@ovirt.org
> > To unsubscribe send an email to users-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/privacy-policy.html
> > oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
> >
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/2CLI3YSYU7BPI62YANJXZV7RIQFOXXED/
> >
> >
> > ___
> > Users mailing list -- users@ovirt.org
> > To unsubscribe send an email to users-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/privacy-policy.html
> > oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/WOBHQDCBZZK5WKRAUNHP5CGFYY3HQYYU/
> >
> > ___
> > Users mailing list -- users@ovirt.org
> > To unsubscribe send an email to users-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/privacy-policy.html
> > oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/UY52JRY5EMQJTMKG3POE2YXSFGL7P55S/
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
>
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/JYWUVULGUNLTU6QOY6WOUKBCA5IAO5QR/
>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/DW4XQ7SFMFVS6G7WDMN6SHJEHPXBOHTT/


[ovirt-users] Re: uprade from 4.3 to 4.4

2020-08-12 Thread suporte
Hi Shani, 

Ok, thanks. What is the Glusterfs compatibilty version with oVirt 4.4.2 ? 

José 


De: "Shani Leviim"  
Para: supo...@logicworks.pt 
Cc: "users"  
Enviadas: Quarta-feira, 12 De Agosto de 2020 10:29:31 
Assunto: Re: [ovirt-users] uprade from 4.3 to 4.4 

Hi Jose, 
It is possible. 

You can find in this detailed mail Installation instructions, release notes, 
and references for more information: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/VONS2YAHMTYBKWFCY7HAYDPLV47BO6US/
 

Please make sure to meet the prerequisites, as in RHEL 8 / CentOS 8 several 
devices that worked on EL7 are no longer supported. 

Regards, 
Shani Leviim 


On Tue, Aug 11, 2020 at 10:43 PM < supo...@logicworks.pt > wrote: 



Hello, 

is possible to upgrade from ovirt 4.3 to 4.4 ? 

Thanks 

-- 

Jose Ferradeira 
http://www.logicworks.pt 
___ 
Users mailing list -- users@ovirt.org 
To unsubscribe send an email to users-le...@ovirt.org 
Privacy Statement: https://www.ovirt.org/privacy-policy.html 
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/ 
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/JHXZAWTFH5EIZWRKGHOGJ6FY4TF6N4S4/
 




___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/WTSMKXTF5UIJKGHCYADV65RG7LQUAM6Q/


[ovirt-users] Re: oVirt 4.4.0 Release is now generally available

2020-08-12 Thread Olaf Buitelaar
Hi Strahil,

Ok done; https://bugzilla.redhat.com/show_bug.cgi?id=1868393 only it didn't
allow me to select the most recent 4.3.

Thanks Olaf

Op wo 12 aug. 2020 om 15:58 schreef Strahil Nikolov :

> Hi Olaf,
>
> yes but mark it as  '[RFE]' in the name of the bug.
>
> Best Regards,
> Strahil Nikolov
>
> На 12 август 2020 г. 12:41:55 GMT+03:00, olaf.buitel...@gmail.com написа:
> >Hi Strahil,
> >
> >It's not really clear how i can pull requests to the oVirt repo.
> >I've found this bugzilla issue for going from v5 to v6;
> >https://bugzilla.redhat.com/show_bug.cgi?id=1718162 with this
> >corresponding commit; https://gerrit.ovirt.org/#/c/100701/
> >Would the correct route be to issue a bugzilla request for this?
> >
> >Thanks Olaf
> >___
> >Users mailing list -- users@ovirt.org
> >To unsubscribe send an email to users-le...@ovirt.org
> >Privacy Statement: https://www.ovirt.org/privacy-policy.html
> >oVirt Code of Conduct:
> >https://www.ovirt.org/community/about/community-guidelines/
> >List Archives:
> >
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZDGSHGWMDKC5OLYXNBU6HCK56XMCKT2R/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/AECOZINFZHHFJHJLLWGJ6GYOFIMTVVZO/


[ovirt-users] Re: oVirt 4.4.0 Release is now generally available

2020-08-12 Thread Strahil Nikolov via Users
Hi Olaf,

yes but mark it as  '[RFE]' in the name of the bug.

Best Regards,
Strahil Nikolov

На 12 август 2020 г. 12:41:55 GMT+03:00, olaf.buitel...@gmail.com написа:
>Hi Strahil,
>
>It's not really clear how i can pull requests to the oVirt repo.
>I've found this bugzilla issue for going from v5 to v6;
>https://bugzilla.redhat.com/show_bug.cgi?id=1718162 with this
>corresponding commit; https://gerrit.ovirt.org/#/c/100701/
>Would the correct route be to issue a bugzilla request for this?
>
>Thanks Olaf
>___
>Users mailing list -- users@ovirt.org
>To unsubscribe send an email to users-le...@ovirt.org
>Privacy Statement: https://www.ovirt.org/privacy-policy.html
>oVirt Code of Conduct:
>https://www.ovirt.org/community/about/community-guidelines/
>List Archives:
>https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZDGSHGWMDKC5OLYXNBU6HCK56XMCKT2R/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/WQ6IF7WCE6G5YP4UX5L2AF3LSKINWOAJ/


[ovirt-users] Re: oVirt 4.4.0 Release is now generally available

2020-08-12 Thread olaf . buitelaar
Hi Strahil,

It's not really clear how i can pull requests to the oVirt repo.
I've found this bugzilla issue for going from v5 to v6; 
https://bugzilla.redhat.com/show_bug.cgi?id=1718162 with this corresponding 
commit; https://gerrit.ovirt.org/#/c/100701/
Would the correct route be to issue a bugzilla request for this?

Thanks Olaf
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZDGSHGWMDKC5OLYXNBU6HCK56XMCKT2R/


[ovirt-users] Re: uprade from 4.3 to 4.4

2020-08-12 Thread Shani Leviim
Hi Jose,
It is possible.

You can find in this detailed mail Installation instructions, release
notes, and references for more information:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/VONS2YAHMTYBKWFCY7HAYDPLV47BO6US/

Please make sure to meet the prerequisites, as in RHEL 8 / CentOS 8 several
devices that worked on EL7 are no longer supported.


*Regards,*

*Shani Leviim*


On Tue, Aug 11, 2020 at 10:43 PM  wrote:

> Hello,
>
> is possible to upgrade from ovirt 4.3 to 4.4 ?
>
> Thanks
>
> --
> --
> Jose Ferradeira
> http://www.logicworks.pt
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/JHXZAWTFH5EIZWRKGHOGJ6FY4TF6N4S4/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/PRWXDEBU2OIGFCB7SY63IQQEN5FHODGA/


[ovirt-users] Re: Reverting to Snapshot

2020-08-12 Thread Christian Reiss
Hey Eyal,

thanks for the explanation. I really would not have guessed that.
Works like a charm, thank you very much!

-Chris


On 12/08/2020 08:06, Eyal Shenitzky wrote:
> Hi Christian,
> 
> Once you take a snapshot you can preview it by pressing the
> *preview* button, as you said it will take you back to 
> the point in time when the snapshot was created.
> 
> Once you are in a '*preview*' mode you have two options - 
> 
>   * *commit* - means that you want to go back to that state of the VM,
> it will cause all the data and snapshots that were taken after that
> point in time to be removed.
>   * *undo *- means that you don't want to go back to that point in time
> of the VM, so the VM will return to his latest state. 


-- 
with kind regards,
mit freundlichen Gruessen,

Christian Reiss




signature.asc
Description: OpenPGP digital signature
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/W3U2LWDWPJSAMGT3YWPTFJNXT6PNWB66/


[ovirt-users] Re: oVirt Node 4.1.1 Hosted Engine Deployment Fibre Channel No LUNS found

2020-08-12 Thread Lao Dh via Users
 Update for all. The deployment finally detect the SAS collected storage. After 
manual compile the driver for the RAID control PCI card.

2020年8月8日土曜日 15:14:03 GMT+8、Strahil Nikolov via Users 
が書いたメール:  
 
 Not when both client and server is the same node and you use 
"localhost:/nfs-share"

Best Regards,
Strahil Nikolov






В събота, 8 август 2020 г., 05:56:10 Гринуич+3, Lao Dh  
написа: 







NFS utilize the network adapter, am I right? The LAN port max speed on the 
storage is just 100Mb/s. That's too slow for hosting VMs.

Regards,
Jeremy




2020年8月8日土曜日 2:15:08 GMT+8、Strahil Nikolov via Users が書いたメール: 





Do  you have the option for POSIX compliant FS ?
If not,  I guess the simplest way is to setup NFS export that to be used for 
the engine.

Best  Regards,
Strahil Nikolov

На 7 август 2020 г. 15:59:55 GMT+03:00, Lao Dh via Users  
написа:
>Hello Strahil,I follow the guide in "Installing oVirt as a self-hosted
>engine using the Cockpit web interface". Only 1 host and 1 SAS storage.
>Host and storage are direct attached. CentOS 8 was installed in host
>local disk.Only 1 SAS cable connected. So I think shouldn't be the
>issue of Multipath.
>
>Regards,Jeremy
>
>
>
>
>
>2020年8月7日金曜日 20:37:47 GMT+8、Strahil Nikolov
>が書いたメール:  
> 
> Are you using the single-node wizard  ?
>
>Best Regards,
>Strahil Nikolov
>
>На 7 август 2020 г. 11:34:52 GMT+03:00, hkexdong--- via Users
> написа:
>>I've an external RAID subsystem connect to the host by SAS cable
>>(SFF-8644).
>>I follow the instructions of the RAID card manufacture. Include the
>>driver during host installation. And I can see the created RAID
>volumes
>>(LUNs) available in "Installation Destination". Although I choose to
>>install the engine in host local disk.
>>The installation success and I proceed to hosted engine deployment by
>>Cockpit. And now I stuck at part 4 Storage.
>>I believe "Storage Type" select "Fibre Channel" is correct even I'm
>not
>>using fibre cable. As NFS and iSCSI are utilize network.
>>I confirm there are 2 RAID volume (LUN0 & LUN1) created in the
>external
>>RAID subsystem. Why oVirt cannot discover them. What could be wrong :(
>>___
>>Users mailing list -- users@ovirt.org
>>To unsubscribe send an email to users-le...@ovirt.org
>>Privacy Statement: https://www.ovirt.org/privacy-policy.html
>>oVirt Code of Conduct:
>>https://www.ovirt.org/community/about/community-guidelines/
>>List Archives:
>>https://lists.ovirt.org/archives/list/users@ovirt.org/message/IIMW6VBS4JBL5WJFTS7AWDS5ENQDB63Y/
> 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/5WYU5SRXKGYDTTLA5WOMYZQULXP4OGLN/


___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZJMQOJLFRMQTN6DCESUYALRXKLZWG74R/
  ___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/PAZVRJJYZ5U52QW7SAIEGJGCQ4XY5QPJ/


[ovirt-users] Re: Support for Shared SAS storage

2020-08-12 Thread Lao Dh via Users
 Update for all. The deployment finally detect the SAS collected storage. After 
manual compile the driver for the RAID control PCI card.Nir is correct. FC 
detect anything that is not "NFS, iSCSI". As this time it also detect a local 
connected SATA SSD.
2020年8月10日月曜日 1:55:37 GMT+8、Nir Soffer が書いたメール:  
 
 On Sat, Aug 8, 2020 at 6:56 AM Jeff Bailey  wrote:
>
> I haven't tried with 4.4 but shared SAS works just fine with 4.3 (and has for 
> many, many years).  You simply treat it as Fibre Channel.  If your LUNs 
> aren't showing up I'd make sure they're being claimed as multipath devices.  
> You want them to be.  After that, just make sure they're sufficiently wiped 
> so they don't look like they're in use.

Correct. FC in oVirt means actually not "iSCSI". Any device - including local
devices - that multipath expose, and is not iSCSI is considered as FC.

This is not officially supported and not documented anywhere. I learned
about it only we tried to deploy strict multipath blacklist allowing
only "iscsi"
or "fc" transport, and found that it broke users' setups with sas other esoteric
storage.

Since 4.4 is the last feature release, this will never change even if it is not
documented.

Nir

> On 8/7/2020 10:49 PM, Lao Dh via Users wrote:
>
> Wow. That's sound bad. Then what storage type you choose at last (with your 
> SAS connected storage)? VMware vSphere support DAS. Red Hat should do 
> something.
>
> 2020年8月8日土曜日 4:06:34 GMT+8、Vinícius Ferrão via Users が書いたメール:
>
>
> No, there’s no support for direct attached shared SAS storage on oVirt/RHV.
>
> Fibre Channel is a different thing that oVirt/RHV supports.
>
> > On 7 Aug 2020, at 08:52, hkexdong--- via Users  wrote:
> >
> > Hello Vinícius,
> > Do you able to connect the SAS external storage?
> > Now I've the problem during host engine setup. Select Fibre Channel and end 
> > up show "No LUNS found".
> > ___
> > Users mailing list -- users@ovirt.org
> > To unsubscribe send an email to users-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/privacy-policy.html
> > oVirt Code of Conduct: 
> > https://www.ovirt.org/community/about/community-guidelines/
> > List Archives: 
> > https://lists.ovirt.org/archives/list/users@ovirt.org/message/RDPLKGIRN5ZGIEPWGOKMGNFZNMCEN5RC/
>
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/2CLI3YSYU7BPI62YANJXZV7RIQFOXXED/
>
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/WOBHQDCBZZK5WKRAUNHP5CGFYY3HQYYU/
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/UY52JRY5EMQJTMKG3POE2YXSFGL7P55S/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/JYWUVULGUNLTU6QOY6WOUKBCA5IAO5QR/
  ___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZN56FVFS5DUWRZ4SNBIIGV3FB3WFAEA4/


[ovirt-users] Re: Hosted Engine Deployment stuck at 3. Prepare VM

2020-08-12 Thread Lao Dh via Users
 Thanks all of you. The deployment did running and finished. It take 3+ hours 
to complete. Compare to previously only take less than an hour.Also, I found 
where to check the logs in cockpit. The log default filter to show only 
"Warning or above". I change it to show "Everything".

2020年8月12日水曜日 11:15:39 GMT+8、 が書いたメール:  
 
 I came across this in an environment where the proxy was very slow. The 
downloaded image for the appliance gets deleted every so often (and perhaps 
also via the cleanup script), so when it needs to be reloaded from the 
internet, it can take its time, because its quite large (>1GB).

Another source of trouble can be that PackageKit or simply another instance of 
yum/dnf is already running and that is blocking the download. Check with htop 
or similar.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/HDY6W2N2VJURBPP35YWDDRPCL6F2HUY4/
  ___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/H6K2ZZNFTQ5UGR2J6YX4G6NJDI3FFINS/


[ovirt-users] Re: Reverting to Snapshot

2020-08-12 Thread Eyal Shenitzky
Hi Christian,

Once you take a snapshot you can preview it by pressing the *preview* button,
as you said it will take you back to
the point in time when the snapshot was created.

Once you are in a '*preview*' mode you have two options -

   - *commit* - means that you want to go back to that state of the VM, it
   will cause all the data and snapshots that were taken after that point in
   time to be removed.
   - *undo *- means that you don't want to go back to that point in time of
   the VM, so the VM will return to his latest state.



On Wed, 12 Aug 2020 at 08:34, Christian Reiss 
wrote:

> Hey folks,
>
> this, I hope, is a trivial question. But I really can't find the button
> for it. If you take a snapshot of any vm - how do you revert to that
> snapshot, discarding all changes after?
>
> I see options to clone, delete, take snapshot, preview... but revert?
> Really in the true sense of "discard all changes, go back to this
> snapshot state".
>
> What am I not seeing here? :)
>
> --
> with kind regards,
> mit freundlichen Gruessen,
>
> Christian Reiss
>
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/GIZPB4OSZU3SOQKGYZD42WMF4LIZLPRX/
>


-- 
Regards,
Eyal Shenitzky
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/VORCQIMTPPSKGFGOHUL7L7AU7YVCQN3W/