Hello oVirt guru out there:
I notice our oVirt engine postgres db size is growing quite fast for past
couple of months. I checked the database size. Found that our
ovirt_engine_history is 73GB in size.
engine=# \connect ovirt_engine_history
You are now connected to database
Jon,
Thanks for the advice!
On 10/13/2015 05:51 PM, Jon Archer wrote:
Personally I would take full advantage of the maintenance modes,
upgrading the engine before the hosts too.
Putting the hosts in maintenance mode before upgrading at least will
allow for the vm's to migrate to the other
On Tue, Oct 13, 2015 at 9:24 AM, Nico wrote:
> Le 2015-10-13 09:08, Nico a écrit :
>
> Le 2015-10-12 09:17, Nico a écrit :
>
> Le 2015-10-12 09:09, Barak Korren a écrit :
>
>
>
> What that procedure describes is backing up an existing engine,
> installing a new one and then
Le 2015-10-12 09:17, Nico a écrit :
> Le 2015-10-12 09:09, Barak Korren a écrit :
>
> What that procedure describes is backing up an existing engine,
> installing a new one and then restoring the backed up data into it.
> This was probably written to describe migration from a stand-alone
>
Le 2015-10-13 09:08, Nico a écrit :
> Le 2015-10-12 09:17, Nico a écrit :
>
> Le 2015-10-12 09:09, Barak Korren a écrit :
>
> What that procedure describes is backing up an existing engine,
> installing a new one and then restoring the backed up data into it.
> This was probably written
Here the log error during VM creaation:
2015-10-13 09:37:06 DEBUG
otopi.plugins.ovirt_hosted_engine_setup.vm.runvm plugin.execute:937
execute-output: ['/bin/vdsClient', '-s', 'localhost', 'setVmTicket',
'e88a4313-863f-4d08-87e3-110fa002a6a5', '**FILTERED**', '10800'] stderr:
2015-10-13
Le 2015-10-13 09:27, Simone Tiraboschi a écrit :
>> I don't understand what is it expecting for the PATH ? i've no idea what
>> INSTALLATION MEDIA is about.
>>
>> Could you please give me a clue ?
>
> You choose to create your new engine VM booting from a CDRom image so you
> have to
hi
is ovirt useable with xen? is there any doc/howto how to use it?
Am 2015-10-12 15:04, schrieb Sven Kieske:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/10/15 10:13, Nux! wrote:
Hi Nir,
I have not tried to use Ovirt with Ceph, my question was about
libvirt and was directed to ask
I'm generating network activity on a VM using iperf.The VM acts as an iperf
client.On the client,iperf reports that data has been successfully sent to
iperf server.The iperf server also shows that it's successfully receiving
data from the iperf client.But,network is at 0% on the ovirt UI.The
I'm generating network activity on a VM using iperf.The VM acts as an iperf
client.On the client,iperf reports that data has been successfully sent to
iperf server.The iperf server also shows that it's successfully receiving
data from the iperf client.But,network is at 0% on the ovirt UI.The
I'm generating network activity on a RHEV 3.5 VM using iperf.The VM acts as
an iperf client.On the client,iperf reports that data has been successfully
sent to iperf server.The iperf server also shows that it's successfully
receiving data from the iperf client.But,network is at 0% on the RHEV-M
Julian,
Lets try a more systematic approach (similar to what Donny suggests):
Please disable your arp script, and reproduce the situation where your vm
cannot connect to the outside.
It will be also a good idea to have the failing machine be the only powered
on machine connected to the network
Hi Elad,
Is the image located under the same storage pool the host is currently
connected to?
You can check the current connected storage pool by the following:
# vdsClient -s 0 getConnectedStoragePoolsList
yes, it is located on the same storage pool
vdsClient -s 0
On 10/13/2015 12:48 PM, Budur Nagaraju wrote:
While installing am getting the error ,tried by increasing CPU but no
luck,
getting the error below error.
'system thread exception not handled"
Please change the Disk interface type to 'IDE'
To change that you go to the admin interface
Choose
On Tue, Oct 13, 2015 at 12:03 PM, Budur Nagaraju wrote:
> HI
>
> Getting below error and using ovirt node version is "oVirt Node Hypervisor
> release 3.5 (0.999.201509102313.el7.centos)"
>
>
> " your PC ran into problem and needs to restart"
>
> could you pls help me in
While installing am getting the error ,tried by increasing CPU but no luck,
getting the error below error.
'system thread exception not handled"
On Tue, Oct 13, 2015 at 4:06 PM, Gianluca Cecchi
wrote:
> On Tue, Oct 13, 2015 at 12:03 PM, Budur Nagaraju
HI
Getting below error and using ovirt node version is "oVirt Node Hypervisor
release 3.5 (0.999.201509102313.el7.centos)"
" your PC ran into problem and needs to restart"
could you pls help me in resolving the issue ?
Thanks,
Nagaraju
On Fri, Oct 9, 2015 at 6:53 PM, Vinzenz Feenstra
- Original Message -
> From: "Indunil Jayasooriya"
> To: users@ovirt.org
> Sent: Tuesday, October 13, 2015 6:13:22 AM
> Subject: [ovirt-users] oVirt - High Availability
>
> Hi users,
>
>
> I have setup OVIRT 3.5 with 2 REDHAT 7.1 hosts. Everything is ok other
Fedora 20 is not supportrd, in particular with virt-preview repo, which is
not maintained few month before Fedora 20 went EOL.
The best advice is to upgrade the host to Fedora 21.
בתאריך 13 באוק׳ 2015 3:04 אחה״צ, "Roel de Rooy" כתב:
> Hi all,
>
>
>
> 1 of our older clusters
Hi Marc
I think this will answer your question --> we have an open bug for this issue
-->
https://bugzilla.redhat.com/show_bug.cgi?id=1196640
Kind regards,
- Original Message -
From: "Marc Seward"
To: users@ovirt.org
Sent: Monday, October 12, 2015 6:31:09 PM
Hi all,
1 of our older clusters in use, consists of 2 nodes contain Fedora 20, with the
virt-preview repository enabled.
The Engine itself is installed on a dedicated server (CentOS 6) and is still on
version 3.5.1.1-1.el6.
During some maintenance a couple of days ago on the Fedora 20 nodes,
Is there a best practice when upgrading from ovirt 3.4 to 3.5?
I upgraded my development server which is a self hosted server and I
just did a regular update without putting anything under maintenance...
Though my vm's where turned off. It all went well and the migration from
krb/ldap to AAA
Hi,
Thank you very much for your reply.
I would like to know in which cases HA will happen?
1. network failure? ( i.e , if we accidentally remove the network cable or
if network card stopped working due to some reasons. )
2. Server is suddenly shut-down due to power failure (i.e - NOT a proper
On 10/12/2015 06:43 PM, Nico wrote:
Le 2015-10-12 14:04, Nir Soffer a écrit :
Yes, engine will let you use such volume in 3.5 - this is a bug. In
3.6 you will
not be able to use such setup.
replica 2 fails in a very bad way when one brick is down; the
application may get
stale data, and
Hello oVirt guru out there:
I notice our oVirt engine postgres db size is growing quite fast for past
couple of months. I checked the database size. Found that our
ovirt_engine_history is 73GB in size.
engine=# \connect ovirt_engine_history
You are now connected to database
On Wed, Oct 7, 2015 at 6:49 PM, wrote:
>> Hi ccox,
>> you can see the disk id mapping to device if you execute 'ls -l
>> /dev/disk/by-id/' .
>> Second way, and easier, is to make sure you have guest-agent installed on
>> your guest virtual machine and using rest API you can
On Wed, Oct 7, 2015 at 7:58 PM, Jiří Sléžka wrote:
> Hi,
>
> Dne 6.10.2015 v 22:07 c...@endlessnow.com napsal(a):
>>
>> I want to correlate virtual disks back to their originating storage under
>> ovirt. Is there any way to do this?
>>
>> e.g. (made up example)
>>
>> /dev/vda
Personally I would take full advantage of the maintenance modes,
upgrading the engine before the hosts too.
Putting the hosts in maintenance mode before upgrading at least will
allow for the vm's to migrate to the other hosts in the cluster incase
of an outage.
Jon
On 13/10/15 16:25,
Thanks for your response Michael.
This is not the same issue as the one reported in
https://bugzilla.redhat.com/show_bug.cgi?id=1196640 and here's why.
I can see network activity on the Virtual Machines tab when network
activity is generated using wget to download a file from a public site,but
29 matches
Mail list logo