RE: [Xen-users] 64-bit PV domU (2.6.27) hangs during boot?

["Logan, John G." <John.G.Logan@xxxxxxx>]

> > extra = '2 console=xvc0'
> try instead:
>
> extra = '2 console=hvc0'
> (as the pvops kernel using hvc0)
>
Thanks, Todd - that did help a bit.  I now see that the root's not being 
mounted:

[    0.669545] device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: 
dm-devel@xxxxxxxxxx
Done.
Begin: Running /scripts/init-premount ...
Done.
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top ...
Done.
Begin: Waiting for root file system... ...
Done.
  Reading all physical volumes.  This may take a while...
Begin: Waiting for root file system... ...
Done.
  Reading all physical volumes.  This may take a while...
<<and so on...>>

http://wiki.xensource.com/xenwiki/XenParavirtOps says to use xvd devices, so 
I'm doing that, as well as using tap:aio.  'xm block-list' on the domain gives 
me:

Vdev  BE handle state evt-ch ring-ref BE-path
51713  0    0     1      -1     -1    /local/domain/0/backend/tap/30/51713
51714  0    0     1      -1     -1    /local/domain/0/backend/tap/30/51714

I wish I understood more about what this output means, but the event channel ID 
of -1 for these devices doesn't seem like a good sign.

Could it be that something's missing from the initramfs I'm using?  I had 
thought that the Ubuntu intrepid stuff was ready to go as a 64-bit domU.

jgl

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users