Re: Error in SeaBIOS

On Thu, Jan 31, 2019, 05:45 LIONS TECNOLOGIA Good night! > > I would like to have a help, I am starting this journey in virtualization > and I am having difficulty, I installed the ovirt but when I install a > virtual machine to test, it happens that it is black screen as described in > the

Error in SeaBIOS

Good night! I would like to have a help, I am starting this journey in virtualization and I am having difficulty, I installed the ovirt but when I install a virtual machine to test, it happens that it is black screen as described in the attachment. Anyone who has a little more experience could

[CQ]: 96998, 16 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 96998,16 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 96178,9 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

oVirt infra daily report - unstable production jobs - 721

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/721//artifact/exported-artifacts/upstream_report.html Cheers, Jenkins

[JIRA] (OVIRT-2664) OST runs engine 4.2 by default, misleading developers

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38914#comment-38914 ] Nir Soffer commented on OVIRT-2664: --- On Wed, Jan 30, 2019 at 9:45 PM Dan Kenigsberg wrote: > On Wed, Jan

[JIRA] (OVIRT-2664) OST runs engine 4.2 by default, misleading developers

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38913#comment-38913 ] danken commented on OVIRT-2664: --- On Wed, Jan 30, 2019 at 8:55 PM Nir Soffer wrote: > > When creating OST manual

[JIRA] (OVIRT-2664) OST runs engine 4.2 by default, misleading developers

Nir Soffer created OVIRT-2664: - Summary: OST runs engine 4.2 by default, misleading developers Key: OVIRT-2664 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2664 Project: oVirt - virtualization made

TAISTE: Hyperkitty and Unicode

Quack, This is a test! 日本語を分かりますか？ \_o< signature.asc Description: OpenPGP digital signature ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement:

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #3372 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #3371 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct vdsm_standard-check-patch

Failed to run project_setup.sh for: #2406 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[CQ]: 97109, 12 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 97109,12 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 96178,9 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #3369 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JIRA] (OVIRT-2663) Please add ManageIQ Hammer-1 to glance repository

sbonazzo created OVIRT-2663: --- Summary: Please add ManageIQ Hammer-1 to glance repository Key: OVIRT-2663 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2663 Project: oVirt - virtualization made easy

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #3366 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr

Failed to run project_setup.sh for: #1173 containerized-data-importer [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr

Failed to run project_setup.sh for: #1172 containerized-data-importer [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[CQ]: 96903, 16 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 96903,16 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 96178,9 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #3362 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #3360 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #3358 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

Build failed in Jenkins: system-sync_mirrors-centos-qemu-ev-release-el7-x86_64 #1740

See Changes: [Evgheni Dereveanchin] build Node-NG on VMs with large disk -- Started by timer [EnvInject] - Loading node environment

[CQ]: 5e928a1 (ovirt-ansible-hosted-engine-setup) failed "ovirt-master" system tests

Change 5e928a1 (ovirt-ansible-hosted-engine-setup) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For