incubator-tashi-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kushal Dalmia" <kdal...@andrew.cmu.edu>
Subject Issues with CreateVM
Date Sun, 23 Oct 2011 20:54:47 GMT
Hi,

We have setup Tashi on a local machine and are running the node manager
and cluster manager on the same machine. When we use the client to create
a VM, no VM gets instantiated. We do not see any errors from the client,
however the NodeManager(running in DEBUG = 1 mode) shows us the following
log:

2011-10-23 16:03:58,996
[/usr/share/tashi/src/tashi/nodemanager/vmcontrol/qemu.pyc:INFO] QEMU
command: /usr/local/bin/qemu-system-x86_64   -clock dynticks -drive
file=/dfs/images/rhel.img,if=ide,index=0,cache=off,snapshot=on  -net
nic,macaddr=52:54:00:03:d6:80,model=virtio,vlan=1 -net
tap,ifname=tashi3.0,vlan=1,script=/etc/qemu-ifup.1  -m 128 -smp 1 -serial
null -vnc none -monitor pty
2011-10-23 16:03:58,998
[/usr/share/tashi/src/tashi/nodemanager/vmcontrol/qemu.pyc:INFO] Adding
vmId 20037
2011-10-23 16:03:59,615
[/usr/share/tashi/src/tashi/nodemanager/vmcontrol/qemu.pyc:INFO] Removing
vmId 20037
2011-10-23 16:03:59,615
[/usr/share/tashi/src/tashi/nodemanager/vmcontrol/qemu.pyc:INFO] Removing
scratch for foobar
File descriptor 3 (/var/log/nodemanager.log) leaked on lvremove
invocation. Parent PID 18905: /usr/bin/python
File descriptor 5 (socket:[10134749]) leaked on lvremove invocation.
Parent PID 18905: /usr/bin/python
File descriptor 6 (socket:[10143094]) leaked on lvremove invocation.
Parent PID 18905: /usr/bin/python
File descriptor 8 (socket:[10143099]) leaked on lvremove invocation.
Parent PID 18905: /usr/bin/python
File descriptor 9 (pipe:[10143285]) leaked on lvremove invocation. Parent
PID 18905: /usr/bin/python
File descriptor 10 (/dev/pts/6 (deleted)) leaked on lvremove invocation.
Parent PID 18905: /usr/bin/python
File descriptor 12 (/tmp/ffiFLuWSq (deleted)) leaked on lvremove
invocation. Parent PID 18905: /usr/bin/python
  Volume group "vgscratch" not found
  Skipping volume group vgscratch

Since the NodeManager just creates the VM ID and removes it, we are not
sure what/where we are wrong. Attached herewith is the Tashi.cfg we are
using.

Any help would be greatly appreciated.

Thanks,
Kushal Dalmia
Mime
View raw message