Comments on: Quick bridging with KVM on Ubuntu jaunty http://blog.loftninjas.org/2009/04/06/quick-bridging-with-kvm-on-ubuntu-jaunty/ Sat, 21 Jan 2012 06:46:54 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Getting started with KVM on Ubuntu 9.04 « Solely For me http://blog.loftninjas.org/2009/04/06/quick-bridging-with-kvm-on-ubuntu-jaunty/comment-page-1/#comment-2038 Getting started with KVM on Ubuntu 9.04 « Solely For me Thu, 08 Oct 2009 21:27:55 +0000 http://blog.loftninjas.org/?p=308#comment-2038 [...] Quick bridging with kvm on Ubuntu Jaunty Ubuntu server guide, virtualization HowtoForge: Virtualization With KVM On Ubuntu [...] [...] Quick bridging with kvm on Ubuntu Jaunty Ubuntu server guide, virtualization HowtoForge: Virtualization With KVM On Ubuntu [...]

]]> By: Rafo http://blog.loftninjas.org/2009/04/06/quick-bridging-with-kvm-on-ubuntu-jaunty/comment-page-1/#comment-1763 Rafo Tue, 26 May 2009 18:10:33 +0000 http://blog.loftninjas.org/?p=308#comment-1763 The "could not launch network script" may also indicate a problem with the script format. I was getting that diagnostic so I used `strace -f -e file kvm ...' and found out that there was a "ENOEXEC (Exec format error)" occurring behind the scene. This went away when I adjusted my script to strictly follow the convention for interpreter scripts in the EXECVE(2) manpage: The first line of the script should be #! INTERPRETER where INTERPRETER is the absolute path of a binary executable (/bin/bash on my system). The “could not launch network script” may also indicate a problem with the script format. I was getting that diagnostic so I used `strace -f -e file kvm …’ and found out that there was a “ENOEXEC (Exec format error)” occurring behind the scene. This went away when I adjusted my script to strictly follow the convention for interpreter scripts in the EXECVE(2) manpage: The first line of the script should be

#! INTERPRETER

where INTERPRETER is the absolute path of a binary executable (/bin/bash on my system).

]]> By: Cheif http://blog.loftninjas.org/2009/04/06/quick-bridging-with-kvm-on-ubuntu-jaunty/comment-page-1/#comment-1756 Cheif Mon, 25 May 2009 14:03:28 +0000 http://blog.loftninjas.org/?p=308#comment-1756 Hi, I've tried to make it work but it shows the message: "Could not initialize device 'tap'" do you know wath could it be? I've been looking in google but I havent find anything... Thanks Hi,

I’ve tried to make it work but it shows the message: “Could not initialize device ‘tap’” do you know wath could it be?
I’ve been looking in google but I havent find anything…

Thanks

]]> By: Slestak http://blog.loftninjas.org/2009/04/06/quick-bridging-with-kvm-on-ubuntu-jaunty/comment-page-1/#comment-1753 Slestak Sun, 24 May 2009 03:44:43 +0000 http://blog.loftninjas.org/?p=308#comment-1753 Does anyone see a way to integrate this method with the templated python-vmbuilder method published in teh ubuntu server documentation? Does anyone see a way to integrate this method with the templated python-vmbuilder method published in teh ubuntu server documentation?

]]> By: Marlon http://blog.loftninjas.org/2009/04/06/quick-bridging-with-kvm-on-ubuntu-jaunty/comment-page-1/#comment-1710 Marlon Mon, 27 Apr 2009 22:24:23 +0000 http://blog.loftninjas.org/?p=308#comment-1710 Thanks, I just reinstalled my Jaunty disk and found your instructions on setting up bridged networking within kvm. I had been using the qemu interface before but didn't like it because of the limited configuration (e.g. no sdl). Thanks for posting this. I got it set up without a hitch! Thanks, I just reinstalled my Jaunty disk and found your instructions on setting up bridged networking within kvm. I had been using the qemu interface before but didn’t like it because of the limited configuration (e.g. no sdl). Thanks for posting this. I got it set up without a hitch!

]]>