Installing ovirt 3.6 on centOS 6.9 error
by dinushawww
Hi,
After install ovirt 3.5 on centOS 6.9, the ovirt engine has stopped. while
trying to start ovirt-engine it will say /usr/share/jboss-as not found. i
manually download jboss 7.1.1 final and installed in /usr/share and again
start the oviert-engine, this time it will start and then run the command
service ovirt-engine status, ovirt-engine stopped, pid file exist. please
help me to solve. i need to crate a lab using ovirt 3.5.
Thank You
Dinusha
6 years, 12 months
VDI - SPICE zero clients
by cmcl＠dneg.com
Hi,
I gt hold of a 10zig V1200-P for testing VDI under ovirt/RHEV, as I'd read that they support SPICE. However, I haven't found how to connect it successfully to a VM as yet. Has anyone had any experience with these using ovirt/RHEV? I haven't been able to find any manuals or support info on the 10zig website regarding these V1200-P zero clients. I've read that they are discontinuing SPICE support in the future, but I just need to be able to demonstrate it working for now.
Thanks for any help,
Cam
6 years, 12 months
Console issues in a distributed environment over NAT
by shailigum＠gmail.com
Hi all, i'm trying to deploy oVirt to manage multiple 'data centers' (really just very basic deployments of single hosts using local storage that are deployed in varying geographic locations), where each host/resource pool is (unfortunately) only accessible via NAT.
I've setup port-forwards for all functions, including SPICE/VNC, but am running into issues with the 'console' button in the GUI. When I initially added the host I added it using the NAT IP, however when trying to connect to console the console.vv file generated from the GUI references the local (private) IP of the host, instead of the NAT IP of the upstream firewall - so I have to manually open the file to change it to the NAT IP in order to connect to a VM's console.
This is a minor annoyance for me, but it does ultimately the tool will be used by others who are less comfortable with steps like these. Is there a way around this, to have the console.vv generate with the IP oVirt is using to connect to the host, instead of its discovered local IP?
Also if you can think of any other concerns I may encounter in a NAT deployment like this, please share! Thanks!
6 years, 12 months
NFS Mount on EMC VNXe3200 / User - Group 36:36 / Permission issue
by jeanbaptiste.coupiac＠nfrance.com
Hello,
I try to mount an NFS Data share from a EMC VNXe3200 export. Unfortunately,
NFS share cannot be mount, there is permission error.
(Indeed, after the same issue on another NFS ISO repo, I've change exported
directory user/group to 36:36, and O-Virt NFS mount was great).
So, I think issue with my VNXe3200 is regarding UID / GID owner on VNXe3200
side. After webex with EMC support, change owner / permission on VNXe side
seems not possible / supported.
Can I mount the NFS share with some options to avoid vdsm:kvm mounting issue
? Can I force mount with root ?
Regards,
Jean-Baptiste COUPIAC
6 years, 12 months
Engine Error
by Sakhi Hadebe
Hi,
I have just re-installed centOS 7 in 3 servers and have configured gluster
volumes following this documentation:
https://www.ovirt.org/blog/2016/03/up-and-running-with-ovirt-3-6/, But I
have installed
http://resources.ovirt.org/pub/yum-repo/ovirt-release42.rpm
package.
Hosted-engine --deploy is failing with this error:
"rhel7", "--virt-type", "kvm", "--memory", "16384", "--vcpus", "4",
"--network", "network=default,mac=00:16:3e:09:5e:5d,model=virtio",
"--disk",
"/var/tmp/localvm0nnJH9/images/eacac30d-0304-4c77-8753-6965e4b8c2e7/d494577e-027a-4209-895b-6132e6fc6b9a",
"--import", "--disk", "path=/var/tmp/localvm0nnJH9/seed.iso,device=cdrom",
"--noautoconsole", "--rng", "/dev/random", "--graphics", "vnc", "--video",
"vga", "--sound", "none", "--controller", "usb,model=none", "--memballoon",
"none", "--boot", "hd,menu=off", "--clock", "kvmclock_present=yes"],
"delta": "0:00:00.979003", "end": "2018-07-10 17:55:11.308555", "msg":
"non-zero return code", "rc": 1, "start": "2018-07-10 17:55:10.329552",
"stderr": "ERROR unsupported configuration: CPU mode 'custom' for x86_64
kvm domain on x86_64 host is not supported by hypervisor\nDomain
installation does not appear to have been successful.\nIf it was, you can
restart your domain by running:\n virsh --connect qemu:///system start
HostedEngineLocal\notherwise, please restart your installation.",
"stderr_lines": ["ERROR unsupported configuration: CPU mode 'custom' for
x86_64 kvm domain on x86_64 host is not supported by hypervisor", "Domain
installation does not appear to have been successful.", "If it was, you can
restart your domain by running:", " virsh --connect qemu:///system start
HostedEngineLocal", "otherwise, please restart your installation."],
"stdout": "\nStarting install...", "stdout_lines": ["", "Starting
install..."]}
I added the root user to the kvm group. but it ddn't work.
Can you please help me out. I have been struggling to deploy the hosted
engine.
--
Regards,
Sakhi
6 years, 12 months
PXE LOCALBOOT issue
by Michael Deffenbaugh
Hey all,
Provisioning a host with Foreman 1.17.1/Katello 3.6. The host
kickstarts fine but when it goes to reboot, iPXE fails to load the local
disk when the Foreman local boot kickstart menu (
https://github.com/theforeman/community-templates/blob/develop/provisioni...,
line 4-10) sends the command "LOCALBOOT 0". It simply fails and says "No
more network devices. No bootable device."
Is this a bug in iPXE? Any input would be greatly appreciated!
Regards,
Mike
6 years, 12 months
upload disk using python sdk
by 董青龙
Hi all,
I want to upload an disk using python sdk instead of web. Which class should I use? I could not find a "upload" method in "class Disk" an "class Disks" in "brokers.py"
Anyone can help? Thanks!
6 years, 12 months
Re: hosted-engine install fails (was: Engine Error)
by Yedidyah Bar David
On Tue, Jul 10, 2018 at 11:32 PM, Sakhi Hadebe <sakhi(a)sanren.ac.za> wrote:
> Hi,
>
> I did not select any CPU architecture. It doenst gove me the option to
> select one. It only states the number of virtual CPUs and the memory for
> the engine VM.
>
> Looking at the documentation of installing ovirt-release36.rpm....it does
> allow you to select te CPU, but not when installing ovirt-release42.rpm
>
> On Tuesday, July 10, 2018, Alastair Neil <ajneil.tech(a)gmail.com> wrote:
>
>> what did you select as your CPU architecture when you created the
>> cluster? It looks like the VM is trying to use a CPU type of "Custom", how
>> many nodes in your cluster? I suggest you specify the lowest common
>> denominator of CPU architecture (e.g. Sandybridge) of the nodes as the CPU
>> architecture of the cluster..
>>
>> On Tue, 10 Jul 2018 at 12:01, Sakhi Hadebe <sakhi(a)sanren.ac.za> wrote:
>>
>>> Hi,
>>>
>>> I have just re-installed centOS 7 in 3 servers and have configured
>>> gluster volumes following this documentation:
>>> https://www.ovirt.org/blog/2016/03/up-and-running-with-ovirt-3-6/, But
>>> I have installed
>>>
>>> http://resources.ovirt.org/pub/yum-repo/ovirt-release42.rpm
>>>
>>> package.
>>> Hosted-engine --deploy is failing with this error:
>>>
>>> "rhel7", "--virt-type", "kvm", "--memory", "16384", "--vcpus", "4",
>>> "--network", "network=default,mac=00:16:3e:09:5e:5d,model=virtio",
>>> "--disk", "/var/tmp/localvm0nnJH9/images/eacac30d-0304-4c77-8753-
>>> 6965e4b8c2e7/d494577e-027a-4209-895b-6132e6fc6b9a", "--import",
>>> "--disk", "path=/var/tmp/localvm0nnJH9/seed.iso,device=cdrom",
>>> "--noautoconsole", "--rng", "/dev/random", "--graphics", "vnc", "--video",
>>> "vga", "--sound", "none", "--controller", "usb,model=none", "--memballoon",
>>> "none", "--boot", "hd,menu=off", "--clock", "kvmclock_present=yes"],
>>> "delta": "0:00:00.979003", "end": "2018-07-10 17:55:11.308555", "msg":
>>> "non-zero return code", "rc": 1, "start": "2018-07-10 17:55:10.329552",
>>> "stderr": "ERROR unsupported configuration: CPU mode 'custom' for x86_64
>>> kvm domain on x86_64 host is not supported by hypervisor\nDomain
>>> installation does not appear to have been successful.\nIf it was, you can
>>> restart your domain by running:\n virsh --connect qemu:///system start
>>> HostedEngineLocal\notherwise, please restart your installation.",
>>> "stderr_lines": ["ERROR unsupported configuration: CPU mode 'custom' for
>>> x86_64 kvm domain on x86_64 host is not supported by hypervisor", "Domain
>>> installation does not appear to have been successful.", "If it was, you can
>>> restart your domain by running:", " virsh --connect qemu:///system start
>>> HostedEngineLocal", "otherwise, please restart your installation."],
>>> "stdout": "\nStarting install...", "stdout_lines": ["", "Starting
>>> install..."]}
>>>
>>
This seems to be in the phase where we create a local vm for the engine. We
do this with plain virt-install, nothing fancy. Searching the net for
"unsupported configuration: CPU mode 'custom'" finds other relevant
reports, you might want to check them. You can see the command in
bootstrap_local_vm.yml .
Please check/share versions of relevant packages (libvirt*, qemu*, etc) and
relevant logs (libvirt).
Also updating the subject line and adding Simone.
Best regards,
--
Didi
6 years, 12 months
Unable to start VM
by Alex K
Hi all,
I did a routine maintenance today (updating the hosts) to ovirt cluster
(4.2) and I have one VM that was complaining about an invalid snapshot.
After shutdown of VM the VM is not able to start again, giving the error:
VM Gitlab is down with error. Exit message: Bad volume specification
{'serial': 'b6af2856-a164-484a-afe5-9836bbdd14e8', 'index': 0, 'iface':
'virtio', 'apparentsize': '51838976', 'specParams': {}, 'cache': 'none',
'imageID': 'b6af2856-a164-484a-afe5-9836bbdd14e8', 'truesize': '52011008',
'type': 'disk', 'domainID': '142bbde6-ef9d-4a52-b9da-2de533c1f1bd',
'reqsize': '0', 'format': 'cow', 'poolID':
'00000001-0001-0001-0001-000000000311', 'device': 'disk', 'path':
'/rhev/data-center/00000001-0001-0001-0001-000000000311/142bbde6-ef9d-4a52-b9da-2de533c1f1bd/images/b6af2856-a164-484a-afe5-9836bbdd14e8/f3125f62-c909-472f-919c-844e0b8c156d',
'propagateErrors': 'off', 'name': 'vda', 'bootOrder': '1', 'volumeID':
'f3125f62-c909-472f-919c-844e0b8c156d', 'diskType': 'file', 'alias':
'ua-b6af2856-a164-484a-afe5-9836bbdd14e8', 'discard': False}.
I see also the following error:
VDSM command CopyImageVDS failed: Image is not a legal chain:
(u'b6af2856-a164-484a-afe5-9836bbdd14e8',)
Seems as a corrupt VM disk?
The VM had 3 snapshots. I was able to delete one from GUI then am not able
to delete the other two as the task fails. Generally I am not allowed to
clone, export or do sth to the VM.
Have you encountered sth similar. Any advice?
Thanx,
Alex
6 years, 12 months
Network Setup Error
by Sakhi Hadebe
Hi,
I have successfully installe oVirtNode 4.2 and gluster storage on CentOS 7.
I am now struggling to deploy the hosted engine.
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Unable
to create bridge virbr0: Package not installed"}
[ ERROR ] Failed to execute stage 'Closing up': Failed executing
ansible-playbook
What is the right package for bridging in centOS 7?
--
Regards,
Sakhi Hadebe
6 years, 12 months
