Well, I seem to have developed a strange issue with the GPL PV drivers in Windows. I''m running Xen 3.2 on SLES 10 SP2 and running some Windows XP HVM domUs. Most (12-15) of my Windows machines work just fine. Two of them, though, have started exhibiting a strange behavior with intermittent network connectivity. Basically, the network starts up and connects initially. After some random amount of time that varies in between reboots, it quits working - doesn''t respond to pings and isn''t able to get access to any network resources at all - cannot ping out, access web sites, etc. If I disable the card and re-enabled, sometimes it will start working, sometimes it will fail to pick up a DHCP address, etc. If it does start working, it only works for a limited amount of time (sometimes 10 seconds, sometimes 5 minutes) and quits working again. If I run tcpdump on the dom0 bridge it''s using or on the dom0 interface for the domU (e.g. vif87.0 where 87 is the number of the running domU), I see ARP requests from hosts for the IP address of the system, but the domU doesn''t seem to respond to those requests - there are never any packets coming out of the domU. I can also see ICMP echo requests to the host, but no responses. If I try to ping out from the domU, I don''t see any packets at all - no ARP requests, no ICMP echo requests, etc. Has anyone seen this behavior before? I''m working on getting both Windows debugging setup and trying to run tcpdump (or something similar) inside the Windows HVM domU to try to capture what it thinks is happening. There don''t appear to be any correlating events for the network card either working or failing to work in the dom0 log files, dmesg, xm dmesg, or xm log. I see the following message in the qemu-dm-<id>.log file, but don''t know if it''s related or not: I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Also, sometimes it seems to be related to whether or not I''m doing something with the VM. For example, last time I tried it, pings were responding fine until I moved my mouse into the VM and then it quit working. IRQ conflict, maybe - the network card seems to have used IRQ 5?? Thanks - 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@lists.xensource.com http://lists.xensource.com/xen-users
What version of GPLPV? 0.9.11 fixes a few odd network issues. The Xen PV network card should be using the same IRQ as the PCI device. Is that not the case? James> -----Original Message----- > From: xen-users-bounces@lists.xensource.com [mailto:xen-users- > bounces@lists.xensource.com] On Behalf Of Nick Couchman > Sent: Tuesday, 11 November 2008 09:50 > To: xen-users@lists.xensource.com > Subject: [Xen-users] GPL PV Intermitent Network Problems > > Well, I seem to have developed a strange issue with the GPL PV driversin> Windows. I''m running Xen 3.2 on SLES 10 SP2 and running some WindowsXP> HVM domUs. Most (12-15) of my Windows machines work just fine. Twoof> them, though, have started exhibiting a strange behavior withintermittent> network connectivity. Basically, the network starts up and connects > initially. After some random amount of time that varies in between > reboots, it quits working - doesn''t respond to pings and isn''t able toget> access to any network resources at all - cannot ping out, access web > sites, etc. If I disable the card and re-enabled, sometimes it willstart> working, sometimes it will fail to pick up a DHCP address, etc. If it > does start working, it only works for a limited amount of time(sometimes> 10 seconds, sometimes 5 minutes) and quits working again. > > If I run tcpdump on the dom0 bridge it''s using or on the dom0interface> for the domU (e.g. vif87.0 where 87 is the number of the runningdomU), I> see ARP requests from hosts for the IP address of the system, but thedomU> doesn''t seem to respond to those requests - there are never anypackets> coming out of the domU. I can also see ICMP echo requests to thehost,> but no responses. If I try to ping out from the domU, I don''t see any > packets at all - no ARP requests, no ICMP echo requests, etc. > > Has anyone seen this behavior before? I''m working on getting bothWindows> debugging setup and trying to run tcpdump (or something similar)inside> the Windows HVM domU to try to capture what it thinks is happening.There> don''t appear to be any correlating events for the network card either > working or failing to work in the dom0 log files, dmesg, xm dmesg, orxm> log. I see the following message in the qemu-dm-<id>.log file, butdon''t> know if it''s related or not: > > I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 > > Also, sometimes it seems to be related to whether or not I''m doing > something with the VM. For example, last time I tried it, pings were > responding fine until I moved my mouse into the VM and then it quit > working. IRQ conflict, maybe - the network card seems to have usedIRQ> 5?? > > Thanks - Nick > > ________________________________ > > This e-mail may contain confidential and privileged material for thesole> 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 theintended> 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 immediatelyby> replying to this e-mail and delete the message from your mailbox. > Information contained in this message that does not relate to thebusiness> 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
Version shows as 0.9.11. Nick Couchman Manager, Information Technology -----Original Message----- From: "James Harper" <james.harper@bendigoit.com.au> To: <xen-users@lists.xensource.com> To: Nick Couchman <Nick.Couchman@seakr.com> Sent: 11/10/2008 3:57:30 PM Subject: RE: [Xen-users] GPL PV Intermitent Network Problems What version of GPLPV? 0.9.11 fixes a few odd network issues. The Xen PV network card should be using the same IRQ as the PCI device. Is that not the case? James> -----Original Message----- > From: xen-users-bounces@lists.xensource.com [mailto:xen-users- > bounces@lists.xensource.com] On Behalf Of Nick Couchman > Sent: Tuesday, 11 November 2008 09:50 > To: xen-users@lists.xensource.com > Subject: [Xen-users] GPL PV Intermitent Network Problems > > Well, I seem to have developed a strange issue with the GPL PV driversin> Windows. I''m running Xen 3.2 on SLES 10 SP2 and running some WindowsXP> HVM domUs. Most (12-15) of my Windows machines work just fine. Twoof> them, though, have started exhibiting a strange behavior withintermittent> network connectivity. Basically, the network starts up and connects > initially. After some random amount of time that varies in between > reboots, it quits working - doesn''t respond to pings and isn''t able toget> access to any network resources at all - cannot ping out, access web > sites, etc. If I disable the card and re-enabled, sometimes it willstart> working, sometimes it will fail to pick up a DHCP address, etc. If it > does start working, it only works for a limited amount of time(sometimes> 10 seconds, sometimes 5 minutes) and quits working again. > > If I run tcpdump on the dom0 bridge it''s using or on the dom0interface> for the domU (e.g. vif87.0 where 87 is the number of the runningdomU), I> see ARP requests from hosts for the IP address of the system, but thedomU> doesn''t seem to respond to those requests - there are never anypackets> coming out of the domU. I can also see ICMP echo requests to thehost,> but no responses. If I try to ping out from the domU, I don''t see any > packets at all - no ARP requests, no ICMP echo requests, etc. > > Has anyone seen this behavior before? I''m working on getting bothWindows> debugging setup and trying to run tcpdump (or something similar)inside> the Windows HVM domU to try to capture what it thinks is happening.There> don''t appear to be any correlating events for the network card either > working or failing to work in the dom0 log files, dmesg, xm dmesg, orxm> log. I see the following message in the qemu-dm-<id>.log file, butdon''t> know if it''s related or not: > > I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 > > Also, sometimes it seems to be related to whether or not I''m doing > something with the VM. For example, last time I tried it, pings were > responding fine until I moved my mouse into the VM and then it quit > working. IRQ conflict, maybe - the network card seems to have usedIRQ> 5?? > > Thanks - Nick > > ________________________________ > > This e-mail may contain confidential and privileged material for thesole> 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 theintended> 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 immediatelyby> replying to this e-mail and delete the message from your mailbox. > Information contained in this message that does not relate to thebusiness> of SEAKR is neither endorsed by nor attributable to SEAKR.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
> > Version shows as 0.9.11.Pity. Okay, please fire up DebugView and in Dom0 type "xm sysrq <domain> C". That will cause some debug information to be dumped. Please put that in an email to me. It should look something like: XenPCI --> XenPci_SysrqHandler XenPCI SysRq Value = C XenPCI path = device/vfb/0 XenPCI backend_path = /local/domain/0/backend/vfb/82/0 XenPCI irq_number = 28 XenPCI irq_level = 9 XenPCI irq_vector = 1a3 XenPCI path = device/vbd/768 XenPCI backend_path = /local/domain/0/backend/vbd/82/768 XenPCI irq_number = 28 XenPCI irq_level = 9 XenPCI irq_vector = 1a3 XenPCI path = device/vbd/5632 XenPCI backend_path = /local/domain/0/backend/vbd/82/5632 XenPCI irq_number = 28 XenPCI irq_level = 9 XenPCI irq_vector = 1a3 XenPCI path = device/vif/0 XenPCI backend_path = /local/domain/0/backend/vif/82/0 XenPCI irq_number = 28 XenPCI irq_level = 9 XenPCI irq_vector = 1a3 XenPCI path = device/vif/1 XenPCI backend_path = /local/domain/0/backend/vif/82/1 XenPCI irq_number = 28 XenPCI irq_level = 9 XenPCI irq_vector = 1a3 XenPCI path = device/vif/2 XenPCI backend_path = /local/domain/0/backend/vif/82/2 XenPCI irq_number = 28 XenPCI irq_level = 9 XenPCI irq_vector = 1a3 XenPCI path = device/console/0 XenPCI backend_path = /local/domain/0/backend/console/82/0 XenPCI irq_number = 28 XenPCI irq_level = 9 XenPCI irq_vector = 1a3 XenPCI <-- XenPci_SysrqHandler Thanks James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Here you go. I ran the command a few times - not sure if that matters or not. -Nick>>> "James Harper" <james.harper@bendigoit.com.au> 2008/11/10 16:13 >>> > > Version shows as 0.9.11.Pity. Okay, please fire up DebugView and in Dom0 type "xm sysrq <domain> C". That will cause some debug information to be dumped. Please put that in an email to me. It should look something like: XenPCI --> XenPci_SysrqHandler XenPCI SysRq Value = C XenPCI path = device/vfb/0 XenPCI backend_path = /local/domain/0/backend/vfb/82/0 XenPCI irq_number = 28 XenPCI irq_level = 9 XenPCI irq_vector = 1a3 XenPCI path = device/vbd/768 XenPCI backend_path = /local/domain/0/backend/vbd/82/768 XenPCI irq_number = 28 XenPCI irq_level = 9 XenPCI irq_vector = 1a3 XenPCI path = device/vbd/5632 XenPCI backend_path = /local/domain/0/backend/vbd/82/5632 XenPCI irq_number = 28 XenPCI irq_level = 9 XenPCI irq_vector = 1a3 XenPCI path = device/vif/0 XenPCI backend_path = /local/domain/0/backend/vif/82/0 XenPCI irq_number = 28 XenPCI irq_level = 9 XenPCI irq_vector = 1a3 XenPCI path = device/vif/1 XenPCI backend_path = /local/domain/0/backend/vif/82/1 XenPCI irq_number = 28 XenPCI irq_level = 9 XenPCI irq_vector = 1a3 XenPCI path = device/vif/2 XenPCI backend_path = /local/domain/0/backend/vif/82/2 XenPCI irq_number = 28 XenPCI irq_level = 9 XenPCI irq_vector = 1a3 XenPCI path = device/console/0 XenPCI backend_path = /local/domain/0/backend/console/82/0 XenPCI irq_number = 28 XenPCI irq_level = 9 XenPCI irq_vector = 1a3 XenPCI <-- XenPci_SysrqHandler 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
Interesting... you are using irq 5. Are you not running with apic=1 in the config? I suspect that the problems you are seeing are because you are using an interrupt < 16, which behave a little differently than those > 16. On my system (apic and acpi left at the default of enabled) the Xen PCI Device gets IRQ 28 and all the sub-devices use the same IRQ (even though device manager reports the IRQ as ISA). James> -----Original Message----- > From: Nick Couchman [mailto:Nick.Couchman@seakr.com] > Sent: Tuesday, 11 November 2008 11:00 > To: James Harper; xen-users@lists.xensource.com > Subject: RE: [Xen-users] GPL PV Intermitent Network Problems > > Here you go. I ran the command a few times - not sure if that mattersor> not. > > -Nick > > >>> "James Harper" <james.harper@bendigoit.com.au> 2008/11/10 16:13 >>> > > > > Version shows as 0.9.11. > > Pity. > > Okay, please fire up DebugView and in Dom0 type "xm sysrq <domain> C". > That will cause some debug information to be dumped. Please put thatin> an email to me. It should look something like: > > XenPCI --> XenPci_SysrqHandler > XenPCI SysRq Value = C > XenPCI path = device/vfb/0 > XenPCI backend_path = /local/domain/0/backend/vfb/82/0 > XenPCI irq_number = 28 > XenPCI irq_level = 9 > XenPCI irq_vector = 1a3 > XenPCI path = device/vbd/768 > XenPCI backend_path = /local/domain/0/backend/vbd/82/768 > XenPCI irq_number = 28 > XenPCI irq_level = 9 > XenPCI irq_vector = 1a3 > XenPCI path = device/vbd/5632 > XenPCI backend_path = /local/domain/0/backend/vbd/82/5632 > XenPCI irq_number = 28 > XenPCI irq_level = 9 > XenPCI irq_vector = 1a3 > XenPCI path = device/vif/0 > XenPCI backend_path = /local/domain/0/backend/vif/82/0 > XenPCI irq_number = 28 > XenPCI irq_level = 9 > XenPCI irq_vector = 1a3 > XenPCI path = device/vif/1 > XenPCI backend_path = /local/domain/0/backend/vif/82/1 > XenPCI irq_number = 28 > XenPCI irq_level = 9 > XenPCI irq_vector = 1a3 > XenPCI path = device/vif/2 > XenPCI backend_path = /local/domain/0/backend/vif/82/2 > XenPCI irq_number = 28 > XenPCI irq_level = 9 > XenPCI irq_vector = 1a3 > XenPCI path = device/console/0 > XenPCI backend_path = /local/domain/0/backend/console/82/0 > XenPCI irq_number = 28 > XenPCI irq_level = 9 > XenPCI irq_vector = 1a3 > XenPCI <-- XenPci_SysrqHandler > > Thanks > > James > > > ________________________________ > > This e-mail may contain confidential and privileged material for thesole> 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 theintended> 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 immediatelyby> replying to this e-mail and delete the message from your mailbox. > Information contained in this message that does not relate to thebusiness> 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, apic was, indeed, disabled, however after re-enabling it, deleting the domain, and recreating the domain, the issue persists, and the network card is still using IRQ 5. Also, I have another domU that has the same behavior that has apic enabled. I''m attempting to delete the network device and re-add it now and see if that works, but I''ve tried this in the other domU and it doesn''t seem to have made a difference. -Nick>>> "James Harper" <james.harper@bendigoit.com.au> 2008/11/10 17:04 >>>Interesting... you are using irq 5. Are you not running with apic=1 in the config? I suspect that the problems you are seeing are because you are using an interrupt < 16, which behave a little differently than those > 16. On my system (apic and acpi left at the default of enabled) the Xen PCI Device gets IRQ 28 and all the sub-devices use the same IRQ (even though device manager reports the IRQ as ISA). James> -----Original Message----- > From: Nick Couchman [mailto:Nick.Couchman@seakr.com] > Sent: Tuesday, 11 November 2008 11:00 > To: James Harper; xen-users@lists.xensource.com > Subject: RE: [Xen-users] GPL PV Intermitent Network Problems > > Here you go. I ran the command a few times - not sure if that mattersor> not. > > -Nick > > >>> "James Harper" <james.harper@bendigoit.com.au> 2008/11/10 16:13 >>> > > > > Version shows as 0.9.11. > > Pity. > > Okay, please fire up DebugView and in Dom0 type "xm sysrq <domain> C". > That will cause some debug information to be dumped. Please put thatin> an email to me. It should look something like: > > XenPCI --> XenPci_SysrqHandler > XenPCI SysRq Value = C > XenPCI path = device/vfb/0 > XenPCI backend_path = /local/domain/0/backend/vfb/82/0 > XenPCI irq_number = 28 > XenPCI irq_level = 9 > XenPCI irq_vector = 1a3 > XenPCI path = device/vbd/768 > XenPCI backend_path = /local/domain/0/backend/vbd/82/768 > XenPCI irq_number = 28 > XenPCI irq_level = 9 > XenPCI irq_vector = 1a3 > XenPCI path = device/vbd/5632 > XenPCI backend_path = /local/domain/0/backend/vbd/82/5632 > XenPCI irq_number = 28 > XenPCI irq_level = 9 > XenPCI irq_vector = 1a3 > XenPCI path = device/vif/0 > XenPCI backend_path = /local/domain/0/backend/vif/82/0 > XenPCI irq_number = 28 > XenPCI irq_level = 9 > XenPCI irq_vector = 1a3 > XenPCI path = device/vif/1 > XenPCI backend_path = /local/domain/0/backend/vif/82/1 > XenPCI irq_number = 28 > XenPCI irq_level = 9 > XenPCI irq_vector = 1a3 > XenPCI path = device/vif/2 > XenPCI backend_path = /local/domain/0/backend/vif/82/2 > XenPCI irq_number = 28 > XenPCI irq_level = 9 > XenPCI irq_vector = 1a3 > XenPCI path = device/console/0 > XenPCI backend_path = /local/domain/0/backend/console/82/0 > XenPCI irq_number = 28 > XenPCI irq_level = 9 > XenPCI irq_vector = 1a3 > XenPCI <-- XenPci_SysrqHandler > > Thanks > > James > > > ________________________________ > > This e-mail may contain confidential and privileged material for thesole> 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 theintended> 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 immediatelyby> replying to this e-mail and delete the message from your mailbox. > Information contained in this message that does not relate to thebusiness> of SEAKR is neither endorsed by nor attributable to SEAKR.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
Deleted the network card and re-added it, and it is still using IRQ 5 and still showing the same behavior. -Nick>>> "James Harper" <james.harper@bendigoit.com.au> 2008/11/10 17:04 >>>Interesting... you are using irq 5. Are you not running with apic=1 in the config? I suspect that the problems you are seeing are because you are using an interrupt < 16, which behave a little differently than those > 16. On my system (apic and acpi left at the default of enabled) the Xen PCI Device gets IRQ 28 and all the sub-devices use the same IRQ (even though device manager reports the IRQ as ISA). James> -----Original Message----- > From: Nick Couchman [mailto:Nick.Couchman@seakr.com] > Sent: Tuesday, 11 November 2008 11:00 > To: James Harper; xen-users@lists.xensource.com > Subject: RE: [Xen-users] GPL PV Intermitent Network Problems > > Here you go. I ran the command a few times - not sure if that mattersor> not. > > -Nick > > >>> "James Harper" <james.harper@bendigoit.com.au> 2008/11/10 16:13 >>> > > > > Version shows as 0.9.11. > > Pity. > > Okay, please fire up DebugView and in Dom0 type "xm sysrq <domain> C". > That will cause some debug information to be dumped. Please put thatin> an email to me. It should look something like: > > XenPCI --> XenPci_SysrqHandler > XenPCI SysRq Value = C > XenPCI path = device/vfb/0 > XenPCI backend_path = /local/domain/0/backend/vfb/82/0 > XenPCI irq_number = 28 > XenPCI irq_level = 9 > XenPCI irq_vector = 1a3 > XenPCI path = device/vbd/768 > XenPCI backend_path = /local/domain/0/backend/vbd/82/768 > XenPCI irq_number = 28 > XenPCI irq_level = 9 > XenPCI irq_vector = 1a3 > XenPCI path = device/vbd/5632 > XenPCI backend_path = /local/domain/0/backend/vbd/82/5632 > XenPCI irq_number = 28 > XenPCI irq_level = 9 > XenPCI irq_vector = 1a3 > XenPCI path = device/vif/0 > XenPCI backend_path = /local/domain/0/backend/vif/82/0 > XenPCI irq_number = 28 > XenPCI irq_level = 9 > XenPCI irq_vector = 1a3 > XenPCI path = device/vif/1 > XenPCI backend_path = /local/domain/0/backend/vif/82/1 > XenPCI irq_number = 28 > XenPCI irq_level = 9 > XenPCI irq_vector = 1a3 > XenPCI path = device/vif/2 > XenPCI backend_path = /local/domain/0/backend/vif/82/2 > XenPCI irq_number = 28 > XenPCI irq_level = 9 > XenPCI irq_vector = 1a3 > XenPCI path = device/console/0 > XenPCI backend_path = /local/domain/0/backend/console/82/0 > XenPCI irq_number = 28 > XenPCI irq_level = 9 > XenPCI irq_vector = 1a3 > XenPCI <-- XenPci_SysrqHandler > > Thanks > > James > > > ________________________________ > > This e-mail may contain confidential and privileged material for thesole> 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 theintended> 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 immediatelyby> replying to this e-mail and delete the message from your mailbox. > Information contained in this message that does not relate to thebusiness> of SEAKR is neither endorsed by nor attributable to SEAKR.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
> > Deleted the network card and re-added it, and it is still using IRQ 5and> still showing the same behavior.Yes, it will always follow the xenpci adapter. I''m not sure how you can make it change... maybe try deleting the xenpci device after booting without GPLPV in your boot.ini. Actually... maybe those IRQ''s also depend on acpi=1 too? I can''t remember. If that''s not already =1 then maybe try setting that? In your previous email you mentioned another machine that did have apic=1 that was exhibiting the same symptoms. Is it definitely not using IRQ 5? Thanks James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James, Yes, acpi is enabled on both these machines. I think the other one may have had apic disabled at one time, though I can''t be sure about that. I''ve tried removing the XEN PCI driver after booting without GPLPV, but it comes back at IRQ 5. -Nick>>> "James Harper" <james.harper@bendigoit.com.au> 2008/11/10 17:24 >>> > > Deleted the network card and re-added it, and it is still using IRQ 5and> still showing the same behavior.Yes, it will always follow the xenpci adapter. I''m not sure how you can make it change... maybe try deleting the xenpci device after booting without GPLPV in your boot.ini. Actually... maybe those IRQ''s also depend on acpi=1 too? I can''t remember. If that''s not already =1 then maybe try setting that? In your previous email you mentioned another machine that did have apic=1 that was exhibiting the same symptoms. Is it definitely not using IRQ 5? 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
In ''Device Manager'', under computer, does it show ''ACPI Multiprocessor PC'' or something that mentions the word ''ACPI''? Maybe ACPI doesn''t install if acpi != 1... James> -----Original Message----- > From: Nick Couchman [mailto:Nick.Couchman@seakr.com] > Sent: Tuesday, 11 November 2008 11:35 > To: James Harper; xen-users@lists.xensource.com > Subject: RE: [Xen-users] GPL PV Intermitent Network Problems > > James, > Yes, acpi is enabled on both these machines. I think the other onemay> have had apic disabled at one time, though I can''t be sure about that. > I''ve tried removing the XEN PCI driver after booting without GPLPV,but it> comes back at IRQ 5. > > -Nick > > >>> "James Harper" <james.harper@bendigoit.com.au> 2008/11/10 17:24 >>> > > > > Deleted the network card and re-added it, and it is still using IRQ5> and > > still showing the same behavior. > > Yes, it will always follow the xenpci adapter. I''m not sure how youcan> make it change... maybe try deleting the xenpci device after booting > without GPLPV in your boot.ini. > > Actually... maybe those IRQ''s also depend on acpi=1 too? I can''t > remember. If that''s not already =1 then maybe try setting that? > > In your previous email you mentioned another machine that did have > apic=1 that was exhibiting the same symptoms. Is it definitely notusing> IRQ 5? > > Thanks > > James > > > > > ________________________________ > > This e-mail may contain confidential and privileged material for thesole> 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 theintended> 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 immediatelyby> replying to this e-mail and delete the message from your mailbox. > Information contained in this message that does not relate to thebusiness> 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
Device Manager -> Computer shows "Advanced Configuration and Power Interfaces (ACPI) PC." I''m pretty sure that I''ve never had ACPI disabled - just apic at some point or another. -Nick>>> "James Harper" <james.harper@bendigoit.com.au> 2008/11/10 17:50 >>>In ''Device Manager'', under computer, does it show ''ACPI Multiprocessor PC'' or something that mentions the word ''ACPI''? Maybe ACPI doesn''t install if acpi != 1... James> -----Original Message----- > From: Nick Couchman [mailto:Nick.Couchman@seakr.com] > Sent: Tuesday, 11 November 2008 11:35 > To: James Harper; xen-users@lists.xensource.com > Subject: RE: [Xen-users] GPL PV Intermitent Network Problems > > James, > Yes, acpi is enabled on both these machines. I think the other onemay> have had apic disabled at one time, though I can''t be sure about that. > I''ve tried removing the XEN PCI driver after booting without GPLPV,but it> comes back at IRQ 5. > > -Nick > > >>> "James Harper" <james.harper@bendigoit.com.au> 2008/11/10 17:24 >>> > > > > Deleted the network card and re-added it, and it is still using IRQ5> and > > still showing the same behavior. > > Yes, it will always follow the xenpci adapter. I''m not sure how youcan> make it change... maybe try deleting the xenpci device after booting > without GPLPV in your boot.ini. > > Actually... maybe those IRQ''s also depend on acpi=1 too? I can''t > remember. If that''s not already =1 then maybe try setting that? > > In your previous email you mentioned another machine that did have > apic=1 that was exhibiting the same symptoms. Is it definitely notusing> IRQ 5? > > Thanks > > James > > > > > ________________________________ > > This e-mail may contain confidential and privileged material for thesole> 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 theintended> 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 immediatelyby> replying to this e-mail and delete the message from your mailbox. > Information contained in this message that does not relate to thebusiness> of SEAKR is neither endorsed by nor attributable to SEAKR.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
Nick, I have built a xenpci.sys that will tell Windows not to give it an IRQ under 16. Other than testing that it doesn''t crash I haven''t given it any other testing. You can download it at: http://www.meadowcourt.org/downloads/xenpci.sys.no_irq_under_16.xp.bin rename the downloaded file to xenpci.sys and copy it to c:\windows\system32\drivers, then reboot. I also have a windows 2003 version there. If, for some reason, windows won''t assign an irq > 16 to it then a boot with /GPLPV will probably fail (bug check 0x7b), but you should still be able to reboot without /GPLPV. Let me know how it goes. If it boots, assigns an irq > 16, and your stability problems go away, then I''ll keep the fix in there. Thanks James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks, James - I''ll give it a shot today and see if I can make it work. I''m guessing there''s some entry somewhere in the Windows registry that allows Windows to "remember" hardware it''s already seen and assign the same resources to that hardware if it sees it again. Cleaning this entry out would probably work, but I haven''t been able to find exactly what entry and where it is. Also, on the Resources tab of the Xen drivers - do you control whether the resources can be modified or not, or is that up to Windows? Many drivers will let you set a manual resource configuration, like changing the IRQ to something else, but it seems like some of them won''t let you modify the settings at all. I know, I know, manually assigning resources isn''t the greatest idea - I should leave it up to the O/S to device - but it seems like something that may provide a way around this situation without the driver rewrite. Anyway, thanks, again for the fix - I''ll give it a try here in a while and let you know. -Nick>>> "James Harper" <james.harper@bendigoit.com.au> 2008/11/11 03:29 >>>Nick, I have built a xenpci.sys that will tell Windows not to give it an IRQ under 16. Other than testing that it doesn''t crash I haven''t given it any other testing. You can download it at: http://www.meadowcourt.org/downloads/xenpci.sys.no_irq_under_16.xp.bin rename the downloaded file to xenpci.sys and copy it to c:\windows\system32\drivers, then reboot. I also have a windows 2003 version there. If, for some reason, windows won''t assign an irq > 16 to it then a boot with /GPLPV will probably fail (bug check 0x7b), but you should still be able to reboot without /GPLPV. Let me know how it goes. If it boots, assigns an irq > 16, and your stability problems go away, then I''ll keep the fix in there. 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
Hmmm...I seem to be getting that 0x7B inaccessible boot device BSOD. Also haven''t had any luck figuring out where Windows stores it''s IRQ mappings... -Nick -----Original Message----- To: Nick Couchman <Nick.Couchman@seakr.com>, xen-users@lists.xensource.com Subject: RE: [Xen-users] GPL PV Intermitent Network Problems Date: Tue, 11 Nov 2008 21:29:23 +1100 Nick, I have built a xenpci.sys that will tell Windows not to give it an IRQ under 16. Other than testing that it doesn''t crash I haven''t given it any other testing. You can download it at: http://www.meadowcourt.org/downloads/xenpci.sys.no_irq_under_16.xp.bin rename the downloaded file to xenpci.sys and copy it to c:\windows\system32\drivers, then reboot. I also have a windows 2003 version there. If, for some reason, windows won''t assign an irq > 16 to it then a boot with /GPLPV will probably fail (bug check 0x7b), but you should still be able to reboot without /GPLPV. Let me know how it goes. If it boots, assigns an irq > 16, and your stability problems go away, then I''ll keep the fix in there. 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