<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#ffffff" text="#000000">
<font size="-1">Hi,<br>
<br>
I'm trying to launch my first KVM machine via one and am running
into what looks like a network problem.<br>
<br>
From one, the error log is:<br>
<br>
<i>Wed Sep 29 22:24:26 2010 [LCM][I]: New VM state is BOOT<br>
Wed Sep 29 22:24:26 2010 [VMM][I]: Generating deployment file:
/var/lib/one/12/deployment.0<br>
Wed Sep 29 22:24:56 2010 [VMM][I]: Command execution fail:
'mkdir -p /home/sharedFS/images/12/images && cat >
/home/sharedFS/images/12/images/deployment.0 && virsh
--connect qemu:///system create
/home/sharedFS/images/12/images/deployment.0'<br>
Wed Sep 29 22:24:56 2010 [VMM][I]: STDERR follows.<br>
Wed Sep 29 22:24:56 2010 [VMM][I]: error: Failed to create
domain from /home/sharedFS/images/12/images/deployment.0<br>
Wed Sep 29 22:24:56 2010 [VMM][I]: error: monitor socket did not
show up.: Connection refused<br>
Wed Sep 29 22:24:56 2010 [VMM][I]: ExitCode: 1<br>
Wed Sep 29 22:24:56 2010 [VMM][E]: Error deploying virtual
machine<br>
Wed Sep 29 22:24:56 2010 [DiM][I]: New VM state is FAILED</i><br>
<br>
I trace that down to the worker node. I find a log file
/var/log/libvirt/qemu/one-12.log containing:<br>
<br>
<i>LC_ALL=C
PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
/usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 128 -smp 1 -name
one-12 -uuid 1cd58679-9171-ad5e-f22c-8df0cc6f7f16 -nographic
-chardev
socket,id=monitor,path=/var/lib/libvirt/qemu/one-12.monitor,server,nowait
-monitor chardev:monitor -boot c -kernel /vmlinuz -initrd
/initrd.img -drive
file=/home/sharedFS/images/12/images/disk.0,if=ide,index=0,boot=on
-net nic,macaddr=00:2a:f9:42:1e:f7,vlan=0,name=nic.0 -net
tap,vlan=0,name=tap.0 -serial none -parallel none -usb <br>
warning: could not configure /dev/net/tun: no virtual network
emulation</i><br>
<br>
Since the one error sounds network related I start to focus on
that warning, even though it's just a warning. So I try running
the machine from a command line:<br>
<br>
<i>$ sudo qemu-system-x86_64 -k en-us -vga vmware -hda
100924-1.img -net nic,macaddr=`macgen` -net tap -boot c -m 384<br>
+ switch=br0<br>
+ [ -n tap4 ]<br>
+ whoami<br>
+ /usr/bin/sudo /usr/sbin/tunctl -u root -t tap4<br>
TUNSETIFF: Device or resource busy<br>
+ /usr/bin/sudo /sbin/ip link set tap4 up<br>
+ sleep 0.5s<br>
+ /usr/bin/sudo /usr/sbin/brctl addif br0 tap4<br>
+ exit 0<br>
</i><br>
The interesting part is "</font><font size="-1">TUNSETIFF: Device
or resource busy". I say it's interesting because, again, it
seems network related and further, if I run those commands from a
shell, they work just fine.<br>
<br>
<i>$ /usr/bin/sudo /usr/sbin/tunctl -u root -t tap4<br>
Set 'tap4' persistent and owned by uid 0<br>
</i><br>
So I'm not sure why when being launched by qemu/one I get that
error. And I'm not even sure it's the root cause. Finally, when
I launch the VM manually (i.e. without one, just with qemu) even
though that 'busy' error shows up the machine starts and
networking is completely functional.<br>
<br>
Any ideas? What else do I need to provide?<br>
<br>
rw2<br>
<br>
</font>
</body>
</html>