- Original Message -
> From: "Jakub Bittner"
> To: users@ovirt.org
> Sent: Tuesday, April 30, 2013 5:19:12 PM
> Subject: [Users] Fault tolerant storage
>
> Hi,
>
> would it be possible in near future to use for example 2 attached DATA
> storage (iSCSi, or so) as fault tolerant storage?
- Original Message -
> From: "Sherry Yu"
> To: "Vered Volansky"
> Cc: users@ovirt.org
> Sent: Wednesday, May 1, 2013 3:39:53 AM
> Subject: Re: [Users] Error Attaching NFS Data Domain to Data Center - oVirt
> 3.3
>
> I upgraded kernel, sanlock, and its dependencies on the f18 host, and
I upgraded kernel, sanlock, and its dependencies on the f18 host, and the error
is gone.
Thanks,
Sherry
- Original Message -
| Hi Sherry,
|
| Since it doesn't seem like permissions, the next guess would be -
| There was a workaround done in regard to broken watchdog.
| This workaround i
- Original Message -
> From: snmis...@linux.vnet.ibm.com
> To: "Alon Bar-Lev"
> Cc: users@ovirt.org
> Sent: Wednesday, May 1, 2013 1:02:27 AM
> Subject: Re: [Users] Unable to install F18 on a VM from engine.
>
>
> Quoting Alon Bar-Lev :
>
> > - Original Message -
> >> From: sn
Quoting Alon Bar-Lev :
- Original Message -
From: snmis...@linux.vnet.ibm.com
To: "Alon Bar-Lev"
Cc: users@ovirt.org
Sent: Tuesday, April 30, 2013 4:50:19 PM
Subject: Re: [Users] Unable to install F18 on a VM from engine.
Quoting Alon Bar-Lev :
> I don't understand...
> How did you
On Tue, Apr 23, 2013 at 8:58 AM, Michal Skrivanek wrote:
>>>
>>
>> do we allow users to cancel the shutdown?
> nope.
> It can be stopped inside the guest, well, if you manage to do that in that
> short time.
>
BTW: I tried today with ovirt 3.2.1 and it is not possible to
interrupt shutdown, at l
my pleasure.
Sorry it took so long to get to it.
- Original Message -
> From: "Dennis Böck"
> To: "Allon Mureinik" , d...@redhat.com
> Cc: "users@oVirt.org"
> Sent: Monday, April 29, 2013 10:47:18 AM
> Subject: AW: [Users] Configure local storage: VAR__TYPE__STORAGE__DOMAIN,
> VAR__ACTI
On Tue, Apr 30, 2013 at 02:27:16PM +, Jonathan Horne wrote:
> I did try to create a new VM and add the 2 disks that were
> originally imported, but still no go. The vm refuses to boot.
You need to be much more specific about how it "refuses to boot".
> I was also unable to import just the D
- Original Message -
> From: snmis...@linux.vnet.ibm.com
> To: "Alon Bar-Lev"
> Cc: users@ovirt.org
> Sent: Tuesday, April 30, 2013 4:50:19 PM
> Subject: Re: [Users] Unable to install F18 on a VM from engine.
>
>
> Quoting Alon Bar-Lev :
>
> > I don't understand...
> > How did you add
I did try to create a new VM and add the 2 disks that were originally imported,
but still no go. The vm refuses to boot.
I was also unable to import just the D drive attached to a VM, it gave me the
error " virt-v2v: No root device found in this operating system image". Right
now I am trying
Hi,
would it be possible in near future to use for example 2 attached DATA
storage (iSCSi, or so) as fault tolerant storage?
I mean I have two data storage connected to data center and they include
exactly same data and my VMs runs from one and all changes are mirrored
to second like RAID 1
Quoting Alon Bar-Lev :
I don't understand...
How did you add the host to the engine? Using "Add Host" or hack?
If "Add Host", can you please attach the relevant log from
/var/log/ovirt-engine/host-deploy?
Thanks!
I did not install engine from RPM, it was built from source. I do not
see a
Hi Sherry,
Since it doesn't seem like permissions, the next guess would be -
There was a workaround done in regard to broken watchdog.
This workaround is in the latest sanlock for fedora 18, which you are already
using.
If this is indeed the case, all you have to do is update sanlock to latest,
Jonathan,
I've asked around (with people not that familiar with v2v) and we're thinking
of two options -
1. Assuming that the disks weren't imported with the vm at all use v2v to
import each disk separately, then create a new VM and configure it from the top.
2. If the disks were indeed imported
14 matches
Mail list logo
