Re: Xen won't start its device backend?

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

On Tue, May 26, 2015 at 10:07:01PM +0200, Reinoud Zandijk wrote:
> Hi Manuel,
> 
> On Tue, May 26, 2015 at 07:32:50PM +0200, Manuel Bouyer wrote:
> > > On Tue, May 26, 2015 at 05:48:04PM +0200, Manuel Bouyer wrote:
> > > > if it's HVM then you probably need:
> > > > disk = [ 'phy:/dev/wd1d,ioemu:hda,rw' ]
> > 
> > error 2 is ENOENT. Maybe it attaches dk0 and dk1 to the wrong disk
> > or partition ?
> > 
> > In order to debug I would boot an INSTALL kernel and see from here
> > exactly what is on dk0 and dk1
> 
> I've booted with the domU running an INSTALL kernel and there it shows up
> again: the disc is shown corrupted! In dom0 it fscks fine but in domU i get
> odd corrupted direntries when i do an `ls -al' on the FS and the /sbin
> directories gives bad file descriptor. Its a roughly 500+ gb. On the dom0 it
> shows:
> 
> ----------
> file system: /dev/wd1a
> format  FFSv2
> endian  little-endian
> location 65536  (-b 128)
> magic   19540119        time    Tue May 26 21:08:51 2015
> superblock location     65536   id      [ 4af1fc0f c52ca99 ]
> cylgrp  dynamic inodes  FFSv2   sblock  FFSv2   fslevel 5
> nbfree  14854404        ndir    641259  nifree  52485537        nffree  312122
> ncg     2546    size    241051356       blocks  233698448
> bsize   16384   shift   14      mask    0xffffc000
> fsize   2048    shift   11      mask    0xfffff800
> frag    8       shift   3       fsbtodb 2
> bpg     11835   fpg     94680   ipg     22976
> minfree 5%      optim   time    maxcontig 4     maxbpg  2048
> symlinklen 120  contigsumsize 4
> maxfilesize 0x000080100202ffff
> nindir  2048    inopb   64
> avgfilesize 16384       avgfpdir 64
> sblkno  40      cblkno  48      iblkno  56      dblkno  2928
> sbsize  2048    cgsize  16384
> csaddr  2928    cssize  40960
> cgrotor 0       fmod    0       ronly   0       clean   0x01
> wapbl version 0x1       location 2      flags 0x0
> wapbl loc0 482122368    loc1 131072     loc2 512        loc3 3
> flags   none
> fsmnt   /mnt
> volname         swuid   0
> ----------
> 
> When booting with a XEN3_DOMU kernel, it shows up normally and can be mounted
> fine, so i guess its qemu going wrong?

Yes, probably. try using /dev/rwd1d instead of /dev/wd1d maybe ?

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