It's FC 19 with all of the latest updates.
On 01/06/2014 05:56 AM, Sven Kieske wrote:
Hi,
just out of curiosity (I'm also looking
at implementing bonding on our ComputeNodes):
Which OS version are you running ?
___
Users mailing list
I've run into another issue with Ovirt 3.3.2.
We have a 2 node VM cluster with Fibre Channel storage. After upgrade
everything to FC 19 and installing Ovirt 3.3 from scratch one of the
nodes has network issues.
The issue is that when we start a VM on the node, the VM cannot access
the network.
Hello All,
A little bit ago I wrote an email about network issues I was having.
I found the problem...
On the VM host, I had a bond set up between two network interfaces. The
bond mode was set to mode 1 (active/passive).
However when I look at the bond on the box, I get this:
[root@node02
Hi,
Has anyone run across this error:
Cannot run VM. Invalid time zone for given OS type.
The OS type for these VMs is set to Linux Other. They were all exported
from an Ovirt 3.2 cluster and are being reimported into an Ovirt 3.3
cluster. None of these VMs will boot. We also can't delete
:41 PM, Dan Ferris wrote:
So, just an update...
I upgraded to Ovirt 3.3.0.1 today and I have the latest libvirt.
I *THINK* the issue may be gone, but I will have to do a little more
testing.
Dan
On 10/18/2013 11:15 AM, Dan Ferris wrote:
That did work. vdsmd decided it would start again.
Dan
So, just an update...
I upgraded to Ovirt 3.3.0.1 today and I have the latest libvirt.
I *THINK* the issue may be gone, but I will have to do a little more
testing.
Dan
On 10/18/2013 11:15 AM, Dan Ferris wrote:
That did work. vdsmd decided it would start again.
Dan
On 10/17/2013 3:15 PM
That did work. vdsmd decided it would start again.
Dan
On 10/17/2013 3:15 PM, Jason Brooks wrote:
- Original Message -
From: Dan Ferris dfer...@prometheusresearch.com
To: users@ovirt.org users@ovirt.org
Sent: Tuesday, October 15, 2013 9:24:44 AM
Subject: [Users] vdsmd seg fault
I
On 10/16/2013 12:27 AM, Dan Kenigsberg wrote:
On Tue, Oct 15, 2013 at 10:24:44AM -0600, Dan Ferris wrote:
I updated to the latest Fedora 19 on two test servers, and now vdsmd
will not start.
Systedctl says this:
dsmd.service - Virtual Desktop Server Manager
Loaded: loaded (/usr/lib
On 10/16/2013 8:55 AM, Dan Kenigsberg wrote:
On Wed, Oct 16, 2013 at 08:33:10AM -0600, Dan Ferris wrote:
On 10/16/2013 12:27 AM, Dan Kenigsberg wrote:
On Tue, Oct 15, 2013 at 10:24:44AM -0600, Dan Ferris wrote:
I updated to the latest Fedora 19 on two test servers, and now vdsmd
On 10/16/2013 7:27 AM, Douglas Schilling Landgraf wrote:
On 10/16/2013 02:27 AM, Dan Kenigsberg wrote:
On Tue, Oct 15, 2013 at 10:24:44AM -0600, Dan Ferris wrote:
I updated to the latest Fedora 19 on two test servers, and now vdsmd
will not start.
Systedctl says this:
dsmd.service
I updated to the latest Fedora 19 on two test servers, and now vdsmd
will not start.
Systedctl says this:
dsmd.service - Virtual Desktop Server Manager
Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled)
Active: failed (Result: exit-code) since Mon 2013-10-14 12:31:30
EDT;
A few decent Linux servers and LIO is what we use. LIO works pretty well.
Dan
On 10/8/2013 11:12 AM, Zachary Musselman wrote:
Hello,
My company is looking to deploy ovirt.
We are looking for recommendations for storage hardware. What vendors
or appliances are individuals using with iscsi
again with the
URL above https://ovirtengine/disks/disk-id send a DELETE using HTTP/CURL
Again, this was a poor mans solution but it worked for me.
On Thu, Sep 26, 2013 at 4:04 AM, Dan Ferris
dfer...@prometheusresearch.com
mailto:dfer...@prometheusresearch.comwrote:
Hi,
I have another
*all* of the vdsm.log* files?
- Original Message -
Hi Dan, it looks like one of the domains is missing:
6cf7e7e9-3ae5-4645-a29c-fb17ecb38a50
Is there any target missing? (disconnected or somehow faulty or
unreachable)
--
Federico
- Original Message -
From: Dan Ferris dfer
Hi,
This is my first post to the list. I am happy to say that we have been
using Ovirt for 6 months with a few bumps, but it's mostly been ok.
Until tonight that is...
I had to do a maintenance that required rebooting both of our Hypervisor
nodes. Both of them run Fedora Core 18 and have
15 matches
Mail list logo