Re: [Xen-users] [xs-devel] vif failing after installing Citrix pv drivers on xen 4.2

[ananthan <ananthannair935@xxxxxxxxx>]

Ohh right,i mixed things i should have posted backend state.Sorry for that and thanks for the explanation.

xenstore-ls /local/domain/0/backend/vif/403/0

frontend = "/local/domain/403/device/vif/0"

frontend-id = "403"

>

state = "2"

script = "/etc/xen/scripts/vif-bridge"

mac = "00:16:3e:78:22:5f"

bridge = "xenbr0"

handle = "0"

type = "vif_ioemu"

feature-sg = "1"

feature-gso-tcpv4 = "1"

feature-rx-copy = "1"

feature-rx-flip = "0"

Do i need to modify vif-bridge script to make this work?

Tried manually adding to bridge using 

ifconfig vif403.0 up

brctl addif vif403.0 xenbr0

Expecting your reply.

Regards,

Ananthan

On Thu, Sep 5, 2013 at 3:32 PM, Paul Durrant <Paul.Durrant@xxxxxxxxxx> wrote:

Ananthan,

 

  From your log it seems like your vif backend is not going to state 4. What does xenstore-ls tell you? You may want to watch xenstored-access.log as you try to bring up the VM to watch the frontend/backend state transitions. The vif *should* get removed from the bridge during boot as the xenbus driver in Wndows will close any device it enumerates (because the Windows device model expects any device to start from D3 – i.e. powered off). The frontend driver should re-initialize the backend (which should cause the hotplug scripts to re-add it to the bridge) as part of its init sequence though, and the fact that your frontend made it to state 4 suggests that has happened.

 

  Paul

 

From: ananthan [mailto:ananthannair935@xxxxxxxxx]
Sent: 05 September 2013 10:46
To: Paul Durrant
Cc: xs-devel@xxxxxxxxxxxxxxxxxxx; xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [xs-devel] vif failing after installing Citrix pv drivers on xen 4.2

 

Thanks for your reply,

 

As per you suggestion updated pv drivers-(Created new instance in XS 6.1 with latest drivers and moved it to xen 4.2).

 

Log shows:

 

PV DRIVERS: VERSION: 5.9.960 BUILD: 49510 (Aug  2 2011.03:41:34)

 

Even though after driver update state of vif in xenstore changed from 1 to 4 and as before there is no error like:

 

WARNING: AdapterConnectBackend: timed out in XenbusWaitForBackendStateChange: 

/local/domain/0/backend/vif/271/0 in state INITWAIT; retry.

 

Guest is still stuck in booting screen and commenting out vif from configuration can boot it with pv drivers for disk.

 

xenstore status:

xenstore-ls /local/domain/396/device/vif/0

 

backend = "/local/domain/0/backend/vif/396/0"

backend-id = "0"

state = "4"

handle = "0"

mac = "00:16:3e:6d:d0:fb"

event-channel = "15"

request-rx-copy = "1"

 

xenstore-ls /local/domain/390/device/vbd/768

 

backend = "/local/domain/0/backend/vbd/396/768"

backend-id = "0"

state = "4"

virtual-device = "768"

device-type = "disk"

target-id = "0"

event-channel = "14"

 

Eventhough state in xenstore is 4,vif got removed from bridge after the BIOS screen.

 

brctl show before guest boot 

vif396.0 

vif396.0-emu

 

During  boot it got removed from bridge.

 

/var/log/messages

 kernel: device vif396.0 entered promiscuous mode

 kernel: ADDRCONF(NETDEV_UP): vif396.0: link is not ready

 kernel: device vif396.0-emu entered promiscuous mode

 kernel: xenbr0: port 5(vif396.0-emu) entered forwarding state

 kernel: xenbr0: port 5(vif396.0-emu) entered forwarding state

 kernel: xenbr0: port 5(vif396.0-emu) entered forwarding state

 kernel: xenbr0: port 5(vif396.0-emu) entered disabled state

 kernel: xenbr0: port 5(vif396.0-emu) entered disabled state

 kernel: device vif396.0-emu left promiscuous mode

 kernel: xenbr0: port 5(vif396.0-emu) entered disabled state

 kernel: xen-blkback:backend/vbd/396/768: prepare for reconnect

 kernel: xen-blkback:ring-ref 497, event-channel 14, protocol 2 (x86_32-abi)

 kernel: xenbr0: port 4(vif396.0) entered disabled state

 kernel: device vif396.0 left promiscuous mode

 kernel: xenbr0: port 4(vif396.0) entered disabled state

 kernel: frontend_changed: backend/vif/396/0: prepare for reconnect

 

Attached :

1.xl dmesg of this domain

2.Logs 

3.configuration-file

 

Can you tell me how to make this work.

 

 

Regards,

Ananthan

 

On Tue, Sep 3, 2013 at 7:39 PM, Paul Durrant <Paul.Durrant@xxxxxxxxxx> wrote:

Hi,

 

  Those are pretty ancient drivers:

 

XENUTIL: PV DRIVERS: VERSION: 5.6.0 BUILD: 30876 (Apr 30 2010.06:57:01)

 

  Have you tried drivers from a more recent version of XenServer? I suggest giving the drivers from 6.0.2 a go, however I am currently working on making the newer driver set (shipped in 6.1 onwards) work with an arbitrary upstream Xen installation. I’ll post more detail when I have something more complete.

 

  Cheers,

 

    Paul

 

From: xs-devel-request@xxxxxxxxxxxxxxxxxxx [mailto:xs-devel-request@xxxxxxxxxxxxxxxxxxx] On Behalf Of ananthan
Sent: 02 September 2013 17:54
To: xs-devel@xxxxxxxxxxxxxxxxxxx
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [xs-devel] vif failing after installing Citrix pv drivers on xen 4.2

 

Hi,

   I am trying to make Citrix PV drivers to work on Windows 2008R2 guests running on Xen 4.2.

But for some reasons guest is not able to boot after installing pv drivers.

 

After commenting vif from configuration file guest booted up with pvdrivers for Disk.

 

brctl show shows guests vif for some time and later got removed. 

 

In vm log its showing :

 

 XEVTCHN: ERROR: Failed to set up device suspend/event-channel.

 XEVTCHN: ERROR: Failed to set up device suspend/event-channel.

 XEVTCHN: ERROR: Failed to set up device suspend/event-channel.

 XEVTCHN: USER: SLGetWindowsInformationDWORD(VirtualXP-licensing-Enabled) failed (c004f012)

 XENUTIL: WARNING: AdapterConnectBackend: timed out in XenbusWaitForBackendStateChange: /local/domain/0/backend/vif/271/0 in state INITWAIT; retry.

Full log attached

 

/var/log/messages

 xl kernel: device vif271.0 entered promiscuous mode

 xl kernel: ADDRCONF(NETDEV_UP): vif271.0: link is not ready

 xl kernel: device vif271.0-emu entered promiscuous mode

 x1 kernel: xenbr0: port 5(vif271.0-emu) entered forwarding state

 x1 kernel: xenbr0: port 5(vif271.0-emu) entered forwarding state

 x1 kernel: xenbr0: port 5(vif271.0-emu) entered disabled state

 x1 kernel: xenbr0: port 5(vif271.0-emu) entered disabled state

 x1 kernel: device vif271.0-emu left promiscuous mode

 x1 kernel: xenbr0: port 5(vif271.0-emu) entered disabled state

 x1 kernel: xenbr0: port 4(vif271.0) entered disabled state

 x1 kernel: device vif271.0 left promiscuous mode

 x1 kernel: xenbr0: port 4(vif271.0) entered disabled state

 x1 kernel: xen-blkback:backend/vbd/271/768: prepare for reconnect

 x1 kernel: xen-blkback:ring-ref 497, event-channel 10, protocol 2 (x86_32-abi)

 x1 kernel: frontend_changed: backend/vif/271/0: prepare for reconnect

 

State in Xenstore:

 

xenstore-ls /local/domain/0/backend/vif/271/0

frontend = "/local/domain/271/device/vif/0"

frontend-id = "271"

>

state = "2"

script = "/etc/xen/scripts/vif-bridge"

mac = "00:16:3e:41:c2:5d"

bridge = "xenbr0"

handle = "0"

type = "vif_ioemu"

feature-sg = "1"

feature-gso-tcpv4 = "1"

feature-rx-copy = "1"

feature-rx-flip = "0"

 

 

xenstore-ls -fp shows:

 

/local/domain/271/device/vif = ""   (n0,r271)

/local/domain/271/device/vif/0 = ""   (n271,r0)

/local/domain/271/device/vif/0/backend = "/local/domain/0/backend/vif/271/0"   (n271,r0)

/local/domain/271/device/vif/0/backend-id = "0"   (n271,r0)

/local/domain/271/device/vif/0/state = "4"   (n271,r0)

/local/domain/271/device/vif/0/handle = "0"   (n271,r0)

/local/domain/271/device/vif/0/mac = "00:16:3e:41:c2:5d"   (n271,r0)

/local/domain/271/device/vif/0/feature-gso-tcpv4-prefix = "1"   (n271,r0)

/local/domain/271/device/vif/0/tx-ring-ref = "353"   (n271,r0)

/local/domain/271/device/vif/0/rx-ring-ref = "163"   (n271,r0)

/local/domain/271/device/vif/0/event-channel = "11"   (n271,r0)

/local/domain/271/device/vif/0/request-rx-copy = "1"   (n271,r0)

/local/domain/271/device/vif/0/feature-sg = "1"   (n271,r0)

/local/domain/271/device/vif/0/feature-rx-notify = "1"   (n271,r0)

/local/domain/271/device/vif/0/feature-no-csum-offload = "1"   (n271,r0)

 

Do i need to make any changes to make network driver to work 

 

 Regards,

Ananthan

 

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users