I''m using W2K2 32bit on a 3.2.1 Lenny-amd64 host. While the pv disk driver works as expected, I encounter problems with the network driver. I tried several installation scenarios, all with the same result. My test looks like this: I install gplpv, but without letting the networking driver install. After reboot I RTL8139 ist still active and working, and gplpv devices manage the disks. Then I click "update driver" on the pv net device, and after it has been enabled I reboot. After reboot, the new LAN device is configured for DHCP, which isn''t good for me so I assign IP address, gw and DNS. When clicking OK, I''m warned about a duplicate IP address (from the dormant RTL8139, as expected). I accept the duplicity and then the taskbar interface icon as well as the status dialog shows "aquiring network address" for ever, the NIC properties dialog stops to respond, the interface won''t come up. After rebooting the VM another time, network seems to work correctly. Is gplpv supposed to work like that? I wonder if the XP fix applies to 2003 as well, since I''ve never seen driver differences between XP and 2003. Regards, Andreas _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> After reboot, the new LAN device is configured for DHCP, which isn''t> good for me so I assign IP address, gw and DNS. When clicking OK, I''m > warned about a duplicate IP address (from the dormant RTL8139, as > expected). I accept the duplicity and then the taskbar interface icon > as well as the status dialog shows "aquiring network address" for ever, > the NIC properties dialog stops to respond, the interface won''t come up. > After rebooting the VM another time, network seems to work correctly. > Is gplpv supposed to work like that? I wonder if the XP fix applies to This has nothing to do with GPLPV. Just Windows that doesn''t like two network devices configured with the same static IP Address, even when disabled. I run into the same trouble, but on reboot windows even didn''t accept the address for the GPLPV device and came up without working network, that killed a Terminalserver Install for me. So do the following: Reboot with "nogplpv" and switch the RTL device to "DHCP", then reboot with gplpv and assign the static address to the xennet device. Otherwise you always will run into deep trouble. Sincerly, Klaus _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > > After reboot, the new LAN device is configured for DHCP, whichisn''t> > good for me so I assign IP address, gw and DNS. When clicking OK,I''m> > warned about a duplicate IP address (from the dormant RTL8139, as > > expected). I accept the duplicity and then the taskbar interfaceicon> > as well as the status dialog shows "aquiring network address" forever,> > the NIC properties dialog stops to respond, the interface won''tcome up.> > After rebooting the VM another time, network seems to workcorrectly.> > > Is gplpv supposed to work like that? I wonder if the XP fix appliesto> > This has nothing to do with GPLPV. Just Windows that doesn''t like two > network devices configured with the same static IP Address, even when > disabled. > > I run into the same trouble, but on reboot windows even didn''t accept > the address for the GPLPV device and came up without working network, > that killed a Terminalserver Install for me. > > So do the following: > > Reboot with "nogplpv" and switch the RTL device to "DHCP", then reboot > with gplpv and assign the static address to the xennet device.Otherwise> you always will run into deep trouble. >I haven''t had any such problems on any servers I''ve installed GPLPV on. When GPLPV is active, the qemu adapter doesn''t exist as far as the windows TCP/IP driver is concerned. In the bin directory there is actually a ''copyconfig'' tool which you can run just after install (before reboot) or if you boot with /nogplpv. That will copy the network config from the qemu adapter to the pv adapter, which is very useful if the machine is a domain controller (_very_ slow to boot with an unconfigured network adapter) or if it just has lots of IP addresses (our web server has 30 or so). James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James Harper wrote:> > > I haven''t had any such problems on any servers I''ve installed GPLPV on. > When GPLPV is active, the qemu adapter doesn''t exist as far as the > windows TCP/IP driver is concerned. In the bin directory there is > actually a ''copyconfig'' tool which you can run just after install > (before reboot) or if you boot with /nogplpv. That will copy the network > config from the qemu adapter to the pv adapter, which is very useful if > the machine is a domain controller (_very_ slow to boot with an > unconfigured network adapter) or if it just has lots of IP addresses > (our web server has 30 or so). >Yeah, Win servers are really unwilling without a network. The MS Loopback adapter does help in this cases, as it does in every *ix. But my point is that the property dialog hangs when reconfiguring from DHCP to static manually (this can traditionally take quite a while, but not THAT long). I had trouble using copyconfig, so the cause might be the same. This happens on a VM migrated from a physical machine. Before installing gplpv, I removed all disks and lan drivers. So maybe there''s some cornercase in the drivers triggered when changing ip addressing. Regards, Andreas _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> James Harper wrote: > > > > > > I haven''t had any such problems on any servers I''ve installed GPLPVon.> > When GPLPV is active, the qemu adapter doesn''t exist as far as the > > windows TCP/IP driver is concerned. In the bin directory there is > > actually a ''copyconfig'' tool which you can run just after install > > (before reboot) or if you boot with /nogplpv. That will copy thenetwork> > config from the qemu adapter to the pv adapter, which is very usefulif> > the machine is a domain controller (_very_ slow to boot with an > > unconfigured network adapter) or if it just has lots of IP addresses > > (our web server has 30 or so). > > > > Yeah, Win servers are really unwilling without a network. The MS > Loopback adapter does help in this cases, as it does in every *ix. > But my point is that the property dialog hangs when reconfiguring from > DHCP to static manually (this can traditionally take quite a while,but> not THAT long). I had trouble using copyconfig, so the cause might be > the same. > This happens on a VM migrated from a physical machine. Beforeinstalling> gplpv, I removed all disks and lan drivers. > > So maybe there''s some cornercase in the drivers triggered whenchanging> ip addressing. >In a previous (unreleased) version there was a problem with the device stopping and starting - it would occasionally fail to stop the network adapter because it thought there were packets still to be sent or something. I thought I''d fixed that problem but it was occasional enough that it was hard to be sure that it was really fixed. I haven''t seen it since though. Is it happening every time? Copyconfig only mucks around in the registry. It doesn''t stop or start any adapters. It has to be run with the qemu device present though I think. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James Harper wrote:> > In a previous (unreleased) version there was a problem with the device > stopping and starting - it would occasionally fail to stop the network > adapter because it thought there were packets still to be sent or > something. I thought I''d fixed that problem but it was occasional enough > that it was hard to be sure that it was really fixed. I haven''t seen it > since though. > > Is it happening every time? >I do have a test VM that shows this when adding the gpvl net driver and configuring it for the first time to static ip addresses, after that the property dialog seems to work normal. I started installing gplpv-net manually when I encountered this freeze problem, and IIRC the problem was persistent when using the standard install, but my memory might trick me. I guess the device is stopped and started when changing from DHCP to static, so there still might be an issue with presumed stuck packets. Regards, Andreas _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users