I''ve been trying to get the pv drivers running on a Win 2003 server install with 2 virtual nics and although the drivers install without error the hvm does not boot correctly afterwards, hangs at the windows splash screen, and xm top shows that the 2 vcpus allocated to the domain are pegged. This continues until the domain is destroyed. It can be booted in safe mode without networking, and if the xVMbus system device is disabled then the os will boot again in normal mode, but of course minus the nics... Has anyone else seen this problem? I''m using a Realtek Gig card (with rge driver) on the box if that''s of any help? Cheers, Alan -- This message posted from opensolaris.org
We haven''t seen that problem. Can you try disabling the network PV driver but leaving the xVMbus driver enabled? Alan Romeril wrote:> I''ve been trying to get the pv drivers running on a Win 2003 server install with 2 virtual nics and although the drivers install without error the hvm does not boot correctly afterwards, hangs at the windows splash screen, and xm top shows that the 2 vcpus allocated to the domain are pegged. This continues until the domain is destroyed. > It can be booted in safe mode without networking, and if the xVMbus system device is disabled then the os will boot again in normal mode, but of course minus the nics... > > Has anyone else seen this problem? I''m using a Realtek Gig card (with rge driver) on the box if that''s of any help? > > Cheers, > Alan-- ----------------------------------------------------- Russ Blaine | Solaris Kernel | russell.blaine@sun.com
On Thu, Oct 30, 2008 at 09:36:39AM -0700, Alan Romeril wrote:> I''ve been trying to get the pv drivers running on a Win 2003 server > install with 2 virtual nics and although the drivers install without > error the hvm does not boot correctly afterwards, hangs at the > windows splash screen, and xm top shows that the 2 vcpus allocated > to the domain are pegged. This continues until the domain is > destroyed. It can be booted in safe mode without networking, and if > the xVMbus system device is disabled then the os will boot again in > normal mode, but of course minus the nics... > > Has anyone else seen this problem? I''m using a Realtek Gig card > (with rge driver) on the box if that''s of any help?Could you try again with 1 vCPU? The drivers are not as well tested with multiple vCPUs.
Yes I can try that...
I''ve set the domain to 1 vcpu, it''s still running the
multiprocessor acpi HAL and have ran the installer as before. Again
it''s the same hang on booting, the VNC console shows the win2k3 boot
screen, the progress bar stops moving and the vcpu is pinned as below:-
xentop - 18:52:18 Xen 3.1.4-xvm
2 domains: 2 running, 0 blocked, 0 paused, 0 crashed, 0 dying, 0 shutdown
Mem: 7601468k total, 7577192k used, 24276k free CPUs: 4 @ 2307MHz
NAME STATE CPU(sec) CPU(%) MEM(k) MEM(%) MAXMEM(k) MAXMEM(%) VCPUS
NETS NETTX(k) NETRX(k) VBDS VBD_OO VBD_RD VBD_WR SSID
Domain-0 -----r 10831 5.7 6386688 84.0 no limit n/a 4
0 0 0 0 0 0 0 0
winpv1 -----r 85 100.0 1056636 13.9 1064960 14.0 1
2 0 0 1 0 0 0 0
Thank goodness for zfs rollback :)
--a
--
This message posted from opensolaris.org
After installing the drivers again, but before rebooting ipconfig /all shows the
interfaces with the description xVM Windows PV NIC, and I can ping other hosts
with them. Then after disabling the NIC devices in hardware manager and
rebooting I get the same hang as before.
I''m running an AMD Phenom processor:-
x86 (AuthenticAMD 100F22 family 16 model 2 step 2 clock 2307 MHz)
AMD Phenom(tm) 9600 Quad-Core Processor
I''ve also had pv b99 Solaris and pv Ubuntu 8.04.1 domains running on
this machine without problems.
Cheers,
Alan
--
This message posted from opensolaris.org
> I''ve been trying to get the pv drivers running on a > Win 2003 server install with 2 virtual nics and > although the drivers install without error the hvm > does not boot correctly afterwards, hangs at the > windows splash screen, and xm top shows that the 2 > vcpus allocated to the domain are pegged. This > continues until the domain is destroyed. > It can be booted in safe mode without networking, and > if the xVMbus system device is disabled then the os > will boot again in normal mode, but of course minus > the nics... > > Has anyone else seen this problem? I''m using a > Realtek Gig card (with rge driver) on the box if > that''s of any help? > > Cheers, > AlanI''ve had the same problem running Win2K3 with 2 vCPUs under nv97. The very first VM I installed the PV drivers on worked, but every other instance has failed with the same symptoms. That first instance still works though, and well. -- This message posted from opensolaris.org
That''s interesting, I had one domain working fine with 1 nic and the pv drivers, it was when I added a second that all the problems started. In the end I reinstalled that domain, with the same name and mac addresses and now I can''t get the pv drivers to work properly at all. -- This message posted from opensolaris.org
I was going crazy trying to figure out what I was doing wrong. I have not been able to install the PV drivers on any domain after that first one. -- This message posted from opensolaris.org
Okay well this still doesn''t seem to be working, I''m going to try an upgrade to b101 and see if that helps matters. Is there any debugging I can helpfully do? I''m under a tight timescale to get something working well for a set of projects and would like to see an xVM solution. Cheers, Alan -- This message posted from opensolaris.org
Still doesn''t work with b101, or moving the image to an x4250. -- This message posted from opensolaris.org
On Tue, Nov 04, 2008 at 03:34:42AM -0800, Alan Romeril wrote:> Still doesn''t work with b101, or moving the image to an x4250.Tried it with b101 and X4600M2 - no problems up to now (almost unusable with b98). To get a small impression, see: http://iws.cs.uni-magdeburg.de/~elkner/xVM/perfWin2008std/ http://iws.cs.uni-magdeburg.de/~elkner/xVM/perfWin2003sbs/ Regards, jel. -- Otto-von-Guericke University http://www.cs.uni-magdeburg.de/ Department of Computer Science Geb. 29 R 027, Universitaetsplatz 2 39106 Magdeburg, Germany Tel: +49 391 67 12768
Yes those numbers look very reasonable, I wonder what''s catching me out here. I''ve extracted the drivers from the msi and have got the xVMBus driver and the xVM PV NIC driver now. So it must be the disk driver that''s causing a problem. Did your domU''s boot.ini get changed in any way? Thanks, Alan -- This message posted from opensolaris.org
Ahhhha! Right I know I''ve been replying to my own posts rather a lot but I''ve managed to get this booting by removing the cdrom device class registry key from the xVMStorFlt.inf file and just installing the disk drive class support. The windows domain is seeing this bug http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6742696 and that must be causing the knock on problems. Well let''s see how it all goes. Cheers, Alan -- This message posted from opensolaris.org
However these drivers do not seem to work with Microsoft''s iscsi initiator. I get a very unhealthy blue screen when I connect to a target. Is this a known bug? Thanks, Alan -- This message posted from opensolaris.org
I''m trying to get Windows 2k3R2 installed. I created an image first
though mkfile and subsequently via qemu-img as suggest in the
documentation and invoked virt install as follows (b99):
# virt-install -n win2k3Server-1 --hvm -r 4096 --vnc \
> -f /files/vdsk/win2k3Server-1.img -s 32 \
> -c /files/images/windows/en_windows_server_2003_with_sp1_standard.iso
Starting install...
virDomainCreateLinux() failed POST operation failed: (xend.err ''Device
5632 (vbd) could not be connected. Backend device not found.'')
Domain installation may not have been
successful. If it was, you can restart your domain
by running ''virsh start win2k3Server-1''; otherwise, please
restart your installation.
Thu, 06 Nov 2008 13:22:17 ERROR virDomainCreateLinux() failed POST
operation failed: (xend.err ''Device 5632 (vbd) could not be connected.
Backend device not found.'')
Traceback (most recent call last):
File "/usr/bin/virt-install", line 511, in ?
main()
File "/usr/bin/virt-install", line 471, in main
dom = guest.start_install(conscb,progresscb)
File
"/export/builds/xvm_99///proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py",
line 889, in start_install File
"/export/builds/xvm_99///proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py",
line 910, in _do_install
File "libvirt.py", line 585, in createLinux
if ret is None:raise libvirtError(''virDomainCreateLinux()
failed'',
conn=self)
libvirtError: virDomainCreateLinux() failed POST operation failed:
(xend.err ''Device 5632 (vbd) could not be connected. Backend device not
found.'')
This seems to be related to bug #6742735
(http://bugs.opensolaris.org/bugdatabase/printableBug.do?bug_id=6742735)
which was fixed in b99, but I''m still seeing it -or- something like it.
I confirmed that see the code addition in vbd-default suggested in this
thread:
http://www.mail-archive.com/xen-discuss@opensolaris.org/msg03371.html.
I''m feeling a little stupid, any suggestions?
=Ron
Alan Romeril wrote:> I''ve been trying to get the pv drivers running on a Win 2003
server install with 2 virtual nics and although the drivers install without
error the hvm does not boot correctly afterwards, hangs at the windows splash
screen, and xm top shows that the 2 vcpus allocated to the domain are pegged.
This continues until the domain is destroyed.
> It can be booted in safe mode without networking, and if the xVMbus system
device is disabled then the os will boot again in normal mode, but of course
minus the nics...
>
> Has anyone else seen this problem? I''m using a Realtek Gig card
(with rge driver) on the box if that''s of any help?
>
> Cheers,
> Alan
>
Ronald J Mann wrote:> I''m trying to get Windows 2k3R2 installed. I created an image first > though mkfile and subsequently via qemu-img as suggest in the > documentation and invoked virt install as follows (b99): > > # virt-install -n win2k3Server-1 --hvm -r 4096 --vnc \ > > -f /files/vdsk/win2k3Server-1.img -s 32 \ > > -c /files/images/windows/en_windows_server_2003_with_sp1_standard.isoWhat build of Solaris? Try the following without the mkfile.. i.e. let vort-install create the file for you... Do this work? # virt-install -n win2k3Server-1 --hvm -r 4096 --vnc \ -f /files/vdsk/win2k3Server-1 -s 32 \ -c /files/images/windows/en_windows_server_2003_with_sp1_standard.iso also, verify # ls -lL /files/images/windows/en_windows_server_2003_with_sp1_standard.iso MRJ> > Starting install... > virDomainCreateLinux() failed POST operation failed: (xend.err ''Device > 5632 (vbd) could not be connected. Backend device not found.'') > Domain installation may not have been > successful. If it was, you can restart your domain > by running ''virsh start win2k3Server-1''; otherwise, please > restart your installation. > Thu, 06 Nov 2008 13:22:17 ERROR virDomainCreateLinux() failed POST > operation failed: (xend.err ''Device 5632 (vbd) could not be connected. > Backend device not found.'') > Traceback (most recent call last): > File "/usr/bin/virt-install", line 511, in ? > main() > File "/usr/bin/virt-install", line 471, in main > dom = guest.start_install(conscb,progresscb) > File > "/export/builds/xvm_99///proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py", > line 889, in start_install File > "/export/builds/xvm_99///proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py", > line 910, in _do_install > File "libvirt.py", line 585, in createLinux > if ret is None:raise libvirtError(''virDomainCreateLinux() failed'', > conn=self) > libvirtError: virDomainCreateLinux() failed POST operation failed: > (xend.err ''Device 5632 (vbd) could not be connected. Backend device not > found.'') > > This seems to be related to bug #6742735 > (http://bugs.opensolaris.org/bugdatabase/printableBug.do?bug_id=6742735) > which was fixed in b99, but I''m still seeing it -or- something like it. > I confirmed that see the code addition in vbd-default suggested in this > thread: > http://www.mail-archive.com/xen-discuss@opensolaris.org/msg03371.html. > I''m feeling a little stupid, any suggestions? > > =Ron> > > Alan Romeril wrote: >> I''ve been trying to get the pv drivers running on a Win 2003 server install with 2 virtual nics and although the drivers install without error the hvm does not boot correctly afterwards, hangs at the windows splash screen, and xm top shows that the 2 vcpus allocated to the domain are pegged. This continues until the domain is destroyed. >> It can be booted in safe mode without networking, and if the xVMbus system device is disabled then the os will boot again in normal mode, but of course minus the nics... >> >> Has anyone else seen this problem? I''m using a Realtek Gig card (with rge driver) on the box if that''s of any help? >> >> Cheers, >> Alan >> > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
On Thu, Nov 06, 2008 at 01:55:58PM -0500, Ronald J Mann wrote:> I''m trying to get Windows 2k3R2 installed. I created an image first > though mkfile and subsequently via qemu-img as suggest in the > documentation and invoked virt install as follows (b99): > > # virt-install -n win2k3Server-1 --hvm -r 4096 --vnc \ > > -f /files/vdsk/win2k3Server-1.img -s 32 \ > > -c /files/images/windows/en_windows_server_2003_with_sp1_standard.isoThe path is probably too long. Try it e.g. with -c /files/images/windows/sp1.iso Regards, jel. -- Otto-von-Guericke University http://www.cs.uni-magdeburg.de/ Department of Computer Science Geb. 29 R 027, Universitaetsplatz 2 39106 Magdeburg, Germany Tel: +49 391 67 12768
Bingo... give that man a cigar! Thanks! =Ron Jens Elkner wrote:> On Thu, Nov 06, 2008 at 01:55:58PM -0500, Ronald J Mann wrote: > >> I''m trying to get Windows 2k3R2 installed. I created an image first >> though mkfile and subsequently via qemu-img as suggest in the >> documentation and invoked virt install as follows (b99): >> >> # virt-install -n win2k3Server-1 --hvm -r 4096 --vnc \ >> > -f /files/vdsk/win2k3Server-1.img -s 32 \ >> > -c /files/images/windows/en_windows_server_2003_with_sp1_standard.iso >> > > The path is probably too long. Try it e.g. with > -c /files/images/windows/sp1.iso > > Regards, > jel. >
Alan Romeril wrote:> However these drivers do not seem to work with Microsoft''s iscsi > initiator. I get a very unhealthy blue screen when I connect to a > target. Is this a known bug?We haven''t tried the MSFT iscsi initiator, no. I''ll file a bug. Meanwhile, were you able to get past the problem you initially reported? Can you get your win2003 domain running with the CD device present? Thanks for all the info, Alan... - Russ ----------------------------------------------------- Russ Blaine | Solaris Kernel | russell.blaine@sun.com
Alan, I have filed 6770912 Guest additions for Windows (9.11) do not work with MSFT iscsi initiator for your iscsi problem. If you have any more details, please update the bug. We''d also love to hear if you have any updates on your other problem with the CD-ROM device. Cheers, - Russ Russ Blaine wrote:> Alan Romeril wrote: >> However these drivers do not seem to work with Microsoft''s iscsi >> initiator. I get a very unhealthy blue screen when I connect to a >> target. Is this a known bug? > > We haven''t tried the MSFT iscsi initiator, no. I''ll file a bug. > > Meanwhile, were you able to get past the problem you initially reported? > Can you get your win2003 domain running with the CD device present? > > Thanks for all the info, Alan... > > - Russ > > ----------------------------------------------------- > Russ Blaine | Solaris Kernel | russell.blaine@sun.com > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org-- ----------------------------------------------------- Russ Blaine | Solaris Kernel | russell.blaine@sun.com
Hi Russ,
I''ve been testing re-adding the cdrom device, and it seems to work
when you don''t use the PV disk driver for it. Removing the second
registry key from the install allows just attaching to the disk device rather
than the cdrom.
The iscsi blue screen names xvmbus.sys, interestingly if you don''t
load the PV disk driver the iscsi volume works fine with the XVMbus and XVMnet
drivers at about 50-60 MB/sec sequential read.
Cheers,
Alan
--
This message posted from opensolaris.org
On Fri, Nov 07, 2008 at 01:40:10AM +0100, Jens Elkner wrote:> > # virt-install -n win2k3Server-1 --hvm -r 4096 --vnc \ > > > -f /files/vdsk/win2k3Server-1.img -s 32 \ > > > -c /files/images/windows/en_windows_server_2003_with_sp1_standard.iso > > The path is probably too long. Try it e.g. with > -c /files/images/windows/sp1.isoThis is a newish bug: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6772442 vbd-check doesn''t work correctly for long paths (Please file bugs for strange issues like this: the worst that can happen is that we waste a bit of time marking it as a duplicate!) regards john
Hi Alan, Which version of the guest additions were you using? From dom0, you can see the build date using /usr/lib/xen/bin/xenstore-ls /local/domain/<domid>, once the guest is up and running. We think that your problem has most likely been fixed in the most recent version of the drivers, available on the download center. - Russ Alan Romeril wrote:> Hi Russ, > I''ve been testing re-adding the cdrom device, and it seems to work when you don''t use the PV disk driver for it. Removing the second registry key from the install allows just attaching to the disk device rather than the cdrom. > The iscsi blue screen names xvmbus.sys, interestingly if you don''t load the PV disk driver the iscsi volume works fine with the XVMbus and XVMnet drivers at about 50-60 MB/sec sequential read. > Cheers, > Alan
Alan Romeril wrote:> The iscsi blue screen names xvmbus.sys, interestingly if you don''t > load the PV disk driver the iscsi volume works fine with the XVMbus > and XVMnet drivers at about 50-60 MB/sec sequential read. Cheers, > AlanWe''ve found the cause of the iscsi problem. The disk driver goes to attach to it (because it is a disk in one sense), and can''t find a device for it in the backend. This case isn''t handled properly, so you get the blue screen. The workaround, as you have already discovered, is to remove the xVMBus.sys driver and run your real disks in emulated mode. The bug is tracking all of this: 6770912 Guest additions for Windows inhibit MSFT iscsi initiator and it will be fixed in January. To answer another question of yours that went unanswered:> I''ve downloaded the EA2 guest additions, what''s the best way to > install them on a domain that already has the earlier versions > running?Best bet is to uninstall them the official Windows way (control panel -> add/remove programs), and then install the new ones (followed by a reboot, of course). Unofficially, you can just replace the .sys driver binaries in c:\windows\system32\drivers with the new versions and reboot. There are three: xVMBus.sys, xVMNet.sys, and xVMStorFlt.sys. - Russ