- Users - oVirt List Archives

Move Export Domain across web via NFS verses Rsync Image
by Matt Simonsen 31 Jan '18

31 Jan '18

Hello all, We have a several oVirt data centers mostly using oVirt 4.1.9 and NFS backed storage. I'm planning a move for what will eventually be an exported VM, from one physical location to another one. Is there any reason it would be problematic to export the image and then use rsync to migrate the image directory to a different export domain? Thanks, Matt

3 3

cloud-init not setting gateway
by Maton, Brett 31 Jan '18

31 Jan '18

Are there any known issues with cloud-init not setting the network gateway ? I'm trying to create a host with the ansible roles, all is Ok apart from network settings. Ansible code: - block: - name: Authenticate ovirt_auth: password: *** url: "https://***/ovirt-engine/api" username: admin@internal - name: "Create Virtual Machines" ovirt_vms: auth: "{{ ovirt_auth }}" clone: false cloud_init: custom_script: "touch /etc/cloud/cloud-init.disabled" dns_search: *** dns_servers: "*** ***" host_name: *** nic_boot_protocol: static nic_gateway: "***" nic_ip_address: "***" nic_name: eth0 nic_netmask: "***" nic_on_boot: true cluster: Default comment: "Ansible Created" name: "***" state: present stateless: false storage_domain: "***" template: CentOS7_1711_could_init timeout: 600 register: ovirt_vm always: - name: "Sign Out" ovirt_auth: ovirt_auth: "{{ ovirt_auth }}" state: absent I've also tried using the web-ui, again most 'things' get set but not the gateway which is a killer as I can only access the VM with remote console until I set the gateway. Regards, Brett

3 3

[ANN] oVirt 4.1.9 Release is now available
by Lev Veyde 31 Jan '18

31 Jan '18

The oVirt Project is pleased to announce the availability of the oVirt 4.1.9 release, as of January 24th, 2017 This update is the ninth in a series of stabilization updates to the 4.1 series. Please note that no further updates will be issued for the 4.1 series. We encourage users to upgrade to 4.2 series to receive new features and updates. This release is available now for: * Red Hat Enterprise Linux 7.4 or later * CentOS Linux (or similar) 7.4 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.4 or later * CentOS Linux (or similar) 7.4 or later * oVirt Node 4.1 See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Live is already available [2] - oVirt Node will be available soon [2] Additional Resources: * Read more about the oVirt 4.1.9 release highlights: http://www.ovirt.org/release/4.1.9/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.1.9/ [2] http://resources.ovirt.org/pub/ovirt-4.1/iso/ -- Lev Veyde Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

6 7

ovirt-guest-agent.service has broken in Debian 8 virtual machines after updates hosts to 4.2
by Алексей Максимов 30 Jan '18

30 Jan '18

Hello, oVirt guru's I just successfully updated my oVirt HE to 4.2. But after I upgraded all hosts and virtual machine restart, the ovirt-guest-agent.service has stopped running in virtual machines with Debian Jessie. ---- # lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 8.10 (jessie) Release: 8.10 Codename: jessie ---- # dpkg -l | grep ovirt ii ovirt-guest-agent 1.0.10.2.dfsg-2+deb8u1 all daemon that resides within guest virtual machines Note: This package installed from Debian Jessie official repo ---- # systemctl status ovirt-guest-agent.service ● ovirt-guest-agent.service - oVirt Guest Agent Loaded: loaded (/lib/systemd/system/ovirt-guest-agent.service; disabled) Active: failed (Result: exit-code) since Tue 2018-01-02 17:36:29 MSK; 23min ago Main PID: 3419 (code=exited, status=1/FAILURE) Jan 02 17:36:29 APP3 systemd[1]: Started oVirt Guest Agent. Jan 02 17:36:29 APP3 systemd[1]: ovirt-guest-agent.service: main process exited, code=exited, status=1/FAILURE Jan 02 17:36:29 APP3 systemd[1]: Unit ovirt-guest-agent.service entered failed state. ---- >From /var/log/ovirt-guest-agent/ovirt-guest-agent.log: MainThread::INFO::2018-01-02 17:36:29,764::ovirt-guest-agent::57::root::Starting oVirt guest agent MainThread::ERROR::2018-01-02 17:36:29,768::ovirt-guest-agent::138::root::Unhandled exception in oVirt guest agent! Traceback (most recent call last): File "/usr/share/ovirt-guest-agent/ovirt-guest-agent.py", line 132, in <module> agent.run(daemon, pidfile) File "/usr/share/ovirt-guest-agent/ovirt-guest-agent.py", line 63, in run self.agent = LinuxVdsAgent(config) File "/usr/share/ovirt-guest-agent/GuestAgentLinux2.py", line 375, in __init__ AgentLogicBase.__init__(self, config) File "/usr/share/ovirt-guest-agent/OVirtAgentLogic.py", line 171, in __init__ self.vio = VirtIoChannel(config.get("virtio", "device")) File "/usr/share/ovirt-guest-agent/VirtIoChannel.py", line 150, in __init__ self._stream = VirtIoStream(vport_name) File "/usr/share/ovirt-guest-agent/VirtIoChannel.py", line 131, in __init__ self._vport = os.open(vport_name, os.O_RDWR) OSError: [Errno 2] No such file or directory: '/dev/virtio-ports/com.redhat.rhevm.vdsm' ---- Before updating to version 4.2 (for version 4.1.8) everything worked fine. Please help solve the problem

4 7

[ANN] oVirt 4.2.1 Fourth Release Candidate is now available
by Lev Veyde 30 Jan '18

30 Jan '18

The oVirt Project is pleased to announce the availability of the oVirt 4.2.1 Fourth Release Candidate, as of January 30th, 2017 This update is a release candidate of the first in a series of stabilization updates to the 4.2 series. This is pre-release software. This pre-release should not to be used in production. This release is available now for: * Red Hat Enterprise Linux 7.4 or later * CentOS Linux (or similar) 7.4 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.4 or later * CentOS Linux (or similar) 7.4 or later * oVirt Node 4.2 See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Node will be available soon [2] Additional Resources: * Read more about the oVirt 4.2.1 release highlights: http://www.ovirt.org/release/4. <http://www.ovirt.org/release/4.2.1/>2 <http://www.ovirt.org/release/4.2.1/>. <http://www.ovirt.org/release/4.2.1/> 1 <http://www.ovirt.org/release/4.2.1/>/ <http://www.ovirt.org/release/4.2.1/> * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4. <http://www.ovirt.org/release/4.2.1/>2 <http://www.ovirt.org/release/4.2.1/>. <http://www.ovirt.org/release/4.2.1/> 1 <http://www.ovirt.org/release/4.2.1/>/ <http://www.ovirt.org/release/4.2.1/> [2] http://resources.ovirt.org/pub/ovirt-4. <http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>2-pre <http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>/iso/ <http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/> -- Lev Veyde Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

Nvidia Tesla M60 Direct GPU-Passthrough giving issues + VNC
by Ravyu Sivakumaran 30 Jan '18

30 Jan '18

Hi, I am running an Ovirt host on a SuperMicro SuperServer 2028GR-TRH equipped with 2x2 Tesla M60s (they are dual GPU Cards). I've followed this guide- https://www.ovirt.org/develop/release-management/features/virt/hostdev-pass… and managed to get a Windows 10 Enterprise guest running with one GPU attached to it. The windows guest successfully detects the single M60 GPU and I can install the latest Tesla drivers (390.65) on it with no problem. However, the GPU refuses to do any work whatsoever. The control panel says the GPU is being used for compute and not as a VGA adapter (shows up as inactive on the activity monitor). Nvidia's GPUModeSwitcher tool tells me that the GPU is in Graphics mode, so there is a driver issue here. I have access to the GRID Drivers. However I'm not sure why I'd need them as I'm only doing a direct-passthrough, not GPU Virtualization. Any ideas? Also, after activating Device-Passthrough, I'm unable to access my VM's via the Hosts' VNC anymore. I get an "unable to connect" error. Im currently accessing the Guests with a direct VNC connection. Problem is, I can't clone/create new VMs anymore because of this. I must've done something wrong, not sure what. Thanks in advance! -- Yours Faithfully Ravyu

2 1

SSL Workflow for oVirt
by Gabriel Stein 29 Jan '18

29 Jan '18

Hi all, I think that I found a way to solve the problem from: http://lists.ovirt.org/pipermail/users/2018-January/086441.html and I'm trying to fix it. But my servers are in Production(50%) and I found that are some errors with my SSL Certificates. ## What I need now? Fixes all certificates problems using my Freeipa generated certificates: vdsmclient* on hosts, ovirt-engine communication ssl certificates on hosted-engine. I made with Freeipa(internal) the certificates for ovirt-engine( only apache - self hosted) and Hosts(vsdmclient and vdsmkey....) and replaced using this howto: https://gist.github.com/qrkourier/9c9ac3e8b190dcb91d3767179d5a39ea ## Now ovirt-engine can't contact a Host(Non Responsive) with the errors(Yes, I have a Backup from all old certificates): *VDSM host.domain.tld command GetCapabilitiesVDS failed: General SSLEngine problem* On engine.log: *2018-01-23 13:33:40,160+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-23) [] Command 'GetAllVmStatsVDSCommand(HostName = host.domain.tld, VdsIdVDSCommandParametersBase:{hostId='d6bc650b-7edd-4019-b316-54313217880f'})' execution failed: VDSGenericException: VDSNetworkException: General SSLEngine problem* *2018-01-23 13:33:40,160+01 INFO [org.ovirt.engine.core.vdsbroker.monitoring.PollVmStatsRefresher] (EE-ManagedThreadFactory-engineScheduled-Thread-23) [] Failed to fetch vms info for host 'host.domain.tld' - skipping VMs monitoring.* ## I read, that ovirt-engine generates certificates for all hosts and it uses his own CA. Questions: - How can I fix the communication from hosted-engine and vsdm on hosts? Should I copy my Freeipa ca.crt and replace the ca.der file on */etc/pki/ovirt-engine/certs*? - Should I change the engine.cer certificate from */etc/pki/ovirt-engine/certs *with my Certificate made using Freeipa? - How to do that properly? - Where can I find a complete workflow from SSL Certificates from oVirt? What certificates should I change? ## I found some links that to me are confusing(or I'm just dumb), I will take my end solution and do a howto to all: - https://www.ovirt.org/develop/release-management/features/infra/pki/ - how updated is that? I can't overwrite a ca from ovirt-engine? - https://www.ovirt.org/documentation/admin-guide/appe-oVirt_and_SSL/ *- * *Note:** Using a commercially issued certificate for HTTPS connections does not affect the certificate used for authentication between your Engine and hosts. They will continue to use the self-signed certificate generated by the Engine... * ... Well, why I keep receiving errors with the self-signed CA from ovirt-engine and the disk uploads?(*Unable to upload image to disk a-b-c-d-e due to a network error. Make sure ovirt-imageio-proxy service is installed and configured, and ovirt-engine's certificate is registered as a valid CA in the browser. The certificate can be fetched from https://<engine_url>/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA* ) Thanks in Advance! Best Regards, Gabriel PS: I would help with the oVirt Wiki if needed, I would follow the rhce path and do the rhcs certification too, will be nice to study a lot. Gabriel Stein ------------------------------ Gabriel Ferraz Stein Tel.: +49 (0) 170 2881531

2 1

No master storage domain, force select?
by Jure Kranjc 29 Jan '18

29 Jan '18

This is a cryptographically signed message in MIME format. --------------ms000006050602060305000308 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Language: en-US Hello, is there a way to force select master storage domain? I have three data=20 domains, we had some storage problems and now none of the domains is=20 master. I cannot activate any because I should first activate the master = one. Any help appreciated. --------------ms000006050602060305000308 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC ChcwggUAMIID6KADAgECAhADS+4XH7fhBjcv1HJCQL0qMA0GCSqGSIb3DQEBCwUAMGUxCzAJ BgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2Vy dC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IEFzc3VyZWQgSUQgUm9vdCBDQTAeFw0xNDExMTgx MjAwMDBaFw0yNDExMTgxMjAwMDBaMGkxCzAJBgNVBAYTAk5MMRYwFAYDVQQIEw1Ob29yZC1I b2xsYW5kMRIwEAYDVQQHEwlBbXN0ZXJkYW0xDzANBgNVBAoTBlRFUkVOQTEdMBsGA1UEAxMU VEVSRU5BIFBlcnNvbmFsIENBIDMwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDG pbsfVYL0pTRyFHJlm1/V6qBo2JuCiU9TYpx7jM4O2tQyDq8bjMum69vg6wM0lMGHflMgqB75 GxeKfQFmEldoXi2cLishqFUvU2cJeM3SaRsLk2BsuCgTzh9NsYgmrUX60KHOq7eYKVZxbPFW JF2nMOBuMXNu2qBXTGSLeLXHnNvG3r7TLzGg1oA5teAxQE6Eo8ySSeIXbP7wZB76urwlh51P IbrJZjkDjdQVELh7OlTP1WO6T/Hf6BsEfeFcpoa1e+MW/lw0VetTPPHQ15HYKYP2WYohHxzD iC+QUwE7UZVBlp9cXIpwHuDzSibc5RG3z0n/j2SQCx0Dk5FMAUErAgMBAAGjggGmMIIBojAS BgNVHRMBAf8ECDAGAQH/AgEAMA4GA1UdDwEB/wQEAwIBhjB5BggrBgEFBQcBAQRtMGswJAYI KwYBBQUHMAGGGGh0dHA6Ly9vY3NwLmRpZ2ljZXJ0LmNvbTBDBggrBgEFBQcwAoY3aHR0cDov L2NhY2VydHMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0QXNzdXJlZElEUm9vdENBLmNydDCBgQYD VR0fBHoweDA6oDigNoY0aHR0cDovL2NybDMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0QXNzdXJl ZElEUm9vdENBLmNybDA6oDigNoY0aHR0cDovL2NybDQuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0 QXNzdXJlZElEUm9vdENBLmNybDA9BgNVHSAENjA0MDIGBFUdIAAwKjAoBggrBgEFBQcCARYc aHR0cHM6Ly93d3cuZGlnaWNlcnQuY29tL0NQUzAdBgNVHQ4EFgQU8CHpSXdzn4WuGDvoUnAU Bu1C7sowHwYDVR0jBBgwFoAUReuir/SSy4IxLVGLp6chnfNtyA8wDQYJKoZIhvcNAQELBQAD ggEBADrCGyv+Y967YbS5R6j8fAWxJiAiUZvIPfn1xVgesF6jspwCQY8xGn/MG04d+Jh97I8I /Xfx29JEEFq2rQmw4PxiO9RiDZ7xoDxNd4rrRDR7jrtOKQP8J+o+ah0vSOP62hnD/zPS7NRM tIyVS2G277KAL5fIR62ngr984fmJghDv0bsjGAmeu3EP0xhUsDJT61IoAGoKBnxBPAeg3WXs dSm4Gn7btyvakeyFtYebr2KmOBSa28PRqGSDur56aZhJoM2eMzc6prmvGwwtAzRsc5t2OsKR uHWV6O3anP2K27jGZR2bi1VX1NQUvIbpVNTuwjm+XcZtsa/AAJF9KGkEseAwggUPMIID96AD AgECAhAIjN7NyFkWCGXu+LbfMlIUMA0GCSqGSIb3DQEBCwUAMGkxCzAJBgNVBAYTAk5MMRYw FAYDVQQIEw1Ob29yZC1Ib2xsYW5kMRIwEAYDVQQHEwlBbXN0ZXJkYW0xDzANBgNVBAoTBlRF UkVOQTEdMBsGA1UEAxMUVEVSRU5BIFBlcnNvbmFsIENBIDMwHhcNMTcxMTE0MDAwMDAwWhcN MjAxMTE0MTIwMDAwWjBHMQswCQYDVQQGEwJTSTESMBAGA1UEBxMJTGp1YmxqYW5hMQ4wDAYD VQQKEwVBcm5lczEUMBIGA1UEAxMLSnVyZSBLcmFuamMwggEiMA0GCSqGSIb3DQEBAQUAA4IB DwAwggEKAoIBAQCgHE2xBKE9iUzRk9FUDtg8mDmUj0HNXP38LsV/md9bkIGuCqxfig7D1Mq3 5Bf15GuYp5bii2scJqYNkN0haf2y27GO2/VsQLvdonHr7iRpltqoSbg8INXyedjDsnnF970e aiQc260SxV8eWFua4CS92mykJIz1koU1du0u4nqoM0yoh4ovIdKWeSmFN3C1uEukAk8jycAM gup39xXCjB+A+V0RA3f8/re2dsIrNG672QrUIHIyAksH1bZztmlVXZYu+qSKwVuuyTb5wkLW TwSZ01MI9jXE9Qy65FzMWVZELTTUcGDB359EPjy3n04uNsp3oGP9/0mhuI7VmGDEQ4CXAgMB AAGjggHTMIIBzzAfBgNVHSMEGDAWgBTwIelJd3Ofha4YO+hScBQG7ULuyjAdBgNVHQ4EFgQU kK/eYmNE8toxdJaCsjvO0lhb1sUwDAYDVR0TAQH/BAIwADAfBgNVHREEGDAWgRRqdXJlLmty YW5qY0Bhcm5lcy5zaTAOBgNVHQ8BAf8EBAMCBaAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsG AQUFBwMEMEMGA1UdIAQ8MDowOAYKYIZIAYb9bAQBAjAqMCgGCCsGAQUFBwIBFhxodHRwczov L3d3dy5kaWdpY2VydC5jb20vQ1BTMHUGA1UdHwRuMGwwNKAyoDCGLmh0dHA6Ly9jcmwzLmRp Z2ljZXJ0LmNvbS9URVJFTkFQZXJzb25hbENBMy5jcmwwNKAyoDCGLmh0dHA6Ly9jcmw0LmRp Z2ljZXJ0LmNvbS9URVJFTkFQZXJzb25hbENBMy5jcmwwcwYIKwYBBQUHAQEEZzBlMCQGCCsG AQUFBzABhhhodHRwOi8vb2NzcC5kaWdpY2VydC5jb20wPQYIKwYBBQUHMAKGMWh0dHA6Ly9j YWNlcnRzLmRpZ2ljZXJ0LmNvbS9URVJFTkFQZXJzb25hbENBMy5jcnQwDQYJKoZIhvcNAQEL BQADggEBAMKWUMYBnUkSdz/tVYzPwEamsxN4QmVVpFzDogZxBspz1p/F9i+dyIPuZHP6/ahm ru3lLvtHT+SH+8YZ1lTeu25Y64gHBsAEGqR2wRt35ZX72+ekU2U8zCA+2QnYD3ejeGSfUuNr Bz9k6JHxg/d2+A4sZI4L2VXrFOnLMTWmxeFN5lS4l2UU72Ckjs6xrb6RUHBqp0XJJs8GGR64 lZjrALDewuZk+Gb6oua1hKNw7obTFLTw+1gKaV+hyOFmcP95iHy/mESGcz+JJz7EjzmbFkQs QS2e/gRmxwZMIs5yWTJXnKjQE9/8GKOwkCqWL0Fd5IlFUEByRo7NdyASSw587rkxggOjMIID nwIBATB9MGkxCzAJBgNVBAYTAk5MMRYwFAYDVQQIEw1Ob29yZC1Ib2xsYW5kMRIwEAYDVQQH EwlBbXN0ZXJkYW0xDzANBgNVBAoTBlRFUkVOQTEdMBsGA1UEAxMUVEVSRU5BIFBlcnNvbmFs IENBIDMCEAiM3s3IWRYIZe74tt8yUhQwDQYJYIZIAWUDBAIBBQCgggH3MBgGCSqGSIb3DQEJ AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTE4MDExODA1MjYwNFowLwYJKoZIhvcN AQkEMSIEILwdN21ICV8CYh//3XjmddP6J/SHbLUwZQqiAdt20otYMGwGCSqGSIb3DQEJDzFf MF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgIC AIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgYwGCSsGAQQBgjcQ BDF/MH0waTELMAkGA1UEBhMCTkwxFjAUBgNVBAgTDU5vb3JkLUhvbGxhbmQxEjAQBgNVBAcT CUFtc3RlcmRhbTEPMA0GA1UEChMGVEVSRU5BMR0wGwYDVQQDExRURVJFTkEgUGVyc29uYWwg Q0EgMwIQCIzezchZFghl7vi23zJSFDCBjgYLKoZIhvcNAQkQAgsxf6B9MGkxCzAJBgNVBAYT Ak5MMRYwFAYDVQQIEw1Ob29yZC1Ib2xsYW5kMRIwEAYDVQQHEwlBbXN0ZXJkYW0xDzANBgNV BAoTBlRFUkVOQTEdMBsGA1UEAxMUVEVSRU5BIFBlcnNvbmFsIENBIDMCEAiM3s3IWRYIZe74 tt8yUhQwDQYJKoZIhvcNAQEBBQAEggEACozEx+i2cc/jB1De3hwoILq4fKLPrZ1isUKE0C7G EuRsT9cPhgAkA7SLZUbaiLqnekwY8q83vTDHlKzcghwgnTb5JGRrIKdgA1gaN3LSqN6Gp6pJ mAcz4/M7uhPr2t1e7DpOVO5tx/TaDhsobeRCcc7YvkxXdCnEJtLIX3TGBAOJba/XHNDhIS21 6jQh3PyY+d96HMiS77QaUXLNtg7V3Yf7sA4ox7xfOOTXXCCRbrDenNYFvehm0513dVjHG3l6 G3F2IWpeEWcfkUsAoAhFgAN/9ipAOrDXy9iMQoFdQ2PcLdYMZdAQKZfi2r7M6T74d6h8m1/L tyGSXZOOeSQwvgAAAAAAAA== --------------ms000006050602060305000308--

2 2

PHX planned maintenance 29.01.2018 @19:00 GMT
by Evgheni Dereveanchin 29 Jan '18

29 Jan '18

Hi everyone, Planned works are going to be performed in the PHX data center today. They are related to core networking hardware upgrades and may cause short connectivity loss to services hosted by the oVirt project, including: * Jenkins CI * Package repositories * project website * mailing lists The maintenance window starts at 19:00 GMT and has a duration of one hour. I will pause CI job execution before the maintenance window so builds will be queued and executed after network upgrades are implemented to decrease the possibility of false positives. I will follow up with any further updates. -- Regards, Evgheni Dereveanchin

1 1

NFS sync vs async
by Jean-Francois Courteau 29 Jan '18

29 Jan '18

Hello there, At first I thought I had a performance problem with virtio-scsi on Windows, but after thorough experimentation, I finally found that my performance problem was related to the way I share my storage using NFS. Using the settings suggested on the oVirt website for the /etc/exports file, I implemented the following line: /storage *(rw,sync,no_subtree_check,all_squash,anonuid=36,anongid=36) The underlying filesystem is ext4. In the end, whatever the VM I am running through this NFS export, I get extremely poor write performance, like sub-100 IOPS (my disks usually can do 800-1k). Under the hood, iotop shows that my host IO is all taken up by jbd2, and if I understand correctly, it is the ext4 logging process. I have read that using the "async" option in my NFS export is unsafe, like if my host crashes during a write operation, it could corrupt my VM Disks. What is the best combination of filesystem / settings if I want to go with NFS sync? Is someone getting good performance with the same options as me? if so, why do I get such abysmal IOPS numbers? Thanks! J-F Courteau

1 0