Re: [ovirt-users] Windows 10 + qemu + Blue Iris = Blue screen

2016-07-26 Thread Frank Wall
On Fri, Jul 22, 2016 at 03:58:56PM -0500, Blaster wrote: > I did try a clean install. Both an upgrade and a fresh install cause a blue > screen. How do I pin point the blue screen? In my case I could solve this issue by changing the number of (virtual) CPUs to only 1 for the Windows 10 VM. The

[ovirt-users] Problems installing Ovirt 4.02 Node

2016-07-26 Thread Peter Michael Calum
Hi group, Im trying to install a Ovirt 4.02 Hypervisor Node (ovirt-node-ng-installer-ovirt-4.0-pre-2016072108.iso). Hardware is IBM X3550M4 with 256 GB Ram. I follow the installation steps and use automatic partitioning and installation goes fine without errors. I only create the root user.

Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages

2016-07-26 Thread Martin Perina
On Tue, Jul 26, 2016 at 5:39 PM, Jiri Belka wrote: > > Hi, > > > > Unfortunately, upgrading to 4.0.1RC didn't solve the problem. Actually, > > the error changed to 'General SSLEngine problem', but the result was the > > same, like this: > > > > 2016-07-13 09:52:22,010 INFO > >

Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages

2016-07-26 Thread Jiri Belka
> > Unfortunately, upgrading to 4.0.1RC didn't solve the problem. Actually, > > the error changed to 'General SSLEngine problem', but the result was the > > same, like this: > > > > 2016-07-13 09:52:22,010 INFO > > [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp > > Reactor) []

Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages

2016-07-26 Thread Jiri Belka
> Hi, > > Unfortunately, upgrading to 4.0.1RC didn't solve the problem. Actually, > the error changed to 'General SSLEngine problem', but the result was the > same, like this: > > 2016-07-13 09:52:22,010 INFO > [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp > Reactor) []

Re: [ovirt-users] Unable to import pre-configured nfs data domain

2016-07-26 Thread Logan Kuhn
I'd be happy to, but how/where do I do that? Regards, Logan - On Jul 25, 2016, at 2:56 PM, Sandro Bonazzola wrote: | Il 22/Lug/2016 17:10, "Logan Kuhn" < log...@wolfram.com > ha scritto: | > Thank you! | > That does do some interesting things, but doesn't appear

Re: [ovirt-users] ovirt 3.6.6 and gluster 3.7.13

2016-07-26 Thread David Gossage
On Tue, Jul 26, 2016 at 4:37 AM, Krutika Dhananjay wrote: > Hi, > > 1. Could you please attach the glustershd logs from all three nodes? > Here are ccgl1 and ccgl2. as previously mentioned ccgl3 third node was down from bad nic so no relevant logs would be on that node.

Re: [ovirt-users] How do I activate a hot-plugged disk (in v3 Python SDK) ?

2016-07-26 Thread Juan Hernández
On 07/26/2016 08:53 AM, Yaniv Kaul wrote: > > > On Mon, Jul 25, 2016 at 4:36 PM, Ondra Machacek > wrote: > > You actually have to run method 'activate()'[1] on VM disk. > > So it will look like this: > >

[ovirt-users] Some question about vdsm rpc

2016-07-26 Thread lifuqiong
1. We know that xmlrpc and jsonrpc are enabled default in vdsm, vdsm supply these two service in one port or two? What's the port number and how we can change it? 2. How can we know a vdsm host can supply an xmlrpc service or a jsonrpc service? 3. I found that while ovirt

Re: [ovirt-users] Fedora 24 SSO

2016-07-26 Thread Tadas
Thank you. This did the trickOn Tue, 2016-07-26 at 12:26 +0200, Vinzenz Feenstra wrote: > > > On Jul 26, 2016, at 11:39 AM, Vinzenz Feenstra > > wrote: > > > > > On Jul 22, 2016, at 7:38 AM, Tadas wrote: > > > > > > Hello, > > > I'm having problems to get

Re: [ovirt-users] Fedora 24 SSO

2016-07-26 Thread Vinzenz Feenstra
> On Jul 26, 2016, at 11:39 AM, Vinzenz Feenstra wrote: > >> >> On Jul 22, 2016, at 7:38 AM, Tadas wrote: >> >> Hello, >> I'm having problems to get SSO working on Fedora24 guest. >> >> The following packages are installed on guest: >> >>

Re: [ovirt-users] Fedora 24 SSO

2016-07-26 Thread Vinzenz Feenstra
> On Jul 22, 2016, at 7:38 AM, Tadas wrote: > > Hello, > I'm having problems to get SSO working on Fedora24 guest. > > The following packages are installed on guest: > > ovirt-guest-agent-common.noarch1.0.12- > 3.fc24@updates >

Re: [ovirt-users] ovirt 3.6.6 and gluster 3.7.13

2016-07-26 Thread Krutika Dhananjay
Hi, 1. Could you please attach the glustershd logs from all three nodes? 2. Also, so far what we know is that the 'Operation not permitted' errors are on the main vm image itself and not its individual shards (ex deb61291-5176-4b81-8315-3f1cf8e3534d). Could you do the following: Get the inode

Re: [ovirt-users] vdsm ssl errors

2016-07-26 Thread Piotr Kliczewski
Christoph, Please apply [1] we would know exactly what verbs were called by this local client. Thanks, Piotr [1] https://gerrit.ovirt.org/#/c/61367/ On Mon, Jul 25, 2016 at 9:50 PM, Piotr Kliczewski < piotr.kliczew...@gmail.com> wrote: > On Mon, Jul 25, 2016 at 6:18 PM, Nir Soffer

Re: [ovirt-users] Hosted Engine & FC Data Domain

2016-07-26 Thread Simone Tiraboschi
On Tue, Jul 26, 2016 at 12:47 AM, Anantha Raghava wrote: > Hello, > > I had recently installed oVirt 4.0.1 Hosted Engine with FC (SAN) Storage. > > I could install the oVirt, deploy hosted-engine. But when I accessed the > Engine Web Admin, I noticed the following:

Re: [ovirt-users] How do I activate a hot-plugged disk (in v3 Python SDK) ?

2016-07-26 Thread Yaniv Kaul
On Mon, Jul 25, 2016 at 4:36 PM, Ondra Machacek wrote: > You actually have to run method 'activate()'[1] on VM disk. > > So it will look like this: > > api.vms.get(VM0_NAME).disks.get(DISK1_NAME).activate() > > [1] >

Re: [ovirt-users] oVirt 4 Hosted Engine deploy on fc storage - [ ERROR ] Failed to execute stage 'Misc configuration': [Errno 101] Network is unreachable

2016-07-26 Thread Edward Haas
On Mon, Jul 25, 2016 at 4:02 PM, Simone Tiraboschi wrote: > On Mon, Jul 25, 2016 at 2:38 PM, wrote: > > telnet kom-ad01-vm31.holding.com 54321 = success connection > > > > telnet ::1 54321 > > Trying ::1... > > telnet: connect to address ::1: