This bug was fixed in the package opennebula - 2.0.1-5
---
opennebula (2.0.1-5) unstable; urgency=low
* d/patches/ldflags_build.diff: Proposed patch from Jaime Melis to allow
LDFLAGS setting in OpenNebula build process. Will be included in next
upstream release.
* d/rules:
Hi!
On 26.03.2010, at 23:45, Ruben S, Montero wrote:
> To address the Apparmor issue in Ubuntu 9.10, just add the
> $ONE_LOCATION/var directory to
> /etc/apparmor.d/abstractions/libvirt-qemu
That's what I found out as well. However, since it took me some time to
find out and I think newly install
Hi Florian
To address the Apparmor issue in Ubuntu 9.10, just add the
$ONE_LOCATION/var directory to
/etc/apparmor.d/abstractions/libvirt-qemu
For example if ONE_LOCATION = /srv/cloud/one then your libvirt-qemu
apparmor file should be:
...
#include
owner @{HOME}/ r,
owner @{HOME}/** rw,
/srv/cl
** Patch added: "Dirty workaround by touching checkpoint file before saving
machine"
http://launchpadlibrarian.net/42094483/one_vmm_kvm.patch
--
Cold migration fails
https://bugs.launchpad.net/bugs/322779
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Hi,
On 26.03.2010, at 10:56, Ruben S, Montero wrote:
> Well actually is the opposite: the patch defaults the driver to use
> qemu:///system. It also does a touch to the checkpoint file before
> saving the image so it belongs to oneadmin and not to root.
Okay, I just assumed the possibility to cha
Hi,
Well actually is the opposite: the patch defaults the driver to use
qemu:///system. It also does a touch to the checkpoint file before
saving the image so it belongs to oneadmin and not to root.
You can check the commit
http://dev.opennebula.org/projects/opennebula/repository/revisions/f8252
Reading issue 131 it seems to me you suggest using qemu:///session
instead of qemu:///system. However, this is no option for me as I use
bridged networking. qemu:///session fails on that:
$ virsh -c qemu:///session create deployment.0
Connecting to uri: qemu:///session
error: Failed to create dom
Hi
This should be working for OpenNebula 1.4. Check issue 131[1] in the
development portal, you can safely apply the associated changes to
OpenNebula 1.2. If you are using 1.4, please send us the log files...
[1] http://dev.opennebula.org/issues/131
Cheers
Ruben
On Fri, Mar 26, 2010 at 7:26 A
One year later, this bug still affects me in Karmic Server. Is there any
workaround yet?
--
Cold migration fails
https://bugs.launchpad.net/bugs/322779
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
To be perfectly honest, I consider this a bug in libvirt, but if you can
come up with a decent workaround in OpenNebula, that would be lovely.
--
Cold migration fails
https://bugs.launchpad.net/bugs/322779
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Does this thread bring any light to the problem?
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/235386
Anyway, we are about to reengineer the drivers so it is a good time to
take care of that problems. We will take a look to this ticket.
--
Cold migration fails
https://bugs.launchpad.net
In summary, the challenge is that libvirtd runs as root, so saves the
memory state as root, mode 600. We need to copy that to another host
somehow while running as oneadmin.
--
Cold migration fails
https://bugs.launchpad.net/bugs/322779
You received this bug notification because you are a member
** Summary changed:
- Migration fails
+ Cold migration fails
** Description changed:
Binary package hint: opennebula
-
- Live migration fails, because we don't use qemu+tcp, which OpenNebula
- expects to work.
Cold migration fails because we're connecting to qemu:///system, so the
save
13 matches
Mail list logo