Re: [ovirt-users] 4.2: failed reconstructing master storage domain

[Idan Shaby]

Hi  Blaster,

First, can you please attach the engine and vdsm logs, so we can see if
there's any clue about this?
Second, if you don't have anything important on you storage domains, I
would suggest trying to force remove all your domains, then force remove
the datacenter, create a new one and reinstall your host via oVirt.
Then you can create new storage domains and attach them to your new
datacenter.


Regards,
Idan

On Tue, Dec 26, 2017 at 6:25 AM, Blaster  wrote:

> So I accidentally wiped out the underlying storage for the master storage
> domain for the default data center for my self hosted configuration.
>
> The re-initialize data center option is greyed out.
>
> I can’t add any other storage domains because there isn’t a master.
>
> I keep getting pop up errors “failed reconstructing master storage domain
> for datacenter default”.
>
> Anyway to get this back?
>
> I don’t see anything in the engine or vddm logs as to why it’s failed.
>
> Anyway to recover from this?
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] [Call for feedback] share also your successful upgrades experience

[Sahina Bose]

On Sun, Dec 24, 2017 at 12:41 AM, Gabriel Stein 
wrote:

> Well, I finally upgraded all to 4.2. Unfortunately I broke a Server in the
> upgrade process and I needed much more time than expected(the Host was with
> Hosted Engine and Gluster). I will not go further on that problems because
> I interrupted the upgrade process and try to fix it and I ended with a
> kernel panic.
>
> I recommend to use tmux or screen for the upgrade.
>
> My experience:
>
> I used this tutorial for the upgrade process: https://ovirt.org/
> documentation/how-to/hosted-engine/#upgrade-hosted-engine
>
> You can use it for the Hosted Engine VM and the Hosts. Be patient, don't
> interrupt the yum update process, and follow the instructions.
> If you have a locale different than US-UTF8, please change it for US-UTF8
> before the upgrade process. Where? /etc/locale.conf on CentOS. If you are
> using e.g. puppet, please deactivate it on upgrade process, to avoid the
> locale change(if you have something on puppet that changes it).
>
> Problems:
>
> I still having problems with glusterfs(Peer Rejected) and unstable, but it
> probably happens because I copied the UUID from the broke server from
> glusterfs and added the new installed server with same ip back to gluster.
>

Are your problems with GlusterFS resolved. If not please reach out to us
and gluster-us...@gluster.org for help



>
> IMHO:
> Please check that you have the engine backup done. Save it somewhere, NFS,
> rsync-it to another server
> When running engine-setup after the yum update on ovirt-engine VM: don't
> to the in place upgrade from postgresql. It's really nice to have it, but
> you you can avoid risks, why do so?
> Keep the Backup from Postgresql.
>
> Previous Version: 4.1.x
> Updated to: 4.2
>
> Setup:
>
> CentOS 7.4.108
> 4 Servers, 3 with Gluster for engine.
>
> If you have questions
>
> Best Regards,
>
> Gabriel
>
>
> Gabriel Stein
> --
> Gabriel Ferraz Stein
> Tel.: +49 (0)  170 2881531
>
> 2017-12-22 12:19 GMT+01:00 Gianluca Cecchi :
>
>> On Fri, Dec 22, 2017 at 12:06 PM, Martin Perina 
>> wrote:
>>
>>>
>>>
>
> Only problem I registered was the first start of engine on the first
> upgraded host (that should be step 7 in link above), where I got error on
> engine (not able to access web admin portal); I see this in server.log
> (see full attach here https://drive.google.com/file/
> d/1UQAllZfjueVGkXDsBs09S7THGDFn9YPa/view?usp=sharing )
>
> 2017-12-22 00:40:17,674+01 INFO  [org.quartz.core.QuartzScheduler]
> (ServerService Thread Pool -- 63) Scheduler 
> DefaultQuartzScheduler_$_NON_CLUSTERED
> started.
> 2017-12-22 00:40:17,682+01 INFO  [org.jboss.as.clustering.infinispan]
> (ServerService Thread Pool -- 63) WFLYCLINF0002: Started timeout-base 
> cache
> from ovirt-engine container
> 2017-12-22 00:44:28,611+01 ERROR 
> [org.jboss.as.controller.management-operation]
> (Controller Boot Thread) WFLYCTL0348: Timeout after [300] seconds waiting
> for service container stability. Operation will roll back. Step that first
> updated the service container was 'add' at address '[
> ("core-service" => "management"),
> ("management-interface" => "native-interface")
> ]'
>

 Adding Vaclav, maybe something in Wildfly? Martin, any hint on engine
 side?

>>>
>>> ​Yeah, I've already seen such error a few times, it usually happens when
>>> access to storage is really slow or the host itself is overloaded and
>>> WildFly is not able to startup properly until default 300 seconds interval​
>>> is over.
>>>
>>> If this is going to happen often, we will have to raise that timeout for
>>> all installations.
>>>
>>>
>> Ok, thanks for the confirmation of what I suspected.
>> Actually this particular environment is based on a single NUC where I
>> have ESXi 6.0U2 and the 3 hosts are actually VMs of this vSphere
>> environment, so that the hosted engine is an L2 VM
>> And the replica 3 (with arbiter) of the hosts insists at the end on a
>> single physical SSD disk below...
>> All in all it is already a great success that this kind of infrastructure
>> has been able to update from 4.1 to 4.2... I use it basically as a
>> functional testing and btw on vSphere there is also another CentOS 7 VM
>> running ;-)
>>
>> Thanks,
>> Gianluca
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] ovirt 4.2 + Win 7 64bit VM + Blue Iris no workie

[Blaster]

On 12/27/2017 12:13 PM, Alex Bartonek wrote:
Got it working!!!   Install Win 7 x86, NOT 64bit.  Install Blue 
Iris.   I only installed ethernet drivers and vid card drivers.   I'll 
install the rest but am assuming it should work fine.  Bye bye XenServer!


Good to know.  QEMU issue I'm going to assume.   I wonder if 
virt-manager and Proxmox would show the same failures, they should.



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] 3 strikes....

[Blaster]

Well, I've spent the last 2.5 days trying to get oVirt 4.2 up and running.

I sneeze on it, vdsm has a conniption and there appears to be no way to 
recover from it.


1) Install 4.2.  Everything looks good.  Start copying over some 
data..accidently wipe out the master storage domain...It's gone. The 
only method google could suggest was to re-initialize the data center.  
Great.  I'd love to!  It's greyed out.  Can't get it back...Try several 
hosted-engine uninstall methods, including


/usr/sbin/ovirt-hosted-engine-cleanup and wiping out the storage.

re-run hosted-engine --deploy
  All I get over and over in the vdsm log file while waiting for vdsm to become 
operational is..
2017-12-27 16:36:22,150-0600 ERROR (periodic/3) [virt.periodic.Operation] 
 operation failed 
(periodic:215)
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdsm/virt/periodic.py", line 213, in 
__call__
self._func()
  File "/usr/lib/python2.7/site-packages/vdsm/virt/sampling.py", line 522, in 
__call__
self._send_metrics()
  File "/usr/lib/python2.7/site-packages/vdsm/virt/sampling.py", line 538, in 
_send_metrics
vm_sample.interval)
  File "/usr/lib/python2.7/site-packages/vdsm/virt/vmstats.py", line 45, in 
produce
networks(vm, stats, first_sample, last_sample, interval)
  File "/usr/lib/python2.7/site-packages/vdsm/virt/vmstats.py", line 322, in 
networks
if nic.name.startswith('hostdev'):
AttributeError: name
2017-12-27 16:36:22,620-0600 INFO  (periodic/1) [vdsm.api] START 
repoStats(domains=()) from=internal, 
task_id=94688cf1-a991-433e-9e22-7065ed5dc1bf (api:46)
2017-12-27 16:36:22,620-0600 INFO  (periodic/1) [vdsm.api] FINISH repoStats 
return={} from=internal, task_id=94688cf1-a991-433e-9e22-7065ed5dc1bf (api:52)
2017-12-27 16:36:22,621-0600 INFO  (periodic/1) [vdsm.api] START 
multipath_health() from=internal, task_id=9c680369-8f2a-439e-8fe5-b2a1e33c0706 
(api:46)
2017-12-27 16:36:22,622-0600 INFO  (periodic/1) [vdsm.api] FINISH 
multipath_health return={} from=internal, 
task_id=9c680369-8f2a-439e-8fe5-b2a1e33c0706 (api:52)
2017-12-27 16:36:22,633-0600 ERROR (periodic/1) [root] failed to retrieve 
Hosted Engine HA score '[Errno 2] No such file or directory'Is the Hosted 
Engine setup finished? (api:196)
2017-12-27 16:36:23,178-0600 INFO  (vmrecovery) [vdsm.api] START 
getConnectedStoragePoolsList(options=None) from=internal, 
task_id=a7e48a2f-8cb7-4ec5-acd7-452c8f0c522b (api:46)
2017-12-27 16:36:23,179-0600 INFO  (vmrecovery) [vdsm.api] FINISH 
getConnectedStoragePoolsList return={'poollist': []} from=internal, 
task_id=a7e48a2f-8cb7-4ec5-acd7-452c8f0c522b (api:52)
2017-12-27 16:36:23,179-0600 INFO  (vmrecovery) [vds] recovery: waiting for 
storage pool to go up (clientIF:643)

sigh...reinstall 7.4 and do it all over again.

2) copying data to master storage pool.  Didn't wipe it out this time, but 
filled the volume instead.  Environment freezes.
 vdsm can't start...infinite loop waiting for storage pool again.  Try clean up 
and redeploy.  Same problem as above.
7.4 reinstall #2 here we go...

3)Up and running again.  Forgot to add my NIC card. Shut it down.  Boot back 
up.  vdsm sees new network interfaces.
for some reason, it switches ovirtmgmt over to one of the new interfaces which 
doesn't have a cable
attached to it.  Clean up ifcfg- files and reboot.  ifcfg-ovirtmgmt is now 
gone.  recreate and reboot.  Interface
comes alive, but vdsm is not starting.
supervdsm log shows:
 Multiple southbound ports per network detected, ignoring this network for the 
QoS report (network: ovirtmgmt, ports: ['enp3s0', 'enp4s0'])
restore-net::DEBUG::2017-12-27 13:10:39,815::cmdutils::150::root::(exec_cmd) 
/usr/share/openvswitch/scripts/ovs-ctl status (cwd None)
restore-net::DEBUG::2017-12-27 13:10:39,856::cmdutils::158::root::(exec_cmd) SUCCESS: 
 = '';  = 0
restore-net::DEBUG::2017-12-27 13:10:39,863::vsctl::58::root::(commit) 
Executing commands: /usr/bin/ovs-vsctl --oneline --format=json -- list Bridge 
-- list Port -- list Interface
restore-net::DEBUG::2017-12-27 13:10:39,864::cmdutils::150::root::(exec_cmd) 
/usr/bin/ovs-vsctl --oneline --format=json -- list Bridge -- list Port -- list 
Interface (cwd None)
restore-net::DEBUG::2017-12-27 13:10:39,944::cmdutils::158::root::(exec_cmd) SUCCESS: 
 = '';  = 0
restore-net::ERROR::2017-12-27 
13:10:39,954::restore_net_config::454::root::(restore) unified restoration 
failed.
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdsm/network/restore_net_config.py", 
line 448, in restore
unified_restoration()
  File "/usr/lib/python2.7/site-packages/vdsm/network/restore_net_config.py", 
line 131, in unified_restoration
classified_conf = _classify_nets_bonds_config(available_config)
  File "/usr/lib/python2.7/site-packages/vdsm/network/restore_net_config.py", 
line 260, in _classify_nets_bonds_config
current_config = kernelconfig.KernelConfig(net_info)
  File 

Re: [ovirt-users] ovirt 4.2 + Win 7 64bit VM + Blue Iris no workie

[Yaniv Kaul]

On Dec 27, 2017 6:52 PM, "Alex Bartonek"  wrote:

Replying to myself..lol.  Figured you guys would also be interested or
someone else who would like Blue Iris working.

One of the things I read was the "cpu type".  I'm running this on a HP
DL360 g5 with dual Xeon 5160's.  That CPU "Woodcrest" isnt listed, so I
specified "Conroe".  Maybe thats the cause, I'm not sure.  On my other
DL360 g5, it also has dual 5160's but running XenServer.  Blue Iris works
fine under that setup with the same Win 7 64bit install.


What does cpuinfo show in both?
Perhaps worth trying custom cpu (passthrough for example)?
Y.


So now, IMO, it goes back to drivers that I have installed in the VM I
believe.  I'm going to build another Win 7 64 bit VM but only install the
NIC once the VM boots in oVirt.  Maybe something else is causing it to
BSOD.

At any rate, I appreciate the replys from all of you.  Thanks again.. I'll
reply if I find something useful.


Sent with ProtonMail  Secure Email.

 Original Message 
Subject: Re: [ovirt-users] ovirt 4.2 + Win 7 64bit VM + Blue Iris no workie
Local Time: December 26, 2017 8:10 PM
UTC Time: December 27, 2017 2:10 AM
From: a...@unix1337.com
To:
users@ovirt.org 

Yep..found that already.  Still have the same issue.  TBH, I'm looking at
ZoneMinder.  I used to use it instead of Blue Iris a few years back.  If
that works, even better.  If someone were to find a fix for Blue Iris, that
would be nice also.


Sent with ProtonMail  Secure Email.

 Original Message 
Subject: Re: [ovirt-users] ovirt 4.2 + Win 7 64bit VM + Blue Iris no workie
Local Time: December 26, 2017 7:14 PM
UTC Time: December 27, 2017 1:14 AM
From: do...@fortnebula.com
To: Alex Bartonek 
users@ovirt.org 

http://lists.ovirt.org/pipermail/users/2016-July/074936.html

On Tue, Dec 26, 2017 at 6:07 PM, Alex Bartonek  wrote:

> This is a first time install of 4.2, first time build of a Win 7 64bit vm,
> first time oVirt user.  :-)
> Blue Iris works fine under XenServer but thats what I'm migrating away
> from.
>
> VM is nothing special.  4gb ram assigned, OS set as "Win 7 64 bit", 1
> virtual cpu everything else is default.  Virtio drivers installed after
> first boot.  I'll re-install Win 7 64bit, have it take a dump and then post
> the dump details.
>
>
> Copy of the dump analysis:
> http://textuploader.com/dcpbp
>
>  Original Message 
> Subject: Re: [ovirt-users] ovirt 4.2 + Win 7 64bit VM + Blue Iris no workie
> Local Time: December 26, 2017 3:36 PM
> UTC Time: December 26, 2017 9:36 PM
> From: yk...@redhat.com
> To: Alex Bartonek 
> Ovirt Users 
>
>
>
> On Dec 26, 2017 10:49 PM, "Alex Bartonek"  wrote:
>
> I have a dl360 g5 with a Xeon 5160 cpu, installed 4.2, Win 7 64 bit in a
> VM.  Installed the virtio drivers also.   Plain jane Win 7 setup, nothing
> extra.  Installed Blue Iris.  When I run Blue Iris, it blue screens.
> Anyone got Blue Iris to work under 4.2 in a Windows VM?
>
>
> There are many missing details, it'd be interesting to begin with the blue
> screen details and the VM configuration.
> Did it work with previous versions?
> Y.
>
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] ovirt 4.2 + Win 7 64bit VM + Blue Iris no workie

[Alex Bartonek]

Got it working!!!   Install Win 7 x86, NOT 64bit.  Install Blue Iris.   I only 
installed ethernet drivers and vid card drivers.   I'll install the rest but am 
assuming it should work fine.  Bye bye XenServer!

Sent with [ProtonMail](https://protonmail.com) Secure Email.

>  Original Message 
> Subject: Re: [ovirt-users] ovirt 4.2 + Win 7 64bit VM + Blue Iris no workie
> Local Time: December 27, 2017 11:05 AM
> UTC Time: December 27, 2017 5:05 PM
> From: blas...@556nato.com
> To: Yaniv Kaul 
> Alex Bartonek , users@ovirt.org 
>
> I did that over a year ago when I first had the issue.  They washed their 
> hands of it saying it was known to work on ESXi and they don’t have any 
> device drivers nor where they doing anything but standard Windows library 
> calls, so they pushed it back to a Hypervisor issue.
>
> It’s known to work with ESXi and Xenserver.   I haven’t heard either way on 
> Proxmox.  I’m guessing there’s some issue with QEMU.
>
>> On Dec 27, 2017, at 1:28 AM, Yaniv Kaul  wrote:
>>
>> On Wed, Dec 27, 2017 at 1:07 AM, Alex Bartonek  wrote:
>>
>>> This is a first time install of 4.2, first time build of a Win 7 64bit vm, 
>>> first time oVirt user.  :-)
>>> Blue Iris works fine under XenServer but thats what I'm migrating away from.
>>>
>>> VM is nothing special.  4gb ram assigned, OS set as "Win 7 64 bit", 1 
>>> virtual cpu everything else is default.  Virtio drivers installed after 
>>> first boot.  I'll re-install Win 7 64bit, have it take a dump and then post 
>>> the dump details.
>>>
>>> Copy of the dump analysis:
>>> http://textuploader.com/dcpbp
>>
>> Perhaps worth contacting the developers of Blue Iris?
>> ( Based on: PROCESS_NAME:  BlueIris.exe in the dump analysis).
>>
>> Y.
>>
  Original Message 
 Subject: Re: [ovirt-users] ovirt 4.2 + Win 7 64bit VM + Blue Iris no workie
 Local Time: December 26, 2017 3:36 PM
 UTC Time: December 26, 2017 9:36 PM
 From: yk...@redhat.com
 To: Alex Bartonek 
 Ovirt Users 

 On Dec 26, 2017 10:49 PM, "Alex Bartonek"  wrote:

> I have a dl360 g5 with a Xeon 5160 cpu, installed 4.2, Win 7 64 bit in a 
> VM.  Installed the virtio drivers also.   Plain jane Win 7 setup, nothing 
> extra.  Installed Blue Iris.  When I run Blue Iris, it blue screens.   
> Anyone got Blue Iris to work under 4.2 in a Windows VM?

 There are many missing details, it'd be interesting to begin with the blue 
 screen details and the VM configuration.
 Did it work with previous versions?
 Y.

>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] ovirt 4.2 + Win 7 64bit VM + Blue Iris no workie

[Alex Bartonek]

Ok, so I wont build another VM.

Never tried Q35 till now.  Same problem.  Stil BSOD.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

>  Original Message 
> Subject: Re: [ovirt-users] ovirt 4.2 + Win 7 64bit VM + Blue Iris no workie
> Local Time: December 27, 2017 11:02 AM
> UTC Time: December 27, 2017 5:02 PM
> From: blas...@556nato.com
> To: Alex Bartonek 
> users@ovirt.org 
>
> I tried that back in July of 16 when I first reported the issue to this list. 
>  I installed bare Win 10 with no VirtIO drivers (ie, using e1000 for network 
> and IDE for disk) and it still blue screened as soon as the Blue Iris service 
> started.
>
> The other thing you could possible try is a different chipset type.  I’m 
> using the 440-4.2.  Have you tried Q35?.
>
>> On Dec 27, 2017, at 10:51 AM, Alex Bartonek  wrote:
>>
>> Replying to myself..lol.  Figured you guys would also be interested or 
>> someone else who would like Blue Iris working.
>>
>> One of the things I read was the "cpu type".  I'm running this on a HP DL360 
>> g5 with dual Xeon 5160's.  That CPU "Woodcrest" isnt listed, so I specified 
>> "Conroe".  Maybe thats the cause, I'm not sure.  On my other DL360 g5, it 
>> also has dual 5160's but running XenServer.  Blue Iris works fine under that 
>> setup with the same Win 7 64bit install.
>>
>> So now, IMO, it goes back to drivers that I have installed in the VM I 
>> believe.  I'm going to build another Win 7 64 bit VM but only install the 
>> NIC once the VM boots in oVirt.  Maybe something else is causing it to BSOD.
>>
>> At any rate, I appreciate the replys from all of you.  Thanks again.. I'll 
>> reply if I find something useful.
>>
>> Sent with [ProtonMail](https://protonmail.com/) Secure Email.
>>
>>>  Original Message 
>>> Subject: Re: [ovirt-users] ovirt 4.2 + Win 7 64bit VM + Blue Iris no workie
>>> Local Time: December 26, 2017 8:10 PM
>>> UTC Time: December 27, 2017 2:10 AM
>>> From: a...@unix1337.com
>>> To:
>>> users@ovirt.org 
>>>
>>> Yep..found that already.  Still have the same issue.  TBH, I'm looking at 
>>> ZoneMinder.  I used to use it instead of Blue Iris a few years back.  If 
>>> that works, even better.  If someone were to find a fix for Blue Iris, that 
>>> would be nice also.
>>>
>>> Sent with [ProtonMail](https://protonmail.com/) Secure Email.
>>>
  Original Message 
 Subject: Re: [ovirt-users] ovirt 4.2 + Win 7 64bit VM + Blue Iris no workie
 Local Time: December 26, 2017 7:14 PM
 UTC Time: December 27, 2017 1:14 AM
 From: do...@fortnebula.com
 To: Alex Bartonek 
 users@ovirt.org 

 http://lists.ovirt.org/pipermail/users/2016-July/074936.html

 On Tue, Dec 26, 2017 at 6:07 PM, Alex Bartonek  wrote:

> This is a first time install of 4.2, first time build of a Win 7 64bit 
> vm, first time oVirt user.  :-)
> Blue Iris works fine under XenServer but thats what I'm migrating away 
> from.
>
> VM is nothing special.  4gb ram assigned, OS set as "Win 7 64 bit", 1 
> virtual cpu everything else is default.  Virtio drivers installed after 
> first boot.  I'll re-install Win 7 64bit, have it take a dump and then 
> post the dump details.
>
> Copy of the dump analysis:
> http://textuploader.com/dcpbp
>
>>  Original Message 
>> Subject: Re: [ovirt-users] ovirt 4.2 + Win 7 64bit VM + Blue Iris no 
>> workie
>> Local Time: December 26, 2017 3:36 PM
>> UTC Time: December 26, 2017 9:36 PM
>> From: yk...@redhat.com
>> To: Alex Bartonek 
>> Ovirt Users 
>>
>> On Dec 26, 2017 10:49 PM, "Alex Bartonek"  wrote:
>>
>>> I have a dl360 g5 with a Xeon 5160 cpu, installed 4.2, Win 7 64 bit in 
>>> a VM.  Installed the virtio drivers also.   Plain jane Win 7 setup, 
>>> nothing extra.  Installed Blue Iris.  When I run Blue Iris, it blue 
>>> screens.   Anyone got Blue Iris to work under 4.2 in a Windows VM?
>>
>> There are many missing details, it'd be interesting to begin with the 
>> blue screen details and the VM configuration.
>> Did it work with previous versions?
>> Y.
>>
>>>
>>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users___
Users mailing list
Users@ovirt.org

Re: [ovirt-users] ovirt 4.2 + Win 7 64bit VM + Blue Iris no workie

[Blaster]

I did that over a year ago when I first had the issue.  They washed their hands 
of it saying it was known to work on ESXi and they don’t have any device 
drivers nor where they doing anything but standard Windows library calls, so 
they pushed it back to a Hypervisor issue.

It’s known to work with ESXi and Xenserver.   I haven’t heard either way on 
Proxmox.  I’m guessing there’s some issue with QEMU.



> On Dec 27, 2017, at 1:28 AM, Yaniv Kaul  wrote:
> 
> 
> 
> On Wed, Dec 27, 2017 at 1:07 AM, Alex Bartonek  > wrote:
> This is a first time install of 4.2, first time build of a Win 7 64bit vm, 
> first time oVirt user.  :-)
> Blue Iris works fine under XenServer but thats what I'm migrating away from.
> 
> VM is nothing special.  4gb ram assigned, OS set as "Win 7 64 bit", 1 virtual 
> cpu everything else is default.  Virtio drivers installed after first boot.  
> I'll re-install Win 7 64bit, have it take a dump and then post the dump 
> details.  
> 
> 
> Copy of the dump analysis:
> http://textuploader.com/dcpbp 
> 
> Perhaps worth contacting the developers of Blue Iris?
> ( Based on: PROCESS_NAME:  BlueIris.exe in the dump analysis).
> 
> Y.
> 
>  
> 
> 
>>  Original Message 
>> Subject: Re: [ovirt-users] ovirt 4.2 + Win 7 64bit VM + Blue Iris no workie
>> Local Time: December 26, 2017 3:36 PM
>> UTC Time: December 26, 2017 9:36 PM
>> From: yk...@redhat.com 
>> To: Alex Bartonek >
>> Ovirt Users >
>> 
>> 
>> 
>> On Dec 26, 2017 10:49 PM, "Alex Bartonek" > > wrote:
>> I have a dl360 g5 with a Xeon 5160 cpu, installed 4.2, Win 7 64 bit in a VM. 
>>  Installed the virtio drivers also.   Plain jane Win 7 setup, nothing extra. 
>>  Installed Blue Iris.  When I run Blue Iris, it blue screens.   Anyone got 
>> Blue Iris to work under 4.2 in a Windows VM?
>> 
>> There are many missing details, it'd be interesting to begin with the blue 
>> screen details and the VM configuration. 
>> Did it work with previous versions? 
>> Y. 
>> 
>> 
>>  
>> 
>> ___
>> Users mailing list
>> Users@ovirt.org 
>> http://lists.ovirt.org/mailman/listinfo/users 
>> 
>> 
> 
> 
> ___
> Users mailing list
> Users@ovirt.org 
> http://lists.ovirt.org/mailman/listinfo/users 
> 
> 
> 
> ___
> Users mailing list
> Users@ovirt.org 
> http://lists.ovirt.org/mailman/listinfo/users 
> 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] ovirt 4.2 + Win 7 64bit VM + Blue Iris no workie

[Blaster]

I tried that back in July of 16 when I first reported the issue to this list.  
I installed bare Win 10 with no VirtIO drivers (ie, using e1000 for network and 
IDE for disk) and it still blue screened as soon as the Blue Iris service 
started.

The other thing you could possible try is a different chipset type.  I’m using 
the 440-4.2.  Have you tried Q35?.

> On Dec 27, 2017, at 10:51 AM, Alex Bartonek  wrote:
> 
> Replying to myself..lol.  Figured you guys would also be interested or 
> someone else who would like Blue Iris working.
> 
> One of the things I read was the "cpu type".  I'm running this on a HP DL360 
> g5 with dual Xeon 5160's.  That CPU "Woodcrest" isnt listed, so I specified 
> "Conroe".  Maybe thats the cause, I'm not sure.  On my other DL360 g5, it 
> also has dual 5160's but running XenServer.  Blue Iris works fine under that 
> setup with the same Win 7 64bit install.
> 
> So now, IMO, it goes back to drivers that I have installed in the VM I 
> believe.  I'm going to build another Win 7 64 bit VM but only install the NIC 
> once the VM boots in oVirt.  Maybe something else is causing it to BSOD.  
> 
> At any rate, I appreciate the replys from all of you.  Thanks again.. I'll 
> reply if I find something useful.
> 
> 
> Sent with ProtonMail  Secure Email.
> 
>>  Original Message 
>> Subject: Re: [ovirt-users] ovirt 4.2 + Win 7 64bit VM + Blue Iris no workie
>> Local Time: December 26, 2017 8:10 PM
>> UTC Time: December 27, 2017 2:10 AM
>> From: a...@unix1337.com
>> To: 
>> users@ovirt.org 
>> 
>> Yep..found that already.  Still have the same issue.  TBH, I'm looking at 
>> ZoneMinder.  I used to use it instead of Blue Iris a few years back.  If 
>> that works, even better.  If someone were to find a fix for Blue Iris, that 
>> would be nice also.
>> 
>> 
>> Sent with ProtonMail  Secure Email.
>> 
>>>  Original Message 
>>> Subject: Re: [ovirt-users] ovirt 4.2 + Win 7 64bit VM + Blue Iris no workie
>>> Local Time: December 26, 2017 7:14 PM
>>> UTC Time: December 27, 2017 1:14 AM
>>> From: do...@fortnebula.com
>>> To: Alex Bartonek 
>>> users@ovirt.org 
>>> 
>>> http://lists.ovirt.org/pipermail/users/2016-July/074936.html 
>>> 
>>> 
>>> On Tue, Dec 26, 2017 at 6:07 PM, Alex Bartonek >> > wrote:
>>> This is a first time install of 4.2, first time build of a Win 7 64bit vm, 
>>> first time oVirt user.  :-)
>>> Blue Iris works fine under XenServer but thats what I'm migrating away from.
>>> 
>>> VM is nothing special.  4gb ram assigned, OS set as "Win 7 64 bit", 1 
>>> virtual cpu everything else is default.  Virtio drivers installed after 
>>> first boot.  I'll re-install Win 7 64bit, have it take a dump and then post 
>>> the dump details.  
>>> 
>>> 
>>> Copy of the dump analysis:
>>> http://textuploader.com/dcpbp 
>>> 
  Original Message 
 Subject: Re: [ovirt-users] ovirt 4.2 + Win 7 64bit VM + Blue Iris no workie
 Local Time: December 26, 2017 3:36 PM
 UTC Time: December 26, 2017 9:36 PM
 From: yk...@redhat.com 
 To: Alex Bartonek >
 Ovirt Users >
 
 
 
 On Dec 26, 2017 10:49 PM, "Alex Bartonek" > wrote:
 I have a dl360 g5 with a Xeon 5160 cpu, installed 4.2, Win 7 64 bit in a 
 VM.  Installed the virtio drivers also.   Plain jane Win 7 setup, nothing 
 extra.  Installed Blue Iris.  When I run Blue Iris, it blue screens.   
 Anyone got Blue Iris to work under 4.2 in a Windows VM?
 
 There are many missing details, it'd be interesting to begin with the blue 
 screen details and the VM configuration. 
 Did it work with previous versions? 
 Y. 
 
 
  
 
 ___
 Users mailing list
 Users@ovirt.org 
 http://lists.ovirt.org/mailman/listinfo/users 
 
 
>>> 
>>> 
>>> ___
>>> Users mailing list
>>> Users@ovirt.org 
>>> http://lists.ovirt.org/mailman/listinfo/users 
>>> 
>>> 
>> 
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] ovirt 4.2 + Win 7 64bit VM + Blue Iris no workie

[Alex Bartonek]

Replying to myself..lol.  Figured you guys would also be interested or someone 
else who would like Blue Iris working.

One of the things I read was the "cpu type".  I'm running this on a HP DL360 g5 
with dual Xeon 5160's.  That CPU "Woodcrest" isnt listed, so I specified 
"Conroe".  Maybe thats the cause, I'm not sure.  On my other DL360 g5, it also 
has dual 5160's but running XenServer.  Blue Iris works fine under that setup 
with the same Win 7 64bit install.

So now, IMO, it goes back to drivers that I have installed in the VM I believe. 
 I'm going to build another Win 7 64 bit VM but only install the NIC once the 
VM boots in oVirt.  Maybe something else is causing it to BSOD.

At any rate, I appreciate the replys from all of you.  Thanks again.. I'll 
reply if I find something useful.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

>  Original Message 
> Subject: Re: [ovirt-users] ovirt 4.2 + Win 7 64bit VM + Blue Iris no workie
> Local Time: December 26, 2017 8:10 PM
> UTC Time: December 27, 2017 2:10 AM
> From: a...@unix1337.com
> To:
> users@ovirt.org 
>
> Yep..found that already.  Still have the same issue.  TBH, I'm looking at 
> ZoneMinder.  I used to use it instead of Blue Iris a few years back.  If that 
> works, even better.  If someone were to find a fix for Blue Iris, that would 
> be nice also.
>
> Sent with [ProtonMail](https://protonmail.com) Secure Email.
>
>>  Original Message 
>> Subject: Re: [ovirt-users] ovirt 4.2 + Win 7 64bit VM + Blue Iris no workie
>> Local Time: December 26, 2017 7:14 PM
>> UTC Time: December 27, 2017 1:14 AM
>> From: do...@fortnebula.com
>> To: Alex Bartonek 
>> users@ovirt.org 
>>
>> http://lists.ovirt.org/pipermail/users/2016-July/074936.html
>>
>> On Tue, Dec 26, 2017 at 6:07 PM, Alex Bartonek  wrote:
>>
>>> This is a first time install of 4.2, first time build of a Win 7 64bit vm, 
>>> first time oVirt user.  :-)
>>> Blue Iris works fine under XenServer but thats what I'm migrating away from.
>>>
>>> VM is nothing special.  4gb ram assigned, OS set as "Win 7 64 bit", 1 
>>> virtual cpu everything else is default.  Virtio drivers installed after 
>>> first boot.  I'll re-install Win 7 64bit, have it take a dump and then post 
>>> the dump details.
>>>
>>> Copy of the dump analysis:
>>> http://textuploader.com/dcpbp
>>>
  Original Message 
 Subject: Re: [ovirt-users] ovirt 4.2 + Win 7 64bit VM + Blue Iris no workie
 Local Time: December 26, 2017 3:36 PM
 UTC Time: December 26, 2017 9:36 PM
 From: yk...@redhat.com
 To: Alex Bartonek 
 Ovirt Users 

 On Dec 26, 2017 10:49 PM, "Alex Bartonek"  wrote:

> I have a dl360 g5 with a Xeon 5160 cpu, installed 4.2, Win 7 64 bit in a 
> VM.  Installed the virtio drivers also.   Plain jane Win 7 setup, nothing 
> extra.  Installed Blue Iris.  When I run Blue Iris, it blue screens.   
> Anyone got Blue Iris to work under 4.2 in a Windows VM?

 There are many missing details, it'd be interesting to begin with the blue 
 screen details and the VM configuration.
 Did it work with previous versions?
 Y.

>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] OVS error logs after upgrade to 4.2

[Marcin Mirecki]

Hello Misak,

This error hints that your ovn databases are not up (or at least can not be
connected to).
Could you please check if the following command gives any output:

ps -ef|grep 'ovnsb_db\|ovnnb_db'

The databases can be started (if not active) using:
   /usr/share/openvswitch/scripts/ovn-ctl start_ovsdb

Could you please also check the content of:
  /var/run/openvswitch/

The filenames don't look normal (usually they do not contain any numbers as
part of them), please give me some time to check this.

Thanks,
Marcin





On Wed, Dec 27, 2017 at 3:44 PM, Mor Kalfon  wrote:

> Hello Misak,
>
> Could you please file a bug about those error messages that you receive
> from OVS?
> You can use the log collector tool (https://www.ovirt.org/documen
> tation/admin-guide/chap-Utilities/#the-log-collector-tool)
> which gathers all the required logs for us to investigate this issue.
>
> Thanks for reporting this issue!
>
> On Wed, Dec 27, 2017 at 11:03 AM, Misak Khachatryan 
> wrote:
>
>> On Wed, Dec 27, 2017 at 12:42 PM, Dan Kenigsberg 
>> wrote:
>> > On Wed, Dec 27, 2017 at 8:49 AM, Misak Khachatryan 
>> wrote:
>> >> Hi,
>> >>
>> >> It's not on log file, it's from automatic email sent by cron daemon.
>> >> This one from logrotate.
>> >
>> > Would you file a bug about this daily logrotate spam?
>> >
>>
>> Sure, will do.
>>
>> >>
>> >> I'd like to migrate my network to OVS, but as i can't find any guide
>> >> for that, it's a bit scary.
>> >
>> > Why would you like to do that? OVN is useful for big deployments, that
>> > have many isolated networks. It is not universally recommended, as it
>> > uses more CPU.
>> >
>>
>> No particular reason, thought that will be future in oVIRT networking,
>> also i work in relatively big ISP with many PoP and DCs in many
>> cities. And I'm interested to try it some time.
>>
>> >>
>> >> Best regards,
>> >> Misak Khachatryan
>> >>
>> >>
>> >> On Tue, Dec 26, 2017 at 3:29 PM, Dan Kenigsberg 
>> wrote:
>> >>> On Tue, Dec 26, 2017 at 8:35 AM, Misak Khachatryan 
>> wrote:
>>  Hi,
>> 
>>  After upgrade to 4.2 I started getting this error from engine:
>> 
>>  /etc/cron.daily/logrotate:
>> 
>>  2017-12-25T23:12:02Z|1|unixctl|WARN|failed to connect to
>>  /var/run/openvswitch/ovnnb_db.19883.ctl
>>  ovs-appctl: cannot connect to
>>  "/var/run/openvswitch/ovnnb_db.19883.ctl" (No such file or
>> directory)
>>  2017-12-25T23:12:02Z|1|unixctl|WARN|failed to connect to
>>  /var/run/openvswitch/ovnsb_db.19891.ctl
>>  ovs-appctl: cannot connect to
>>  "/var/run/openvswitch/ovnsb_db.19891.ctl" (No such file or
>> directory)
>> 
>> 
>>  Seems harmless as i don't use OVS, but how to fix it?
>> >>>
>> >>> By default, ovirt-4.2 installs and configure OVN (which uses OVS). You
>> >>> can turn it off on Engine host by running
>> >>> systemctl stop ovirt-provider-ovn ovn-northd openvswitch
>> >
>> > did you try that?
>> >
>>
>> No, but is correct way to disable it completely?
>>
>> >>>
>> >>> but I'd appreciate your help to understand in which log file do you
>> >>> see these warnings?
>> >
>> >>> Have you already disabled openvswitch?
>> >
>> > have you ^^ ?
>>
>> No, what is a correct way to do it?
>>
>
>
>
> --
> Mor Kalfon
> RHV Networking Team
> Red Hat IL-Raanana
> Tel: +972-54-6514148 <+972%2054-651-4148>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Assign external IP to VM

[Alex Bartonek]

geez.. I was super far off. LOL.  That did it!!!   This is so awesome.  Thanks 
for the assist!

Sent with [ProtonMail](https://protonmail.com) Secure Email.

>  Original Message 
> Subject: Re: [ovirt-users] Assign external IP to VM
> Local Time: December 27, 2017 1:20 AM
> UTC Time: December 27, 2017 7:20 AM
> From: eh...@redhat.com
> To: Alex Bartonek 
> users@ovirt.org 
>
> It is not clear what you did exactly, but, if I try to summarize, this setup 
> should work for you:
> - Create a network (network->networks) and mark it as a VM network.
> - Create a vNIC profile (network->networks->[network]->Vnic Profiles.
> - Attach the network on the relevant NIC on your host 
> (compute->hosts->[host]->Network Interface->Setup Hos Networks).
> (No need to set an IP on these networks, unless you need the host stack 
> itself and not only the vms to access these networks)
> - Create or edit your VM, create a vnic (or edit one) and point it to the 
> relevant vnic profile you created earlier.
>
> Do this for each nic you mentioned, and it should work for you.
>
> The use of SRIOV or pci-passthrough is taking this a step further, mainly 
> when you need high throughput.
> For SRIOV you need special NIC hardware and the pci-passthrough is limiting 
> one vnic per nic, which is wasteful if you do not really need it.
> Thanks,
> Edy.
>
> On Wed, Dec 27, 2017 at 12:38 AM, Alex Bartonek  wrote:
>
>> Need some guidance on this one.
>>
>> Config:
>> 1U with 2 NICs.
>> NIC 1 plugged to local switch - gets local IP
>> NIC 2 plugged direct to cable modem - need to set IP inside VM to public 
>> static IP
>> VM will be CentOS, already know how to configure NIC once I can get the 2nd 
>> NIC assigned to it.
>>
>> Do I use PCI passthru?  Or where do I start to get this configured?  I did 
>> setup NIC 2 under Network --> Networks.   Created a NIC called 
>> "external_NIC".  External NIC has description and then I configured 2 DNS 
>> servers which are given to me by the ISP.
>>
>> Under Compute --> Hosts -->  --> Network Interfaces (I have both 
>> NICs showing as up) --> Setup Host Networks ---> NIC 2 is the interface --> 
>> Assignment of Logical networks is "external_NIC".
>>
>> I was assuming I was done, so I go to my VM add NIC 2, click run and I see:
>>
>> Cannot run VM. There is no host that satisfies current scheduling 
>> constraints. See below for details:
>>
>> - The host  did not satisfy internal filter Network because there 
>> are no free virtual functions which are suitable for virtual nic(s) nic2. A 
>> virtual function is considered as suitable if the VF's configuration of its 
>> physical function contains the virtual nic's network/network label.
>>
>> Need guidance on what to read to get this working.
>>
>> Thanks!
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt virtio drivers for fedora 5

[Yedidyah Bar David]

On Wed, Dec 27, 2017 at 3:24 PM, Yaniv Kaul  wrote:
>
>
> On Wed, Dec 27, 2017 at 3:07 PM, Anantha Raghava
>  wrote:
>>
>> Hi,
>>
>> We have converted a very old fedora 5 server to run on oVirt. However,
>> since the Fedora 5 does not have virtio drivers, or virtio-scsi drivers, the
>> disks are connected to virtual IDE interface. The problem here is on a
>> single IDE interface, we cannot connect more than 2 disks. But the old
>> converted server had 4 disks on 2 IDE controllers.
>>
>> First question is can we add one more virtual IDE Controller to the VM? If
>> yes, please share the procedure. Or whether any one can share the proper
>> virtio or virtio scsi for fedora 5 OS drivers so that we can get other two
>> inactive disks working.

You might manage to write a vdsm hook to do this, no idea how hard
this can be. See e.g.:

https://www.ovirt.org/develop/developer-guide/vdsm/hooks-catalogue/
https://www.ovirt.org/develop/developer-guide/vdsm/hook/vmdisk/

Latter adds a virtio disk, you might try to write something based on it.

>>
>> Unfortunately we cannot upgrade from Fedora 5 at the moment.
>
>
> Neither are possible. Does the Fedora have an iSCSI initiator support
> perhaps? You can expose those disk via different VMs to that VM - but still
> it might look different to the OS.
> (We don't even support such an old OS - but if it works, great).

You might try to use a newer kernel. It seems like Fedora 9 or 10 started
supporting virtio, so you can try their kernel.

No idea if it will work, and what might break. Try first on a test VM.

> Y.
>
>> Await your inputs.
>>
>> --
>>
>> Thanks & Regards,
>>
>>
>> Anantha Raghava
>>
>> Do not print this e-mail unless required. Save Paper & trees.
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>



-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt virtio drivers for fedora 5

[Anantha Raghava]

Hello Yaniv,

Thanks for very quick response.

--

Thanks & Regards,


Anantha Raghava

Do not print this e-mail unless required. Save Paper & trees.

On 27/12/17 6:54 PM, Yaniv Kaul wrote:



On Wed, Dec 27, 2017 at 3:07 PM, Anantha Raghava 
> 
wrote:


Hi,

We have converted a very old fedora 5 server to run on oVirt.
However, since the Fedora 5 does not have virtio drivers, or
virtio-scsi drivers, the disks are connected to virtual IDE
interface. The problem here is on a single IDE interface, we
cannot connect more than 2 disks. But the old converted server had
4 disks on 2 IDE controllers.

First question is can we add one more virtual IDE Controller to
the VM? If yes, please share the procedure. Or whether any one can
share the proper virtio or virtio scsi for fedora 5 OS drivers so
that we can get other two inactive disks working.

Unfortunately we cannot upgrade from Fedora 5 at the moment.


Neither are possible. Does the Fedora have an iSCSI initiator support 
perhaps? You can expose those disk via different VMs to that VM - but 
still it might look different to the OS.

(We don't even support such an old OS - but if it works, great).
Y.

Await your inputs.

-- 


Thanks & Regards,


Anantha Raghava


Do not print this e-mail unless required. Save Paper & trees.


___
Users mailing list
Users@ovirt.org 
http://lists.ovirt.org/mailman/listinfo/users





___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt virtio drivers for fedora 5

[Yaniv Kaul]

On Wed, Dec 27, 2017 at 3:07 PM, Anantha Raghava <
rag...@exzatechconsulting.com> wrote:

> Hi,
>
> We have converted a very old fedora 5 server to run on oVirt. However,
> since the Fedora 5 does not have virtio drivers, or virtio-scsi drivers,
> the disks are connected to virtual IDE interface. The problem here is on a
> single IDE interface, we cannot connect more than 2 disks. But the old
> converted server had 4 disks on 2 IDE controllers.
>
> First question is can we add one more virtual IDE Controller to the VM? If
> yes, please share the procedure. Or whether any one can share the proper
> virtio or virtio scsi for fedora 5 OS drivers so that we can get other two
> inactive disks working.
>
> Unfortunately we cannot upgrade from Fedora 5 at the moment.
>

Neither are possible. Does the Fedora have an iSCSI initiator support
perhaps? You can expose those disk via different VMs to that VM - but still
it might look different to the OS.
(We don't even support such an old OS - but if it works, great).
Y.

Await your inputs.
>
> --
>
> Thanks & Regards,
>
>
> Anantha Raghava
>
> Do not print this e-mail unless required. Save Paper & trees.
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] oVirt virtio drivers for fedora 5

[Anantha Raghava]

Hi,

We have converted a very old fedora 5 server to run on oVirt. However, 
since the Fedora 5 does not have virtio drivers, or virtio-scsi drivers, 
the disks are connected to virtual IDE interface. The problem here is on 
a single IDE interface, we cannot connect more than 2 disks. But the old 
converted server had 4 disks on 2 IDE controllers.


First question is can we add one more virtual IDE Controller to the VM? 
If yes, please share the procedure. Or whether any one can share the 
proper virtio or virtio scsi for fedora 5 OS drivers so that we can get 
other two inactive disks working.


Unfortunately we cannot upgrade from Fedora 5 at the moment.

Await your inputs.

--

Thanks & Regards,


Anantha Raghava


Do not print this e-mail unless required. Save Paper & trees.

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Turn on "Nested Virtualization" on the "hosted-engine"

[Michal Skrivanek]

> On 27 Dec 2017, at 13:06, Martin Sivak  wrote:
> 
> Hi,
> 
> it might be a good idea to install vdsm-hooks-nestedvt and
> vdsm-hook-macspoof on the host as described for example here:
> https://community.redhat.com/blog/2013/08/testing-ovirt-3-3-with-nested-kvm/
> 
> Those two hooks will configure the kvm module properly and allow
> dhcp/pxe to be used from within the nested VM.

Yes. Though it’s likely not going to work out of the box anyway due to older 
kernel.
See a guide from Ladi[1], there was also a presentation about nested hyper-v on 
KVMForum 2017 

Thanks,
michal

[1] https://ladipro.wordpress.com/2017/02/24/running-hyperv-in-kvm-guest/ 


> 
> Best regards
> 
> --
> Martin Sivak
> SLA / oVirt
> 
> On Wed, Dec 27, 2017 at 9:05 AM, Michal Skrivanek
>  wrote:
>> 
>> 
>> On 25 Dec 2017, at 13:03, Roman Drovalev  wrote:
>> 
>>> I'm not sure I understand the layering - hyper-V on oVirt or vice-versa?
>> 
>> the layering: oVirt host -> Hyper-V_VM on oVirt -> VM on Hyper-V_VM
>> 
>> CentOS based on linux kernel. I manual modified linux kernel parametrs.
>> 
>> 
>> if you modified the kernel parameters already (which you did, as seen in
>> screen shot your cmdline does have nested virt param) then there’s nothing
>> else to do in the GUI, your host should support nested virtualization.
>> I’m not sure why do you need SR-IOV but that’s not going to work on top of
>> hyperv
>> 
>> 
>> oVirt-engine based on oVirt API. How to manually change the parameters of
>> ovirt-engine through API?
>> 
>>> In any case, I assume an additional host is needed, the host hosting the
>>> Hosted-Engine VM cannot be changed with those parameters when the HE is up.
>>> Y.
>> 
>> It's impossible, the second host is now - Hyper-V with working VM's.
>> 
>> 25.12.2017 12:19, Yaniv Kaul
>> 
>> 
>> 
>> On Mon, Dec 25, 2017 at 10:14 AM, Roman Drovalev 
>> wrote:
>>> 
>>> Thanks for the quick response.
>>> 
 You probably need an additional host.
>>> 
>>> I'm migrating from Hyper-V at the moment there is no way to add a second
>>> host.
>>> 
>>> 
>>> 25.12.2017 10:43, Yaniv Kaul пишет:
 What are you trying to achieve?
>>> 
>>> "Nested Virtualization" . I need run on Hyper-V one VM on the my oVirt
>> 
>> 
>> I'm not sure I understand the layering - hyper-V on oVirt or vice-versa?
>> In any case, I assume an additional host is needed, the host hosting the
>> Hosted-Engine VM cannot be changed with those parameters when the HE is up.
>> Y.
>> 
>>> 
>>> 
>>> 
>>> 
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>> 
>> 
>> 
>> --
>> С уважением, Дровалев Роман
>> инженер ГБУЗ "МИАЦ",
>> Калужской области.
>> тел. 4842 705 004
>> 
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>> 
>> 
>> 
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>> 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Turn on "Nested Virtualization" on the "hosted-engine"

[Martin Sivak]

Hi,

it might be a good idea to install vdsm-hooks-nestedvt and
vdsm-hook-macspoof on the host as described for example here:
https://community.redhat.com/blog/2013/08/testing-ovirt-3-3-with-nested-kvm/

Those two hooks will configure the kvm module properly and allow
dhcp/pxe to be used from within the nested VM.

Best regards

--
Martin Sivak
SLA / oVirt

On Wed, Dec 27, 2017 at 9:05 AM, Michal Skrivanek
 wrote:
>
>
> On 25 Dec 2017, at 13:03, Roman Drovalev  wrote:
>
>>I'm not sure I understand the layering - hyper-V on oVirt or vice-versa?
>
> the layering: oVirt host -> Hyper-V_VM on oVirt -> VM on Hyper-V_VM
>
> CentOS based on linux kernel. I manual modified linux kernel parametrs.
>
>
> if you modified the kernel parameters already (which you did, as seen in
> screen shot your cmdline does have nested virt param) then there’s nothing
> else to do in the GUI, your host should support nested virtualization.
> I’m not sure why do you need SR-IOV but that’s not going to work on top of
> hyperv
>
>
> oVirt-engine based on oVirt API. How to manually change the parameters of
> ovirt-engine through API?
>
>>In any case, I assume an additional host is needed, the host hosting the
>> Hosted-Engine VM cannot be changed with those parameters when the HE is up.
>>Y.
>
> It's impossible, the second host is now - Hyper-V with working VM's.
>
> 25.12.2017 12:19, Yaniv Kaul
>
>
>
> On Mon, Dec 25, 2017 at 10:14 AM, Roman Drovalev 
> wrote:
>>
>> Thanks for the quick response.
>>
>> >You probably need an additional host.
>>
>> I'm migrating from Hyper-V at the moment there is no way to add a second
>> host.
>>
>>
>> 25.12.2017 10:43, Yaniv Kaul пишет:
>> > What are you trying to achieve?
>>
>> "Nested Virtualization" . I need run on Hyper-V one VM on the my oVirt
>
>
> I'm not sure I understand the layering - hyper-V on oVirt or vice-versa?
> In any case, I assume an additional host is needed, the host hosting the
> Hosted-Engine VM cannot be changed with those parameters when the HE is up.
> Y.
>
>>
>>
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
> --
> С уважением, Дровалев Роман
> инженер ГБУЗ "МИАЦ",
> Калужской области.
> тел. 4842 705 004
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] OVS error logs after upgrade to 4.2

[Misak Khachatryan]

On Wed, Dec 27, 2017 at 12:42 PM, Dan Kenigsberg  wrote:
> On Wed, Dec 27, 2017 at 8:49 AM, Misak Khachatryan  wrote:
>> Hi,
>>
>> It's not on log file, it's from automatic email sent by cron daemon.
>> This one from logrotate.
>
> Would you file a bug about this daily logrotate spam?
>

Sure, will do.

>>
>> I'd like to migrate my network to OVS, but as i can't find any guide
>> for that, it's a bit scary.
>
> Why would you like to do that? OVN is useful for big deployments, that
> have many isolated networks. It is not universally recommended, as it
> uses more CPU.
>

No particular reason, thought that will be future in oVIRT networking,
also i work in relatively big ISP with many PoP and DCs in many
cities. And I'm interested to try it some time.

>>
>> Best regards,
>> Misak Khachatryan
>>
>>
>> On Tue, Dec 26, 2017 at 3:29 PM, Dan Kenigsberg  wrote:
>>> On Tue, Dec 26, 2017 at 8:35 AM, Misak Khachatryan  wrote:
 Hi,

 After upgrade to 4.2 I started getting this error from engine:

 /etc/cron.daily/logrotate:

 2017-12-25T23:12:02Z|1|unixctl|WARN|failed to connect to
 /var/run/openvswitch/ovnnb_db.19883.ctl
 ovs-appctl: cannot connect to
 "/var/run/openvswitch/ovnnb_db.19883.ctl" (No such file or directory)
 2017-12-25T23:12:02Z|1|unixctl|WARN|failed to connect to
 /var/run/openvswitch/ovnsb_db.19891.ctl
 ovs-appctl: cannot connect to
 "/var/run/openvswitch/ovnsb_db.19891.ctl" (No such file or directory)


 Seems harmless as i don't use OVS, but how to fix it?
>>>
>>> By default, ovirt-4.2 installs and configure OVN (which uses OVS). You
>>> can turn it off on Engine host by running
>>> systemctl stop ovirt-provider-ovn ovn-northd openvswitch
>
> did you try that?
>

No, but is correct way to disable it completely?

>>>
>>> but I'd appreciate your help to understand in which log file do you
>>> see these warnings?
>
>>> Have you already disabled openvswitch?
>
> have you ^^ ?

No, what is a correct way to do it?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] OVS error logs after upgrade to 4.2

[Dan Kenigsberg]

On Wed, Dec 27, 2017 at 8:49 AM, Misak Khachatryan  wrote:
> Hi,
>
> It's not on log file, it's from automatic email sent by cron daemon.
> This one from logrotate.

Would you file a bug about this daily logrotate spam?

>
> I'd like to migrate my network to OVS, but as i can't find any guide
> for that, it's a bit scary.

Why would you like to do that? OVN is useful for big deployments, that
have many isolated networks. It is not universally recommended, as it
uses more CPU.

>
> Best regards,
> Misak Khachatryan
>
>
> On Tue, Dec 26, 2017 at 3:29 PM, Dan Kenigsberg  wrote:
>> On Tue, Dec 26, 2017 at 8:35 AM, Misak Khachatryan  wrote:
>>> Hi,
>>>
>>> After upgrade to 4.2 I started getting this error from engine:
>>>
>>> /etc/cron.daily/logrotate:
>>>
>>> 2017-12-25T23:12:02Z|1|unixctl|WARN|failed to connect to
>>> /var/run/openvswitch/ovnnb_db.19883.ctl
>>> ovs-appctl: cannot connect to
>>> "/var/run/openvswitch/ovnnb_db.19883.ctl" (No such file or directory)
>>> 2017-12-25T23:12:02Z|1|unixctl|WARN|failed to connect to
>>> /var/run/openvswitch/ovnsb_db.19891.ctl
>>> ovs-appctl: cannot connect to
>>> "/var/run/openvswitch/ovnsb_db.19891.ctl" (No such file or directory)
>>>
>>>
>>> Seems harmless as i don't use OVS, but how to fix it?
>>
>> By default, ovirt-4.2 installs and configure OVN (which uses OVS). You
>> can turn it off on Engine host by running
>> systemctl stop ovirt-provider-ovn ovn-northd openvswitch

did you try that?

>>
>> but I'd appreciate your help to understand in which log file do you
>> see these warnings?

>> Have you already disabled openvswitch?

have you ^^ ?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Turn on "Nested Virtualization" on the "hosted-engine"

[Michal Skrivanek]

> On 25 Dec 2017, at 13:03, Roman Drovalev  wrote:
> 
> >I'm not sure I understand the layering - hyper-V on oVirt or vice-versa?
> 
> the layering: oVirt host -> Hyper-V_VM on oVirt -> VM on Hyper-V_VM
> 
> CentOS based on linux kernel. I manual modified linux kernel parametrs.

if you modified the kernel parameters already (which you did, as seen in screen 
shot your cmdline does have nested virt param) then there’s nothing else to do 
in the GUI, your host should support nested virtualization.
I’m not sure why do you need SR-IOV but that’s not going to work on top of 
hyperv

> 
> oVirt-engine based on oVirt API. How to manually change the parameters of 
> ovirt-engine through API?
> 
> >In any case, I assume an additional host is needed, the host hosting the 
> >Hosted-Engine VM cannot be changed with those parameters when the HE is up.
> >Y.
> 
> It's impossible, the second host is now - Hyper-V with working VM's.
> 
> 25.12.2017 12:19, Yaniv Kaul
>> 
>> 
>> On Mon, Dec 25, 2017 at 10:14 AM, Roman Drovalev > > wrote:
>> Thanks for the quick response.
>> 
>> >You probably need an additional host.
>> 
>> I'm migrating from Hyper-V at the moment there is no way to add a second
>> host.
>> 
>> 
>> 25.12.2017 10 :43, Yaniv Kaul пишет:
>> > What are you trying to achieve?
>> 
>> "Nested Virtualization" . I need run on Hyper-V one VM on the my oVirt
>> 
>> I'm not sure I understand the layering - hyper-V on oVirt or vice-versa?
>> In any case, I assume an additional host is needed, the host hosting the 
>> Hosted-Engine VM cannot be changed with those parameters when the HE is up.
>> Y.
>>  
>> 
>> 
>> 
>> ___
>> Users mailing list
>> Users@ovirt.org 
>> http://lists.ovirt.org/mailman/listinfo/users 
>> 
>> 
> 
> -- 
> С уважением, Дровалев Роман
> инженер ГБУЗ "МИАЦ",
> Калужской области.
> тел. 4842 705 004
> ___
> Users mailing list
> Users@ovirt.org 
> http://lists.ovirt.org/mailman/listinfo/users 
> 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Ovirt 4.2 and host console

[Yuval Turgeman]

Hi

As you can see from the systemctl status, the difference is caused due to
the preset rule for cockpit.socket, which is enabled on the node-ng based
system, and disabled on your regular centos based system.
If you take a look at the cockpit postinstall script, you'd see something
like:

systemctl --no-reload preset cockpit.socket...

This sets the cockpit.socket according to its preset rule.

Thanks,
Yuval.




On Tue, Dec 26, 2017 at 3:35 PM, Gianluca Cecchi 
wrote:

> On Sat, Dec 23, 2017 at 11:18 AM, Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>> On Fri, Dec 22, 2017 at 10:22 PM, Sandro Bonazzola 
>> wrote:
>>
>>>
>>>
>>> Il 22 Dic 2017 10:12 PM, "Yaniv Kaul"  ha scritto:
>>>
>>>
>>>
>>> On Dec 22, 2017 7:33 PM, "Gianluca Cecchi" 
>>> wrote:
>>>
>>> Hello, after upgrading engine and then  plain CentOS 7.4 host from 4.1
>>> to 4.2, I see in host section if I select line for the host, right click
>>> and host console... That tries to go to the typical 9090 cockpit Port of
>>> node-ng...
>>> Is this an error or in 4.2 the access to host console is for plain OS
>>> nodes too?
>>> In that case is there any service I have to enable on host?
>>> It seems indeed my host is not currently listening on 9090 Port
>>>
>>>
>>> Cockpit + firewall settings to enable to get to it.
>>>
>>>
>>> Cockpit service should be up and running after the upgrade. Ovirt hist
>>> depliy takes care of it. Firewall is configured by the engine unless you
>>> disabled firewall config on the host configuration dialog.
>>>
>>> Didi, can you help here? Gianluca, can you share host upgrade logs?
>>>
>>>
>>>
>> Hello,
>> this is a plain CentOS, not ovirt-node-ng one, that was upgraded from
>> 4.1.7 to 4.2
>> So the upgrade path has been to put the host into maintenance, yum
>> update, reboot.
>>
>> Indeed cockpit has been installed as part of the yum update part:
>>
>> Dec 22 10:40:07 Installed: cockpit-bridge-155-1.el7.centos.x86_64
>> Dec 22 10:40:07 Installed: cockpit-system-155-1.el7.centos.noarch
>> Dec 22 10:40:40 Installed: cockpit-networkmanager-155-1.el7.centos.noarch
>> Dec 22 10:40:42 Installed: cockpit-ws-155-1.el7.centos.x86_64
>> Dec 22 10:40:43 Installed: cockpit-155-1.el7.centos.x86_64
>> Dec 22 10:40:52 Installed: cockpit-storaged-155-1.el7.centos.noarch
>> Dec 22 10:40:57 Installed: cockpit-dashboard-155-1.el7.centos.x86_64
>> Dec 22 10:41:35 Installed: cockpit-ovirt-dashboard-0.11.3
>> -0.1.el7.centos.noarch
>>
>> I also see that there is a systemd cockpit.service unit that is
>> configured as static and requires a cockpit.socket unit, that in turn is
>> WantedBy sockets.target
>>
>> But if I run
>>
>> [root@ovirt01 ~]# remotectl certificate
>> remotectl: No certificate found in dir: /etc/cockpit/ws-certs.d
>> [root@ovirt01 ~]#
>>
>> So it seems that the cockpit.service ExecStartPre has not been ever
>> run...
>> ExecStartPre=/usr/sbin/remotectl certificate --ensure --user=root
>> --group=cockpit-ws --selinux-type=etc_t
>>
>> [root@ovirt01 ~]# systemctl status cockpit.service
>> ● cockpit.service - Cockpit Web Service
>>Loaded: loaded (/usr/lib/systemd/system/cockpit.service; static;
>> vendor preset: disabled)
>>Active: inactive (dead)
>>  Docs: man:cockpit-ws(8)
>> [root@ovirt01 ~]#
>>
>> Gianluca
>>
>>
>>
> At the end I compared my CentOS 7.4 oVirt 4.2 configuration with the
> configuration of a RHEV 4.1 RHV-H environment and there I see this kind of
> config
>
> [root@rhevora1 ~]# systemctl status cockpit.socket
> ● cockpit.socket - Cockpit Web Service Socket
>Loaded: loaded (/usr/lib/systemd/system/cockpit.socket; enabled;
> vendor preset: enabled)
>Active: active (listening) since Fri 2017-10-27 17:02:30 CEST; 1 months
> 29 days ago
>  Docs: man:cockpit-ws(8)
>Listen: [::]:9090 (Stream)
>
> Oct 27 17:02:30 rhevora1.mydomain systemd[1]: Listening on Cockpit Web
> Service Socket.
> Oct 27 17:02:30 rhevora1.mydomain systemd[1]: Starting Cockpit Web Service
> Socket.
> [root@rhevora1 ~]#
>
> So there is basically the difference that on RHEV RHV-H the cockpit.socket
> systemd unit is enabled by default (cockpit-ws-148-1.el7.x86_64), while on
> this just updated to 4.2 oVirt host on plain CentOS we have
>
> [root@ovirt01 etc]# systemctl status cockpit.socket
> ● cockpit.socket - Cockpit Web Service Socket
>Loaded: loaded (/usr/lib/systemd/system/cockpit.socket; disabled;
> vendor preset: disabled)
>Active: inactive (dead)
>  Docs: man:cockpit-ws(8)
>Listen: 0.0.0.0:9090 (Stream)
> [root@ovirt01 etc]#
>
> On oVirt 4.2 the version is currently cockpit-ws-155-1.el7.centos.x86_64
>
> What I've done has been
> systemctl enable cockpit.socket
> systemctl start cockpit.socket
>
> and now I have the ovirt01 host correctly listening on 9090 port and I'm
> able to web connect and enjoy...
>
> Let me know if this is a sort of regression of cockpit-ws package or
> what...
>
>