Getting error while trying to add VmPool using ovirtsdk4 version of the python api
by Manuel Luis Aznar
Hello there,
I am trying to add a VmPool to oVirt using the python ovirtSDK4 with
following lines:
I am omitting the import packages lines and connection lines.
system_service = connection.system_service()
vm_pools_service = system_service.vm_pools_service()
templates_service = system_service.templates_service()
clusters_service = system_service.clusters_service()
tplist = templates_service.list(search='name=prueba')
tpl=None
biggest=-1
for t in tplist:
ver = t.version
if ver.version_number > biggest:
biggest = ver.version_number
tid = t.id
tpl = t
c = None
for cluster in clusters_service.list():
if cluster.name == 'Pruebacluster':
c = cluster
pool = ovirtsdk4.types.VmPool(name='PRUEBA',size=1,type
=ovirtsdk4.types.VmPoolType('manual'),template=tpl,cluster=c)
vm_pools_service.add(pool=pool)
I am getting the following error:
Fault reason is "Request syntactically incorrect.". Fault detail is "For
correct usage, see:
https://ovirt.example.com/ovirt-engine/api/v4/model#services/vm-pools/met...".
HTTP response code is 400.
I am a newbie in using this version of the API, suppose this is quite easy
problem.
Thanks for all the answers to come,
Manuel
7 years, 9 months
VDAgent
by Fernando Fuentes
Team,
After a host update on my cluster, All of my Windows vm's running the
vdagent from the ovirt tools are running at 100% CPU utilization.
Any ideas why would this happen?
Regards,
--
Fernando Fuentes
ffuentes(a)txweather.org
http://www.txweather.org
7 years, 9 months
How to change disk from thin to pre allocated
by ovirt＠timmi.org
Hi oVirt List,
I'm trying to change the disk allocation policy of a VM disk and I'm not
able to perform this task via the oVirt front-end.
Is someone able to tell me how I can do that?
Best regards and thank you
Christoph
7 years, 9 months
Importing existing (dirty) storage domains
by Doug Ingham
Hi All,
My original HE died & was proving too much of a hassle to restore, so I've
setup a new HE on a new host & now want to import my previous data storage
domain with my VMs.
The problem is when I try to attach the new domain to the datacenter, it
hangs for a minute and then comes back with, "Failed to attach Storage
Domain data2 to Data Center Default"
It's a gluster volume, and I'm able to mount & write to it via the CLI on
the host, without issue.
It's also using the same gluster volume options as the initialized master
domain.
I get this in sanlock.log:
2017-02-09 14:54:57-0300 1698758 [9303]: s10:r12 resource
60455567-ad30-42e3-a9df-62fe86c7fd25:SDM:/rhev/data-center/mnt/glusterSD/localhost:data2/60455567-ad30-42e3-a9df-62fe86c7fd25/dom_md/leases:1048576
for 3,15,12533
2017-02-09 14:54:57-0300 1698758 [9303]: open error -5
/rhev/data-center/mnt/glusterSD/localhost:data2/60455567-ad30-42e3-a9df-62fe86c7fd25/dom_md/leases
2017-02-09 14:54:57-0300 1698758 [9303]: r12 acquire_token open error -5
2017-02-09 14:54:57-0300 1698758 [9303]: r12 cmd_acquire 3,15,12533
acquire_token -5
Any ideas?
--
Doug
7 years, 9 months
Host DNS
by Todd Punderson
I changed my DNS servers since installing my hosted engine and hosts. I've
manually set my /etc/resolv.conf to have the correct nameserver entries.
But I found when I rebooted that it was being overwritten. I did some
googling and found that in /var/lib/vdsm/persistence/netconf/nets/ovirtmgmt
(My management network name) there is a nameservers config that gets
applied when vdsm starts which updated my ifcfg files. I edited that file
to include my correct name servers.
Now, if I choose a host, go to the network interfaces tab, then click
"Setup Host Network" when I exit out with the "Save" checkbox checked, the
file in the vdsm directory is being changed back to my old nameserver entry.
I searched all over the hosted engine UI and I can't find where that's old
entry is coming from. Where do I go to change this?
Thanks
7 years, 9 months
Info on oVirt 4.1 and qcow2 v3 format
by Gianluca Cecchi
Hello,
after upgrading to oVirt 4.1 and setting cluster/datacenter to version 4,
new images and snapshots should be created in qcow2 v3 format, based on
bugzilla included in release notes:
https://bugzilla.redhat.com/827529
Correct?
What about existing disks? Is there any way to convert?
What in case I have an old disk, I create a snapshot in 4.1 and then delete
the snapshot? Will the live merged disk be in v3 format or v2?
Thanks,
Gianluca
7 years, 9 months
[ANN] oVirt 4.1.1 Test compose
by Sandro Bonazzola
The oVirt Project is pleased to announce the availability of the First
Test Compose of oVirt 4.1.1 for testing, as of February 9th, 2017
This is pre-release software. Please take a look at our community page[1]
to know how to ask questions and interact with developers and users.
All issues or bugs should be reported via oVirt Bugzilla[2].
This pre-release should not to be used in production.
This update is a test compose allowing to test fixes included in
ovirt-4.1.1 since
4.1.0 release.
See the release notes [3] for installation / upgrade instructions and a
list of new features and bugs fixed.
This release is available now for:
* Fedora 24 (tech preview)
* Red Hat Enterprise Linux 7.3 or later
* CentOS Linux (or similar) 7.3 or later
This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.3 or later
* CentOS Linux (or similar) 7.3 or later
* Fedora 24 (tech preview)
See the release notes draft [3] for installation / upgrade instructions and
a list of new features and bugs fixed.
Notes:
- oVirt Live, oVirt Node and oVirt Engine appliance has not been built for
this test compose
Additional Resources:
* Read more about the oVirt 4.1.1 release highlights:
http://www.ovirt.org/release/4.1.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] https://www.ovirt.org/community/
[2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt
[3] http://www.ovirt.org/release/4.1.1/
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
7 years, 9 months
web admin gui timeout changes in 4.1
by Gianluca Cecchi
Hello,
while in 4.0.6 it seemed perhaps too short and you got logged out, in 4.1
it seems very relaxed
Did the default values changed? In which measures?
Any way to tweak?
Thanks,
Gianluca
7 years, 9 months
Re: [ovirt-users] USB 2.0 compatibility -- RESOLVED!
by Jonathan Woytek
I was finally able to resolve this. So that maybe other users can find how
to fix this if they run into the same issues:
tl;dr:
Edit the virtual machine in question, go under Console, make sure SPICE is
chosen for graphics, and under "USB Redirection" choose "Native." When you
reboot the VM, it will have both UHCI and EHCI (2.0) controllers. Now, any
USB 2.0 devices that you attach will work correctly.
Long version:
I struggled with this for quite a while. While doing some additional
research, I found a note in the 4.1.0 release notes referencing BZ 1373223.
This particular note was for ppc64 architecture systems, but it curiously
said that enabling USB Redirection under SPICE would change the USB
controllers available on the host. I dug a little deeper into the bug
thread and found a couple of references that seemed to indicate that
x86/x86_64 exhibited the same behavior. Apparently, UHCI (1.1) is the
default because it supports SmartCards, but the EHCI (2.0) controller does
not. So, turning on USB Redirection under SPICE settings for the console
enables an EHCI controller, thereby enabling devices that require USB 2.0.
Personal opinion:
This is really obfuscated. It would be great if this switch lived somewhere
more obvious. Even if that doesn't happen, this should exist in a document
somewhere. Maybe it does and I couldn't find it, but I tried!
jonathan
--
Jonathan Woytek
http://www.dryrose.com
KB3HOZ
PGP: 462C 5F50 144D 6B09 3B65 FCE8 C1DC DEC4 E8B6 AABC
7 years, 9 months
some mismatch in mom versions in the repository
by Arman Khalatyan
Hi,
I just upgraded 4.0.6 to 4.1.
The 4.0 repository still there but after upgrade everything is ok except
the mom
The mom version in the 4.0 is higher than in 4.1 therefore it is not
upgraded from 4.1:
yum provides /usr/sbin/momd
mom-0.5.8-0.0.master.el7.centos.noarch : Dynamically manage system
resources on virtualization hosts
Repo : ovirt-4.1
Matched from:
Filename : /usr/sbin/momd
mom-0.5.8-1.el7.noarch : Dynamically manage system resources on
virtualization hosts
Repo : centos-ovirt-common-candidate
Matched from:
Filename : /usr/sbin/momd
mom-0.5.8-1.el7.noarch : Dynamically manage system resources on
virtualization hosts
Repo : centos-ovirt40-release
Matched from:
Filename : /usr/sbin/momd
mom-0.5.8-1.el7.centos.noarch : Dynamically manage system resources on
virtualization hosts
Repo : ovirt-4.0
Matched from:
Filename : /usr/sbin/momd
mom-0.5.8-1.el7.centos.noarch : Dynamically manage system resources on
virtualization hosts
Repo : @ovirt-4.0
Matched from:
Filename : /usr/sbin/momd
7 years, 9 months
