Fwd: VirtIO and BSOD On Windows Server 2003

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jun 4, 2013 at 7:55 AM, Aaron Clausen <mightymartianca@xxxxxxxxx> wrote:
> On Tue, Jun 4, 2013 at 7:29 AM, Vadim Rozenfeld <vrozenfe@xxxxxxxxxx> wrote:
>>
>> If IDE works fine, try adding another disk as virtio and see it the secondary
>> disk works smoothly as well.
>
> That's what I did, and the instant the virtio block driver initialized
> in BSODed on me with 0x0000007f (reason code 0x805000f). According to
> Microsoft "this problem occurs because the NTFS driver incorrectly
> locks the resource when the NTFS driver tries to access the resource."
>
> I've attempted to start the guest with the virtio driver cache
> disabled, but with no success.

As a further bit of disclosure, I'm using raw images right now. I'm
going to convert one of my Server 2003 guests to qcow2 and see if that
makes a difference.


--
Aaron Clausen
mightymartianca@xxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux