Subject: Re: problem booting dom0
To: John Hayward <John.C.Hayward@wheaton.edu>
From: Sarton O'Brien <bsd-xen@roguewrt.org>
List: port-xen
Date: 02/05/2008 16:47:41
Hi John,

John Hayward wrote:
> When I attempt to boot a netbsd dom0 boot I see in the log file:
> ====
> xenbackendd[446]: Failed to read 
> /local/domain/0/backend/console/5/0/script (No such file or directory)
> ====
>


This is non-fatal. Not something I have ever looked into but I believe 
it is either left over from linux related code or displayed due to boot 
options/parameters not being utilised. Actually, I'd like to know why 
it's still displayed ... but be assured you can completely ignore it.


> Can someone point me in the direction to get booting?
> It looks like it finds the disk image and CD.
> There are issues with the network which I can look into later.
> It seems that I am not getting the console of the dom0 to show up.
>
>
> the config file looks like:
> ===
> kernel = "/netbsd-INSTALL_XEN3_DOMU"
> memory = 256
> name = "netbd"
> nics = 1
> vif = [ 'mac=aa:00:00:50:02:f0, bridge=bridge0' ]
> disk = [ 'file:/var/xen/netbd-disk,0x01,w', 'phy:/dev/cd0a,0x2,r' ]
> root = "/dev/wd0d"
> ===
>
> Sample run:
> ===
> xm create -c /usr/pkg/etc/xen/netbd
> Using config file "/usr/pkg/etc/xen/netbd".
> Warning: The nics option is deprecated.  Please use an empty vif entry 
> instead:
>
>   vif = [ '' ]
> ===
> After a while
> ===
> newserver: {242} Error: Device 0 (vif) could not be connected. Hotplug 
> scripts not working.
> ===
> it exits and the /var/log/messages shows:
> ===
> Feb  4 23:23:08 newserver /netbsd: xbd backend: attach device vnd1d 
> (size 4096000) for domain 5
> Feb  4 23:23:08 newserver /netbsd: xbd backend: attach device cd0a 
> (size 359844) for domain 5
> Feb  4 23:23:08 newserver /netbsd: xvif5.0: Ethernet address 
> aa:00:00:51:02:f0
> Feb  4 23:23:08 newserver xenbackendd[446]: Failed to read 
> /local/domain/0/backend/console/5/0/script (No such file or directory)
> Feb  4 23:24:50 newserver xenbackendd[446]: Failed to read 
> /local/domain/0/backend/console/5/0/script (No such file or directory)
> Feb  4 23:24:50 newserver /netbsd: xbd backend: detach device vnd1d 
> for domain 5
> Feb  4 23:24:50 newserver /netbsd: xbd backend: detach device cd0a for 
> domain 5
> Feb  4 23:24:50 newserver /netbsd: xvif5.0: disconnecting
> ===
>
> johnh...


I haven't looked at your config in detail but I'd suggest heeding the 
warning that pleads with you to remove your nics line.

OK, I just looked ... remove 'nics' and 'root' lines, they're not 
needed. To add, if you were to use the 'root' line, it would be xbd0 
which is the xen assignment for a vnd ... but you don't need it.

The symptoms you are experiencing will either be config or sparse image 
file ... unless of course I'm wrong ;)

Sarton