- Users - oVirt List Archives

libvirtError: Cannot get interface MTU
by Tyson Landon 10 Feb '17

10 Feb '17

I am new to Ovirt and have a test cluster running with 2 hosts. I have errors when live migrating that started after I installed a new NIC in one host. Live migrate was working fine before the changes. The vdsm log shows the errors below depending on if i am migrating from host1 or host2. Running ovs-vsctl list-br shows that the bridge exists. Ip a shows the interface is down. I do not know what a vdsm bridge is for or if the server just needs to restart a service to get things in order again. Have any of you seen this error before and were able to fix it? HOST 1 libvirtError: Cannot get interface MTU on 'vdsmbr_TK4cSEjh': No such device HOST 2 libvirtError: Cannot get interface MTU on 'vdsmbr_vqqOTlrR': No such device HOST 1 ovs-vsctl list-br vdsmbr_3fDBsCCF vdsmbr_TK4cSEjh vdsmbr_VWhs9soF HOST2 ovs-vsctl list-br vdsmbr_YBtJDFGg vdsmbr_qf3gXZdq vdsmbr_vqqOTlrR Thanks Tyson

2 4

Manually starting VMs via vdsClient (HE offline)
by Doug Ingham 10 Feb '17

10 Feb '17

Hi Guys, My Hosted-Engine has failed & it looks like the easiest solution will be to install a new one. Now before I try to re-add the old hosts (still running the guest VMs) & import the storage domain into the new engine, in case things don't go to plan, I want to make sure I'm able to bring up the guests on the hosts manually. The problem is vdsClient is giving me an "Unexpected exception", without much more info as to why it's failing. Any idea? [root@v0 ~]# vdsClient -s 0 list table | grep georep 9d1c3fef-498e-4c20-b124-01364d4d45a8 30455 georep-proxy Down [root@v0 ~]# vdsClient -s 0 continue 9d1c3fef-498e-4c20-b124-01364d4d45a8 Unexpected exception /var/log/vdsm/vdsm.log periodic/1063::WARNING::2017-02-08 17:57:52,532::periodic::276::virt.periodic.VmDispatcher::(__call__) could not run <class 'vdsm.virt.periodic.DriveWatermarkMonitor'> on ['65c9807c-7216-40b3-927c-5fd93bbd42ba', u'9d1c3fef-498e-4c20-b124-01364d4d45a8'] Cheers, -- Doug

4 12

Best way to shutdown and restart hypervisor?
by Gianluca Cecchi 10 Feb '17

10 Feb '17

Hello, what is considered the best way to shutdown and restart an hypervisor, supposing plain CentOS 7 host? For example to cover these scenarios: 1) update host from 4.0 to 4.1 2) planned maintenance to the cabinet where the server is located and take the opportunity to update also OS packages My supposed workflow: - put host into maintenance - yum update on host - shutdown os from inside host (because from power mgmt it is brutal power off / power on) --> should I get any warning from web admin gui in this case, even if the host was in maintenance mode? - power mgmt -> start from webadmin gui (or power on button/virtual button at host side?) Would be advisable to put inside power mgmt functionality some logic about os mgmt, so for example, if action is restart, first try to shutdown OS and only in case of failure power off/power on? Thanks in advance, Gianluca

4 6

Getting error while trying to add VmPool using ovirtsdk4 version of the python api
by Manuel Luis Aznar 10 Feb '17

10 Feb '17

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/metho…". 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

2 1

VDAgent
by Fernando Fuentes 10 Feb '17

10 Feb '17

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

2 8

How to change disk from thin to pre allocated
by ovirt＠timmi.org 10 Feb '17

10 Feb '17

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

2 5

Importing existing (dirty) storage domains
by Doug Ingham 09 Feb '17

09 Feb '17

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

1 0

Host DNS
by Todd Punderson 09 Feb '17

09 Feb '17

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

2 2

Info on oVirt 4.1 and qcow2 v3 format
by Gianluca Cecchi 09 Feb '17

09 Feb '17

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

3 2

[ANN] oVirt 4.1.1 Test compose
by Sandro Bonazzola 09 Feb '17

09 Feb '17

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

1 0