Re: [win-pv-devel] Windows server 2012 R2 domUs problem after save/restore

[Fabio Fantoni <fabio.fantoni@xxxxxxx>]

Il 30/01/2015 19:04, Paul Durrant ha scritto:
> > -----Original Message-----
> > From: Fabio Fantoni [mailto:fabio.fantoni@xxxxxxx]
> > Sent: 30 January 2015 15:45
> > To: Paul Durrant
> > Cc: win-pv-devel@xxxxxxxxxxxxxxxxxxxx
> > Subject: Re: [win-pv-devel] Windows server 2012 R2 domUs problem after
> > save/restore
> >
> > Il 30/01/2015 16:31, Paul Durrant ha scritto:
> > > > -----Original Message-----
> > > > From: Fabio Fantoni [mailto:fabio.fantoni@xxxxxxx]
> > > > Sent: 30 January 2015 15:14
> > > > To: Paul Durrant; win-pv-devel@xxxxxxxxxxxxxxxxxxxx
> > > > Subject: Re: [win-pv-devel] Windows server 2012 R2 domUs problem
> > after
> > > > save/restore
> > > >
> > > > Il 30/01/2015 16:07, Paul Durrant ha scritto:
> > > > > > -----Original Message-----
> > > > > > From: win-pv-devel-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:win-pv-
> > devel-
> > > > > > bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of Fabio Fantoni
> > > > > > Sent: 30 January 2015 14:42
> > > > > > To: Paul Durrant; win-pv-devel@xxxxxxxxxxxxxxxxxxxx
> > > > > > Subject: Re: [win-pv-devel] Windows server 2012 R2 domUs problem
> > > > after
> > > > > > save/restore
> > > > > >
> > > > > > Il 30/01/2015 15:31, Paul Durrant ha scritto:
> > > > > > > > -----Original Message-----
> > > > > > > > From: win-pv-devel-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:win-pv-
> > > > devel-
> > > > > > > > bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of Fabio Fantoni
> > > > > > > > Sent: 30 January 2015 14:17
> > > > > > > > To: Paul Durrant; win-pv-devel@xxxxxxxxxxxxxxxxxxxx
> > > > > > > > Subject: Re: [win-pv-devel] Windows server 2012 R2 domUs
> > problem
> > > > > > after
> > > > > > > > save/restore
> > > > > > > >
> > > > > > > > Il 28/01/2015 21:14, Paul Durrant ha scritto:
> > > > > > > > > > -----Original Message-----
> > > > > > > > > > From: Fabio Fantoni [mailto:fabio.fantoni@xxxxxxx]
> > > > > > > > > > Sent: 28 January 2015 09:19
> > > > > > > > > > To: Paul Durrant; win-pv-devel@xxxxxxxxxxxxxxxxxxxx
> > > > > > > > > > Subject: Re: [win-pv-devel] Windows server 2012 R2 domUs
> > > > problem
> > > > > > > > after
> > > > > > > > > > save/restore
> > > > > > > > > >
> > > > > > > > > > Il 22/01/2015 16:00, Paul Durrant ha scritto:
> > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > From: win-pv-devel-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:win-
> > > > pv-
> > > > > > > > devel-
> > > > > > > > > > > > bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of Fabio Fantoni
> > > > > > > > > > > > Sent: 22 January 2015 10:10
> > > > > > > > > > > > To: win-pv-devel@xxxxxxxxxxxxxxxxxxxx
> > > > > > > > > > > > Cc: Paul Durrant
> > > > > > > > > > > > Subject: Re: [win-pv-devel] Windows server 2012 R2 domUs
> > > > > > problem
> > > > > > > > > > after
> > > > > > > > > > > > save/restore
> > > > > > > > > > > >
> > > > > > > > > > > > Il 19/01/2015 16:30, Fabio Fantoni ha scritto:
> > > > > > > > > > > > > Hi, I installed winpv driver build of 15 january on Windows
> > server
> > > > > > > > > > > > > 2012 R2 standard 64 bit and have problem after save/restore.
> > > > > > > > > > > > > xl save/restore didn't show any errors, trying to connected
> > with
> > > > rdp
> > > > > > I
> > > > > > > > > > > > > was unable and with spice I saw screen with data and time
> > (time
> > > > > > > > update
> > > > > > > > > > > > > after restore) but doing ctrl+alt+canc it changed something in
> > > > > > screen
> > > > > > > > > > > > > only after 5-10 minutes and still without showing login field.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Dom0 is Wheezy with kernel 3.16.7-ckt2-1~bpo70+1 (from
> > > > official
> > > > > > > > > > > > > backport), build of xen based on start of 4.4.2-pre and qemu
> > 1.6
> > > > > > from
> > > > > > > > > > > > > xen build.
> > > > > > > > > > > > > DomU xl cfg:
> > > > > > > > > > > > > > name='w2012r2-01'
> > > > > > > > > > > > > > builder="hvm"
> > > > > > > > > > > > > > memory=8192
> > > > > > > > > > > > > > vcpus=4
> > > > > > > > > > > > > > acpi_s3=0
> > > > > > > > > > > > > > acpi_s4=0
> > vif=['bridge=xenbr2,mac=00:16:3e:24:b7:d7','bridge=xenbr10,mac=00:16:3e:
> > > > > > > > > > > > 18:2a:f2,script=vif-openvswitch']
> > > > > > > > > > > > > > #vfb=['vnc=1,vncunused=1,vnclisten="0.0.0.0",keymap=it']
> > > > > > > > > > > > > > disk=['/mnt/vm/disks/w2012r2-
> > > > > > > > > > > > 01.disk1.xm,raw,hda,rw',',raw,hdb,ro,cdrom']
> > > > > > > > > > > > > > boot='dc'
> > > > > > > > > > > > > > device_model_version="qemu-xen"
> > > > > > > > > > > > > > viridian=1
> > > > > > > > > > > > > > vnc=0
> > > > > > > > > > > > > > keymap="it"
> > > > > > > > > > > > > > on_crash="destroy"
> > > > > > > > > > > > > > vga="stdvga"
> > > > > > > > > > > > > > spice=1
> > > > > > > > > > > > > > spicehost='0.0.0.0'
> > > > > > > > > > > > > > spiceport=6000
> > > > > > > > > > > > > > spicepasswd="test"
> > > > > > > > > > > > > > spicevdagent=1
> > > > > > > > > > > > > > spice_clipboard_sharing=0
> > > > > > > > > > > > > > spiceusbredirection=4
> > > > > > > > > > > > > > soundhw="hda"
> > > > > > > > > > > > > > localtime=1
> > > > > > > > > > > > > I added in attachments qemu logs (before and after
> > > > save/restore)
> > > > > > > > with
> > > > > > > > > > > > > xen trace enabled.
> > > > > > > > > > > > >
> > > > > > > > > > > > > If you need more informations tests tell me and I'll post them.
> > > > > > > > > > > > >
> > > > > > > > > > > > > I have also another small question:
> > > > > > > > > > > > > is ms_vm_genid needed for this case? for what I understand
> > is
> > > > only
> > > > > > > > for
> > > > > > > > > > > > > active directory controller and this it isn't.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Thanks for any reply and sorry for my bad english.
> > > > > > > > > > > > I also tried to uninstall the pv drivers from control panel but
> > > > windows
> > > > > > > > > > > > crash, minidump in attachments.
> > > > > > > > > > > I'm re-working the FIFO event channel code at the moment so I'll
> > > > run
> > > > > > a
> > > > > > > > > > quick suspend/resume test when I'm done.
> > > > > > > > > > >         Paul
> > > > > > > > > > Thanks for your reply.
> > > > > > > > > > I did other tests and seems that save/restore problems with
> > > > windows
> > > > > > > > 2012
> > > > > > > > > > was for missed ms_vm_genid="generate" even if clean for now
> > (no
> > > > > > active
> > > > > > > > > > directory or other server services enabled nor domain member).
> > > > > > > > > > Remain windows crash on winpv drivers uninstall with minidump
> > > > refer
> > > > > > to
> > > > > > > > > > xenvif and other important and occasional problem:
> > > > > > > > > > network not working after some time and after 2-3 minutes all
> > > > > > windows
> > > > > > > > > > become unusable.
> > > > > > > > > > I hope these problem will be solved by new network pv driver
> > > > patches,
> > > > > > > > > > I'll test them ASAP when build with them will be ready.
> > > > > > > > > I pushed my big series into xenbus today. You should definitely
> > take
> > > > > > that; it
> > > > > > > > fixes several bugs in FIFO event channels and a couple of other
> > things.
> > > > > > > > >        Paul
> > > > > > > > Thanks.
> > > > > > > > I tested now new pv drivers build on a windows 7 64 bit domU.
> > > > > > > > On update I saw a strange thing, xenvif and xennet even if updated
> > > > > > > > showed message "Ready to use" instead "Driver updated".
> > > > > > > > After update of all drivers components I rebooted windows but it
> > didn't
> > > > > > > > start, stay blocked on windows logo, seems there is a critical
> > > > > > > > regression in latest pv drivers build :(
> > > > > > > > DomU's qemu log with xen-platform trace in attachment.
> > > > > > > I don't see either XENVIF or XENNET loading at all so perhaps the
> > > > problem is
> > > > > > with PV storage and Windows is unable to load the drivers? Does this
> > > > happen
> > > > > > if you fresh-install a VM? I tested on Win7 64 and didn't see any
> > problem,
> > > > but
> > > > > > it was a fresh VM in my case.
> > > > > > >       Paul
> > > > > > Is a windows 7 with only few things installed that I use for new xen and
> > > > > > pv drivers testing only.
> > > > > > There was installed previous official builds from here:
> > > > > > http://xenproject.org/downloads/windows-pv-drivers.html
> > > > > > Previous update was 2-3 weeks ago and reboot was succesfull, update
> > of
> > > > > > today not.
> > > > > > I didn't have installed/updated any other software in this domU
> > between
> > > > > > the latest 2 pv driver updates.
> > > > > Ah, I wonder if I've unwittingly introduced a dependency on the per-vpu
> > > > event channel callback patch into Xen. I did my testing with that in place.
> > I'll
> > > > try running on 4.5.
> > > > >      Paul
> > > > My actual testing dom0 where I tested the new pv drivers is xen 4.5.0
> > > > with some patches:
> > > > https://github.com/Fantu/Xen/commits/rebase/m2r-testing
> > > > Including backports of this 2 patches:
> > > > x86/hvm: add per-vcpu evtchn upcalls
> > > > x86/hvm: extend HVM cpuid leaf with vcpu id
> > > In that case I can't really think of anything. As I said, it worked for me when
> > I tested it all. I'll give it another try just to make sure.
> > >     Paul
> > I restored the domUs from backup of 10 days ago, when was working, after
> > backup I didn't install anythings until today when I installed latest pv
> > drivers build and windows was unable to boot after reboot.
> > Screenshoot of software installed in attachments.
> I think I found your problem,. I just posted a small patch to the list and 
> pushed it immediately to kick off a new build.
>
>    Paul
Thanks!
I tested now the update on 2 different domUs and the critical boot 
problem is solved.
I did many other tests, there is still a bug in xenvif and/or xennet: 
after their update I still got the message "Ready to use" instead 
"Device updated".
After uninstalling all pv drivers and rebooting, the network doesn't 
work even if Windows sees the emulated network card (however before 
installing the pv drivers it was usable). I tried also the uninstall on 
other domU with a pv drivers build of one month ago and it did the same 
thing, so it doesn't seem to be a recent regression. Can you take a look 
at it when you have time?
There is also another minor strange thing: in "control center->programs" 
after drivers update it keeps all pv drivers builds instead of only the 
latest, as you can see in the screenshot of my previous mail. Is it normal?
Thanks for any reply and sorry for my bad english.

_______________________________________________
win-pv-devel mailing list
win-pv-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/win-pv-devel