netz-haut - stephan seitz
2008-Jul-21 10:43 UTC
[Xen-users] Xen GPL PV, W2k3 SBS, Xen Net driver
Hi, I''m currently trying to boot with 0.9.11-pre9 on a snapshot of a completely installed W2k3 SBS (dhcp server, exchange, etc...) After booting /gplpv, the system stalls with "Network connections are being prepared." (loose translation ;) ) I assume there are some essentials bound to the (ioemu) Realtek NICs. My question is, are there some switches available to use the gpl pv drivers in conjunction with the emulated Realtek NICs ? Thanks in advance. cheers, Stephan -- Stephan Seitz Senior System Administrator *netz-haut* e.K. multimediale kommunikation zweierweg 22 97074 würzburg fon: +49 931 2876247 fax: +49 931 2876248 web: www.netz-haut.de <http://www.netz-haut.de/> registriergericht: amtsgericht würzburg, hra 5054 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Hi, > > I''m currently trying to boot with 0.9.11-pre9 on a snapshot of a > completely installed W2k3 SBS (dhcp server, exchange, etc...) > > After booting /gplpv, the system stalls with "Network connections are > being prepared." (loose translation ;) ) > > I assume there are some essentials bound to the (ioemu) Realtek NICs. > > My question is, are there some switches available to use the gpl pv > drivers in conjunction with the emulated Realtek NICs ? >I posted some info on how to do this just recently (today?). It might have been on the -dev list though. It is easiest just to not install the xennet drivers in the first place. This problem shouldn''t happen though... can you tell me as much as you can about your Dom0 and hypervisor (eg what dist, how did you install xen, etc) as I have not been able to reproduce the problem yet... James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
netz-haut - stephan seitz
2008-Jul-21 14:08 UTC
RE: [Xen-users] Xen GPL PV, W2k3 SBS, Xen Net driver
> I posted some info on how to do this just recently (today?). It might > have been on the -dev list though. It is easiest just to not install the > xennet drivers in the first place. > > This problem shouldn''t happen though... can you tell me as much as you > can about your Dom0 and hypervisor (eg what dist, how did you install > xen, etc) as I have not been able to reproduce the problem yet... > > JamesHi James, i''ll look for the posting you''ve mentioned. Here a short overview of the system: The Hypervisor used is: (XEN) Xen version 3.2.1-rc1-pre (buildd@buildd) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) Fri Apr 11 01:13:51 UTC 2008 (I know, RC1 pre ... but otherwise _really_ rock solid) root@franconia:~# xm info host : franconia release : 2.6.18.8-xen version : #3 SMP Mon Apr 14 20:36:16 CEST 2008 machine : x86_64 nr_cpus : 2 nr_nodes : 1 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 2660 hw_caps : bfebfbff:20100800:00000000:00000140:0000e3fd:00000000:00000001 total_memory : 8189 free_memory : 5 max_free_memory : 2416 max_para_memory : 2412 max_hvm_memory : 2398 node_to_cpu : node0:0-1 xen_major : 3 xen_minor : 2 xen_extra : .1-rc1-pre xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7) cc_compile_by : buildd cc_compile_domain : buildd cc_compile_date : Fri Apr 11 01:13:51 UTC 2008 xend_config_format : 4 The particular domU is a Windows 2003 SBS 32bit w/ all Servicepacks installed. root@franconia:~# cat /etc/xen/exchangesbs.hvm | grep -v \# | grep -v -e ''^$'' name = ''exchangesbs.hvm'' kernel = ''/usr/lib/xen-ioemu-3.2/boot/hvmloader'' builder = ''hvm'' device_model = ''/usr/lib/xen-ioemu-3.2/bin/qemu-dm'' memory = 2048 shadow_memory = 8 vif = [ ''mac=00:16:3e:14:A2:24,type=ioemu,bridge=eth1'', ''mac=00:16:3e:15:A2:25,type=ioemu,bridge=dummy0'' ] disk = [ ''phy:/dev/vg0/exchange-sbs-disk-c,xvda,w'', ''phy:/dev/vg0/exchange-sbs-disk-d,xvdb,w'', ''phy:/dev/vg0/exchange-disk-e,xvdc,w'' ] boot = ''cd'' localtime=''0'' acpi=1 apic=1 pae=1 vcpus=1 usb=1 usbdevice=''tablet'' vnc=1 vncunused=1 keymap=''de'' vncviewer=0 on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' I currently don''t know which of the qemu-dm-*.log files were written with /gplpv enabled. I don''t expect any differences but will peek into this after business hours. Another domU running a Windows 2003 Server w/ all available Servicepacks is running without any problems. Config is similar: name = ''blackberry.hvm'' kernel = ''/usr/lib/xen-ioemu-3.2/boot/hvmloader'' builder = ''hvm'' device_model = ''/usr/lib/xen-ioemu-3.2/bin/qemu-dm'' memory = 1536 shadow_memory = 8 vif = [ ''mac=00:16:3e:14:82:25,type=ioemu,bridge=eth1'' ] disk = [ ''phy:/dev/vg0/blackberry-disk-c,xvda,w'' ] boot = ''cd'' localtime=''0'' acpi=1 apic=1 pae=1 vcpus=1 usb=1 usbdevice=''tablet'' vnc=1 vncunused=1 keymap=''de'' vncviewer=0 on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' You might note that there''s a bridge bound to dummy0, this is correct. I don''t think this causes the problems as the other HVM domU formerly used this bridge also without a problem. cheers, Stephan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Markus Plischke
2008-Jul-21 14:47 UTC
RE: [Xen-users] Xen GPL PV, W2k3 SBS, Xen Net driver
I had the same problem when I tryed to install the GPLPV Drivers on a production Windows Server 2003 R2 with Exchange 2007 installed. If I boot without GPLPV the network is fully functional but with GPLPV the network does not work because it is not configured and I cant configure it, I cant open the Network Configuration. My Workarround for this is to install a new Exchange, install Windows Server 2003, the GPLPV Drivers, configure it and then install ADS and Exchange. Now the Server runs with and withount the GPLPV boot flag (with GPLPV the performance is excellent). If there is another Solution that would be great, I cant find the post from James. The main problem is ADS/Exchange that blocks all activities if there is no network configuration I think. Also with DHCP I have the same problem. Markus -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of netz-haut - stephan seitz Sent: Monday, July 21, 2008 4:09 PM To: James Harper Cc: xen-users@lists.xensource.com Subject: RE: [Xen-users] Xen GPL PV, W2k3 SBS, Xen Net driver> I posted some info on how to do this just recently (today?). It might > have been on the -dev list though. It is easiest just to not install > the xennet drivers in the first place. > > This problem shouldn''t happen though... can you tell me as much as you > can about your Dom0 and hypervisor (eg what dist, how did you install > xen, etc) as I have not been able to reproduce the problem yet... > > JamesHi James, i''ll look for the posting you''ve mentioned. Here a short overview of the system: The Hypervisor used is: (XEN) Xen version 3.2.1-rc1-pre (buildd@buildd) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) Fri Apr 11 01:13:51 UTC 2008 (I know, RC1 pre ... but otherwise _really_ rock solid) root@franconia:~# xm info host : franconia release : 2.6.18.8-xen version : #3 SMP Mon Apr 14 20:36:16 CEST 2008 machine : x86_64 nr_cpus : 2 nr_nodes : 1 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 2660 hw_caps : bfebfbff:20100800:00000000:00000140:0000e3fd:00000000:00000001 total_memory : 8189 free_memory : 5 max_free_memory : 2416 max_para_memory : 2412 max_hvm_memory : 2398 node_to_cpu : node0:0-1 xen_major : 3 xen_minor : 2 xen_extra : .1-rc1-pre xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7) cc_compile_by : buildd cc_compile_domain : buildd cc_compile_date : Fri Apr 11 01:13:51 UTC 2008 xend_config_format : 4 The particular domU is a Windows 2003 SBS 32bit w/ all Servicepacks installed. root@franconia:~# cat /etc/xen/exchangesbs.hvm | grep -v \# | grep -v -e ''^$'' name = ''exchangesbs.hvm'' kernel = ''/usr/lib/xen-ioemu-3.2/boot/hvmloader'' builder = ''hvm'' device_model = ''/usr/lib/xen-ioemu-3.2/bin/qemu-dm'' memory = 2048 shadow_memory = 8 vif = [ ''mac=00:16:3e:14:A2:24,type=ioemu,bridge=eth1'', ''mac=00:16:3e:15:A2:25,type=ioemu,bridge=dummy0'' ] disk = [ ''phy:/dev/vg0/exchange-sbs-disk-c,xvda,w'', ''phy:/dev/vg0/exchange-sbs-disk-d,xvdb,w'', ''phy:/dev/vg0/exchange-disk-e,xvdc,w'' ] boot = ''cd'' localtime=''0'' acpi=1 apic=1 pae=1 vcpus=1 usb=1 usbdevice=''tablet'' vnc=1 vncunused=1 keymap=''de'' vncviewer=0 on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' I currently don''t know which of the qemu-dm-*.log files were written with /gplpv enabled. I don''t expect any differences but will peek into this after business hours. Another domU running a Windows 2003 Server w/ all available Servicepacks is running without any problems. Config is similar: name = ''blackberry.hvm'' kernel = ''/usr/lib/xen-ioemu-3.2/boot/hvmloader'' builder = ''hvm'' device_model = ''/usr/lib/xen-ioemu-3.2/bin/qemu-dm'' memory = 1536 shadow_memory = 8 vif = [ ''mac=00:16:3e:14:82:25,type=ioemu,bridge=eth1'' ] disk = [ ''phy:/dev/vg0/blackberry-disk-c,xvda,w'' ] boot = ''cd'' localtime=''0'' acpi=1 apic=1 pae=1 vcpus=1 usb=1 usbdevice=''tablet'' vnc=1 vncunused=1 keymap=''de'' vncviewer=0 on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' You might note that there''s a bridge bound to dummy0, this is correct. I don''t think this causes the problems as the other HVM domU formerly used this bridge also without a problem. cheers, Stephan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> My Workarround for this is to install a new Exchange, install Windows > Server 2003, the GPLPV Drivers, configure it and then install ADS and > Exchange. Now the Server runs with and withount the GPLPV boot flag(with> GPLPV the performance is excellent).One of the things we do is to perform test restores for customer machines, to ensure that their backups will actually do the job in the event that they are needed. Xen is great for this - easy to set up a new domain and then tear it down when the job is done! When doing the above, one thing I have found though is with servers with AD etc (mostly SBS2K3), the boot does appear to hang at the ''Preparing network connections'' screen, sometimes for up to a few hours. This is just with the qemu drivers but the cause would be the same. Have you waited that long? If possible, can you please give it a go? I wonder if you could shortcut it by booting in one of safe mode, safe mode with networking, or active directory recovery mode (or whatever it''s called)... Another thing I have done before is to make xenpci and xenscsi installable from the ''Text Mode Setup'' (the blue screen you first get when booting from the Windows install CD), via the ''F6 to install OEM drivers''. This is done so that the SCSI passthrough is usable so Backup Exec cab access the tape drive from the IDR Lice CD. It may be possible to install all the drivers this way, although I have never tested it before...> > If there is another Solution that would be great, I cant find the post > from James. >The subject was ''GPLPV but network problem'' and it was posted to the xen-users list on Sunday (not Monday as I previously thought). The text is below, but please have a read of the thread in its original context first, just in case the below instructions aren''t complete: 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
Nathan Eisenberg
2008-Jul-22 01:55 UTC
RE: [Xen-users] Xen GPL PV, W2k3 SBS, Xen Net driver
This is at the risk of getting offtopic, however... When you''re doing these restores, you''re restoring the full system state, right? Typically, what happens is since the ID of the NIC in the restored enviroment is different from the original NIC, the IP address information is not restored to that device - however, there are still some traces of the hardware in the registry (it''s a ghost device). What is essentially happening here is waiting for the domain controller to ''give up'' on replicating with its peers - this can take quite a while. My workaround for this issue was to actually perform the restore in this way: Install server 2003, patch to current. Restore from system state backup. Shutdown. Boot from server 2003 media, perform repair install. Patch to current. The end result is a domain controller that is more properly configured, and not in that weird and nonproduction state that they often end up in. Even here, the resulting domain controller isn''t production-stock - you should still build a fresh install, make it a DC, transfer the roles, and then retire and rebuild the old DC - but at least it doesn''t take forever to boot. Even with the repair and repatch, I''ve found it saves time - especially in a DomU where you''re booting off of an ISO. :) Anyways, just my experience, hope it helps! Nathan Eisenberg -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of James Harper Sent: Monday, July 21, 2008 6:45 PM To: Markus Plischke; netz-haut - stephan seitz Cc: xen-users@lists.xensource.com Subject: RE: [Xen-users] Xen GPL PV, W2k3 SBS, Xen Net driver> My Workarround for this is to install a new Exchange, install Windows > Server 2003, the GPLPV Drivers, configure it and then install ADS and > Exchange. Now the Server runs with and withount the GPLPV boot flag(with> GPLPV the performance is excellent).One of the things we do is to perform test restores for customer machines, to ensure that their backups will actually do the job in the event that they are needed. Xen is great for this - easy to set up a new domain and then tear it down when the job is done! When doing the above, one thing I have found though is with servers with AD etc (mostly SBS2K3), the boot does appear to hang at the ''Preparing network connections'' screen, sometimes for up to a few hours. This is just with the qemu drivers but the cause would be the same. Have you waited that long? If possible, can you please give it a go? I wonder if you could shortcut it by booting in one of safe mode, safe mode with networking, or active directory recovery mode (or whatever it''s called)... Another thing I have done before is to make xenpci and xenscsi installable from the ''Text Mode Setup'' (the blue screen you first get when booting from the Windows install CD), via the ''F6 to install OEM drivers''. This is done so that the SCSI passthrough is usable so Backup Exec cab access the tape drive from the IDR Lice CD. It may be possible to install all the drivers this way, although I have never tested it before...> > If there is another Solution that would be great, I cant find the post > from James. >The subject was ''GPLPV but network problem'' and it was posted to the xen-users list on Sunday (not Monday as I previously thought). The text is below, but please have a read of the thread in its original context first, just in case the below instructions aren''t complete: 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 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > This is at the risk of getting offtopic, however... > > When you''re doing these restores, you''re restoring the full systemstate,> right? Typically, what happens is since the ID of the NIC in therestored> enviroment is different from the original NIC, the IP addressinformation> is not restored to that device - however, there are still some tracesof> the hardware in the registry (it''s a ghost device).Corrent. It''s not really a problem though, I just use netsh to copy the config across to the ''new'' adapter. I understand why the problem occurs and was just pointing out to the original poster that when booting with /gplpv he is introducing a similar situation - old network adapter disappears and new one appears in it''s place. I suspect that when he rebooted, the system hadn''t really hung it was just taking a long time to boot. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Markus Plischke
2008-Jul-22 07:19 UTC
RE: [Xen-users] Xen GPL PV, W2k3 SBS, Xen Net driver
If i start the production Exchange 2007 Server with /gplpv the "Preparing Network Connections" Dialog takes approxymattly one hour, then the System boots correct and I can login. The login takes a few minutes, but then it is not possible to open the network configuration, when I click to open this dialog,nothing happen within two hours. If I try to configure the network over the Powershell I enter the configure command and wait two hours, noting happened. I cant wait longer as a few hours because I can shutdown the system only in the early morning hours between 2 and 5. -----Original Message----- From: James Harper [mailto:james.harper@bendigoit.com.au] Sent: Tuesday, July 22, 2008 3:45 AM To: Markus Plischke; netz-haut - stephan seitz Cc: xen-users@lists.xensource.com Subject: RE: [Xen-users] Xen GPL PV, W2k3 SBS, Xen Net driver> My Workarround for this is to install a new Exchange, install Windows > Server 2003, the GPLPV Drivers, configure it and then install ADS and > Exchange. Now the Server runs with and withount the GPLPV boot flag(with> GPLPV the performance is excellent).One of the things we do is to perform test restores for customer machines, to ensure that their backups will actually do the job in the event that they are needed. Xen is great for this - easy to set up a new domain and then tear it down when the job is done! When doing the above, one thing I have found though is with servers with AD etc (mostly SBS2K3), the boot does appear to hang at the ''Preparing network connections'' screen, sometimes for up to a few hours. This is just with the qemu drivers but the cause would be the same. Have you waited that long? If possible, can you please give it a go? I wonder if you could shortcut it by booting in one of safe mode, safe mode with networking, or active directory recovery mode (or whatever it''s called)... Another thing I have done before is to make xenpci and xenscsi installable from the ''Text Mode Setup'' (the blue screen you first get when booting from the Windows install CD), via the ''F6 to install OEM drivers''. This is done so that the SCSI passthrough is usable so Backup Exec cab access the tape drive from the IDR Lice CD. It may be possible to install all the drivers this way, although I have never tested it before...> > If there is another Solution that would be great, I cant find the post > from James. >The subject was ''GPLPV but network problem'' and it was posted to the xen-users list on Sunday (not Monday as I previously thought). The text is below, but please have a read of the thread in its original context first, just in case the below instructions aren''t complete: 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
> > If i start the production Exchange 2007 Server with /gplpv the"Preparing> Network Connections" Dialog takes approxymattly one hour, then theSystem> boots correct and I can login. The login takes a few minutes, but thenit> is not possible to open the network configuration, when I click toopen> this dialog,nothing happen within two hours.I hope you''ve backed up your production system first :) Thanks for testing this. The "Preparing Network Connections" delay is expected, as Windows seems to do this whenever network cards are fiddled with. The delay (or hang?) in opening the network configuration is not expected though... Could you try and change config using ''netsh''? It''s a command line tool, and if you aren''t familiar with it it might be a bit baffling... I wonder how hard it would be to copy the registry config across from the card that is being replaced, eg look through the registry and find the config for the qemu card with the same MAC address as the gplpv card... that might break more things than it fixes though. I''ll try and find time to test the above situation but it will involve setting up active directory which is more involved than just a simple setup. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
netz-haut - stephan seitz
2008-Jul-22 07:29 UTC
RE: [Xen-users] Xen GPL PV, W2k3 SBS, Xen Net driver
Hi, I had also no luck trying the same. After todays office hours, I''ll try to add one ore two additional nics. Maybe I''ll be able to switch over to the new nics... Report follows ;) Am Dienstag, den 22.07.2008, 09:21 +0200 schrieb James Harper:> > > > If i start the production Exchange 2007 Server with /gplpv the > "Preparing > > Network Connections" Dialog takes approxymattly one hour, then the > System > > boots correct and I can login. The login takes a few minutes, but > then > it > > is not possible to open the network configuration, when I click to > open > > this dialog,nothing happen within two hours. > > I hope you''ve backed up your production system first :) > > Thanks for testing this. The "Preparing Network Connections" delay is > expected, as Windows seems to do this whenever network cards are > fiddled > with. The delay (or hang?) in opening the network configuration is > not > expected though... > > Could you try and change config using ''netsh''? It''s a command line > tool, > and if you aren''t familiar with it it might be a bit baffling... > > I wonder how hard it would be to copy the registry config across from > the card that is being replaced, eg look through the registry and > find > the config for the qemu card with the same MAC address as the gplpv > card... that might break more things than it fixes though. > > I''ll try and find time to test the above situation but it will > involve > setting up active directory which is more involved than just a simple > setup. > > James > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- Stephan Seitz Senior System Administrator *netz-haut* e.K. multimediale kommunikation zweierweg 22 97074 würzburg fon: +49 931 2876247 fax: +49 931 2876248 web: www.netz-haut.de <http://www.netz-haut.de/> registriergericht: amtsgericht würzburg, hra 5054 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Markus Plischke
2008-Jul-22 07:30 UTC
RE: [Xen-users] Xen GPL PV, W2k3 SBS, Xen Net driver
I always backup a machine before make important changes on the Setup. If I boot the described machine without /gplpv, the system runs fine. Next week all accounts are moved to another Server, this Exchange Server is empty and I can test all you want. -----Original Message----- From: James Harper [mailto:james.harper@bendigoit.com.au] Sent: Tuesday, July 22, 2008 9:22 AM To: Markus Plischke Cc: xen-users@lists.xensource.com Subject: RE: [Xen-users] Xen GPL PV, W2k3 SBS, Xen Net driver> > If i start the production Exchange 2007 Server with /gplpv the"Preparing> Network Connections" Dialog takes approxymattly one hour, then theSystem> boots correct and I can login. The login takes a few minutes, but thenit> is not possible to open the network configuration, when I click toopen> this dialog,nothing happen within two hours.I hope you''ve backed up your production system first :) Thanks for testing this. The "Preparing Network Connections" delay is expected, as Windows seems to do this whenever network cards are fiddled with. The delay (or hang?) in opening the network configuration is not expected though... Could you try and change config using ''netsh''? It''s a command line tool, and if you aren''t familiar with it it might be a bit baffling... I wonder how hard it would be to copy the registry config across from the card that is being replaced, eg look through the registry and find the config for the qemu card with the same MAC address as the gplpv card... that might break more things than it fixes though. I''ll try and find time to test the above situation but it will involve setting up active directory which is more involved than just a simple setup. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > > I have experienced this same phenomenon with my SBS server. The slow > login looks like the explorer.exe process hanging. I can press > <ctrl><alt><del> and run taskmgr which I can then use to get to a > command prompt. > > Could you try and change config using ''netsh''? It''s a command linetool,> > and if you aren''t familiar with it it might be a bit baffling... > > > Running netsh from the command prompt hung. I''m sure it would''ve > completed eventually but I gave up on it.Ah. That kind of makes sense. Netsh uses the same backend api as the network manager. Are you able to try booting in one of the recovery/safe modes? James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James Harper wrote:>> I have experienced this same phenomenon with my SBS server. The slow >> login looks like the explorer.exe process hanging. I can press >> <ctrl><alt><del> and run taskmgr which I can then use to get to a >> command prompt. >> >>> Could you try and change config using ''netsh''? It''s a command line >>> > tool, > >>> and if you aren''t familiar with it it might be a bit baffling... >>> >>> >> Running netsh from the command prompt hung. I''m sure it would''ve >> completed eventually but I gave up on it. >> > > Ah. That kind of makes sense. Netsh uses the same backend api as the > network manager. > > Are you able to try booting in one of the recovery/safe modes? > > James > >I did a fresh install of 0.9.11-pre9. On first boot I went into Safe Mode with Networking support and selected the boot option with GPLPV. </downloads/Xen%20PV%20Drivers%200.9.11-pre9.exe>It took about 5mins "preparing network connections" before the login prompt was displayed but I got logged in to the desktop in the usual time. Once logged in I was able to give the adapter an address, reboot and every thing works as expected - normal boot up and login speed. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users