From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vadim Rozenfeld Subject: Re: VirtIO and BSOD On Windows Server 2003 Date: Tue, 4 Jun 2013 08:29:55 -0400 (EDT) Message-ID: <569146573.11161903.1370348995129.JavaMail.root@redhat.com> References: <20130604121050.GA10055@stefanha-thinkpad.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: Aaron Clausen , kvm@vger.kernel.org To: Stefan Hajnoczi Return-path: Received: from mx3-phx2.redhat.com ([209.132.183.24]:39396 "EHLO mx3-phx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751733Ab3FDM34 (ORCPT ); Tue, 4 Jun 2013 08:29:56 -0400 In-Reply-To: <20130604121050.GA10055@stefanha-thinkpad.redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: ----- Original Message ----- From: "Stefan Hajnoczi" To: "Aaron Clausen" Cc: kvm@vger.kernel.org, vrozenfe@redhat.com Sent: Tuesday, June 4, 2013 10:10:50 PM Subject: Re: VirtIO and BSOD On Windows Server 2003 On Mon, Jun 03, 2013 at 09:56:41AM -0700, Aaron Clausen wrote: > I recently built a new kvm server with Debian Wheezy which comes with > KVM 1.1.2 and when I moved this guest over, I immediately started > getting BSODs (0x0000007). I disabled virtio block driver and then > attempted to upgrade to the latest with no luck. Stop code 0x7b "Inaccessible boot device"? How did you create the guest on the new server? Perhaps the hardware configuration changed - I suggest trying to make it as close to the original guest as possible (including the same PCI slots). Stefan It usually happens when system unable to find a bootable device. Check qemu options, you probably missed something. Vadim.