Hi I had installed the gpl-pv drivers 0.9.11-pre5 installed and had the following problem: All drivers seemed to work correctly, but the network card never received any packet. Now I have updated to 0.9.11-pre7, but the problem persists. I cannot access the network at all, the incoming packet counter stays at 0. I can only access it using the VNC console. Can anyone give me a hint, what to try? Regards, Steffen _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Same issue here - I''m running 0.9.11-pre7 and my network cards do not pick up an IP address. I boot w/o the /gplpv switch and the RTL-based interface works fine. -Nick>>> On 2008/07/14 at 13:07, "Steffen Heil" <lists@steffen-heil.de> wrote:Hi I had installed the gpl-pv drivers 0.9.11-pre5 installed and had the following problem: All drivers seemed to work correctly, but the network card never received any packet. Now I have updated to 0.9.11-pre7, but the problem persists. I cannot access the network at all, the incoming packet counter stays at 0. I can only access it using the VNC console. Can anyone give me a hint, what to try? Regards, Steffen 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@lists.xensource.com http://lists.xensource.com/xen-users
> I had installed the gpl-pv drivers 0.9.11-pre5 installed and had the > following problem: > > All drivers seemed to work correctly, but the network card neverreceived> any packet. > > Now I have updated to 0.9.11-pre7, but the problem persists. > I cannot access the network at all, the incoming packet counter staysat> 0. > > I can only access it using the VNC console. > > Can anyone give me a hint, what to try?Can you tell me what IRQ each of the xen based things are bound to? If you go into the hardware manager, view by resource, expand everything that has Xen under it, and send me a screenshot that will suffice. Thanks James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi> > All drivers seemed to work correctly, but the network card never > > received any packet. > > Can you tell me what IRQ each of the xen based things are > bound to? If you go into the hardware manager, view by > resource, expand everything that has Xen under it, and send > me a screenshot that will suffice.You propably didn''t get the mail with this information that I sent you directly. So here it is again: Xen PCI Device Driver pci 0-3-0, driver 0.9.10.5, 3.7.08 io c100-c1ff, ram f3000000-f3ffffff, irq 28 Xen Net Device Driver driver 0.9.10.5, 3.7.08 irq 11 Xen Block Device Driver pci 0-3-0, driver 0.9.10.5, 3.7.08 irq 11 Xen PV DISK SCSCI Disk Device pci 0-0-0, driver 5.2.3790.0, 01.10.2002 (Microsoft !???!) --- No more Xen devices. Display Adapter is still Cirrus Logic 5446 compatible. Anything more? Regards, Steffen _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I think IRQ 7 on my XEN network adapter, but I''ll let you know for sure when I get into the office today. -Nick>>> On 2008/07/14 at 19:00, "James Harper" <james.harper@bendigoit.com.au> wrote: > I had installed the gpl-pv drivers 0.9.11-pre5 installed and had the > following problem: > > All drivers seemed to work correctly, but the network card neverreceived> any packet. > > Now I have updated to 0.9.11-pre7, but the problem persists. > I cannot access the network at all, the incoming packet counter staysat> 0. > > I can only access it using the VNC console. > > Can anyone give me a hint, what to try?Can you tell me what IRQ each of the xen based things are bound to? If you go into the hardware manager, view by resource, expand everything that has Xen under it, and send me a screenshot that will suffice. Thanks James 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@lists.xensource.com http://lists.xensource.com/xen-users
Here you go... -Nick>>> On Mon, Jul 14, 2008 at 7:00 PM, "James Harper" <james.harper@bendigoit.com.au> wrote:> I had installed the gpl-pv drivers 0.9.11-pre5 installed and had the > following problem: > > All drivers seemed to work correctly, but the network card neverreceived> any packet. > > Now I have updated to 0.9.11-pre7, but the problem persists. > I cannot access the network at all, the incoming packet counter staysat> 0. > > I can only access it using the VNC console. > > Can anyone give me a hint, what to try?Can you tell me what IRQ each of the xen based things are bound to? If you go into the hardware manager, view by resource, expand everything that has Xen under it, and send me a screenshot that will suffice. Thanks James 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@lists.xensource.com http://lists.xensource.com/xen-users
On Tue July 15 2008 9:52:07 am Nick Couchman wrote:> xen-resources.JPGWell, that''s interesting, James: Why are xennet, xenblk, etc. considered ISA devices, but xenpci is a pci device? (My system looks similar.) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Nick, I just upgraded to GPLPV 0.9.11-pre8. Now I have the following IRQs: ISA 7 Xen Net Device Driver ISA 7 Xen Stub Device Driver (Console) ISA 7 Xen Stub Device Driver (Virtual Frame Buffer) ISA 11 Xen Block Device Driver PCI 28 Xen PCI Device Driver However, the network issue persists. Windows tries to send packets (only a few over time), but Windows doesn''t receive any. Did you have any luck getting it to work for you? BTW: As intermediate solution, I would like to enable the QEMU network driver while keeping the PV block devices. Is this possible? Regards, Steffen _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I''ll have to try -pre8 here soon and see if that works. I was able to get my Xen Network device to work by manually switching the IRQ over to some other one (5, I think). Unfortunately that caused a lot of other issues with stability of the system, and it''s now very hard to keep it running, so I''m afraid I may have to undo that. James, I''m still curious on the question someone else asked about why the Xen devices show up on the ISA bus? I know it probably doesn''t really make a difference, since it is "virtual" hardware, but that just seems a little strange. Definitely not a criticism, just curious about it... Thanks - Nick>>> On Sat, Jul 19, 2008 at 12:46 PM, "Steffen Heil" <lists@steffen-heil.de> wrote:Hi Nick, I just upgraded to GPLPV 0.9.11-pre8. Now I have the following IRQs: ISA 7 Xen Net Device Driver ISA 7 Xen Stub Device Driver (Console) ISA 7 Xen Stub Device Driver (Virtual Frame Buffer) ISA 11 Xen Block Device Driver PCI 28 Xen PCI Device Driver However, the network issue persists. Windows tries to send packets (only a few over time), but Windows doesn''t receive any. Did you have any luck getting it to work for you? BTW: As intermediate solution, I would like to enable the QEMU network driver while keeping the PV block devices. Is this possible? Regards, Steffen 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@lists.xensource.com http://lists.xensource.com/xen-users
Looking through some docs, I think irq7 (and probably irq15 too) is incompatible with being called via the asm ''int x'' instruction. Easy enough to try - i''ll fix it when get some time today. James -----Original Message----- From: "Steffen Heil"<lists@steffen-heil.de> Sent: 20/07/08 4:46:58 AM To: "''Nick Couchman''"<Nick.Couchman@seakr.com> Cc: "''James Harper''"<james.harper@bendigoit.com.au>, "xen-users@lists.xensource.com"<xen-users@lists.xensource.com> Subject: RE: [Xen-users] GPLPV but network problem Hi Nick, I just upgraded to GPLPV 0.9.11-pre8. Now I have the following IRQs: ISA 7 Xen Net Device Driver ISA 7 Xen Stub Device Driver (Console) ISA 7 Xen Stub Device Driver (Virtual Frame Buffer) ISA 11 Xen Block Device Driver PCI 28 Xen PCI Device Driver However, the network issue persists. Windows tries to send packets (only a few over time), but Windows doesn''t receive any. Did you have any luck getting it to work for you? BTW: As intermediate solution, I would like to enable the QEMU network driver while keeping the PV block devices. Is this possible? Regards, Steffen _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi> Looking through some docs, I think irq7 (and probably irq15 > too) is incompatible with being called via the asm ''int x'' > instruction. Easy enough to try - i''ll fix it when get some > time today.I just tried setting IRQ to 10 and 5. Both settings did not change anything. BTW: As intermediate solution, I would like to enable the QEMU network driver while keeping the PV block devices. Is this possible? Regards, Steffen _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> I just upgraded to GPLPV 0.9.11-pre8. > > Now I have the following IRQs: > ISA 7 Xen Net Device Driver > ISA 7 Xen Stub Device Driver (Console) > ISA 7 Xen Stub Device Driver (Virtual Frame Buffer) > ISA 11 Xen Block Device Driver > PCI 28 Xen PCI Device Driver > > However, the network issue persists. > Windows tries to send packets (only a few over time), but Windows doesn''t > receive any.I''ve just uploaded a -pre9 which will prevent the drivers from using IRQ7. In order to make things behave like real hardware (makes scsi _much_ easier) I assign a fake hardware interrupt and then call it using the asm ''int x'' instruction. I read ages ago that this doesn''t work with irq 7 and irq 15, and thought I had excluded them for that reason, but obviously I hadn''t.> BTW: As intermediate solution, I would like to enable the QEMU network > driver while keeping the PV block devices. Is this possible?If you don''t install the network driver then the filter will not get installed which disables the qemu driver. You can''t get the same effect by uninstalling the network driver though, you''d have to go in and remove the upper filter from the Network class. This -pre9 update should get things working for you though. Please let me know if it does. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> James, I''m still curious on the question someone else asked about whythe> Xen devices show up on the ISA bus? I know it probably doesn''t really > make a difference, since it is "virtual" hardware, but that just seemsa> little strange. Definitely not a criticism, just curious about it...The interrupts that those devices use are virtual and are nothing to do with the PCI interrupt that the xenpci driver uses. They are triggered by calling an asm ''int x'' instruction from the xenpci driver. It would be nice to be able to use the PCI interrupts, as there are more of them available and there are performance improvements to be had by using non-shared interrupts, but when I ask the Windows PnP manager for an interrupt it appears that I can only ask for one in the range of 1-15, and for various reasons, 2, 7, 9, and 15 don''t work. 2 and 9 because of the way the ISA interrupt controllers link to each other, and 7 and 15 for reasons that I can''t remember right now. If I ask for an interrupt in the range 16-63, windows won''t give me one. I can''t just use a 16-63 interrupt without allocating them as I need the PnP manager to set up the irq vector properly. This is the problem of trying to interface with closed source code like Windows - you are stuck with what you get :) I think ''ISA'' in this case just means a non-APIC sourced interrupt, the xen devices are on an ''Internal'' bus as far as Windows is concerned. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Hi > > > Looking through some docs, I think irq7 (and probably irq15 > > too) is incompatible with being called via the asm ''int x'' > > instruction. Easy enough to try - i''ll fix it when get some > > time today. > > I just tried setting IRQ to 10 and 5. > Both settings did not change anything.D''oh. I didn''t see this email before I just answered the other one. For the sake of completeness, please try the -pre9 release, but if you have manually tried moving away from IRQ7 I guess it''s probably not going to work. Pity.> BTW: As intermediate solution, I would like to enable the QEMU network > driver while keeping the PV block devices. Is this possible?Yes. Given that it looks like the -pre9 drivers won''t make any difference, please do the following (slightly more verbose than previous email as I was hoping you wouldn''t have to do it): 1. Remove xennet.sys from c:\windows\system32\drivers 2. Remove any oem.* files from C:\Windows\inf that contain the string "xennet.sys" 3. Remove HKLM\SYSTEM\CurrentControlSet\Services\XenNet from the registry 4. Remove HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11C E-BFC1-08002bE10318}\UpperFilters - it should contain xennet.sys only. If it contains other things too then just delete the text xennet.sys from it. 5. Reboot Please test on a non critical system first - I haven''t tested the above instructions myself! James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks for the explanation, and for the -pre9 version - I''ll give it a try next time I get chance... -Nick>>> On 2008/07/19 at 21:43, "James Harper" <james.harper@bendigoit.com.au> wrote: > James, I''m still curious on the question someone else asked about whythe> Xen devices show up on the ISA bus? I know it probably doesn''t really > make a difference, since it is "virtual" hardware, but that just seemsa> little strange. Definitely not a criticism, just curious about it...The interrupts that those devices use are virtual and are nothing to do with the PCI interrupt that the xenpci driver uses. They are triggered by calling an asm ''int x'' instruction from the xenpci driver. It would be nice to be able to use the PCI interrupts, as there are more of them available and there are performance improvements to be had by using non-shared interrupts, but when I ask the Windows PnP manager for an interrupt it appears that I can only ask for one in the range of 1-15, and for various reasons, 2, 7, 9, and 15 don''t work. 2 and 9 because of the way the ISA interrupt controllers link to each other, and 7 and 15 for reasons that I can''t remember right now. If I ask for an interrupt in the range 16-63, windows won''t give me one. I can''t just use a 16-63 interrupt without allocating them as I need the PnP manager to set up the irq vector properly. This is the problem of trying to interface with closed source code like Windows - you are stuck with what you get :) I think ''ISA'' in this case just means a non-APIC sourced interrupt, the xen devices are on an ''Internal'' bus as far as Windows is concerned. James 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@lists.xensource.com http://lists.xensource.com/xen-users
Hi> For the sake of completeness, please try the -pre9 > release, but if you have manually tried moving away from IRQ7 > I guess it''s probably not going to work. Pity.Just installed -pre9 and it uses IRQ 11 now, but is still not working. Any other idea?> Yes. Given that it looks like the -pre9 drivers won''t make > any difference, please do the following (slightly more > verbose than previous email as I was hoping you wouldn''t have > to do it): > > 1. Remove xennet.sys from c:\windows\system32\drivers 2. > Remove any oem.* files from C:\Windows\inf that contain the > string "xennet.sys" > 3. Remove HKLM\SYSTEM\CurrentControlSet\Services\XenNet from > the registry 4. Remove > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D3 > 6E972-E325-11C > E-BFC1-08002bE10318}\UpperFilters - it should contain > xennet.sys only. If it contains other things too then just > delete the text xennet.sys from it. > 5. Reboot > > Please test on a non critical system first - I haven''t tested > the above instructions myself!Thanks for this information. I will try it soon, but I need some backups first :D. I will report back wether this works. Regards, Steffen _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > For the sake of completeness, please try the -pre9 > > release, but if you have manually tried moving away from IRQ7 > > I guess it''s probably not going to work. Pity. > > Just installed -pre9 and it uses IRQ 11 now, but is still not working.After I updated I noticed that my domain was using IRQ7 and was working, so I guess that wasn''t it after all.> Any other idea?Could you please try some packet traces on the vifX.Y interface in Dom0. Also, please check that it is linked to the bridge correctly, and that you don''t have firewall rules that are allowing tunX traffic through but not vifX.Y traffic. In case you can''t tell I''m running out of ideas :) James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Well, I''ll try a couple of those things, but in my setup I have another 20 Windows XP domUs that are running either without the GPLPV drivers or with an older set of the drivers and they work perfectly fine, all on exactly the same bridge as this one with the latest GPLPV drivers is on. Additionally, on this particular domU if I boot w/o the /gplpv switch, it works fine. -Nick>>> On Mon, Jul 21, 2008 at 6:53 AM, "James Harper" <james.harper@bendigoit.com.au> wrote:> > For the sake of completeness, please try the -pre9 > > release, but if you have manually tried moving away from IRQ7 > > I guess it''s probably not going to work. Pity. > > Just installed -pre9 and it uses IRQ 11 now, but is still not working.After I updated I noticed that my domain was using IRQ7 and was working, so I guess that wasn''t it after all.> Any other idea?Could you please try some packet traces on the vifX.Y interface in Dom0. Also, please check that it is linked to the bridge correctly, and that you don''t have firewall rules that are allowing tunX traffic through but not vifX.Y traffic. In case you can''t tell I''m running out of ideas :) James 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@lists.xensource.com http://lists.xensource.com/xen-users
Well, I can report success using the -pre9 version of the drivers! I booted w/o /gplpv and updated from pre7 to pre9, then booted back into the GPLPV version and all is working well. All of the XEN PV devices seem to be on IRQ 11. I''ll be happy to give more info if needed to try to understand while mine works and Steffen''s doesn''t. Thanks - Nick>>> On Mon, Jul 21, 2008 at 6:53 AM, "James Harper" <james.harper@bendigoit.com.au> wrote:> > For the sake of completeness, please try the -pre9 > > release, but if you have manually tried moving away from IRQ7 > > I guess it''s probably not going to work. Pity. > > Just installed -pre9 and it uses IRQ 11 now, but is still not working.After I updated I noticed that my domain was using IRQ7 and was working, so I guess that wasn''t it after all.> Any other idea?Could you please try some packet traces on the vifX.Y interface in Dom0. Also, please check that it is linked to the bridge correctly, and that you don''t have firewall rules that are allowing tunX traffic through but not vifX.Y traffic. In case you can''t tell I''m running out of ideas :) James 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@lists.xensource.com http://lists.xensource.com/xen-users
Okay...but now I decided to try -pre9 in an XP domU that did not have a version of the GPLPV drivers previously installed and now at boot time I get a STOP: 0x000000A (0x0000000C, 0x000000FF, 0x00000000, 0x805327AE) IRQL_NOT_LESS_OR_EQUAL bsod and the domU reboots.>>> On Mon, Jul 21, 2008 at 6:53 AM, "James Harper" <james.harper@bendigoit.com.au> wrote:> > For the sake of completeness, please try the -pre9 > > release, but if you have manually tried moving away from IRQ7 > > I guess it''s probably not going to work. Pity. > > Just installed -pre9 and it uses IRQ 11 now, but is still not working.After I updated I noticed that my domain was using IRQ7 and was working, so I guess that wasn''t it after all.> Any other idea?Could you please try some packet traces on the vifX.Y interface in Dom0. Also, please check that it is linked to the bridge correctly, and that you don''t have firewall rules that are allowing tunX traffic through but not vifX.Y traffic. In case you can''t tell I''m running out of ideas :) James 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@lists.xensource.com http://lists.xensource.com/xen-users