Re: upgrading from netbsd 4/xen 3.1 on i386 to HEAD on amd64

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Tue, Mar 11, 2008 at 03:52:23PM -0500, Chris Brookes wrote:
> > > xenbackendd is empty,
> >
> > Strange, mine has a bunch of (harmless) messages. Is it really running ?
> 
> Sorry I should be more careful with my explanation: xenbackendd did
> contain stuff like:
> 
> Failed to read /local/domain/0/backend/console/3/0/script (No such
> file or directory)
> Failed to read /local/domain/0/backend/vif/3/0/state (No such file or 
> directory)
> Failed to read /local/domain/0/backend/vbd/3/2050/state (No such file
> or directory)
> 
> Which my mind auto deleted and therefore summarized the file as empty.

that's OK then 

> 
> 
> > > xend.log does seem to have, to my untrained
> > > eyes, anything that jumps out suggesting a problem.
> > > http://txrx.org/logs/xend.log.
> >
> > This seems to suggest that the domU did indeed start. Is it the linux
> > kernel which complains about the timeout ?
> 
> If I launch the NetBSD domU first, and then launch the Linux domU,
> then the NetBSD domU is fine, but the linux kernel does this:
> 
> XENBUS: Waiting for devices to initialise:
> 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s...
> XENBUS: Timeout connecting to device: device/vbd/2051 (local state 3,
> remote state 2)
> 
> If I do it the other way around and launch the Linux domU first, then
> the NetBSD complains about a Timeout.
> 
> > Anything in the NetBSD dmesg ?
> 
> In the DOM0, yes I just noticed the can't VOP_OPEN device here:
> 
> Mar 11 23:35:56 container /netbsd: xbd backend: attach device vnd2d
> (size 12582912) for domain 4
> Mar 11 23:35:56 container /netbsd: xbd backend: attach device vnd3d
> (size 131072) for domain 4
> Mar 11 23:35:56 container /netbsd: xbdback backend/vbd/4/2051: can't
> VOP_OPEN device 0x1310: 16

16 is EBUSY; it looks like you can't open a block twice now. I find it
strange that it did work before. Did you do it with a physical device,
or a file: ?
What happens if you make it 'r' in both NetBSD and linux domU ?

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--