- Users - oVirt List Archives

Re: Windows Guest timezone
by Strahil 11 Apr '19

11 Apr '19

I used to set windows machines to use HW clock in UTC , which helped for dual-boot hardware machines. Can't you use that approach and never worry about DST? Best Regards, Strahil NikolovOn Apr 11, 2019 11:42, Stefano Danzi <s.danzi(a)hawai.it> wrote: > > Hello! > > I've a guest windows VM (Server 2016) and hardware clock in oVirt > machine configuration is GMT +1. > Now we are DST period and machine timezone is GMT +2. Engine Dashboard > warn me about timezone > mismatch between configuration and running VM. I can't see a setting to > enable DST on emulated hardware. > > Some ideas? > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/ENKC37PNVQEZ2…

1 0

Windows Guest timezone
by Stefano Danzi 11 Apr '19

11 Apr '19

Hello! I've a guest windows VM (Server 2016) and hardware clock in oVirt machine configuration is GMT +1. Now we are DST period and machine timezone is GMT +2. Engine Dashboard warn me about timezone mismatch between configuration and running VM. I can't see a setting to enable DST on emulated hardware. Some ideas?

1 0

Ovirt does not support AMD EPYC CPUs?
by Erick Perez 11 Apr '19

11 Apr '19

Hi, In its current release, OVIRT only shows AMD Opteron G1,G2,G3,G4,G5 and no mention of EPYC. This thread mentioned that a respin of Ovirt will address this, but never happened. https://lists.ovirt.org/archives/list/users@ovirt.org/message/2PEAYGK5PE33W… comments?

1 0

Get Disk used size
by mustafa.taha.mu95＠gmail.com 11 Apr '19

11 Apr '19

Hi Can i have way to know the allocated/used size of the VM disk , without install any agent on the VM ?

2 1

change self-hosted engine storage domain
by jason.cox＠harris.com 11 Apr '19

11 Apr '19

Is it possible to change a self-hosted engine's storage domain's settings? I setup a 3-node ovirt + gluster cluster with a dedicated 'engine' storage domain. I can see through the administration portal that the engine storage domain is using a single gluster host and no backup volfile servers. The single gluster host that the engine storage domain settings refer to had to be removed, so now I'm getting issues where VDSM is reporting that it cannot get the volume file information for the engine storage domain. I'm not sure how to go about changing the settings since the only way I've seen how to do this is through the administration portal, which relies on the engine VM (and its storage) being available. What I'd like to do is change the storage domain's path and add mount options for the backup volfile servers.

2 1

Re: Get Disk used size
by Strahil 10 Apr '19

10 Apr '19

What type of storage is being used. If it's file based (NFS,Cluster , other POSIX compliant) you can use qemu-img info to check virtual and actual size of the disk. Still ,this method can be inaccurate. Best Regards, Strahil NikolovOn Apr 10, 2019 15:02, mustafa.taha.mu95(a)gmail.com wrote: > > Hi > Can i have way to know the allocated/used size of the VM disk , without install any agent on the VM ? > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/IAQPQLKHNZ5QS…

1 0

Re: Different credentials ovirt_vm module
by Ondra Machacek 10 Apr '19

10 Apr '19

Hello, this seems ok to me. Can you please check the engine.log, for some error? On 09/04/2019 22:26, Florian Rädler wrote: > Hi, > > how can i use other credentials (run once) in the ansible playbook for > Sysprep domain join? > > My playbook: > > User_name and root_password does not sound like it’s the right option. > > How can I realize that? > > BR > > Florian > > > ------------------------------------------------------------------------ > > Pflichtangaben anzeigen > <http://www.deutschebahn.com/pflichtangaben/20190408> > > Nähere Informationen zur Datenverarbeitung im DB-Konzern finden Sie > hier: http://www.deutschebahn.com/de/konzern/datenschutz > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZOKA7M24U5HSZ… >

1 0

accessing ovirt-image-repository from behind proxy?
by Jarosław Prokopowski 10 Apr '19

10 Apr '19

Hi, Is there a way to connect to ovirt-image-repository from ovirt-engine through proxy server? I tried to set http_proxy in /etc/profile of the hosted-engine VM and restarted the VM but it does not help... Errors I get while testing the connection: 2019-04-10 12:36:49,590+03 ERROR [org.ovirt.engine.core.bll.storage.repoimage.GetImagesListQuery] (default task-3) [58f90541-0212-4f1e-9b14-eafc9a8237b9] Failed to retrieve image list: Connec tion timed out (Connection timed out) ... 2019-04-10 12:57:40,609+03 ERROR [org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand] (default task-3) [3c3baa28-c1ac-4783-b362-44b21d7430b5] Command 'org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand' failed: EngineException: (Failed with error PROVIDER_FAILURE and code 5050) Thanks Jarek

1 0

Installing VM - Fedora installer stuck on "Setting up installation source..."
by Jarosław Prokopowski 10 Apr '19

10 Apr '19

Hello, I installed oVirt 4.3.2, added NFS ISO domain and trying to create Fedora 26 VM. The installer starts but is stuck on "Installation Source Setting up installation source..." on the "INSTALLATION SUMMARY" screen. I cannot find any useful information in logs. Do you have any idea what can cause the issue and how to fix that? Thanks Jarek

2 3

Re: Vagrant Plugin
by Jeremy Tourville 10 Apr '19

10 Apr '19

Thanks for your reply Luca, I confirmed the cluster name, it is "Default". I even tried to run the script again and I made sure the D in default was upper case because linux is case sensitive. It still fails in the same way as before. [cid:c5758639-8ce0-46d1-ad0b-900af9cc138e] ________________________________ From: Luca 'remix_tj' Lorenzetto <lorenzetto.luca(a)gmail.com> Sent: Saturday, March 30, 2019 3:34 AM To: Jeremy Tourville Subject: Re: [ovirt-users] Vagrant Plugin Il ven 29 mar 2019, 19:12 Jeremy Tourville <Jeremy_Tourville(a)hotmail.com<mailto:Jeremy_Tourville@hotmail.com>> ha scritto: I am having some trouble getting the Ovirt Vagrant plugin working. I was able to get Vagrant installed and could even run the example scenario listed in the blog. https://www.ovirt.org/blog/2017/02/using-oVirt-vagrant.html My real issue is getting a vm generated by the SecGen project https://github.com/SecGen/SecGen to come up. If I use the VirtualBox provider everything works as expected and I can launch the vm with vagrant up. If I try to run using Ovirt provider it fails. I had originally posted this over in Google groups / Vagrant forums and it was suggested to take it to Ovirt. Hopefully, somebody here has some insights. The process fails quickly with the following output. Can anyone give some suggestions on how to fix the issue? I have also included a copy of my vagrantfile below. Thanks in advance for your assistance! ***Output*** Bringing machine 'escalation' up with 'ovirt4' provider... ==> escalation: Creating VM with the following settings... ==> escalation: -- Name: SecGen-default-scenario-escalation ==> escalation: -- Cluster: default ==> escalation: -- Template: debian_stretch_server_291118 ==> escalation: -- Console Type: spice ==> escalation: -- Memory: ==> escalation: ---- Memory: 512 MB ==> escalation: ---- Maximum: 512 MB ==> escalation: ---- Guaranteed: 512 MB ==> escalation: -- Cpu: ==> escalation: ---- Cores: 1 ==> escalation: ---- Sockets: 1 ==> escalation: ---- Threads: 1 ==> escalation: -- Cloud-Init: false ==> escalation: An error occured. Recovering.. ==> escalation: VM is not created. Please run `vagrant up` first. /home/secgenadmin/.vagrant.d/gems/2.4.4/gems/ovirt-engine-sdk-4.0.12/lib/ovirtsdk4/service.rb:52:in `raise_error': Fault reason is "Operation Failed". Fault detail is "Entity not found: Cluster: name=default". HTTP response code is 404. Hello Jeremy, Looks like you have no cluster called default in your setup. Edit your vagrant file accordingly to your setup. Luca

2 2