| 2009-08-09 16:27:16 |
Andreas Heck |
description |
If you run vmbuilder on a fresh karmic installation you get the following error message at the end of the vmbuilder run:
2009-08-09 01:06:56,792 INFO : Cleaning up
Traceback (most recent call last):
File "/home/ahe/Desktop/Projekte/VMbuilder/vmbuilder-gui/vmbuilder", line 29, in <module>
VMBuilder.run()
File "/home/ahe/Desktop/Projekte/VMbuilder/vmbuilder-gui/VMBuilder/__init__.py", line 65, in run
frontend.run()
File "/home/ahe/Desktop/Projekte/VMbuilder/vmbuilder-gui/VMBuilder/plugins/cli/__init__.py", line 70, in run
vm.create()
File "/home/ahe/Desktop/Projekte/VMbuilder/vmbuilder-gui/VMBuilder/vm.py", line 483, in create
self.install()
File "/home/ahe/Desktop/Projekte/VMbuilder/vmbuilder-gui/VMBuilder/vm.py", line 416, in install
self.distro.install_bootloader()
File "/home/ahe/Desktop/Projekte/VMbuilder/vmbuilder-gui/VMBuilder/plugins/ubuntu/distro.py", line 173, in install_bootloader
EOT''')
File "/home/ahe/Desktop/Projekte/VMbuilder/vmbuilder-gui/VMBuilder/util.py", line 105, in run_cmd
proc = subprocess.Popen(args, stdin=stdin_arg, stderr=subprocess.PIPE, stdout=subprocess.PIPE, env=proc_env)
File "/usr/lib/python2.6/subprocess.py", line 595, in __init__
errread, errwrite)
File "/usr/lib/python2.6/subprocess.py", line 1092, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
A quick look at VMBuilder/vm.py shows that it tries to call the program "grub" but this program doesn't exist with grub2. |
If you run vmbuilder on a fresh karmic installation you get the following error message at the end of the vmbuilder run:
2009-08-09 01:06:56,792 INFO : Cleaning up
Traceback (most recent call last):
File "/home/ahe/Desktop/Projekte/VMbuilder/vmbuilder-gui/vmbuilder", line 29, in <module>
VMBuilder.run()
File "/home/ahe/Desktop/Projekte/VMbuilder/vmbuilder-gui/VMBuilder/__init__.py", line 65, in run
frontend.run()
File "/home/ahe/Desktop/Projekte/VMbuilder/vmbuilder-gui/VMBuilder/plugins/cli/__init__.py", line 70, in run
vm.create()
File "/home/ahe/Desktop/Projekte/VMbuilder/vmbuilder-gui/VMBuilder/vm.py", line 483, in create
self.install()
File "/home/ahe/Desktop/Projekte/VMbuilder/vmbuilder-gui/VMBuilder/vm.py", line 416, in install
self.distro.install_bootloader()
File "/home/ahe/Desktop/Projekte/VMbuilder/vmbuilder-gui/VMBuilder/plugins/ubuntu/distro.py", line 173, in install_bootloader
EOT''')
File "/home/ahe/Desktop/Projekte/VMbuilder/vmbuilder-gui/VMBuilder/util.py", line 105, in run_cmd
proc = subprocess.Popen(args, stdin=stdin_arg, stderr=subprocess.PIPE, stdout=subprocess.PIPE, env=proc_env)
File "/usr/lib/python2.6/subprocess.py", line 595, in __init__
errread, errwrite)
File "/usr/lib/python2.6/subprocess.py", line 1092, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
A quick look at VMBuilder/vm.py shows that it tries to call the program "grub" but this program doesn't exist with grub2.
The main problem here is that you can't have both of the packages grub and grub-pc installed at the same time since they replace each other. It looks like the maintainers of the grub packages didn't think about the not so common use case where you install a bootmanager package but don't want it to boot your machine. But if you have a freshly installed karmic machine you need both bootloader packages to be present or otherwise you couldn't create any VMs with an Ubuntu version older than karmic, even if vmbuilder supported grub2. A similar problem would occur, if you used an PC with EFI and the EFI version of grub2 so that you needed the PC version of grub2 to install the bootloader of the virtual machine. |
|
