See the migration instructions at the bottom of the relese notes. Basically
you shut down all of your VMs, export them to your export domain. Now all you
have to do is preserve that export domain storage. Everything else should be
blown away and rebuilt as a completely new install. Then you
[lp...@redhat.com]
Sent: Tuesday, August 07, 2012 2:05 AM
To: Jacob Wyatt
Cc: users@oVirt.org
Subject: Re: [Users] 3.1 network setup
On 06/08/12 20:52, Jacob Wyatt wrote:
I'm using the iso images for oVirt Node Hypervisor release 2.5.0 (2.0.fc17).
I was able to manually edit the ifcfg files
# grep -v ^# /etc/libvirt/qemu-sanlock.conf
auto_disk_leases=0
require_lease_for_disks=0
I did try systemd-vdsmd reconfigure.
From: Mark Wu [wu...@linux.vnet.ibm.com]
What does grep -v ^# /etc/libvirt/qemu-sanlock.conf say?
Have you tried
Solved with a hack.
oVirt Node Hypervisor release 2.5.0 (2.0.fc17)
Couldn't start a VM because sanlock wasn't running.
Sanlock wasn't running because wdmd wasn't running.
wdmd was running because softdog kernel module wasn't loaded.
As I didn't know of another way of making the change
I don't know if this is the same issue but for some reason my CA cert for spice
was a blank file. I copied another one from the vdsm directory (mostly
guessing) and it worked.
cp /etc/pki/vdsm/certs/cacert.pem /etc/pki/vdsm/libvirt-spice/ca-cert.pem
Anyone know if I can share an nfs export volume between two discrete ovirt
installations? I'm migrating VMs from a 3.0 install to a 3.1 install and
wondered if I could have the same export domain connected both that the same
time? Just curious.
-Jacob
I need to work that out so I can
actually test the networking.
From: Livnat Peer [lp...@redhat.com]
Sent: Monday, August 06, 2012 2:04 AM
To: Jacob Wyatt
Cc: users@oVirt.org
Subject: Re: [Users] 3.1 network setup
On 06/08/12 05:06, Jacob Wyatt wrote:
OK
I just installed a new 3.1 engine and I have one node with the latest node iso
installed. After setting up one of the network interfaces on the node and
confirming I have network I am able to attach it to the engine. I've done this
starting from both the node and the engine and it seems to
If I wanted to have a script run on the on oVirt Node after it has finished
booting, where would I do that? Between the persistent files configuration and
the newer systemd initialization, I'm trying to find the right way to do this.
-Jacob
___
Users
. Hopefully I won't make it again next time.
Thank you again,
-Jacob
From: Federico Simoncelli [fsimo...@redhat.com]
Sent: Thursday, May 10, 2012 3:38 AM
To: Jacob Wyatt
Cc: users@ovirt.org
Subject: Re: [Users] image ownership
- Original Message -
From
Greetings all,
I've set up a new oVirt installation and it's behaving strangely with regard to
virtual machine image files on the NFS storage. Whenever I shut down a machine
it's changing the owner of the image to root:root (0:0) instead of vdsm:kvm
(36:36). After that it can't start or do
Hi,
I'm new to oVirt myself but I thought that the top level directory name was the
UUID of the storage pool. In that case the UUID it lists
(af5bcc86-898a-11e1-9632-003048c85226) isn't there. Have you looked directly
on the storage machine itself? Perhaps the node can't see that directory
12 matches
Mail list logo
