- Users - oVirt List Archives

rest api
by David David 24 Oct '15

24 Oct '15

Hi. ovirt-engine 3.5.1. Can't shutdown a VM. Getting the error message: HTTP Status 405 - ------------------------------ *type* Status report *message* *description* *The specified HTTP method is not allowed for the requested resource ().* ------------------------------ JBoss Web/7.0.13.Final I do like this: https://10.64.0.222/api/vms/7c4072ae-8da1-49dc-ad1e-b869d47eb215/shutdown also when exporting VM or starting, etc, the above error appears.

2 1

Testing self hosted engine in 3.6: hostname not resolved error
by Gianluca Cecchi 23 Oct '15

23 Oct '15

Hello, playing with an environment where I have a CentOS 7.1 + updates server with 3.6 repos configured. no DNS resolution in place. running the command hosted-engine --deploy I initially get, during the prompts inside setup, the message if I want to set hostname for the sh engine and if I want to setup /etc/hosts of hypervisor and sh engine so that it will add them with clud-init, that translates in these lines inside log file: 2015-10-21 15:45:29 DEBUG otopi.context context.dumpEnvironment:510 ENV OVEHOSTED_VM/cloudinitInstanceDomainName=str:'localdomain.local' 2015-10-21 15:45:29 DEBUG otopi.context context.dumpEnvironment:510 ENV OVEHOSTED_VM/cloudinitInstanceHostName=str:'shengine.localdomain.local' 2015-10-21 15:45:29 DEBUG otopi.context context.dumpEnvironment:510 ENV OVEHOSTED_VM/cloudinitRootPwd=str:'**FILTERED**' 2015-10-21 15:45:29 DEBUG otopi.context context.dumpEnvironment:510 ENV OVEHOSTED_VM/cloudinitVMDNS=str:'192.168.122.1' 2015-10-21 15:45:29 DEBUG otopi.context context.dumpEnvironment:510 ENV OVEHOSTED_VM/cloudinitVMETCHOSTS=bool:'True' But then I get the error related to failure of sh engine hostname resolution and installation terminates, with these finale lines in log file..... 2015-10-21 15:45:29 DEBUG otopi.context context.dumpEnvironment:510 ENV SYSTEM/reboot=bool:'False' 2015-10-21 15:45:29 DEBUG otopi.context context.dumpEnvironment:510 ENV SYSTEM/rebootAllow=bool:'True' 2015-10-21 15:45:29 DEBUG otopi.context context.dumpEnvironment:510 ENV SYSTEM/rebootDeferTime=int:'10' 2015-10-21 15:45:29 DEBUG otopi.context context.dumpEnvironment:514 ENVIRONMENT DUMP - END 2015-10-21 15:45:29 DEBUG otopi.context context._executeMethod:142 Stage pre-terminate METHOD otopi.plugins.otopi.dialog.cli.Plugin._pre_terminate 2015-10-21 15:45:29 DEBUG otopi.context context._executeMethod:148 condition False 2015-10-21 15:45:29 INFO otopi.context context.runSequence:427 Stage: Termination 2015-10-21 15:45:29 DEBUG otopi.context context.runSequence:431 STAGE terminate 2015-10-21 15:45:29 DEBUG otopi.context context._executeMethod:142 Stage terminate METHOD otopi.plugins.otopi.dialog.human.Plugin._terminate 2015-10-21 15:45:29 DEBUG otopi.context context._executeMethod:142 Stage terminate METHOD otopi.plugins.otopi.dialog.machine.Plugin._terminate 2015-10-21 15:45:29 DEBUG otopi.context context._executeMethod:148 condition False 2015-10-21 15:45:29 DEBUG otopi.context context._executeMethod:142 Stage terminate METHOD otopi.plugins.otopi.core.log.Plugin._terminate and the message of a generated answer file. Why does it ask and then fails? Can I re-run using the answer file? In this case do I have to pre-insert sh engine hostname inside /etc/hosts of hypervisor? Thanks. Gianluca

3 22

Change host using php api
by Shanil S 23 Oct '15

23 Oct '15

Hi All, I would like to change the host of a vm using the api call. I tried it by using the following xml but didn't work <action> <vm> <initialization> <cloud_init> <host> <name>compute11</name> </host> </cloud_init> </initialization> </vm> </action> Could you please check it ? -- Regards Shanil

1 0

Can´t use a VM Network VLAN, because the Virtual Machines inside can't reach the Gateway
by Julián Tete 23 Oct '15

23 Oct '15

Hi Friends of oVirt I'm trying to migrate my company from VMware to oVirt. In my final tests, I set up 2 more VLANs in oVirt, (VM VLANs) The Virtual Machines in these VLANs, can be reached from the external IPs from the net range, but from the Virtual machines only can ping the Host with the Bridge and itself, can't reach the gateway. ¿? I configured a IP Forwarding in the Host with the virtual machine, and nothing changes... Any idea ? This is the last duty before embrace oVirt in the company. Look to the VLAN 100 configuration (My desired VM Network): http://postimg.org/image/7hrog0a2n/ http://postimg.org/image/68b40i1vr/ http://postimg.org/image/lu6mlshgp/ http://postimg.org/image/540o1qc0t/ http://postimg.org/image/4kyg787bt/ http://postimg.org/image/v7ralh7zb/ http://postimg.org/image/kn903cl03/ For any idea, thanks in advance

6 12

trunk mode for getting vlan into vms.
by Nathanaël Blanchet 22 Oct '15

22 Oct '15

As explained here http://blog.davidvassallo.me/2012/05/05/kvm-brctl-in-linux-bringing-vlans-t… , does it exist any way to do the same with ovirt hosts? (e.g. vlan at the bridge level and untagged by the nics vm themselves) -- Nathanaël Blanchet Supervision réseau Pôle Infrastrutures Informatiques 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

2 1

All host non operational after engine upgrade
by Jonas Israelsson 22 Oct '15

22 Oct '15

Greetings. Upgraded my Engine from a pre 3.6 version (not sure about the version, but it's only a month old or so) to RC today and found to my great surprise all hosts marked as Non Operational. The cluster working fine just hours ago now have some mismatch with my hosts CPUs. The cluster is set to Opteron G4 and all hosts CPU have Opteron 4226 installed. 2015-10-19 20:23:09,509 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-62) [36da0975] Correlation ID: 36da0975, Job ID: 44cf7ac9-5fe1-4151-9f6f-f1396124f179, Call Stack: null, Custom Event ID: -1, Message: Host patty.elementary.se does not comply with the cluster AMD_G4 emulated machines. The current cluster compatibility level supports [pc-i440fx-rhel7.2.0, pc-i440fx-2.1, pseries-rhel7.2.0] and the host emulated machines are pc-i440fx-rhel7.1.0,rhel6.3.0,pc-q35-rhel7.0.0,rhel6.1.0,rhel6.6.0,rhel6.2.0,pc,pc-q35-rhel7.1.0,q35,rhel6.4.0,rhel6.0.0,rhel6.5.0,pc-i440fx-rhel7.0.0. The error above look qemu to me so I tried reinstalling one of the node with the latest Ovirt-node snapshot downloaded from Jenkins --> http://jenkins.ovirt.org/job/ovirt-node_ovirt-3.6_create-iso-el7_merged/las… That made however no difference. I could use some help.. TIA Rgds Jonas

3 3

[ANN] oVirt 3.6.0 Third Release Candidate is now available for testing
by Sandro Bonazzola 22 Oct '15

22 Oct '15

[ANN] oVirt 3.6.0 Third Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of the Third Release Candidate of oVirt 3.6 for testing, as of October 22nd, 2015. This release is available now for Fedora 22, Red Hat Enterprise Linux 6.7, CentOS Linux 6.7 (or similar) and Red Hat Enterprise Linux 7.1, CentOS Linux 7.1 (or similar). This release supports Hypervisor Hosts running Red Hat Enterprise Linux 7.1, CentOS Linux 7.1 (or similar), Fedora 21 and Fedora 22. Highly experimental support for Debian 8.1 Jessie has been added too. This release of oVirt 3.6.0 includes numerous bug fixes. See the release notes [1] for an initial list of the new features and bugs fixed. Please refer to release notes [1] for Installation / Upgrade instructions. New oVirt Node ISO and oVirt Live ISO will be available soon as well[2]. Please note that mirrors[3] may need usually one day before being synchronized. Please refer to the release notes for known issues in this release. [1] http://www.ovirt.org/OVirt_3.6_Release_Notes [2] http://plain.resources.ovirt.org/pub/ovirt-3.6-pre/iso/ [3] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[ANN] oVirt 3.6.0 Third Release Candidate is now available for testing
by Sandro Bonazzola 22 Oct '15

22 Oct '15

The oVirt Project is pleased to announce the availability of the Third Release Candidate of oVirt 3.6 for testing, as of October 22nd, 2015. This release is available now for Fedora 22, Red Hat Enterprise Linux 6.7, CentOS Linux 6.7 (or similar) and Red Hat Enterprise Linux 7.1, CentOS Linux 7.1 (or similar). This release supports Hypervisor Hosts running Red Hat Enterprise Linux 7.1, CentOS Linux 7.1 (or similar), Fedora 21 and Fedora 22. Highly experimental support for Debian 8.1 Jessie has been added too. This release of oVirt 3.6.0 includes numerous bug fixes. See the release notes [1] for an initial list of the new features and bugs fixed. Please refer to release notes [1] for Installation / Upgrade instructions. New oVirt Node ISO and oVirt Live ISO will be available soon as well[2]. Please note that mirrors[3] may need usually one day before being synchronized. Please refer to the release notes for known issues in this release. [1] http://www.ovirt.org/OVirt_3.6_Release_Notes [2] http://plain.resources.ovirt.org/pub/ovirt-3.6-pre/iso/ [3] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

How to change the hosted engine VM RAM size after deploying
by Bond, Darryl 22 Oct '15

22 Oct '15

?I am testing 3.6 and created the hosted engine with too little RAM. How can I increase the RAM for the VM without re-deploying it? Regards Darryl ? ________________________________ The contents of this electronic message and any attachments are intended only for the addressee and may contain legally privileged, personal, sensitive or confidential information. If you are not the intended addressee, and have received this email, any transmission, distribution, downloading, printing or photocopying of the contents of this message or attachments is strictly prohibited. Any legal privilege or confidentiality attached to this message and attachments is not waived, lost or destroyed by reason of delivery to any person other than intended addressee. If you have received this message and are not the intended addressee you should notify the sender by return email and destroy all copies of the message and any attachments. Unless expressly attributed, the views expressed in this email do not necessarily represent the views of the company.

2 3

Failed to start domain due to internal error with sanlock
by Joris Dobbelsteen 21 Oct '15

21 Oct '15

This is a multi-part message in MIME format. ------_=_NextPart_001_01D10BDD.D1221AD9 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all, I'm currently using oVirt 3.5.4.2 on Centos 6 (single system, not a = cluster setup). After running for a long while (months), it has run into = an issue where it current cannot start a new VM. An internal error happens due to feature (0x01) from = libvirt...SanLock...New. If there are request for specific log files for analysis, please let me = know and I will include these. Does anyone recognize this issue or know a resolution? Best regards, - Joris Dobbelsteen ------_=_NextPart_001_01D10BDD.D1221AD9 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>Failed to start domain due to internal error with sanlock</TITLE> </HEAD> <BODY>  Hi all, I'm currently using oVirt 3.5.4.2 on Centos 6 (single system, not a = cluster setup). After running for a long while (months), it has run into = an issue where it current cannot start a new VM. An internal error happens due to feature (0x01) from = libvirt...SanLock...New. If there are request for specific log files for analysis, please let me = know and I will include these. Does anyone recognize this issue or know a resolution? Best regards, - Joris Dobbelsteen </BODY> </HTML> ------_=_NextPart_001_01D10BDD.D1221AD9--

2 3