Based on the last few comments, I expect this is fixed in oneiric (and
natty). Marking this fix released, please comment if that's mistaken.
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Ah! That would explain it. This is actually a libvirt bug, probably
solved with the following commit:
http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=a7fb2258cac63b2420b51d5720a6e2b8734d818d
** Package changed: virt-manager (Ubuntu) => libvirt (Ubuntu)
** Changed in: libvirt (Ubuntu)
Mark,
Actually, removing the trailing "/" resolved the issue.
On Sep 22, 2010, at 10:58 AM, Marc Deslauriers wrote:
> @Damon,
>
> Could you please attach the xml files from your /etc/libvirt/storage
> directory? Thanks.
>
> --
> unable to add existing storage image to KVM
> https://bugs.launc
@Damon,
Could you please attach the xml files from your /etc/libvirt/storage
directory? Thanks.
--
unable to add existing storage image to KVM
https://bugs.launchpad.net/bugs/564678
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
Hello,
I have the same issue in ubuntu 10.4 : I get "Name 'ABCD' already in use by
another volume" when y create a new volume with virt-manager (in ssh).
It was ok in default pool (/var/lib/libvirt/images) but not in my new pool
(/mydirectory/). So I campared both storage pool to find differences
> - Is your user in the "libvirt" group?
Yes. The user is in the libvirtd group.
> - What directory is your pool located in?
I have three directories.
1. default (/var/lib/libvirt/images) - This is where ISOs are stored for
new virtual machines.
2. servers (/vms) - This is where new virtual ma
I still cannot reproduce this with two lucid machines.
- Is your user in the "libvirt" group?
- What directory is your pool located in?
- What are the permissions on that directory, and on the images that are
created in it?
- Is the image used by any other vm on that machine? (maybe an old vm tha
I'm connecting to a remote host over SSH.
On Sep 3, 2010, at 11:56 AM, Marc Deslauriers
wrote:
> Thanks for the info!
>
> Unfortunately, I'm unable to reproduce this either on Maverick or on
> Lucid.
>
> Are you connecting to the localhost using virt-manager, or are you
> connecting to a second
Thanks for the info!
Unfortunately, I'm unable to reproduce this either on Maverick or on
Lucid.
Are you connecting to the localhost using virt-manager, or are you
connecting to a second machine?
--
unable to add existing storage image to KVM
https://bugs.launchpad.net/bugs/564678
You received
Marc,
Be glad to assist. Here's the info I can provide, let me know if you
need more.
Dist: Ubuntu 10.04
Package: virt-manager 0.8.2-2ubuntu8
ProcVersionSignature: Linux version 2.6.32-24-generic (bui...@vernadsky) (gcc
version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) )
Execute virt-manager from the comma
Actually, I think I misunderstood the original problem. This may not be
fixed in maverick after all.
Could you please give me detailed steps on how to reproduce the problem?
Thanks.
** Changed in: virt-manager (Ubuntu)
Status: Fix Released => Incomplete
--
unable to add existing storag
Thanks Serge. That's basically the workaround I've applied to get things
up and running and it works, but is not optimal. What I'm hoping for
(crossing my fingers) is that the maintainer might be able to apply a
patch to the Lucid package to address virtual machine creation with the
wizard. Conside
Damon: I'd recommend trying to use 'virsh edit' to do it from the
command line. For instance, to add a disk called
'/srv/libvirt-storage-pool-1/lucid2.img'
to a VM called lucid1, I would do:
virsh edit lucid1
which pulls up $VISUAL editor with the xml definition for lucid1. Then add
something
Are there any workarounds that can be used in Lucid? I'm currently
unable to create virtual machines using the wizard because I use a
storage pool that isn't the default (e.g., /data/virtual_machines
instead of /var/lib/libvirt/images).
--
unable to add existing storage image to KVM
https://bugs.
Thanks for reporting this issue.
This has been fixed in the version of virt-manager that is now in
Maverick.
** Changed in: virt-manager (Ubuntu)
Status: New => Fix Released
--
unable to add existing storage image to KVM
https://bugs.launchpad.net/bugs/564678
You received this bug notifi
I seem to have this problem too, but only when running as a non-
privileged user (i.e. 'QEMU Usermode'). I create a new raw storage
image using the wizard in virt-manager, but I get "Name 'foo' already in
use by another volume" and am unable to add it to any VMs. This does
not affect me when runn
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/44425488/Dependencies.txt
--
unable to add existing storage image to KVM
https://bugs.launchpad.net/bugs/564678
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
17 matches
Mail list logo
