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:
systemct
> 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
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
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
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 withi
> 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 config
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
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. T
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
mailto:rag...@exzatechconsulting.com>>
wrote:
Hi
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 co
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 Tim
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
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 t
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
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 wi
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:
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 Messa
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
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.
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 a
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 interr
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 rei
22 matches
Mail list logo
