Re: [win-pv-devel] Network and disk pv not working on windows 10 pro 64 bit with latest winpv build and xen 4.6.0

[Fabio Fantoni <fabio.fantoni@xxxxxxx>]

Il 13/10/2015 16:20, Paul Durrant ha scritto:
> > -----Original Message-----
> > From: Fabio Fantoni [mailto:fabio.fantoni@xxxxxxx]
> > Sent: 13 October 2015 15:14
> > To: Paul Durrant; win-pv-devel@xxxxxxxxxxxxxxxxxxxx
> > Cc: Stefano Stabellini
> > Subject: Re: [win-pv-devel] Network and disk pv not working on windows 10
> > pro 64 bit with latest winpv build and xen 4.6.0
> >
> >
> >
> > Il 13/10/2015 15:39, Paul Durrant ha scritto:
> > > > -----Original Message-----
> > > > From: Fabio Fantoni [mailto:fabio.fantoni@xxxxxxx]
> > > > Sent: 13 October 2015 14:21
> > > > To: Paul Durrant; win-pv-devel@xxxxxxxxxxxxxxxxxxxx
> > > > Cc: Stefano Stabellini
> > > > Subject: Re: [win-pv-devel] Network and disk pv not working on windows
> > 10
> > > > pro 64 bit with latest winpv build and xen 4.6.0
> > > >
> > > >
> > > >
> > > > Il 13/10/2015 11:45, Paul Durrant ha scritto:
> > > > > > -----Original Message-----
> > > > > > From: win-pv-devel-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:win-pv-
> > devel-
> > > > > > bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of Fabio Fantoni
> > > > > > Sent: 12 October 2015 16:39
> > > > > > To: Paul Durrant; win-pv-devel@xxxxxxxxxxxxxxxxxxxx
> > > > > > Cc: Stefano Stabellini
> > > > > > Subject: Re: [win-pv-devel] Network and disk pv not working on
> > windows
> > > > 10
> > > > > > pro 64 bit with latest winpv build and xen 4.6.0
> > > > > >
> > > > > > Il 12/10/2015 14:15, Paul Durrant ha scritto:
> > > > > > > > -----Original Message-----
> > > > > > > > From: win-pv-devel-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:win-pv-
> > > > devel-
> > > > > > > > bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of Fabio Fantoni
> > > > > > > > Sent: 12 October 2015 11:26
> > > > > > > > To: win-pv-devel@xxxxxxxxxxxxxxxxxxxx
> > > > > > > > Cc: Paul Durrant
> > > > > > > > Subject: [win-pv-devel] Network and disk pv not working on
> > windows
> > > > 10
> > > > > > pro
> > > > > > > > 64 bit with latest winpv build and xen 4.6.0
> > > > > > > >
> > > > > > > > Dom0: Jessie (debian 8) 64 bit, kernel 3.16 from official repository,
> > > > > > > > xen 4.6.0, other installation details here:
> > > > > > > > ./configure --prefix=/usr --disable-blktap1 --disable-qemu-
> > traditional
> > > > > > > > --disable-rombios --with-system-seabios=/usr/share/seabios/bios-
> > > > > > 256k.bin
> > > > > > > > --with-extra-qemuu-configure-args="--enable-spice --enable-usb-
> > > > redir"
> > > > > > > > --disable-blktap2 --enable-systemd
> > > > > > > > xen services enabled with:
> > > > > > > > systemctl enable xenstored.service
> > > > > > > > systemctl enable xenconsoled.service
> > > > > > > > systemctl enable xen-init-dom0.service
> > > > > > > > systemctl enable xen-qemu-dom0-disk-backend.service
> > > > > > > > systemctl enable xendomains.service
> > > > > > > >
> > > > > > > > domU xl cfg:
> > > > > > > > http://lists.xen.org/archives/html/xen-devel/2015-
> > > > 10/txtsAaP2yM2Vx.txt
> > > > > > > > Still use emualted disk and network and xen pv network is unable to
> > > > > > > > start for code 10 error (from windows devices manager). (see also
> > > > > > > > screenshot in attachment)
> > > > > > > >
> > > > > > > > In attachment full qemu log with xen_platform trace.
> > > > > > > xen_platform_log xen platform: XENVIF|SettingsSave: FROM
> > Ethernet
> > > > > > (Realtek RTL8139C+ Fast Ethernet NIC)
> > > > > > > xen_platform_log xen platform: XENVIF|SettingsCopyIpAddresses:
> > > > > > Version4: ADDRESSES NOT FOUND
> > > > > > > xen_platform_log xen platform: XENVIF|SettingsCopyIpAddresses:
> > > > > > Version6: ADDRESSES NOT FOUND
> > > > > > > xen_platform_log xen platform: XENVIF|DriverRequestReboot:
> > <===>
> > > > > > > xen_platform_log xen platform: XENVIF|PdoStartDevice: fail7
> > > > > > > xen_platform_log xen platform: XENVIF|PdoStartDevice: fail6
> > > > > > > xen_platform_log xen platform: XENVIF|PdoStartDevice: fail5
> > > > > > > xen_platform_log xen platform: XENVIF|PdoStartDevice: fail4
> > > > > > > xen_platform_log xen platform: XENVIF|PdoStartDevice: fail3
> > > > > > > xen_platform_log xen platform: XENVIF|PdoStartDevice: fail2
> > > > > > > xen_platform_log xen platform: XENVIF|PdoStartDevice: fail1
> > > > (c0000001)
> > > > > > > xen_platform_log xen platform: XENNET|DriverUnload: XENNET 8.2.0
> > > > (31)
> > > > > > (17.09.2015)
> > > > > > > That means you have not rebooted to allow the emulated device to
> > be
> > > > > > unplugged. Other versions of Windows will prompt for the reboot but
> > > > > > Microsoft broke the class installer in Windows 10 so it won't.
> > > > > > >       Paul
> > > > > > Thanks for reply.
> > > > > > I already did a windows reboot after pv install but after doing another
> > > > > > seem ok.
> > > > > > Remain the dubt with ahci, I saw both emulated and pv ok in windows
> > > > > > devices manager and I not understand if a changes is needed for ahci
> > > > > > qemu side as Stefano Stabellini told.
> > > > > > Can you take a look to this new qemu log please? Is ok or with ahci disk
> > > > > > is not pv correctly?
> > > > > The log shows:
> > > > >
> > > > > xen_platform_log xen platform: XENVBD|__ReadDiskInfo:Target[0] :
> > > > 104857600 sectors of 512 bytes (512)
> > > > > xen_platform_log xen platform: XENVBD|__ReadDiskInfo:Target[0] : 50
> > GB
> > > > (00000000)
> > > > > xen_platform_log xen platform:
> > XENVBD|FrontendReadDiskInfo:Target[0]
> > > > : Features: BARRIER FLUSH DISCARD
> > > > > xen_platform_log xen platform:
> > XENVBD|FrontendReadDiskInfo:Target[0]
> > > > : DISCARD 0/1000
> > > > > xen_platform_log xen platform:
> > XENVBD|FrontendReadFeatures:Target[0]
> > > > : Features: PERSISTENT INDIRECT
> > > > > xen_platform_log xen platform:
> > XENVBD|FrontendReadFeatures:Target[0]
> > > > : INDIRECT 100
> > > > > xen_platform_log xen platform: XENVBD|__FrontendSetState:Target[0]
> > :
> > > > in state CONNECTED
> > > > > xen_platform_log xen platform: XENVBD|__FrontendSetState:Target[0]
> > :
> > > > in state ENABLED
> > > > > xen_platform_log xen platform: XENVBD|PdoCreate:Target[0] : Created
> > > > (PV)
> > > > > That last line says you have a functioning PV disk.
> > > > >
> > > > >      Paul
> > > > Thanks for your reply.
> > > > So with ahci even if Windows sees also emulated one in device manager
> > > > should properly use the pv?
> > > XENFILT is installed as a filter on the IDE channel class in Windows so that it
> > can make sure that, in the event of an emulated disk being present in the
> > VM, the PV device does not come online... otherwise you've got two disks in
> > the VM referencing the same storage and you'll get data corruption pretty
> > quickly.
> > > So, if you use AHCI, I'm not convinced that:
> > >
> > > a) The emulated device unplug code in QEMU will actually unplug the
> > emulated AHCI disk
> > > b) XENFILT will spot the problem
> > >
> > > Hence, if you see any corruption of the VMs disks I would not be surprised.
> > >
> > >     Paul
> > I had disk corruption but with qcow2 disk overlay and also using ide
> > instead as I reported time ago. Without qcow2 I not saw disk corruption
> > for sure if I remember good. I saw domUs windows unbootable in other
> > cases about updated/remove the new pv but also with ide.
> > Is there a way to check if corruption happen in raw disks even if domU
> > seems still working correctly?
> Go look at the number of disks the VM thinks it has. If you only gave it one 
> but it thinks it has two then corruption is imminent.
>
>    Paul
See 2 but one (the emulated as offline), see the screenshot attached.
In this case can risk corruption or not?

Thanks for any reply and sorry for my bad english.



> > @ Stefano Stabellini: can you add unplug support for ahci in qemu to be
> > sure it can't do unexpected things please?
> >
> >
> > If you need more information and/or test tell me and I'l post them.
> > Thanks for any reply and sorry for my bad english.

Attachment: disk_ahci_screen.JPG
Description: JPEG image

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