Windows 7 x64 HVM and error 07B - how to change scsi controller type - 4.0RC3

[happymeal00]

Qubes OS version:

4.0 RC3

Affected TemplateVMs:

StandaloneVM (Windows 7 HVM)

---

Steps to reproduce the behavior:

when booting an existing Windows 7 x64 systems exported from VirtualBox, the system hangs with BSOD error 0x0000007B.
I have tried to follow suggested changes by enabling other scsi controllers by booting back into Virtual box and as explained here: http://www.justandrew.net/2009/10/stop-0x0000007b-on-p2vd-windows-7.html but nothing has changed.

While looking at xen logs written in /var/log/xen/console/guest--dm.log i can see that passed scsi controller is a mptsas1068 controller for which my Windows system doesn't have any 64 bit driver.

Expected behavior:

normal boot of the Windows x64 HVM machine and recognition of the associated storage controller/ attached disks

Actual behavior:

BSOD just after boot before loading all *.sys system drivers.
BSOD error number is 0x0000007B

General notes:

I have tried to understand how to pass a diffrent scsi controller (lsi for instance) but it's unclear for me where to set this in the libvirt template. Directly in the xen.xml template file or in the block.xml template file? under what section and which syntax to be used?

---

Related issues:

[happymeal00]

I found a bypass solution for this problem by booting back the vm into virtualbox and by enabling the following registry keyword responsible for the load of the scsi mptsas1060 controller:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LSI_SAS key:Start value:0 (0 meaning to be loaded).

As a general solution i believe it would make sense to provide a way to edit (either temporary or permanently) a template configuration file allowing the choiche between available qemu emulated controller.

[happymeal00]

I found a bypass solution for this problem by booting back the vm into virtualbox and by enabling the following registry keyword responsible for the load of the scsi mptsas1060 controller:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LSI_SAS key:Start value:0 (0 meaning to be loaded).

As a general solution i believe it would make sense to provide a way to edit (either temporary or permanently) a template configuration file allowing the choiche between available qemu emulated controller.