RE: [Xen-users] Xen 3.2 on debian dom0 2.6.18 x86_64 running Windows XP SP3 : gplpv 0.9.11pre11 not working

["Dustin Henning" <Dustin.Henning@xxxxxxxxxxx>]

Peter,
        I would most definitely try rebuilding if you have the time.  It is
possible that following the cleanup steps from the wiki might work, but I
never had much luck with them.  After a rebuild, I would set up a snapshot,
try 0.9.10 again, and wait for the add new hardware windows to disappear (I
don't know if this should happen in 0.9.11-preX as well or not), hopefully
at this point, all of the drivers work.  The xenvbd driver is the disk
driver, so if it isn't working right, it's no wonder the system locks up and
goes to 100% CPU, xenhide is preventing Windows from seeing the qemu
disk(s), and the driver for the xen ones (xenvbd) isn't working.  If the
same problem were encountered, I would drop changes from the snapshot, try
the new 0.9.11-pre12, and respond to the thread about it with any problems
and a brief history of your experience thus far (dutch Windows, version of
Debian, version of Xen, versions of GPLPV tried, issues encountered).  He
may have some more insight on Debian, or he may be able to gather additional
information to potentially test or fix your problem if it is related to the
Dutch version [I am assuming it is a fully different version, but truthfully
I don't know whether it's the same version with a language pack or a
different version, and neither would surprise me]).  Good luck,
        Dustin

-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Peter Van Biesen
Sent: Wednesday, August 20, 2008 05:45
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Xen 3.2 on debian dom0 2.6.18 x86_64 running
Windows XP SP3 : gplpv 0.9.11pre11 not working

Hi Dustin,

I found this thread too and I tried without the cdrom devices already. This
makes no difference.

I reverted and installed the 0.9.10. I only get "the device was not plugged
in" error twice now. The devices still have an exclamation mark in the
device manager but the "add new hardware" dialog does disappear after a
while. After reboot, windows seems to hang on the splash screen. I then
disabled usb ( this is sometimes an issue when hanging on mup.sys ), and now
the screen goes black and the domu uses 100% CPU. At the third reboot, I
select safe mode and behold - windows boots. 

When looking in the device manager, only the xen vbd driver had an
exclamation mark. The network drivers seems to work ( I had now some 10
network devices ). I disabled the vdb driver and rebooted. Again a hang on a
black screen.

So, basically, after installation of the driver, the only way to get windows
back online is to
1) disable usb
2) boot in safe mode

Maybe I should completely reinstall windows xp ? 

Concerning performance : I pick my users carefully. First migrate users who
only use mail, browser and occasionally office. They do not need much
diskperformance, in fact, they do not even know if an application is running
on their pc or on the network ( browser ). Once you have a userbase that is
satisfied with the performance, migrate a somewhat heavier user. If he
complains, you can tell him : look, there are 10 users happy why you're not
? This buys you some time to figure the problem out en gets the user off
your back. This is where I'm now.

Never ever start with power users !! It is my experience that most of the
userbase don't care where or how their OS is running - even 3/4 of our
developers don't care, as long as the performance is ok. For the 1/4
developers who do care, don't bitch and just give them a standalone machine.
It is really a win-win situation with xen, we have the control over the
hardware while they have control over their windows game console ... er OS
*cough* :-) .

But definitely need the gplpv drivers to work if I am to migrate most of my
users.

Anyway, thanks for the advise.

Peter.

On Tuesday 19 August 2008 14:50:19 Dustin Henning wrote:
> Peter,
>       OK, first and foremost, I think I forgot to mention this thread in
> my last response:
> http://lists.xensource.com/archives/html/xen-users/2008-08/msg00428.html
> I bring it up now because I looked over your config again and noticed the
> two CD-ROM drives.  It may be that you need to get rid of them as this may
> be a new problem with 0.9.11-pre11 (if you really need those images
mounted
> in Windows, you might be able to use something like Elby Virtual Clone
Drive
> [http://elby.ch/fun/software/index.html] to mount those images from within
> the domU, but I don't know if this can be done automatically [might
require
> manual remount after each reboot]).
>       I haven't even messed with 0.9.11-preX, I am running 0.9.10.  Seeing
> as how you had problems with it, my only thought is that if the installer
> changed for 0.9.11-pre11 vs 0.9.10, you might revert again and try 0.9.10
to
> see if the add new hardware windows disappear on their own given a bit of
> time.  I know I've had hanging like that in the past with previous
versions,
> and it seems like in some cases waiting long enough would make it work
> (though not necessarily with the performance the drivers are supposed to
> provide) and in others I had to restore (or rebuild) Windows, and try
again,
> as it used to (and may still) be absolutely crucial that the drivers are
> installed on a clean system, but I honestly don't remember all the details
> here.  Alternatively, since 0.9.10 caused your system to hang, you might
try
> the suggestion mentioned here on 0.9.11-pre11 (even though the issue being
> resolved appears to be unrelated and has potentially been solved in
pre11):
> http://lists.xensource.com/archives/html/xen-users/2008-08/msg00203.html
>       I think the risk with doing that (disabling the xenhide.sys driver)
> is that if the system loads the qemu drivers and the gplpv drivers at the
> same time you will get massive HD corruption (should not be a big deal
with
> a snapshot).  However, for the record, I am shooting in the dark on all
> counts here (I haven't suggested anything I wouldn't try, but that doesn't
> mean I haven't suggested some things others wouldn't recommend trying), so
> don't get your hopes up.  Unless removing the 0.9.10 drivers was done via
a
> method other than reverting to a backup/snapshot (you said removing them
via
> device manager and it has always taken more steps than that) or the
drivers
> and their installation methods changed quite a bit between 0.9.10 and
> 0.9.11-pre11 (assuming you didn't get the same error on 0.9.10), the error
> ending in "but can't find the device itself" might ultimately have
something
> to do with your environment (for instance, perhaps your version of Windows
> is different or there is an issue with your version of debian).  I think
> James usually spends more time dealing with his drivers and the list on
> weekends, so it might be a few days or a couple weeks before you hear much
> from him, but unless you luck out somehow, that's probably what it will
> take.
>       Finally, as an aside, regarding your thread on the performance of
> the GPLPV drivers, it surprises me that your users haven't complained
about
> performance with qemu drivers, they must be easy to please.  The
difference
> is most certainly noticeable and worth the trouble.
>       Dustin
> 
> 
> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Peter Van
Biesen
> Sent: Tuesday, August 19, 2008 04:47
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-users] Xen 3.2 on debian dom0 2.6.18 x86_64 running
> Windows XP SP3 : gplpv 0.9.11pre11 not working
> 
> Hi Dustin,
> 
> reverting is a matter of seconds, as I am running my domU on a lvm
snapshot
> volume.
> 
> I tried installing again. When I got the new hardware windows, I did
> nothing, but they did nog go away. So I hit cancel on every one.
> 
> In the device manager, the xen devices still had the exclamation mark. 
> 
> I then added the /gplpv line in the boot.ini and rebooted. This worked
fine
> ! But windows still didn't use the xen drivers ( no change in the counters
> in xm top ). The drivers still have the exclamation mark and every time I
> reboot I get all the "new hardware" windows again and again. 
> 
> I had installed the 0.9.10 drivers last week, this made windows hang, but
> the counters in xm top did go up.
> 
> I removed all faulty drivers from the device manager and rebooted. When I
> then look at the devices, no drivers are installed. I then installed them
> one by one and get error :
> 
> " Windows has loaded the driver in memory, but can't find the device
itself
> ( code 41 )" ( this is a translation from dutch )
> 
> Any suggestions ?
> 
> Thanks in advance,
> 
> Peter.
> 
> On Monday 18 August 2008 17:32:37 Dustin Henning wrote:
> >     I don't remember what version this applies to, but at one point,
> when 
> > installing, I was going through the "new hardware" windows and letting 
> > Windows install the drivers automatically.  I had problems when I did
> this.
> > After recovering to a pre GPLPV-installed environment, I ran the 
> > installer again and let it deal with these windows.  They eventually 
> > disappeared without me even clicking next and then everything worked 
> > great.  I tried this because that is how some Windows driver 
> > installers work (i.e. most mainboard RealTek sound drivers).  However, 
> > this may not help you, as this may have been with an installer for a 
> > previous version that didn't have the "the device is not plugged in, 
> > cannot update driver" error, which I believe was added to prevent
> confusion when upgrading from one version to another.
> > Hopefully someone else can come back with more/better information, but 
> > in the meantime, odds are that you'll need to get to a pre 
> > GPLPV-installed state (restore from backup) and try again, so if 
> > getting back to that state is easy and you want to try the install 
> > again before anyone else responds, just don't interfere with the parts 
> > of the install that look like they need manual intervention for a while
> and see what happens.  Good luck,
> >     Dustin
> > 
> > -----Original Message-----
> > From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> > [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Peter Van 
> > Biesen
> > Sent: Monday, August 18, 2008 09:05
> > To: xen-users@xxxxxxxxxxxxxxxxxxx
> > Subject: [Xen-users] Xen 3.2 on debian dom0 2.6.18 x86_64 running 
> > Windows XP
> > SP3 : gplpv 0.9.11pre11 not working
> > 
> > Hi,
> > 
> > I installed a debian xen server using the 3.2 xen hypervisor and the 
> > 2.6.18 xen enabled kernel ( from stable ) x86_64 . I installed a 32bit 
> > windows xp using hvm. This all worked perfectly. Networking and disk io
> work.
> > 
> > I installed SP1a, SP3 and the .net 2.0 framework.
> > 
> > I then tried to install the gplpv drivers. I downloaded the 
> > 0.9.11pre11 and installed it.
> > 
> > While installation, I get "the device is not plugged in, cannot update 
> > driver" 6 times, installation of the driver seems to work ( windows 
> > complains a couple of times that it cannot verify the drivers are of 
> > its own 'high' standard ). After installation, I get several "new
> hardware" windows.
> > I let windows install the default drivers ( which are the gplpv drivers
).
> > 
> > I then reboot the domU ( without altering the boot.ini ). In the 
> > device manager, the vbd xen devices and the xen net device all have a 
> > exclamation mark on them. The only xen device working without problems 
> > is "xen pci device driver".
> > 
> > All drivers have the same error : Code 12 : insufficient free 
> > resources ( its a dutch installation, so this is a translation ).
> > 
> > When I edit the boot.ini to add the /gplpv and boot with that, I get 
> > een BSOD on Mup.sys.
> > 
> > Here's my config. Strangely enough, I do not need to put any ioemu 
> > stuff in the file for windows to boot ( maybe this is new in 3.2 ? ):
> > ------------------------------------
> > kernel = "/usr/lib/xen-default/boot/hvmloader"
> > builder='hvm'
> > memory = 512
> > name = "windows2"
> > disk = [
> > 'phy:/dev/vg00/windows2-snap,hda,w','file:/root/winxp-nl-setup-Q6TD9-9
> > FMQ3-F 
> > RVF4-VPF7Y-38JV3.iso,hdc:cdrom,r','file:/root/wintemp.iso,hdd:cdrom,r'
> > , ] vif = [ 'bridge=eth0,mac=00:16:3E:00:02:01', ] device_model = 
> > '/usr/lib/xen-default/bin/qemu-dm'
> > 
> > boot='cd'
> > sdl=0
> > vnc=1
> > vnclisten="0.0.0.0"
> > vncunused=1
> > acpi=1
> > apic=0
> > pae=1
> > usb = 1
> > usbdevice = 'tablet'
> > #serial="pty"
> > ----------------------------------
> > 
> > Does anybody have an idea of what could be wrong ?
> > 
> > Thanks in advance,
> > 
> > Peter.
> > --
> > Peter Van Biesen
> > Sysadmin VAPH
> > 
> > tel: +32 (0) 2 225 85 70
> > fax: +32 (0) 2 225 85 88
> > e-mail: peter.vanbiesen@xxxxxxx
> > PGP: http://www.vaph.be/pgpkeys
> > 
> > 
> > 
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
> > 
> > 
> 
> 
> 
> --
> Peter Van Biesen
> Sysadmin VAPH
> 
> tel: +32 (0) 2 225 85 70
> fax: +32 (0) 2 225 85 88
> e-mail: peter.vanbiesen@xxxxxxx
> PGP: http://www.vaph.be/pgpkeys
> 
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 
> 



-- 
Peter Van Biesen
Sysadmin VAPH

tel: +32 (0) 2 225 85 70
fax: +32 (0) 2 225 85 88
e-mail: peter.vanbiesen@xxxxxxx
PGP: http://www.vaph.be/pgpkeys

Opgelet ! De domeinnaam van het Vlaams Agentschap is vanaf heden
vaph.be. Dit betekent dat u uw correspondent kan bereiken via
voornaam.naam@xxxxxxxx Gelieve aub dit aan te passen in uw adresboek.

DISCLAIMER
----------------------------------------------------------------------------
---
De personeelsleden van het agentschap doen hun best om in e-mails
betrouwbare informatie te geven. 
Toch kan niemand rechten doen gelden op basis van deze inhoud. 
Als in de e-mail een stellingname voorkomt, is dat niet noodzakelijk het
standpunt van het agentschap. 
Rechtsgeldige beslissingen of officiele standpunten worden alleen per
brief toegestuurd.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users