[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [win-pv-devel] Windows 10 domU is unstable with PV Bus Driver
> -----Original Message----- > From: win-pv-devel [mailto:win-pv-devel-bounces@xxxxxxxxxxxxxxxxxxxx] On > Behalf Of Michel D'HOOGE > Sent: 07 November 2017 13:46 > To: win-pv-devel@xxxxxxxxxxxxxxxxxxxx > Subject: [win-pv-devel] Windows 10 domU is unstable with PV Bus Driver > > Hello, > > This is my first post here so please forgive me if I missed something > obvious… But I've been searching for a while :-/ > > So, my Windows 10 domU is stable as long as I don't install the PV drivers. > I couldn't install version 8.2.1 of the PV drivers, so in July I tried > the test version from http://xenbits.xen.org/pvdrivers/win/. It worked > well for a while but last month it started to reboot from times to > times (I'd say after a "big" Windows upgrade). > I uninstalled all PV drivers and the OS was stable again. So yesterday > I tried again with the latest versions of the PV driver and I managed > to install xenbus and xenvbd before it got unstable again. > Painfully I managed to remove everything and it's back to stable. > > I can live without the PV drivers (especially given the time I've lost > trying to use them compared to the benefit!) but it's a bit of a pity > and I'd like to understand. > Is there something I can try to debug that? > Michael, Sounds like it is xenvbd that's probably interacting badly with your storage backend. If you leave don't install xenvbd, but install the rest (xenvif, xennet and xeniface) do you see any instability? What storage backend are you using? Also, can you get hold of your VM's QEMU log? It might have some clues. Also, I'm curious as to why version 8.2.1 was not working for you. Cheers, Paul > Thank you for your help > Michel > > > I collected some data, but this isn't meaningful to me. > > Name ID Mem VCPUs State > Time(s) > win10 3 3800 4 ---sr- > 79.8 > > (XEN) *** Dumping Dom3 vcpu#1 state: *** > (XEN) ----[ Xen-4.9.0 x86_64 debug=n Not tainted ]---- > (XEN) CPU: 1 > (XEN) RIP: 0010:[<fffff802d49785a3>] > (XEN) RFLAGS: 0000000000010082 CONTEXT: hvm guest (d3v1) > (XEN) rax: ffffd30041debb10 rbx: ffffd30041de8328 rcx: 0000000000000000 > (XEN) rdx: 0000000000006380 rsi: 0000000000000007 rdi: ffffd30041de8328 > (XEN) rbp: ffffd30041debbd0 rsp: ffffd30041deb9d0 r8: 00000000000000ff > (XEN) r9: 00000000000000de r10: fffff802d49785a3 r11: 0000000000000000 > (XEN) r12: ffffd30041de81f0 r13: 00000000ffffff00 r14: ffffd30041de83d0 > (XEN) r15: 0000000000000000 cr0: 0000000080050031 cr4: 00000000001506f8 > (XEN) cr3: 00000000001aa000 cr2: 0000000000006380 > (XEN) ds: 002b es: 002b fs: 0053 gs: 002b ss: 0018 cs: 0010 > > > Name ID Mem VCPUs State > Time(s) > win10 6 3800 4 ---sc- > 99.5 > > (XEN) *** Dumping Dom6 vcpu#0 state: *** > (XEN) ----[ Xen-4.9.0 x86_64 debug=n Not tainted ]---- > (XEN) CPU: 1 > (XEN) RIP: 0010:[<fffff800bf56574f>] > (XEN) RFLAGS: 0000000000010086 CONTEXT: hvm guest (d6v0) > (XEN) rax: fffff800c2860f70 rbx: 00000000c0000001 rcx: fffff80790829310 > (XEN) rdx: 000000000000004d rsi: 0000000000000028 rdi: 0000000000000000 > (XEN) rbp: fffff800c2860e80 rsp: fffff800c2860e60 r8: 0000000000000000 > (XEN) r9: fffff80790829000 r10: 0000000000000027 r11: fffff800c2860f58 > (XEN) r12: 000000000000003d r13: fffff800c2863301 r14: 0000000000000028 > (XEN) r15: fffff80790813f80 cr0: 0000000080050031 cr4: 00000000001506f8 > (XEN) cr3: 0000000000212000 cr2: fffff800c284a080 > (XEN) ds: 002b es: 002b fs: 0053 gs: 002b ss: 0018 cs: 0010 > > _______________________________________________ > win-pv-devel mailing list > win-pv-devel@xxxxxxxxxxxxxxxxxxxx > https://lists.xenproject.org/cgi-bin/mailman/listinfo/win-pv-devel _______________________________________________ win-pv-devel mailing list win-pv-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/cgi-bin/mailman/listinfo/win-pv-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |