[ovirt-users] Windows 10 Guest with nvidia Tesla P40 vGpu Bluescreens when I enable nested virtualization

[domw]

Hi all,

I have this issue when I go to create a VM, I want to run WSL2 but when I 
install it or windows defender application guard the computer bluescreens.


So I am using CentOS 8 stream host connected to a VirtIO cluster the hardware 
is 2 Nvidia Tesla P40 graphics cards installed on a poweredge R480. My windows 
10 20H2 Image would bluescreen after the nvidia drivers are installed. I did 
some testing and discovered after installing a clean ISO windows 10 20H2 that 
it worked fine even after installing the drivers for the vGPU but the master 
image does have WSL2 installed out of the box so I installed it on my Vanilla 
image and it would bluescreen. I imagine this is due to the nested 
virtualization and the installation of some hyper-v service maybe it is trying 
to initialize some hardware acceleration. Has anyone had this issue I really 
need WSL and would love to use version 2.


Tesla Version I have tried is 450.12 and the latest 460.32


Kernel Bitmap Dump File: Kernel address space is available, User address space 
may not be available.


Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 19041 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 19041.1.amd64fre.vb_release.191206-1406

Machine Name:

Kernel base = 0xf805`5e80 PsLoadedModuleList = 0xf805`5f42a490

Debug session time: Sat Jun 26 04:58:37.807 2021 (UTC - 7:00)

System Uptime: 0 days 0:00:09.469

Loading Kernel Symbols

...

...Page 799b not present in the dump file. Type ".hh 
dbgerr004" for details

.

.

Loading User Symbols

PEB is paged out (Peb.Ldr = 002e`f91fa018). Type ".hh dbgerr001" for details

Loading unloaded module list

...

For analysis of this file, run !analyze -v

3: kd> !analyze -v

ERROR: FindPlugIns 8007007b

***

* *

* Bugcheck Analysis *

* *

***


SYSTEM_SERVICE_EXCEPTION (3b)

An exception happened while executing a system service routine.

Arguments:

Arg1: c005, Exception code that caused the bugcheck

Arg2: f80567d55b24, Address of the instruction which caused the bugcheck

Arg3: 8487974646a0, Address of the context record for the exception that 
caused the bugcheck

Arg4: , zero.


Debugging Details:

--


Page fd6196 not present in the dump file. Type ".hh dbgerr004" for details

Page fd6196 not present in the dump file. Type ".hh dbgerr004" for details


KEY_VALUES_STRING: 1


Key : Analysis.CPU.Sec

Value: 3


Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on BCCO050


Key : Analysis.DebugData

Value: CreateObject


Key : Analysis.DebugModel

Value: CreateObject


Key : Analysis.Elapsed.Sec

Value: 27


Key : Analysis.Memory.CommitPeak.Mb

Value: 81


Key : Analysis.System

Value: CreateObject



BUGCHECK_CODE: 3b


BUGCHECK_P1: c005


BUGCHECK_P2: f80567d55b24


BUGCHECK_P3: 8487974646a0


BUGCHECK_P4: 0


CONTEXT: 8487974646a0 -- (.cxr 0x8487974646a0)

rax= rbx=b406f7d85000 rcx=e17f3f1e8efe

rdx= rsi= rdi=b406f1667270

rip=f80567d55b24 rsp=8487974650a0 rbp=0002

r8= r9= r10=

r11=848797465040 r12=f80568511c80 r13=b406f1667270

r14=b406f194c660 r15=

iopl=0 nv up ei pl nz na pe nc

cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050202

nvlddmkm+0x1d5b24:

f805`67d55b24 4c8b80c822 mov r8,qword ptr [rax+22C8h] 
ds:002b:`22c8=

Resetting default scope


PROCESS_NAME: csrss.exe


STACK_TEXT:

8487`974650a0 f805`67cab38a : b406`f7d85000 b406`f194c660 
` 8487`97465220 : nvlddmkm+0x1d5b24

8487`974650e0 f805`67cdb663 : ` b406`f7d85000 
8487`97465220 b406`f1989000 : nvlddmkm+0x12b38a

8487`97465160 f805`67cb5df8 : b406`f7d85000 b406`f7d85000 
b406`f7d85000 8487`97465220 : nvlddmkm+0x15b663

8487`97465190 f805`67ca3ce5 : b406`f1a3b000 `0001 
b406`0001 b406`f7d85000 : nvlddmkm+0x135df8

8487`974651c0 f805`67ca4e8c : `0800 b406`f7d85000 
b406`f194c660 b406`f1a3b000 : nvlddmkm+0x123ce5

8487`974651f0 f805`67c8a41c : b406`f1b8271c 0002`0001 
b406`0007 ` : nvlddmkm+0x124e8c

8487`97465260 f805`67c90f8b : `0060 f805`684baeb8 
`0060 b406`f1b826b8 : nvlddmkm+0x10a41c

8487`97466440 f805`67c284f3 : b406`f1b81000 8487`97466640 
b406`0002 a001`ce6c4d80 : nvlddmkm+0x110f8b

[ovirt-users] Windows 10 on older CPUs

[Chris Adams]

I have an oVirt cluster running 4.3.10 on older hardware with a cluster
CPU type of Intel Nehalem.  I needed to install a Windows 10 (latest
release) VM, which oVirt rejected because of the CPU model.  I remember
there being issues with certain versions of Windows and this CPU model
under oVirt (I don't do Windows very often and had forgotten).

I instead told oVirt I was installing Windows 8 (which it accepted), and
then installed - it installed and appears to be working just fine.  I
don't know if Microsoft changed whatever used to break or what... I
remember the problem before not even getting through install, so it
seems to be okay.

Any issues I should be worried about?
-- 
Chris Adams 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/MSMHLELIC2AXPQY6EBSBRLWPI2E5KJCA/

[ovirt-users] Windows 10 Pro 64 (1909) crashes when migrating

[Maton, Brett]

I recently added a Windows 10 Pro 64 bit (release 1909) VM, and I'm seeing
a lot of failures when oVirt tries to move the VM to another host
(triggered by load balancing),

These errors are showing up in the UI event log

Migration failed  (VM: , Source: , Destination: ).

Followed by:

VM  is down with error. Exit message: Lost connection with qemu
process.

Google returned some references to 'options kvm ignore_msrs=1' which I've
added to /etc/modprobe/d/kvm.conf and restarted the hosts but that doesn't
appear to have made a difference.

Is this a known issue with Windows 10 guests?
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/QNJ7GFDXKBVREHJY4FBIORLBVEBO353R/

[ovirt-users] Windows 10 - Ovirt 4.3 - EPYC

[Darin Schmidt]

I have successfully setup a centos vm, its up and running. Now I need to
setup a windows 10 VM and I cant seem to get anything to work.

Ive tried setting the OS type to other or Windows 10 64bit. With Windows
64bit, it fails to startup at all When I select OtherOS it will allow
me to start to run the Windows ISO, but then fails after a few seconds as
well. Is there something I'm not correctly configuring?
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/QFUOS7MX2J37YWNVFSDTJC4PJYAFHOV3/

[ovirt-users] Windows 10 VM Virtio Drivers

[Sebastian Antunez N.]

Hello Guys

In my enviroment Ovirt 4.2 when create a new VM with Windows 10, in the
boot options menu, add the Floppy Disk for mount virtio driver but only
show me sysprep.

I check in my ISO Folder and show all vfd drivers for Windows and ISO but I
can not add the drivers who floppy.

This problem only is with Windows VM.

Any idea because this is issue.

Regards

Sebastian
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/HRMP6A4WSCZR4IO2S6VRNY7OSSPJJNDZ/

[ovirt-users] Windows 10 vs others windows

[carl langlois]

Hi

Why when en try to do a Windows 10 machine i have a error on the cpu guest
os not supported but not windows 8 or 7?

Thanks,
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/GYOFKCJXTUI4ZHU3PHGYT4MYRETZM7G7/

[ovirt-users] Windows 10 & 2016 snapshot error

[femi adegoke]

oVirt Guest Tools 4.2-1.el7.centos & QEMU guest agent v7.5 are installed.

When I try & take a snapshot, I get this warning:
"The VM will be paused while saving the memory
Could not detect Guest Agent on the VM. 
Note that without a Guest Agent the data on the created snapshot may be 
inconsistent."

What am I missing or doing wrong?
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZAQQH4HMHU57WEFLDS24XRSLO7C6E52Y/

Re: [ovirt-users] Windows 10 floppy not found during setup

[Christophe TREFOIS]

VMs use a vNIC on ovirtmgmt logical network. There should be nothing to do with 
the engine itself.

It was working fine for us after we are able to load the drivers properly.
  

> On 3 Feb 2018, at 23:07, Vincent Royer  wrote:
> 
> Thanks I tried it and it did in fact work.  Just threw me off because all the 
> instructions say to load the floppy. 
> 
> My windows install got right up to the point where it was loading the NICs, 
> and then it all came crashing down.  I expected the VMs and the engine to be 
> able to share the same NIC, but I suppose it doesn't work that way.  More 
> reading...
> 
> Vincent Royer
> 778-825-1057
> 
> 
>  
> SUSTAINABLE MOBILE ENERGY SOLUTIONS
> 
> 
> 
> 
> On Sat, Feb 3, 2018 at 9:58 AM, Christophe TREFOIS  > wrote:
> We had to do the swapping CD trick for Windows 10 yes.
> 
> Regards,
> -- 
> 
> Dr Christophe Trefois, Dipl.-Ing.  
> Technical Specialist / Post-Doc
> 
> UNIVERSITÉ DU LUXEMBOURG
> 
> LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
> Campus Belval | House of Biomedicine  
> 6, avenue du Swing 
> L-4367 Belvaux  
> T: +352 46 66 44 6124  
> F: +352 46 66 44 6949   
> http://www.uni.lu/lcsb 
>        
>    
>    
> 
> 
> This message is confidential and may contain privileged information. 
> It is intended for the named recipient only. 
> If you receive it in error please notify me and permanently delete the 
> original message and any copies. 
> 
> 
>   
> 
>> On 3 Feb 2018, at 11:31, Vincent Royer > > wrote:
>> 
>> I am trying to install Windows 10 on Ovirt 4.2
>> 
>> I pushed the virtio-win iso and vfd files to my ISO domain.   I created the 
>> VM and loaded the CD rom with the windows install ISO and in the "run once" 
>> settings I chose the virtio-win selection as a floppy.  However when 
>> entering windows setup, there is no drive to install to, and no floppy shows 
>> up in the usual place to install the drivers. 
>> 
>> the installation did succeed when selecting "IDE" as the target disk instead 
>> of the virtio or virtio-SCSI options.
>> 
>> Is there any way to install the drivers after the fact and then change the 
>> disk mode from IDE to virtio?
>> 
>> Is the method on this page 
>> https://www.ovirt.org/documentation/how-to/virtual-machines/create-a-windows-7-virtual-machine/
>>  
>> 
>>  
>> still relevant?  Looks like they suggest swapping the CD disk once the 
>> windows setup has begun. 
>> 
>> Thanks!
>> ___
>> Users mailing list
>> Users@ovirt.org 
>> http://lists.ovirt.org/mailman/listinfo/users 
>> 
> 
> 



smime.p7s
Description: S/MIME cryptographic signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Windows 10 floppy not found during setup

[Vincent Royer]

Thanks I tried it and it did in fact work.  Just threw me off because all
the instructions say to load the floppy.

My windows install got right up to the point where it was loading the NICs,
and then it all came crashing down.  I expected the VMs and the engine to
be able to share the same NIC, but I suppose it doesn't work that way.
More reading...

*Vincent Royer*
*778-825-1057*



*SUSTAINABLE MOBILE ENERGY SOLUTIONS*




On Sat, Feb 3, 2018 at 9:58 AM, Christophe TREFOIS <
christophe.tref...@uni.lu> wrote:

> We had to do the swapping CD trick for Windows 10 yes.
>
> Regards,
>
> --
>
> Dr Christophe Trefois, Dipl.-Ing.
> Technical Specialist / Post-Doc
>
> UNIVERSITÉ DU LUXEMBOURG
>
> LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
> Campus Belval | House of Biomedicine
> 6, avenue du Swing
> L-4367 Belvaux
> T: +352 46 66 44 6124 <+352%2046%2066%2044%206124>
> F: +352 46 66 44 6949 <+352%2046%2066%2044%206949>
> http://www.uni.lu/lcsb
>
> [image: Facebook]   [image: Twitter]
>   [image: Google Plus]
>   [image: Linkedin]
>   [image: skype]
> 
>
> 
> This message is confidential and may contain privileged information.
> It is intended for the named recipient only.
> If you receive it in error please notify me and permanently delete the
> original message and any copies.
> 
>
>
> On 3 Feb 2018, at 11:31, Vincent Royer  wrote:
>
> I am trying to install Windows 10 on Ovirt 4.2
>
> I pushed the virtio-win iso and vfd files to my ISO domain.   I created
> the VM and loaded the CD rom with the windows install ISO and in the "run
> once" settings I chose the virtio-win selection as a floppy.  However when
> entering windows setup, there is no drive to install to, and no floppy
> shows up in the usual place to install the drivers.
>
> the installation did succeed when selecting "IDE" as the target disk
> instead of the virtio or virtio-SCSI options.
>
> Is there any way to install the drivers after the fact and then change the
> disk mode from IDE to virtio?
>
> Is the method on this page https://www.ovirt.org/
> documentation/how-to/virtual-machines/create-a-windows-7-virtual-machine/
> still relevant?  Looks like they suggest swapping the CD disk once the
> windows setup has begun.
>
> Thanks!
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Windows 10 floppy not found during setup

[Christophe TREFOIS]

We had to do the swapping CD trick for Windows 10 yes.

Regards,
-- 

Dr Christophe Trefois, Dipl.-Ing.  
Technical Specialist / Post-Doc

UNIVERSITÉ DU LUXEMBOURG

LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
Campus Belval | House of Biomedicine  
6, avenue du Swing 
L-4367 Belvaux  
T: +352 46 66 44 6124 
F: +352 46 66 44 6949  
http://www.uni.lu/lcsb 
       
   
   

This message is confidential and may contain privileged information. 
It is intended for the named recipient only. 
If you receive it in error please notify me and permanently delete the original 
message and any copies. 


  

> On 3 Feb 2018, at 11:31, Vincent Royer  wrote:
> 
> I am trying to install Windows 10 on Ovirt 4.2
> 
> I pushed the virtio-win iso and vfd files to my ISO domain.   I created the 
> VM and loaded the CD rom with the windows install ISO and in the "run once" 
> settings I chose the virtio-win selection as a floppy.  However when entering 
> windows setup, there is no drive to install to, and no floppy shows up in the 
> usual place to install the drivers. 
> 
> the installation did succeed when selecting "IDE" as the target disk instead 
> of the virtio or virtio-SCSI options.
> 
> Is there any way to install the drivers after the fact and then change the 
> disk mode from IDE to virtio?
> 
> Is the method on this page 
> https://www.ovirt.org/documentation/how-to/virtual-machines/create-a-windows-7-virtual-machine/
>  
> 
>  
> still relevant?  Looks like they suggest swapping the CD disk once the 
> windows setup has begun. 
> 
> Thanks!
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users



smime.p7s
Description: S/MIME cryptographic signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Windows 10 floppy not found during setup

[Vincent Royer]

I am trying to install Windows 10 on Ovirt 4.2

I pushed the virtio-win iso and vfd files to my ISO domain.   I created the
VM and loaded the CD rom with the windows install ISO and in the "run once"
settings I chose the virtio-win selection as a floppy.  However when
entering windows setup, there is no drive to install to, and no floppy
shows up in the usual place to install the drivers.

the installation did succeed when selecting "IDE" as the target disk
instead of the virtio or virtio-SCSI options.

Is there any way to install the drivers after the fact and then change the
disk mode from IDE to virtio?

Is the method on this page
https://www.ovirt.org/documentation/how-to/virtual-machines/create-a-windows-7-virtual-machine/

still relevant?  Looks like they suggest swapping the CD disk once the
windows setup has begun.

Thanks!
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Windows 10 + qemu + Blue Iris = Blue screen

[Michal Skrivanek]

> On 22 Jul 2016, at 22:58, Blaster  wrote:
> 
> 
>> On Jul 22, 2016, at 4:27 AM, Michal Skrivanek  
>> wrote:
>> 
>> 
>>> On 21 Jul 2016, at 20:05, Blaster  wrote:
>>> 
>>> I am running an application called Blue Iris which records video from IP 
>>> cameras.
>>> 
>>> This was working great under Ovirt 3.6.3 + Windows 7.  Now I’ve upgraded to 
>>> Windows 10 and as soon as the Blue Iris service starts, the VM blue screens.
>>> 
>>> I talked to the software vendor, and they said it’s not their problem, they 
>>> aren’t doing anything that could cause a blue screen, so it must be  
>>> driver/memory/hardware problem.  They say the application works just fine 
>>> under Windows 10.
>>> 
>>> So thinking maybe the upgrade went bad, I created a new VM, used e1000 and 
>>> IDE interfaces (i.e., no Virtualized hardware or drivers were used) and 
>>> re-installed Blue Iris.
>> 
>> I would expect better luck with virtio drivers. Either way, if it was 
>> working before and not working in Win10 it’s likely related to drivers. Can 
>> you make sure you try latest drivers? Can you pinpoint the blue screen…to 
>> perhaps USB or other subsystem?
>> Might be worth trying on clean Win10 install just to rule out upgrade issues 
>> (I didn’t understand whether you cloned the old VM and just reinstalled blue 
>> iris or reinstalled everything) , and if it still reproduces it is likely 
>> some low level incompatibility in QEMU/KVM. You would likely have to try 
>> experiment with qemu cmdline or use latest qemu and check the qemu mailing 
>> list
>> 
>> Thanks,
>> michal
> 
> Hi Michal, 
> 
> I did try a clean install.  Both an upgrade and a fresh install cause a blue 
> screen.How do I pin point the blue screen?  I’m guessing it’s a QEMU 
> issue with Win 10.  I’m on Fed 22, how do I get a newer QEMU than what’s in 
> the distribution?  or should I just 
> upgrade to Fedora 24?

Hi,
As the next email in the thread mentions, worth trying different CPU family 
(make sure you dont’ use anything too old due like Conroe), or host CPU 
passthrough.
I would certainly suggest to try the qemu-kvm-rhev/ev since it focuses on 
stability. Try RHEL/CentOS host instead of Fedora. 

Thanks,
michal

> 
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 
> 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Windows 10 + qemu + Blue Iris = Blue screen

[Frank Wall]

On Fri, Jul 22, 2016 at 03:58:56PM -0500, Blaster wrote:
> I did try a clean install.  Both an upgrade and a fresh install cause a blue
> screen. How do I pin point the blue screen?

In my case I could solve this issue by changing the number of (virtual)
CPUs to only 1 for the Windows 10 VM. The Windows 10 VM is running
pretty stable for several months now.

IIRC this is related to the Host CPU or Cluster CPU Type.


Regards
- Frank
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Windows 10 + qemu + Blue Iris = Blue screen

[Blaster]

> On Jul 22, 2016, at 4:27 AM, Michal Skrivanek  
> wrote:
> 
> 
>> On 21 Jul 2016, at 20:05, Blaster  wrote:
>> 
>> I am running an application called Blue Iris which records video from IP 
>> cameras.
>> 
>> This was working great under Ovirt 3.6.3 + Windows 7.  Now I’ve upgraded to 
>> Windows 10 and as soon as the Blue Iris service starts, the VM blue screens.
>> 
>> I talked to the software vendor, and they said it’s not their problem, they 
>> aren’t doing anything that could cause a blue screen, so it must be  
>> driver/memory/hardware problem.  They say the application works just fine 
>> under Windows 10.
>> 
>> So thinking maybe the upgrade went bad, I created a new VM, used e1000 and 
>> IDE interfaces (i.e., no Virtualized hardware or drivers were used) and 
>> re-installed Blue Iris.
> 
> I would expect better luck with virtio drivers. Either way, if it was working 
> before and not working in Win10 it’s likely related to drivers. Can you make 
> sure you try latest drivers? Can you pinpoint the blue screen…to perhaps USB 
> or other subsystem?
> Might be worth trying on clean Win10 install just to rule out upgrade issues 
> (I didn’t understand whether you cloned the old VM and just reinstalled blue 
> iris or reinstalled everything) , and if it still reproduces it is likely 
> some low level incompatibility in QEMU/KVM. You would likely have to try 
> experiment with qemu cmdline or use latest qemu and check the qemu mailing 
> list
> 
> Thanks,
> michal

Hi Michal, 

I did try a clean install.  Both an upgrade and a fresh install cause a blue 
screen.How do I pin point the blue screen?  I’m guessing it’s a QEMU issue 
with Win 10.  I’m on Fed 22, how do I get a newer QEMU than what’s in the 
distribution?  or should I just upgrade to Fedora 24?


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Windows 10 + qemu + Blue Iris = Blue screen

[Michal Skrivanek]

> On 21 Jul 2016, at 20:05, Blaster  wrote:
> 
> I am running an application called Blue Iris which records video from IP 
> cameras.
> 
> This was working great under Ovirt 3.6.3 + Windows 7.  Now I’ve upgraded to 
> Windows 10 and as soon as the Blue Iris service starts, the VM blue screens.
> 
> I talked to the software vendor, and they said it’s not their problem, they 
> aren’t doing anything that could cause a blue screen, so it must be  
> driver/memory/hardware problem.  They say the application works just fine 
> under Windows 10.
> 
> So thinking maybe the upgrade went bad, I created a new VM, used e1000 and 
> IDE interfaces (i.e., no Virtualized hardware or drivers were used) and 
> re-installed Blue Iris.

I would expect better luck with virtio drivers. Either way, if it was working 
before and not working in Win10 it’s likely related to drivers. Can you make 
sure you try latest drivers? Can you pinpoint the blue screen…to perhaps USB or 
other subsystem?
Might be worth trying on clean Win10 install just to rule out upgrade issues (I 
didn’t understand whether you cloned the old VM and just reinstalled blue iris 
or reinstalled everything) , and if it still reproduces it is likely some low 
level incompatibility in QEMU/KVM. You would likely have to try experiment with 
qemu cmdline or use latest qemu and check the qemu mailing list

Thanks,
michal

> 
> Still blue screens.
> 
> How do I go about figuring out what’s causing the blue screen?  
> 
> Thanks….
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Windows 10 + qemu + Blue Iris = Blue screen

[Blaster]

I am running an application called Blue Iris which records video from IP cameras.This was working great under Ovirt 3.6.3 + Windows 7.  Now I’ve upgraded to Windows 10 and as soon as the Blue Iris service starts, the VM blue screens.I talked to the software vendor, and they said it’s not their problem, they aren’t doing anything that could cause a blue screen, so it must be  driver/memory/hardware problem.  They say the application works just fine under Windows 10.So thinking maybe the upgrade went bad, I created a new VM, used e1000 and IDE interfaces (i.e., no Virtualized hardware or drivers were used) and re-installed Blue Iris.Still blue screens.How do I go about figuring out what’s causing the blue screen?  Thanks….___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Windows 10

[Jean-Marie Perron]

Is it planned a development of WDDM driver for Windows 10 fully support with 
SPICE ?

Jean-Marie

De : Sandro Bonazzola [mailto:sbona...@redhat.com]
Envoyé : lundi 14 mars 2016 08:04
À : Jean-Marie Perron <jean-marie.per...@viseo.com>
Cc : Uwe Laverenz <u...@laverenz.de>; users@ovirt.org
Objet : Re: [ovirt-users] Windows 10



On Fri, Mar 11, 2016 at 3:12 PM, Jean-Marie Perron 
<jean-marie.per...@viseo.com<mailto:jean-marie.per...@viseo.com>> wrote:
Hi Uwe,

Thank you for your reply.

I tested versions 0.6, 0.7, 0.11 and 0.12 of qxlwddm. It's always the same.

So, after some investigation, Windows 10 requires the WDDM driver with 3D 
support, and it is not supported by SPICE.
So oVirt Guest Tools supports Windows 10 but SPICE doesn't fully support it.




Jean-Marie

-Message d'origine-
De : users-boun...@ovirt.org<mailto:users-boun...@ovirt.org> 
[mailto:users-boun...@ovirt.org<mailto:users-boun...@ovirt.org>] De la part de 
Uwe Laverenz
Envoyé : vendredi 11 mars 2016 10:49
À : users@ovirt.org<mailto:users@ovirt.org>
Objet : Re: [ovirt-users] Windows 10

Hi,

Am 10.03.2016 um 17:18 schrieb Jean-Marie Perron:
> Hello,
>
> OVirt 3.6.3 is installed on CentOS 7.
>
> I use 64-bit Windows 10 client with spice display.
>
> After installing the spice-guest-tools and oVirt-tools-setup on the VM
> Windows 10, the display always lag and slow.
>
> The display on a Windows 7 VM is fluid.
>
> On Device Manager and Display adapters, I see see the graphics card
> "Red Hat QLX Controller"
>
> Are Windows 10 is fully supported by oVirt?

I haven't tested this but please have a look at the qxlwddm driver here:

https://people.redhat.com/vrozenfe/qxlwddm/


Some people reported that this works for Win 8/8.1/10:

https://bugzilla.redhat.com/show_bug.cgi?id=895356

cu,
Uwe
___
Users mailing list
Users@ovirt.org<mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org<mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users



--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com<http://redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Windows 10

[Sandro Bonazzola]

On Fri, Mar 11, 2016 at 3:12 PM, Jean-Marie Perron <
jean-marie.per...@viseo.com> wrote:

> Hi Uwe,
>
> Thank you for your reply.
>
> I tested versions 0.6, 0.7, 0.11 and 0.12 of qxlwddm. It's always the same.
>

So, after some investigation, Windows 10 requires the WDDM driver with 3D
support, and it is not supported by SPICE.
So oVirt Guest Tools supports Windows 10 but SPICE doesn't fully support it.




>
> Jean-Marie
>
> -Message d'origine-
> De : users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] De la part
> de Uwe Laverenz
> Envoyé : vendredi 11 mars 2016 10:49
> À : users@ovirt.org
> Objet : Re: [ovirt-users] Windows 10
>
> Hi,
>
> Am 10.03.2016 um 17:18 schrieb Jean-Marie Perron:
> > Hello,
> >
> > OVirt 3.6.3 is installed on CentOS 7.
> >
> > I use 64-bit Windows 10 client with spice display.
> >
> > After installing the spice-guest-tools and oVirt-tools-setup on the VM
> > Windows 10, the display always lag and slow.
> >
> > The display on a Windows 7 VM is fluid.
> >
> > On Device Manager and Display adapters, I see see the graphics card
> > "Red Hat QLX Controller"
> >
> > Are Windows 10 is fully supported by oVirt?
>
> I haven't tested this but please have a look at the qxlwddm driver here:
>
> https://people.redhat.com/vrozenfe/qxlwddm/
>
>
> Some people reported that this works for Win 8/8.1/10:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=895356
>
> cu,
> Uwe
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>



-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Windows 10

[Jean-Marie Perron]

Hi Uwe,

Thank you for your reply.

I tested versions 0.6, 0.7, 0.11 and 0.12 of qxlwddm. It's always the same.

Jean-Marie

-Message d'origine-
De : users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] De la part de Uwe 
Laverenz
Envoyé : vendredi 11 mars 2016 10:49
À : users@ovirt.org
Objet : Re: [ovirt-users] Windows 10

Hi,

Am 10.03.2016 um 17:18 schrieb Jean-Marie Perron:
> Hello,
>
> OVirt 3.6.3 is installed on CentOS 7.
>
> I use 64-bit Windows 10 client with spice display.
>
> After installing the spice-guest-tools and oVirt-tools-setup on the VM 
> Windows 10, the display always lag and slow.
>
> The display on a Windows 7 VM is fluid.
>
> On Device Manager and Display adapters, I see see the graphics card 
> "Red Hat QLX Controller"
>
> Are Windows 10 is fully supported by oVirt?

I haven't tested this but please have a look at the qxlwddm driver here:

https://people.redhat.com/vrozenfe/qxlwddm/


Some people reported that this works for Win 8/8.1/10:

https://bugzilla.redhat.com/show_bug.cgi?id=895356

cu,
Uwe
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Windows 10

[Sandro Bonazzola]

On Fri, Mar 11, 2016 at 10:48 AM, Uwe Laverenz  wrote:

> Hi,
>
> Am 10.03.2016 um 17:18 schrieb Jean-Marie Perron:
>
>> Hello,
>>
>> OVirt 3.6.3 is installed on CentOS 7.
>>
>> I use 64-bit Windows 10 client with spice display.
>>
>> After installing the spice-guest-tools and oVirt-tools-setup on the VM
>> Windows 10, the display always lag and slow.
>>
>> The display on a Windows 7 VM is fluid.
>>
>> On Device Manager and Display adapters, I see see the graphics card "Red
>> Hat QLX Controller"
>>
>> Are Windows 10 is fully supported by oVirt?
>>
>
It's supposed to be fully supported.


>
> I haven't tested this but please have a look at the qxlwddm driver here:
>
> https://people.redhat.com/vrozenfe/qxlwddm/
>
>
> Some people reported that this works for Win 8/8.1/10:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=895356



Adding SPICE and WGT relevant people


>
>
> cu,
> Uwe
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>



-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Windows 10

[Uwe Laverenz]

Hi,

Am 10.03.2016 um 17:18 schrieb Jean-Marie Perron:

Hello,

OVirt 3.6.3 is installed on CentOS 7.

I use 64-bit Windows 10 client with spice display.

After installing the spice-guest-tools and oVirt-tools-setup on the VM
Windows 10, the display always lag and slow.

The display on a Windows 7 VM is fluid.

On Device Manager and Display adapters, I see see the graphics card "Red
Hat QLX Controller"

Are Windows 10 is fully supported by oVirt?


I haven't tested this but please have a look at the qxlwddm driver here:

https://people.redhat.com/vrozenfe/qxlwddm/


Some people reported that this works for Win 8/8.1/10:

https://bugzilla.redhat.com/show_bug.cgi?id=895356

cu,
Uwe
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Windows 10

[RK RK]

+1

I am facing the same scenario for Windows 8, 8.1 and 10

On Thu, Mar 10, 2016 at 9:48 PM, Jean-Marie Perron <
jean-marie.per...@viseo.com> wrote:

> Hello,
>
>
>
> OVirt 3.6.3 is installed on CentOS 7.
>
>
>
> I use 64-bit Windows 10 client with spice display.
>
>
>
> After installing the spice-guest-tools and oVirt-tools-setup on the VM
> Windows 10, the display always lag and slow.
>
>
>
> The display on a Windows 7 VM is fluid.
>
>
>
> On Device Manager and Display adapters, I see see the graphics card "Red
> Hat QLX Controller"
>
>
>
> Are Windows 10 is fully supported by oVirt?
>
>
>
> Thank you.
>
>
>
> Jean Marie
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>


-- 

With Regards,
RK,
+91 9840483044
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Windows 10

[Jean-Marie Perron]

Hello,

OVirt 3.6.3 is installed on CentOS 7.

I use 64-bit Windows 10 client with spice display.

After installing the spice-guest-tools and oVirt-tools-setup on the VM Windows 
10, the display always lag and slow.

The display on a Windows 7 VM is fluid.

On Device Manager and Display adapters, I see see the graphics card "Red Hat 
QLX Controller"

Are Windows 10 is fully supported by oVirt?

Thank you.

Jean Marie
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Windows 10

[Michal Skrivanek]

> On 30 Nov 2015, at 07:45, Koen Vanoppen <vanoppen.k...@gmail.com> wrote:
> 
> And which settings are you using for the vm?
> 
> Kind regards,
> 
> Koen
> 
> On 27 November 2015 at 14:37, Raymond <raym...@raymondwortel.nl> wrote:
> I use Win10 since 3.5.4 on CentOS6
> 
> Today I upgraded to 3.5.5 -> 3.6
> Tried it and boots previous machine fine, installs new machine also fine

note you need Intel Westmere or newer CPU
And in some builds we block AMD…which seem to be working fine (G2 onwards). You 
can allow that in osinfo config file

Thanks,
michal

> 
> kind regards
> Raymond
> 
> 
> 
> From: "Koen Vanoppen" <vanoppen.k...@gmail.com>
> To: "Yaniv Dary" <yd...@redhat.com>
> Cc: "users" <users@ovirt.org>
> Sent: Friday, November 27, 2015 7:14:11 AM
> Subject: Re: [ovirt-users] Windows 10
> 
> Thanks!
> 
> On 26 November 2015 at 16:27, Yaniv Dary <yd...@redhat.com> wrote:
> Windows 10 guest will only work on 3.6 with fedora or el7.2 hosts. Might work 
> with el6 as some point. but currently doesn't.
> 
> Yaniv Dary
> Technical Product Manager
> Red Hat Israel Ltd.
> 34 Jerusalem Road
> Building A, 4th floor
> Ra'anana, Israel 4350109
> 
> Tel : 
> +972 (9) 7692306
> 
> 8272306
> Email: 
> yd...@redhat.com
> 
> IRC : ydary
> 
> 
> On Tue, Oct 6, 2015 at 8:53 AM, Koen Vanoppen <vanoppen.k...@gmail.com> wrote:
> Dear all,
> 
> Yes, onther question :-). This time it's about windows 10.
> I'm running ovirt 3.5.4 and I don't manage to install windows 10 on it. Keeps 
> giving me a blue screen (yes, I know, it's still a windows... ;-) ) on reboot.
> 
> Are there any special settings you need to enable when creating the vm? Which 
> OS do I need to select? Or shall I just wait untile the relase of ovirt 3.6 
> :-) ?
> 
> Kind regards,
> 
> Koen
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 
> 
> 
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Windows 10

[Koen Vanoppen]

And which settings are you using for the vm?

Kind regards,

Koen

On 27 November 2015 at 14:37, Raymond <raym...@raymondwortel.nl> wrote:

> I use Win10 since 3.5.4 on CentOS6
>
> Today I upgraded to 3.5.5 -> 3.6
> Tried it and boots previous machine fine, installs new machine also fine
>
> kind regards
> Raymond
>
>
>
> --
> *From: *"Koen Vanoppen" <vanoppen.k...@gmail.com>
> *To: *"Yaniv Dary" <yd...@redhat.com>
> *Cc: *"users" <users@ovirt.org>
> *Sent: *Friday, November 27, 2015 7:14:11 AM
> *Subject: *Re: [ovirt-users] Windows 10
>
> Thanks!
>
> On 26 November 2015 at 16:27, Yaniv Dary <yd...@redhat.com> wrote:
>
>> Windows 10 guest will only work on 3.6 with fedora or el7.2 hosts. Might
>> work with el6 as some point. but currently doesn't.
>>
>> Yaniv Dary
>> Technical Product Manager
>> Red Hat Israel Ltd.
>> 34 Jerusalem Road
>> Building A, 4th floor
>> Ra'anana, Israel 4350109
>>
>> Tel : +972 (9) 7692306
>> 8272306
>> Email: yd...@redhat.com
>> IRC : ydary
>>
>>
>> On Tue, Oct 6, 2015 at 8:53 AM, Koen Vanoppen <vanoppen.k...@gmail.com>
>> wrote:
>>
>>> Dear all,
>>>
>>> Yes, onther question :-). This time it's about windows 10.
>>> I'm running ovirt 3.5.4 and I don't manage to install windows 10 on it.
>>> Keeps giving me a blue screen (yes, I know, it's still a windows... ;-) )
>>> on reboot.
>>>
>>> Are there any special settings you need to enable when creating the vm?
>>> Which OS do I need to select? Or shall I just wait untile the relase of
>>> ovirt 3.6 :-) ?
>>>
>>> Kind regards,
>>>
>>> Koen
>>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Windows 10

[Raymond]

I use Win10 since 3.5.4 on CentOS6 

Today I upgraded to 3.5.5 -> 3.6 
Tried it and boots previous machine fine, installs new machine also fine 

kind regards 
Raymond 




From: "Koen Vanoppen" <vanoppen.k...@gmail.com> 
To: "Yaniv Dary" <yd...@redhat.com> 
Cc: "users" <users@ovirt.org> 
Sent: Friday, November 27, 2015 7:14:11 AM 
Subject: Re: [ovirt-users] Windows 10 

Thanks! 

On 26 November 2015 at 16:27, Yaniv Dary < yd...@redhat.com > wrote: 



Windows 10 guest will only work on 3.6 with fedora or el7.2 hosts. Might work 
with el6 as some point. but currently doesn't. 

Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109

Tel : +972 (9) 7692306 8272306
Email: yd...@redhat.com IRC : ydary 

On Tue, Oct 6, 2015 at 8:53 AM, Koen Vanoppen < vanoppen.k...@gmail.com > 
wrote: 

BQ_BEGIN

Dear all, 

Yes, onther question :-). This time it's about windows 10. 
I'm running ovirt 3.5.4 and I don't manage to install windows 10 on it. Keeps 
giving me a blue screen (yes, I know, it's still a windows... ;-) ) on reboot. 

Are there any special settings you need to enable when creating the vm? Which 
OS do I need to select? Or shall I just wait untile the relase of ovirt 3.6 :-) 
? 

Kind regards, 

Koen 

___ 
Users mailing list 
Users@ovirt.org 
http://lists.ovirt.org/mailman/listinfo/users 






BQ_END



___ 
Users mailing list 
Users@ovirt.org 
http://lists.ovirt.org/mailman/listinfo/users 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Windows 10

[Koen Vanoppen]

Thanks!

On 26 November 2015 at 16:27, Yaniv Dary  wrote:

> Windows 10 guest will only work on 3.6 with fedora or el7.2 hosts. Might
> work with el6 as some point. but currently doesn't.
>
> Yaniv Dary
> Technical Product Manager
> Red Hat Israel Ltd.
> 34 Jerusalem Road
> Building A, 4th floor
> Ra'anana, Israel 4350109
>
> Tel : +972 (9) 7692306
> 8272306
> Email: yd...@redhat.com
> IRC : ydary
>
>
> On Tue, Oct 6, 2015 at 8:53 AM, Koen Vanoppen 
> wrote:
>
>> Dear all,
>>
>> Yes, onther question :-). This time it's about windows 10.
>> I'm running ovirt 3.5.4 and I don't manage to install windows 10 on it.
>> Keeps giving me a blue screen (yes, I know, it's still a windows... ;-) )
>> on reboot.
>>
>> Are there any special settings you need to enable when creating the vm?
>> Which OS do I need to select? Or shall I just wait untile the relase of
>> ovirt 3.6 :-) ?
>>
>> Kind regards,
>>
>> Koen
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Windows 10

[Yaniv Dary]

Windows 10 guest will only work on 3.6 with fedora or el7.2 hosts. Might
work with el6 as some point. but currently doesn't.

Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109

Tel : +972 (9) 7692306
8272306
Email: yd...@redhat.com
IRC : ydary


On Tue, Oct 6, 2015 at 8:53 AM, Koen Vanoppen 
wrote:

> Dear all,
>
> Yes, onther question :-). This time it's about windows 10.
> I'm running ovirt 3.5.4 and I don't manage to install windows 10 on it.
> Keeps giving me a blue screen (yes, I know, it's still a windows... ;-) )
> on reboot.
>
> Are there any special settings you need to enable when creating the vm?
> Which OS do I need to select? Or shall I just wait untile the relase of
> ovirt 3.6 :-) ?
>
> Kind regards,
>
> Koen
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Windows 10

[Koen Vanoppen]

Dear all,

Yes, onther question :-). This time it's about windows 10.
I'm running ovirt 3.5.4 and I don't manage to install windows 10 on it.
Keeps giving me a blue screen (yes, I know, it's still a windows... ;-) )
on reboot.

Are there any special settings you need to enable when creating the vm?
Which OS do I need to select? Or shall I just wait untile the relase of
ovirt 3.6 :-) ?

Kind regards,

Koen
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users