Xen project Mailing List

2017年1月20日下午5:16，"Paul Durrant" <Paul.Durrant@xxxxxxxxxx>写道：

Hi,

The fact that you had to boot into safe mode after uninstalling GPLPV rings alarm bells for me. If you had truly managed to uninstall the old drivers then you should be able boot normally with no problems. Since that was not the case it means there must be some trace of the GPLPV drivers left (probably whatever handles unplug of emulated devices) and leaving this in your system is almost certainly going to mean that the 8.1 drivers will not function properly. They must be installed into a system with no other PV drivers present.

Hmm, I think that makes sense. Do you think it will be better to switch to safe mode first before uninstalling old drivers? Or is there any other flow that can ensure a clean transition in this case? I have snapshot so I can try out different ways as necessary.

I don’t think I’m on the other thread. Could you post your QEMU logs on this thread too?

I'm talking about this thread:

https://lists.xen.org/archives/html/xen-users/2017-01/msg00080.html

Note the attachments in that thread is for a different issue related to driver Dom + stubdom with qemu trad. While I also met domU hang issue in that thread but that's with qemu upstream + old GPL PV driver and I do not have log for it.

So if your suspicion is correct, both cases are related to old driver instead of new driver.

I'm going to offline for two days and will report back later.

Thank you for your help!!

Thanks,

Paul

From: firemeteor.guo@xxxxxxxxx [mailto:firemeteor.guo@gmail.com] On Behalf Of G.R.
Sent: 20 January 2017 02:15
To: Paul Durrant <Paul.Durrant@xxxxxxxxxx>
Cc: win-pv-devel@lists.xenproject.org
Subject: RE: [win-pv-devel] How to diagnose windows domU hang on boot?

2017年1月20日上午2:53，"Paul Durrant" <Paul.Durrant@xxxxxxxxxx>写道：

Hi,

Did you attempt to upgrade from GPLPV to the 8.1 drivers? That’s not a good idea since you could end up with multiple drivers attempting to talk to your VM’s storage (with the possibility of corrupting it). You need to make sure GPLPV drivers are completely removed and all networking and storage is emulated before attempting to install 8.1.

Thank you for your quick response, Paul.

The process I used for update is to uninstall all old PV drivers first and install new driver after rebooting into safe mode.(normal reboot gives me an BSOD, and safe mode is mandatory)

This flow looks fine to me. Do you see an issue here?(e.g. is the BSOD suspicious to you?)

The best way to diagnose problems in the VM is to watch the qemu log in dom0. Assuming you are either using trad, or have enabled trace_log events in upstream qemu then you should see messages from the guest PV drivers appearing in /var/log/xen/qemu-dm-<vm name>.log. These messages should be enough to tell you whether the PV drivers have got stuck waiting for something.

I'm more used to the traditional qemu model, which generates some debug log by default as I attached in the other thread.(stubdom forces traditional qemu I think).

For qemu upstream, it's very quiet by default. Let me check around on how to enable the trace_log event you mentioned above.

Thanks again. will post back if something is really out of control.

Paul

From: win-pv-devel [mailto:win-pv-devel-bounces@lists.xenproject.org] On Behalf Of G.R.
Sent: 19 January 2017 14:31
To: win-pv-devel@lists.xenproject.org
Subject: [win-pv-devel] How to diagnose windows domU hang on boot?

Hi all,

I have a windows 7 domU get stuck in the boot screen forever after a recent driver update.

I'm a user of community version of XEN.
The old driver I have being using for a long time is the GPL PV driver from James Harper.
This driver update is part of the migration from XEN 4.3.2 to XEN 4.8.0.

I'm not sure if this driver update would do me any good, but it does get into trouble in a different setup as mentioned here:
https://lists.xen.org/archives/html/xen-users/2017-01/msg00080.html

So basically I'm reporting two different boot hang issues here:

1. The upgraded driver version (V8.1) causes issue in the original domU config.

2. The old GPL PV driver version causes issue in an experimental storage driver domain + stubdom config.

In both cases the syndrome look exactly the same -- win 7 domU boots into the windows logo on black screen and never make progress further.

But it does not BSOD either.
Could anybody suggest a way to diagnose further to help me understand what's going on in behind?

Thanks,

G.R.

Re: [win-pv-devel] How to diagnose windows domU hang on boot?