I've processed mercurial queues not only for xen.hg , but for every *.hg where m-queue was not empty. I believe, that otherwise data might be inconsistent. Made a build and installed packages on another OSOL129 freshly installed instance. Virsh appears to be completely broken ( virsh list,.. as well) regardless build has been done on OSOL129. # xm console VF12 brought up vnc-console for f12 virt-install . Patch works fine. F12's PV DomU installed and loaded with ext4 boot partition # xm start VF12 # vncviewer localhost:0
Thanks. Boris. ________________________________ Boris Derzhavets wrote: > Just committed via patch submitted to xen-devel:- > > wget http://dlc.sun.com/osol/on/downloads/b129/xvm-src.tar.bz2 > bzcat xvm-src.tar.bz2 | tar xf - > cd xen.hg hg qpush -a hg qimport pygrub-ext4-support.patch hg qpush ../sunos.hg/bin/build-all MRJ > ------------------------------------------------------------------------ > *From:* Mark Johnson <[email protected]> > *To:* Boris Derzhavets <[email protected]> > *Cc:* E. Mike Durbin <[email protected]>; [email protected] > *Sent:* Wed, December 16, 2009 9:22:48 PM > *Subject:* Re: [xen-discuss] Boot loader didn't return any data! > > > > Mark Johnson wrote: > > > > > > Boris Derzhavets wrote: > >> As far as to my knowledge only xen-3.4.1-5.fc12.src.rpm & > xen-3.4.2-2.fc13.src.rpm > >> allows to install Xen on top F12 , mostly with pvops kernel supporting > Dom0, which > >> provide ext4 support for pygrub in meantime. RH's package e2fsprogs-devel > (41) is required to build corresponding packages via source rpm. Some time > ago same question was posted by one > >> of core xVM developers to xen-devel mailing list, so Sun is aware of the > issue. > > > > I have a patch for ext4 support for pygrub which I'm > > testing now.. > > pygrub ext4 support is integrated into b131. > > > > MRJ >
_______________________________________________ xen-discuss mailing list [email protected]
