Hi,

I don't know if this helps with the root problem but I noticed that you 
have mac address spesified in conf file like this:

#kernel = "/xen/kernel/netbsd-XEN3_DOMU.gz"
kernel = "/xen/kernel/netbsd-INSTALL_XEN3_DOMU.gz"
memory = 256
name = "netbsd1"
vif = [ 'mac=aa:00:00:99:99:01, bridge=bridge2' ]
disk = [ 'file:/xen/vm/netbsd1,0x1,w' ]
extra = ""


I dont if this is true anymore but mac address should start with value 
of "00:16:3e" so this works for me:
vif = [ 'mac=00:16:3e:00:00:11, bridge=bridge0' ]

-Anzi-



Martti Kuparinen wrote:
> After more testing I saw these in /var/log/messages. I still don't 
> know what triggers these.
>
> May  8 15:35:54 xen3 xenbackendd[161]: Failed to read 
> /local/domain/0/backend/vif/4/0/state (No such file or directory)
> May  8 15:35:54 xen3 xenbackendd[161]: Failed to read 
> /local/domain/0/backend/vbd/4/1/state (No such file or directory)
> May  8 15:35:54 xen3 xenbackendd[161]: Failed to read 
> /local/domain/0/backend/vif/4/0/state (No such file or directory)
> May  8 15:35:54 xen3 xenbackendd[161]: Failed to read 
> /local/domain/0/backend/vbd/4/1/state (No such file or directory)
>
>
> "xm list" and "xm info" seems to work fine but "xm uptime" gives this:
>
> ROOT xen3:~> xm uptime
> Name                              ID Uptime
> Error: Unable to connect to xend: No such file or directory.
>