2009/6/28 Florian Manschwetus <[email protected]>: > Am 28.06.2009 13:06, schrieb Juergen Keil: >> >> 2009/6/28 Florian Manschwetus<[email protected]>: >>> >>> Am 28.06.2009 11:55, schrieb Juergen Keil: >>>> >>>> 2009/6/28 Florian Manschwetus<[email protected]>: >>>>> >>>>> Am 28.06.2009 10:21, schrieb Florian Manschwetus: >>>>>> >>>>>> https://bugzilla.redhat.com/show_bug.cgi?id=466681 >>>>>> >>>>>> just to be sure that some one in xvm-team notices that before any bits >>>>>> from xvm-gate are putback ;) >>>>>> >>>>>> Florian >>>>> >>>>> And really bad, I have no idea howto use the mentioned workaround with >>>>> xvm... >>>> >>>> I think that Solaris xVM is not affected by this problem; unlike Linux, >>>> the Solaris dom0 disk driver device does not bypass the system cache. >>>> >>> It is I have exactly this problem currently. >>> We have updated the kernel of a DomU but the updated kernel isn't loaded. >> >> dom0 is running Solaris ? > > Yes currently xvm-3.3 gate (I love zfs to be able to have 3 osols in one fs) >> >> What is running in domU ? >> > Opensolaris 2009.06 with slightly patched kernel > (=> [sparks-discuss] AD support for nss_ldap (6834242) - webrev)
Hmm, so the domU is using zfs root. Did you create a new snapshot / boot environment for the new kernel? Does the python config file for the domU force booting from a certain zfs filesystem? Is the domU zpool's bootfs property pointing to the correct zfs boot filesystem? _______________________________________________ xen-discuss mailing list [email protected]
