nseconfigs table is used both as a virtual table and a physical table. When xmlconvert is called during nseparse, we need to clean up the physical part so that rows for the new mapping can be added. I have added this. While I say that there is a physical part, essentially the vname column has the same value as the vname column in the reserved table for the PC such as 'simhost-0', 'simhost-1' etc.
nseconfigs table is used both as a virtual table and a physical table.
When xmlconvert is called during nseparse, we need to clean up the
physical part so that rows for the new mapping can be added. I have
added this. While I say that there is a physical part, essentially
the vname column has the same value as the vname column in the
reserved table for the PC such as 'simhost-0', 'simhost-1' etc.

nmc-probe/emulab-nome,nmc-probe/emulab-nome,nmc-probe/emulab-nome,nmc-probe/emulab-nome,nmc-probe/emulab-nome,nmc-probe/emulab-nome,nmc-probe/emulab-nome,nmc-probe/emulab-nome,nmc-probe/emulab-nome,nmc-probe/emulab-nome,nmc-probe/emulab-nome