Re: AW: [Xen-devel] Re: [Xen-users] Re: Xen 4.0 - Support for Citrix WHQL-certified Windows PV drivers

[Pasi Kärkkäinen <pasik@xxxxxx>]

On Tue, Sep 07, 2010 at 01:26:04PM +0100, Paul Durrant wrote:
>    Presumably the tools are creating a /local/domain/3/console/0 entry if you
>    don't specify VNC; it's another example of the same issue you saw before.
> 
>    The Citrix PV drivers are not routinely tested on xen-unstable; you need
>    to tweak your tools to give them the environment they expect (which is
>    that the only thing under /local/domain/XXX/device are vbd and vif nodes).
> 

I guess the behaviour of Citrix PV drivers has changed recently? 
The drivers from XCP 0.1.x worked OK on Xen 4.0 earlier..


-- Pasi

> 
> 
> 
>    From: Giovanni Bellac [mailto:giovannib1979@xxxxxxxxx]
>    Sent: 07 September 2010 11:40
>    To: Ian Campbell
>    Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; xen-users@xxxxxxxxxxxxxxxxxxx; Paul
>    Durrant
>    Subject: AW: AW: [Xen-devel] Re: [Xen-users] Re: Xen 4.0 - Support for
>    Citrix WHQL-certified Windows PV drivers
> 
> 
> 
>    Hello Ian
> 
>    there is no "vfb" in the .sxp
> 
>    Here is it:
>    (Node: XEN 4.0.1 + 2.6.32.21 pvops)
>    I have found out one interesting point, I have described it under the
>    config file.
> 
>    name = 'windows'
>    kernel = '/usr/lib/xen/boot/hvmloader'
>    builder = 'hvm'
>    device_model = '/usr/lib64/xen/bin/qemu-dm'
>    memory = 4096
>    vcpus=4
>    acpi=1
>    apic=1
>    vif = [ 'bridge=eth0' ]
>    disk = [ 'phy:/dev/vserv/windows,hda,w',
> 
>    
> 'file:/root/SW_DVD5_Windows_Svr_DC_EE_SE_Web_2008R2_64-bit_German_X15-59762.ISO,hdc:cdrom,r'
>    ]
>    boot='c'
>    usbdevice='tablet'
>    vnc=1
>    vncunused=0
>    vnclisten = '10.10.10.137'
>    vncdisplay=2
>    vncconsole=1
>    vncpasswd=''
>    vncviewer=0
>    sdl=0
>    stdvga=0
>    serial='pty'
>    ne2000 = "0"
>    on_poweroff = 'destroy'
>    on_reboot   = 'restart'
>    on_crash    = 'restart'
> 
>    After removing all statements with "vnc" out of the sxp file and
>    restarting the windows domU, I get in the qemu logs:
> 
>     XENUTIL: WARNING: CloseFrontend: timed out in
>    XenbusWaitForBackendStateChange: /local/domain/0/backend/console/3/0 in
>    state INITIALISING; retry.
> 
>    Now it is not vfb, it is CONSOLE.
> 
>    Best regards
>    Gio
> 
> 
> 
>    --------------------------------------------------------------------------
> 
>    Von: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
>    An: Giovanni Bellac <giovannib1979@xxxxxxxxx>
>    CC: Paul Durrant <Paul.Durrant@xxxxxxxxxx>;
>    "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>;
>    "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
>    Gesendet: Dienstag, den 7. September 2010, 11:57:13 Uhr
>    Betreff: Re: AW: [Xen-devel] Re: [Xen-users] Re: Xen 4.0 - Support for
>    Citrix WHQL-certified Windows PV drivers
>    On Tue, 2010-09-07 at 08:53 +0100, Giovanni Bellac wrote:
>    > Hello
>    >
>    > > Since these is actually no fe driver for vfb, I suggest you just
>    > make sure this node does not exist.
>    >
>    > sorry, but I do not understand that 100%
>    > I have one domU with one LVM partition created. There is no other domU
>    > or LVM partition on this system.
> 
>    vfb is the virtual frame buffer.
> 
>    The frontend/backend protocol for VFB is a different to most other
>    device types and is incompatible with the Windows PV drivers.
> 
>    You should remove any "vfb" configuration items from your domain
>    configuration file, I think.
> 
>    Ian.
> 
> 

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


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