Featured Posts

SciPy 2008 - Software & Tools STATUS: Day 1 - Thursday: Concluded. Day 2 - Friday: In progress. Astronomy: Enzo [ home ] yt (related to Enzo) [ home | scipy ] Books: Computational Modeling and Complexity Science...

Readmore

An example of checking out a git tag using Qt 4.6.0... Clone the Qt repository: $ git clone git://gitorious.org/qt/qt.git Show available tags: $ git tag -l output: v4.5.1 v4.5.2 v4.5.3 v4.6.0 v4.6.0-beta1 v4.6.0-rc1 v4.6.0-tp1 Checkout v4.6.0: $...

Readmore

Building 64-bit/32-bit Debug&Release Universal Build... See my directions on checking out Qt 4.6.0 from the git repository if you do not already have the source code. Launch a Terminal and cd to the source directory. Run configure w/ 64-bit & 32-bit...

Readmore

  • Prev
  • Next

xen + routed network (shorewall) + qemu

Posted on : 09-02-2007 | By : Brandon W. King | In : Computers/IT, Error Fixes, Linux, Systems Administration, Virtual Machines

Tags: , , , , ,

5

After setting up xen and configuring buildbot on a xen guest domain, I decided it was time to bite the bullet and setup shorewall to hide the xen guest domains behind a private network.

By the way, there are some nice guides on setting up shorewall with xen:

In the process I had to reconfigure Xen to use routed networking rather then bridged:

Changed (/etc/xen/xend-config.sxp) from:

(network-script network-bridge)
(vif-script vif-bridge)

To:

(network-script network-route)
(vif-script vif-route)

After setting up shorewall properly and being able to log into two different Debian etch guest domains, I noticed that my previously working WinXP hvm was not starting up properly. When I looked into it further I found the following in /var/log/xen/qemu-dm.11384.log

domid: 20
qemu: the number of cpus is 1
/etc/xen/scripts/qemu-ifup: could not launch network script
Could not initialize device ‘tap’

Tap device cure (found here):

tunctl -t tap0

The final piece of the puzzle (since I’m using the routed script with xen)…

Comment out “brctl addif $2 $” from /etc/xen/scripts/qemu-ifup as mentioned by George in this mailing list thread.

UPDATE (2007Feb12): By doing the above two tasks, I was able to launch WinXP under Xen, but I did not have shorewall setup properly. To save time and money, I’m going with the simpler route of buying a hardware firewall/router. I will leave the information above incase it is useful to anyone (including myself) in the future.

xen error: Error: Device 0 (vif) could not be connected. Backend device not found.

Posted on : 17-01-2007 | By : Brandon W. King | In : Computers/IT, Linux, Systems Administration, Virtual Machines

Tags: , , ,

1

Currently, I’m working on setting up Xen 3.0.3 on Debian Etch 64-bit. I installed the debian packages rebooted and used xen-tools to create a Debian etch guest domain. When I used xm create -c debian_etch_guest.cfg vmid=1 I got the following error:

Error: Device 0 (vif) could not be connected. Backend device not found.

I googled for the error and didn’t immediately find a solution to the problem (it may still be there in the search results), but as it turned out, the only thing I needed to do was install bridge-utils:

apt-get install bridge-utils

That’s it, now the guest domain boots without a problem.