[ovirt-users] Long shot on VM failing to start

[simon]

We are moving to an oVirt 4.4.9 environment from a 4.3.4.3 environment and have 
run into a major issue.
The method for migration to the new system is to shutdown a VM on the old 
system, build a new VM on the new system with the same IP/name etc.
This has worked for several VMs so far but the latest new build failed and we 
had to roll back - i.e. start the old VM. The old VM fails to start with the 
following message in the VMs libvirt qemu log:

libvirtd quit during handshake: Input/output error
shutting down, reason=failed

Any ideas?
Regards
Simon...
___
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/4XOQCOLVNTOL2RWJKGREBVMVEHGTV6OX/

[ovirt-users] Re: VM Disk extend not reflected in VM oS

[simon]

Hi Strahil,
Clicked edit on the VMs disk and then entered the required size to extend the 
disk in "Extend size by (GiB)" window.
The UI showed the correct size of the disk but lsblk on the Guest failed to 
show any changes.
___
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/I2CHVVMLLQCOGCVQXK6WZKTHJL3MG2SI/

[ovirt-users] Re: Unable to upload ISO Image in ovirt 4.4.10

[Patrick Hibbs]

The new server is a standalone engine with 2 (also clean Rocky Linux
8.5 installs) hypervisor hosts using GlusterFS in client mode. (I.e.
*NOT* hyperconverged.)

It's basically the same setup I have for my production engine. (The
difference being that the production engine is older and running on
CentOS 8 Stream.)

As for the .truststore file, I meant this one on the engine host:

---snip---

$ ls -la /etc/pki/ovirt-engine/.truststore
-rw-r--r--. 1 root root 4170 Feb 14 18:08 /etc/pki/ovirt-
engine/.truststore

---snip---

If we peek into this on a clean installation we get something like
this:

---snip---

sudo keytool --list --keystore /etc/pki/ovirt-
engine/.truststore.generated
Enter keystore password:  
Keystore type: PKCS12
Keystore provider: SUN

Your keystore contains 2 entries

cacert, Mar 6, 2022, trustedCertEntry, 
Certificate fingerprint (SHA-256):
E9:8E:FC:CF:AE:8C:27:3A:FD:BD:8E:0E:72:DA:99:84:7E:65:55:E6:86:74:D8:3C
:FE:AE:1C:D7:3C:36:D8:C1
qemu-cacert, Mar 6, 2022, trustedCertEntry, 
Certificate fingerprint (SHA-256):
65:D1:E3:14:2D:0D:44:28:B2:A7:EC:AA:B6:84:DA:D6:EC:8A:86:E7:FF:D9:FC:07
:A6:22:8A:A4:86:AD:0E:EB

---snip---

By default, the two certs in /etc/pki/ovirt-engine/.truststore are the
generated CA cert and the host certificate it signed.

If we change this file to include an additional certificate and mark it
as a trustedCertEntry, the imageio service will work without any
additional configuration. This is because oVirt (Used to??? Does for
me.) defaults to using this file out of the box.

The instructions at
https://www.ovirt.org/documentation/administration_guide/index.html#Replacing_the_Manager_CA_Certificate
don't mention this at all. Instead, they instruct the administrator to
create additional config files which creates additional chances for
human error to cause problems.

In oVirt 3.x, modifying /etc/pki/ovirt-engine/.truststore was the
*only* way to get the image uploads working via the Web Admin interface
if you changed apache's certificate. This solution was also not
documented back then. I remember spending about a week back then trying
to hunt down where the upload was failing only to finally stumble over
.truststore by miss typing a ls command. Good times :)


General CA Issue thoughts below:


As for the CA issue in general, this is my take of it. (Keep in mind
it's solely from an end-user perspective, so I'd love to hear what
others have to say about it.):

As of this email, looking at
https://www.ovirt.org/documentation/administration_guide/index.html

and searching for the term "certificate" on that page gives 104
results.

Of those results, we get about 3 different major methods for managing
the various certificates:

1. Manual updating of the certs via ssh. (Apache, imageio, Various SSO
solutions, Various storage protocols)

2. VDSM manages the certs, and administrator changes *will* be
overwritten. (Host Cockpit Console, Host SPICE Console, Host VNC
Console, VDSM internal connections)

3. Uploading the certificates for use via the Web Admin interface
(Interop with other services: ESX / k8 / openstack etc.)

Notice: That there is no overlap for any of the given methods. Each of
these certs *MUST* be managed in their own specific way, and each has
their own checks that must be met (or lack thereof.)

There is also no clear dividing line between what certs are considered
"internal" to oVirt, and what certs should be encountered by end-users
on a regular basis. I.e. The Apache cert is clearly for end users, but
image transfers will fail if imageio isn't dealt with seperately. SPICE
Consoles will work out of the box regardless of changing Apache's cert,
but VNC Consoles will fail entirely unless the web viewer is used. Host
Cockpit consoles also fail if Apache's cert is changed, and this cannot
be fixed at all by the administrator. The only recourse is to install
the engine's generated CA on the end-user terminals.

Further, as the mailing list will attest, sometimes the VDSM managed
certs don't update properly, and expiry notifications are easily missed
by administrators. Leading to multiple headaches and downtime.

In short, the issue in-general is a lack of centralized universal
management for certificates.

A more centralized management system would do away with the multiple
management methods, and focus on providing a consistent view of the
entire PKI infrastructure regardless of who or what accessed it from
anywhere. (I.e. VDSM or an Administrator.) This would cut out the
current configuration headaches, and make it a single check to figure
what's up when things go wrong.

Such a solution would also, in my opinion, include a management tab in
the Web Admin GUI. Such a tab could be used to deploy replacement certs
for the oVirt services that allowed substitutions, or regenerating
certs for the services that do not. In addition to seeing the current
(in-use) certificate information for each service. If I was going to
truly make wishes, I'd also like to see an 

[ovirt-users] [ANN] Async oVirt engine release for oVirt 4.4.10.2

[Lev Veyde]

On March 8th 2022 the oVirt project released an async update of oVirt
engine (4.4.10.7)

Changes:

   -

   Add option to enable/disable sending server.log to remote syslog and Do
   not pass log record timestamp to remote syslog (Fixes BZ#2050218
   )
   -

   VM disk remains in locked state if image transfer (image download) times
   out (Fixes BZ#2057445 )



-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel



l...@redhat.com | lve...@redhat.com

TRIED. TESTED. TRUSTED. 
___
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/HROPDVY57WQVCOTO44K26THXEA3ZFFAA/

[ovirt-users] Re: OVIRT INSTALLATION IN SAS RAID

[Gianluca Cecchi]

On Tue, Mar 8, 2022 at 2:57 PM  wrote:

> I am unable to run lspci command since i am not able to boot the server
> with live cd or install Linux.
>
> anyhow I get some more information about the SAS Driver after installing
> windows server 2012,  here is the information
>
> Device Descprition: DELL PERC 6/i Integrated
>
> Devive Instance path:
>  PCI\VEN_1000_0060_1F0C1028_04\4&254D1C7F&0&0020
>
> hardware ids :
> PCI\VEN_1000_0060_1F0C1028_04
>
>
So, based on the link I already provided, you are here:
"
. . .
 The following adapters from the megaraid_sas driver have been removed:
. . .
SAS1078R, PCI ID 0x1000:0x0060
. . .
"
and the links from elrepo I gave are ok. Kernel module driver to use:
megaraid_sas
Follow also the other link with instructions on how to use the
corresponding dud to install oVirt node.
Gianluca
___
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/XJT6C6ETOLXYFEPPHUW7PZVGER5I6ZVX/

[ovirt-users] Re: OVIRT INSTALLATION IN SAS RAID

[Muhammad Riyaz]

I was unable to run LSPCI command since i am not able to boot with live cd or 
installing Linux to the server

Here is some more details about driver that I catch after installing windows 
server 2012


Device Desscprition:DELL PERC 6/i Integrated

Devive Instance path:  
PCI\VEN_1000_0060_1F0C1028_04\4&254D1C7F&0&0020

hardware ids :
PCI\VEN_1000_0060_1F0C1028_04
PCI\VEN_1000_0060_1F0C1028
PCI\VEN_1000_0060_010400
PCI\VEN_1000_0060_0104


Compatible IDS:
PCI\VEN_1000_0060_04
PCI\VEN_1000_0060
PCI\VEN_1000_010400
PCI\VEN_1000_0104
PCI\VEN_1000
PCI\CC_010400_0
PCI\CC_010400
PCI\CC_0104_0
PCI\CC_0104


driver version:
6.600.21.8


Matching device ID
PCI\VEN_1000_0060_1F0C1028


Service:
Megasas

Configuration ID
megasas.inf:PCI\VEN_1000_0060_1F0C1028,Install_INT.NT
Sent from Mail for Windows




This message (and any associated files) is intended only for the use of the 
individual or entity to which it is addressed and may contain information that 
is confidential, subject to copyright or constitutes a trade secret. If you are 
not the intended recipient you are hereby notified that any dissemination, 
copying or distribution of this message, or files associated with this message, 
is strictly prohibited. If you have received this message in error, please 
notify us immediately by replying to the message and deleting it from your 
computer. Messages sent to and from us may be monitored. Internet 
communications cannot be guaranteed to be secure or error-free as information 
could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or 
contain viruses. Therefore, we do not accept responsibility for any errors or 
omissions that are present in this message, or any attachment, that have arisen 
as a result of e-mail transmission. If verification is required, please request 
a hard-copy version. Any views or opinions presented are solely those of the 
author and do not necessarily represent those of the company.
___
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/VDN5LJLEWEO5SFHHZGL34CDEPS3ZN6VD/

[ovirt-users] Re: OVIRT INSTALLATION IN SAS RAID

[muhammad . riyaz]

I am unable to run lspci command since i am not able to boot the server with 
live cd or install Linux.

anyhow I get some more information about the SAS Driver after installing 
windows server 2012,  here is the information

Device Descprition: DELL PERC 6/i Integrated

Devive Instance path:   
PCI\VEN_1000_0060_1F0C1028_04\4&254D1C7F&0&0020

hardware ids :  
PCI\VEN_1000_0060_1F0C1028_04
PCI\VEN_1000_0060_1F0C1028
PCI\VEN_1000_0060_010400
PCI\VEN_1000_0060_0104


Compatible IDS: 
PCI\VEN_1000_0060_04
PCI\VEN_1000_0060
PCI\VEN_1000_010400
PCI\VEN_1000_0104
PCI\VEN_1000
PCI\CC_010400_0
PCI\CC_010400
PCI\CC_0104_0
PCI\CC_0104

driver version:
6.600.21.8


Matching device ID
PCI\VEN_1000_0060_1F0C1028

Service:
Megasas

Configuration ID
megasas.inf:PCI\VEN_1000_0060_1F0C1028,Install_INT.NT
___
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/3IQN42VDR7BLJH3C4BYO4HVGFAL4HERE/

[ovirt-users] Re: Account on Zanata

[Sharon Gratch]

Hi,


I created an account for you on Zanata and added you to the Japanese
translation group.
I'll send you the account details in a separate mail.


Thanks!
Sharon

On Mon, Feb 21, 2022 at 10:41 AM Sandro Bonazzola 
wrote:

>
>
> Il giorno sab 19 feb 2022 alle ore 14:18 ちゃーりー  ha
> scritto:
>
>> Hi,
>>
>> I'm Yoshihiro Hayashi, just an oVirt user.
>> I found a mistake in Japanese translation on ovirt Web UI, I'm going to
>> fix it.
>> It would be grateful if someone could make an zanata account for me.
>>
>
> Welcome aboard Hayashi-san. Thanks for willing to help!
>
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>
> Red Hat EMEA 
>
> sbona...@redhat.com
> 
>
> *Red Hat respects your work life balance. Therefore there is no need to
> answer this email out of your office hours.*
>
>
> ___
> 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/VL5M4H5OBJSBIVKPOXQ2IPPIHCHHEP3G/
>
___
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/NPKQSOVXLY5ILPIFN6S2QD4BQFY4G7EM/