For the issue I reported above, I believe this is a bug. There are two checks
for pre-existing VMs, and they differ:
/usr/lib/python2.7/dist-packages/VMBuilder/plugins/libvirt/__init__.py
line 54:if hostname in self.all_domains() and not
self.context.overwrite:
line 80:if
For the issue I reported above, I believe this is a bug. There are two checks
for pre-existing VMs, and they differ:
/usr/lib/python2.7/dist-packages/VMBuilder/plugins/libvirt/__init__.py
line 54:if hostname in self.all_domains() and not
self.context.overwrite:
line 80:if
In current Natty, I get a slightly different version of this (output
below). The same error occurs, but at the cleaning up step. The
make_vm.sh blow contains the same vmbuilder command as above. Should
this be raised as a separate bug?
Thanks,
Richard
(example run)
user@host:~$ ./make_vm.sh
In current Natty, I get a slightly different version of this (output
below). The same error occurs, but at the cleaning up step. The
make_vm.sh blow contains the same vmbuilder command as above. Should
this be raised as a separate bug?
Thanks,
Richard
(example run)
user@host:~$ ./make_vm.sh
I also got this error on 10.10 and, to David's comment, changing the
name of the --hostname bypassed the problem as you created a new vm. But
using virsh or virt-manager to delete the pre-existing image resolved
the problem. However, my question is this. Is the -o option intended to
remove any
I also got this error on 10.10 and, to David's comment, changing the
name of the --hostname bypassed the problem as you created a new vm. But
using virsh or virt-manager to delete the pre-existing image resolved
the problem. However, my question is this. Is the -o option intended to
remove any
I also got this error message. In the ubuntu-vm-builder, I had --
hostname 'test-vm' , I changed it to --hostname 'testvm' and the
problem disappears. So I believe the issue has to do with the minus sign
in the hostname parameter.
--
You received this bug notification because you are a member
I also got this error message. In the ubuntu-vm-builder, I had --
hostname 'test-vm' , I changed it to --hostname 'testvm' and the
problem disappears. So I believe the issue has to do with the minus sign
in the hostname parameter.
--
You received this bug notification because you are a member
Yes, when recreating a VM, first do a virsh undefine vm name, then
run your vmbuilder command.
It's too bad that you hit that error 28 mn in the game : a verification
could be added to vmbuilder's preflight_check, or, vmbuilder could
perform the undefine itself.
--
AttributeError: 'Libvirt'
Yes, when recreating a VM, first do a virsh undefine vm name, then
run your vmbuilder command.
It's too bad that you hit that error 28 mn in the game : a verification
could be added to vmbuilder's preflight_check, or, vmbuilder could
perform the undefine itself.
--
AttributeError: 'Libvirt'
I ran into this same problem (Ubuntu 10.04). As the successful use of
the --hostname option already suggests, this has to do with the hostname
given to the VM. This hostname is also used in the xml files that are
placed in the /etc/libvirt/qemu directory as noted in comments
#11/#12/#15. If one
I ran into this same problem (Ubuntu 10.04). As the successful use of
the --hostname option already suggests, this has to do with the hostname
given to the VM. This hostname is also used in the xml files that are
placed in the /etc/libvirt/qemu directory as noted in comments
#11/#12/#15. If one
Fix on comment #7 worked for me. Just needed --hostname
--
AttributeError: 'Libvirt' object has no attribute 'vm'
https://bugs.launchpad.net/bugs/562189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Same here. (Ubuntu 10.04 LTS / 2.6.32-22-server / x86_64)
I've tried with and without -o, with and without extra --addpkg, and with and
without --install-mirror and I removed the generated
/etc/libvirt/qemu/machine.xml and I always have that error :
administrat...@master-server:~$ sudo
Well, I've restarted the server, and run
administrat...@master-server:~$ sudo vmbuilder kvm ubuntu --suite=lucid
--flavour=virtual --arch=amd64 --hostname=test-vm -o --libvirt=qemu:///system
--ip=192.168.0.123 --gw=192.168.0.1 --bridge=br0 --rootsize=40960 -m 512
--user=admin
** Branch linked: lp:vmbuilder
--
AttributeError: 'Libvirt' object has no attribute 'vm'
https://bugs.launchpad.net/bugs/562189
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in ubuntu.
--
Ubuntu-server-bugs mailing list
Same here. (Ubuntu 10.04 LTS / 2.6.32-22-server / x86_64)
I've tried with and without -o, with and without extra --addpkg, and with and
without --install-mirror and I removed the generated
/etc/libvirt/qemu/machine.xml and I always have that error :
administrat...@master-server:~$ sudo
Well, I've restarted the server, and run
administrat...@master-server:~$ sudo vmbuilder kvm ubuntu --suite=lucid
--flavour=virtual --arch=amd64 --hostname=test-vm -o --libvirt=qemu:///system
--ip=192.168.0.123 --gw=192.168.0.1 --bridge=br0 --rootsize=40960 -m 512
--user=admin
** Branch linked: lp:vmbuilder
--
AttributeError: 'Libvirt' object has no attribute 'vm'
https://bugs.launchpad.net/bugs/562189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I got this same error. I did have a previously working vm. I did set
hostname.
I am working on Ubuntu 10.04 64-bit.
I moved ubuntu-kvm.
mv ubuntu-kvm old-ubuntu-kvm
I also moved othost.xml
sudo mv /etc/libvirt/qemu/othost.xml oldothost.xml
After killing libvirtd it worked.
$ sudo
I got this same error. I did have a previously working vm. I did set
hostname.
I am working on Ubuntu 10.04 64-bit.
I moved ubuntu-kvm.
mv ubuntu-kvm old-ubuntu-kvm
I also moved othost.xml
sudo mv /etc/libvirt/qemu/othost.xml oldothost.xml
After killing libvirtd it worked.
$ sudo
IMHO the run.sh script should not be generated at all if the VM is
registered with libvirt. As in this case 'virsh start VM' is the way to
go.
--
AttributeError: 'Libvirt' object has no attribute 'vm'
https://bugs.launchpad.net/bugs/562189
You received this bug notification because you are a
It looks like each supported hypervisor uses it's own policy regarding startup
script:
* Xen = none
* VMWare = none
* VirtualBox = $DESTDIR/deploy_$hostname.sh
* KVM = $DESTDIR/run.sh
While the KVM one will get ownership set to the calling user, the
VirtualBox one will not.
--
AttributeError:
IMHO the run.sh script should not be generated at all if the VM is
registered with libvirt. As in this case 'virsh start VM' is the way to
go.
--
AttributeError: 'Libvirt' object has no attribute 'vm'
https://bugs.launchpad.net/bugs/562189
You received this bug notification because you are a
It looks like each supported hypervisor uses it's own policy regarding startup
script:
* Xen = none
* VMWare = none
* VirtualBox = $DESTDIR/deploy_$hostname.sh
* KVM = $DESTDIR/run.sh
While the KVM one will get ownership set to the calling user, the
VirtualBox one will not.
--
AttributeError:
AFAIK the check is not if an image directory exists, but if there's some
virtual machine with this name is defined in libvirt. --dest doesn't
help for this reason...
@Marcus Bointon: please check if there is some .xml file in
/etc/libvirt/qemu/ that looks like having no, or some kind of default
** Changed in: vm-builder (Ubuntu)
Status: New = Confirmed
--
AttributeError: 'Libvirt' object has no attribute 'vm'
https://bugs.launchpad.net/bugs/562189
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in ubuntu.
--
There are two files in there. One called ubuntu.xml that refers to an image
file created in a folder called ubuntu-kvm (i.e. a default, as you suspected),
the other called vm1.xml, which is what I specified as my hostname.
I'm also curious that that file is in the libvirt folder instead of
AFAIK the check is not if an image directory exists, but if there's some
virtual machine with this name is defined in libvirt. --dest doesn't
help for this reason...
@Marcus Bointon: please check if there is some .xml file in
/etc/libvirt/qemu/ that looks like having no, or some kind of default
** Changed in: vm-builder (Ubuntu)
Status: New = Confirmed
--
AttributeError: 'Libvirt' object has no attribute 'vm'
https://bugs.launchpad.net/bugs/562189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
There are two files in there. One called ubuntu.xml that refers to an image
file created in a folder called ubuntu-kvm (i.e. a default, as you suspected),
the other called vm1.xml, which is what I specified as my hostname.
I'm also curious that that file is in the libvirt folder instead of
I've now tried this without the -o option (having spotted the
self.vm.overwrite is the root of the problem), but that didn't make any
difference. Any chance of getting some attention to this as it's a
complete showstopper for me. It means my entire UEC / JeOS
virtualization plans are on hold.
I got the same problem.
matt...@0xb1ue7:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu lucid (development branch)
Release:10.04
Codename: lucid
matt...@0xb1ue7:~$ uname -a
Linux 0xB1uE7 2.6.32-21-generic #32-Ubuntu SMP Fri Apr 16
Got the same on a Lucid. In my case the problem was that I already had a
virtual host with the same name.
Marcus, it looks like you've called vmbuilder with no --hostname. Don't
know what is taken as hostname in this case, but probably the same on
each invocation.
So I see this as actually being
Yay! That did it! I added a --hostname and it just worked, so thanks very much.
I don't think it's to do with whether a VM already exists as I have none in my
folder and have been wiping /tmp files between each build (because it doesn't
clean up after dying). In my case it should have nothing to
Feel free to fix it in the wiki
https://help.ubuntu.com/community/JeOSVMBuilder which was used as the
source for the doc if you have time.
--
AttributeError: 'Libvirt' object has no attribute 'vm'
https://bugs.launchpad.net/bugs/562189
You received this bug notification because you are a member
I'm wary of making changes there as that page is for the older shell
script version of vmbuilder and I don't know if the same things apply -
I don't want to break things for Intrepid users just because Lucid is
different.
I also noticed that hostname is missing from the man page too.
I'm also
Got the same on a Lucid. In my case the problem was that I already had a
virtual host with the same name.
Marcus, it looks like you've called vmbuilder with no --hostname. Don't
know what is taken as hostname in this case, but probably the same on
each invocation.
So I see this as actually being
Yay! That did it! I added a --hostname and it just worked, so thanks very much.
I don't think it's to do with whether a VM already exists as I have none in my
folder and have been wiping /tmp files between each build (because it doesn't
clean up after dying). In my case it should have nothing to
Feel free to fix it in the wiki
https://help.ubuntu.com/community/JeOSVMBuilder which was used as the
source for the doc if you have time.
--
AttributeError: 'Libvirt' object has no attribute 'vm'
https://bugs.launchpad.net/bugs/562189
You received this bug notification because you are a member
I'm wary of making changes there as that page is for the older shell
script version of vmbuilder and I don't know if the same things apply -
I don't want to break things for Intrepid users just because Lucid is
different.
I also noticed that hostname is missing from the man page too.
I'm also
I've now tried this without the -o option (having spotted the
self.vm.overwrite is the root of the problem), but that didn't make any
difference. Any chance of getting some attention to this as it's a
complete showstopper for me. It means my entire UEC / JeOS
virtualization plans are on hold.
I got the same problem.
matt...@0xb1ue7:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu lucid (development branch)
Release:10.04
Codename: lucid
matt...@0xb1ue7:~$ uname -a
Linux 0xB1uE7 2.6.32-21-generic #32-Ubuntu SMP Fri Apr 16
Still there with libvirt 0.7.5-5ubuntu25
--
AttributeError: 'Libvirt' object has no attribute 'vm'
https://bugs.launchpad.net/bugs/562189
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in ubuntu.
--
Ubuntu-server-bugs
Still there with libvirt 0.7.5-5ubuntu25
--
AttributeError: 'Libvirt' object has no attribute 'vm'
https://bugs.launchpad.net/bugs/562189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Unfortunately it was just hiding, and it's back again with libvirt
0.7.5-5ubuntu23. Same config, same error.
--
AttributeError: 'Libvirt' object has no attribute 'vm'
https://bugs.launchpad.net/bugs/562189
You received this bug notification because you are a member of Ubuntu
Server Team, which
Still there with libvirt 0.7.5-5ubuntu24.
--
AttributeError: 'Libvirt' object has no attribute 'vm'
https://bugs.launchpad.net/bugs/562189
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in ubuntu.
--
Ubuntu-server-bugs
Unfortunately it was just hiding, and it's back again with libvirt
0.7.5-5ubuntu23. Same config, same error.
--
AttributeError: 'Libvirt' object has no attribute 'vm'
https://bugs.launchpad.net/bugs/562189
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Still there with libvirt 0.7.5-5ubuntu24.
--
AttributeError: 'Libvirt' object has no attribute 'vm'
https://bugs.launchpad.net/bugs/562189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: vm-builder (Ubuntu)
Importance: Undecided = Medium
--
AttributeError: 'Libvirt' object has no attribute 'vm'
https://bugs.launchpad.net/bugs/562189
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in ubuntu.
** Changed in: vm-builder (Ubuntu)
Importance: Undecided = Medium
--
AttributeError: 'Libvirt' object has no attribute 'vm'
https://bugs.launchpad.net/bugs/562189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I noticed that libvirt got updated to 0.7.5-5ubuntu22 today, and it's
possible that this bug has been fixed by it, however, I'm not sure as
I've got another bug instead that may just be obscuring it...
--
AttributeError: 'Libvirt' object has no attribute 'vm'
I noticed that libvirt got updated to 0.7.5-5ubuntu22 today, and it's
possible that this bug has been fixed by it, however, I'm not sure as
I've got another bug instead that may just be obscuring it...
--
AttributeError: 'Libvirt' object has no attribute 'vm'
53 matches
Mail list logo
