Re: [Xen-users] Upgrade Xen up to 4.0.1 on openSUSE 11.3 and broken VFB

[Boris Derzhavets <bderzhavets@xxxxxxxxx>]

> A couple of things:
- You probably should open a bug with Novell/openSuSE on this issue.  The Xen version that gets packaged with openSuSE is nowhere near the vanilla Xen version included on the site - it's very heavily patched by the Novell/openSuSE developers.  So, any regressions in the package need to be reported to those developers. 

Please , view .
https://bugzilla.novell.com/show_bug.cgi?id=640410

Udevd fails to create /dev/xen/gnttab under 4.0.1 & 2.6.34.7-0.2-xen,
what causes failure to to proceed in VNC window ( during  F13 PV DomU virt-install)
That's already known issue for pvops kernel. xen_gntdev should be hard linked to kernel
in pvops case.


> When you say Original Xen 4.0, do you mean the vanilla version, from xen.org, or do you mean the original openSuSE 11.3 version?


I mean original openSuSE 11.3 version, it differs from xensource release.


> - The openSuSE 11.3 kernel has been updated via the 11.3 Updates channel, and now works for booting Xen machines.  So, unless you have some reason for using KOTD, I'd go back to the officially released version,

Bug comes up in environment :-

host                   : linux-6t07
release                : 2.6.34.7-0.2-xen
version                : #1 SMP 2010-09-14 14:21:06 +0200
machine                : x86_64
nr_cpus                : 2
nr_nodes               : 1
cores_per_socket       : 2
threads_per_core       : 1
cpu_mhz                : 2999
hw_caps                : bfebfbff:20100800:00000000:00000940:0008e3fd:00000000:00000001:00000000
virt_caps              : hvm
total_memory           : 8191
free_memory            : 137
free_cpus              : 0
max_free_memory        : 7582
max_para_memory        : 7578
max_hvm_memory         : 7552
node_to_cpu            : node0:0-1
node_to_memory         : node0:137
node_to_dma32_mem      : node0:75
max_node_id            : 0
xen_major              : 4
xen_minor              : 0
xen_extra              : .1_21326_01-1.1
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : 21326
xen_commandline        : vgamode=0x31a vgamode=0x31a
cc_compiler            : gcc version 4.5.0 20100604 [gcc-4_5-branch revision 160292] (SU
cc_compile_by          : root
cc_compile_domain      : site
cc_compile_date        : Tue Sep 14 15:32:30 MSD 2010
xend_config_format     : 4

>as KOTD is likely to be somewhat unstable and subject to change/development.  I'm assuming you were using KOTD because of the bug in the kernel in the original 11.3 release that kept a domU from booting more than once without rebooting your dom0?

I was using  2.6.34.7-0.2-xen  installed via updates.
"zypper update" for entity system has been run aswell

Boris.

--- On Mon, 9/20/10, Nick Couchman <Nick.Couchman@xxxxxxxxx> wrote:

From: Nick Couchman <Nick.Couchman@xxxxxxxxx>
Subject: Re: [Xen-users] Upgrade Xen up to 4.0.1 on openSUSE 11.3 and broken VFB
To: xen-users@xxxxxxxxxxxxxxxxxxx, "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: jfehlig@xxxxxxxxxx
Date: Monday, September 20, 2010, 9:53 AM

>>> On 2010/09/19 at 09:55, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:
> After upgrade via
> http://download.opensuse.org/repositories/Virtualization:/openSUSE11.3/openSU
> SE_11.3/src/xen-4.0.1_21326_01-1.1.src.rpm with any "kotd" or 2.6.34.4-2.2-xen
> VFB gets broken . It worked with original  Xen 4.0, no matter of  some
> additional patching to support ZFS 24 has been done and 4.0 src.rpm has been
> rebuilt to reinstall 4.0
>
>   In particular,  virt-install fails to install PV DomU in "vnc" mode.
>
> Boris.
>

A couple of things:
- You probably should open a bug with Novell/openSuSE on this issue.  The Xen version that gets packaged with openSuSE is nowhere near the vanilla Xen version included on the site - it's very heavily patched by the Novell/openSuSE developers.  So, any regressions in the package need to be reported to those developers.  When you say Original Xen 4.0, do you mean the vanilla version, from xen.org, or do you mean the original openSuSE 11.3 version?
- The openSuSE 11.3 kernel has been updated via the 11.3 Updates channel, and now works for booting Xen machines.  So, unless you have some reason for using KOTD, I'd go back to the officially released version, as KOTD is likely to be somewhat unstable and subject to change/development.  I'm assuming you were using KOTD because of the bug in the kernel in the original 11.3 release that kept a domU from booting more than once without rebooting your dom0?

-Nick

-Nick



--------
This e-mail may contain confidential and privileged material for the sole use of the intended recipient.  If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information.  In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way.  If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox.  Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.

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

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