Some more information.
I had shutdown the VM on VMWare workstation, exported it as an ova, did
the virt-v2v and imported it. To work on it I went to another
workstation running the same OS (Fedora 23) and ran the oVirt web
portal. From there I tried to access this new VM's console (or any but
c
I'm on 3.6.4 (yes I'll update soon when I get time) and I can't access
the VMs via console anymore. At one time I right clicked, choose
consoel and had a console open in a window.
The VMS show SPICE as the graphics in the admin web so I assume that's
default. Now if I try and open a console I'm
The oVirt Project is pleased to announce the availability of the Second
Release Candidate of oVirt 3.6.6 for testing, as of May 7th, 2016
This release is available now for:
* Fedora 22
* Red Hat Enterprise Linux 6.7
* CentOS Linux 6.7 (or similar)
* Red Hat Enterprise Linux 7.2 or later
* CentOS L
That’s in iptables, right? I have iptables disabled on my oVirt nodes...
From: Yaniv Kaul [mailto:yk...@redhat.com]
Sent: Friday, May 06, 2016 3:50 PM
To: Will Dennis
Subject: Re: [ovirt-users] virt-in-virt problem: DHCP failing for a container
in a oVirt VM
Long shot - you need to disable the E
Hi all,
Have an interesting problem - I am running a VM in oVirt that is running
Proxmox VE 4.1 OS, which I have spun up a container on. The container is set
for DHCP, and I have verified that it is sending Discover packets as normal,
and that these packets are making it out of the Proxmox VM
To try to learn the python SDK, and help the automation of my setup, I wrote a
CLI to oVirt.
It tries to hide some of the complexity, so some simple python script like :
dc = context.datacenter(name="dc1")
if dc is not None:
dc.delete(force=True)
context.datacenter().create(name="dc1", local
I'm following the example given in http://www.ovirt.org/develop/api/pythonapi/
for bonding interfaces.
I'm checking that the network is a plain configuration, exporting
/api/hosts//nics return :
eth1
none
down
Once upon a time, Nir Soffer said:
> On Fri, May 6, 2016 at 4:01 PM, Chris Adams wrote:
> > One of my oVirt clusters, running 3.6.5, lost power last night (power
> > failure plus bad UPS batteries - batteries on order!). When power came
> > back, the storage and nodes came back, and then the hos
On Fri, May 6, 2016 at 4:01 PM, Chris Adams wrote:
> One of my oVirt clusters, running 3.6.5, lost power last night (power
> failure plus bad UPS batteries - batteries on order!). When power came
> back, the storage and nodes came back, and then the hosted engine
> started, but nothing else happe
One of my oVirt clusters, running 3.6.5, lost power last night (power
failure plus bad UPS batteries - batteries on order!). When power came
back, the storage and nodes came back, and then the hosted engine
started, but nothing else happened (no other VMs started).
I expected that VMs that were r
On 05/06/2016 05:57 PM, Piotr Kliczewski wrote:
Hi,
You may want to experiment with [1]. Instead of writing a bash script
you can use python for your testing.
Here [2] is an example how to use it. Let me know if you need more
help with creating a script.
Thanks,
Piotr
[1]
https://gerrit.ovirt
Hi,
You may want to experiment with [1]. Instead of writing a bash script
you can use python for your testing.
Here [2] is an example how to use it. Let me know if you need more
help with creating a script.
Thanks,
Piotr
[1]
https://gerrit.ovirt.org/gitweb?p=vdsm.git;a=blob;f=lib/vdsm/jsonrpcvd
Hi,
Back to Import Storage domain questions -
To ensure consistency, we snapshot the running VMs prior to replicating
the gluster volume to a central site. The VMs have been setup such that
OS disks are on a gluster volume called "vmstore" and non-OS disks are
on a gluster volume called "data
Hi All,
I want to write a script to poweroff vms and start vms in a loop for
my testing. I found the command to poweroff the vms by looking at the
vdsClient -h, but can some one help me how to start the powered off vm
using vdsClient command ??
Thanks
kasturi.
On 05/06/2016 07:58 AM, Jorick Astrego wrote:
> Hi,
>
> One of our older ovirt engine 3.5.5 (CentOS 7) machines had a raid
> controller faillure and no recent ovirt-engine backup.
>
> So I recovered the files + database and reinstalled with
> ovirt-engine-3.5.6.2-1. But I can't get it to work.
>
Hi,
could you please share comple engine logs?
Thanks
Martin Perina
On Fri, May 6, 2016 at 7:58 AM, Jorick Astrego wrote:
> Hi,
>
> One of our older ovirt engine 3.5.5 (CentOS 7) machines had a raid
> controller faillure and no recent ovirt-engine backup.
>
> So I recovered the files + datab
16 matches
Mail list logo