From: Vadim Rozenfeld <vrozenfe@redhat.com>
To: Alon Levy <alevy@redhat.com>
Cc: Carlos Rodrigues <cmar@eurotux.com>, kvm@vger.kernel.org
Subject: Re: Problem after update windows VirtIO drivers
Date: Mon, 9 Dec 2013 21:24:02 -0500 (EST) [thread overview]
Message-ID: <1488140279.34434310.1386642242307.JavaMail.root@redhat.com> (raw)
In-Reply-To: <52A5F3AC.3090705@redhat.com>
----- Original Message -----
From: "Alon Levy" <alevy@redhat.com>
To: "Carlos Rodrigues" <cmar@eurotux.com>, kvm@vger.kernel.org, "Vadim Rozenfeld" <vrozenfe@redhat.com>
Sent: Tuesday, December 10, 2013 3:45:32 AM
Subject: Re: Problem after update windows VirtIO drivers
On 12/09/2013 04:45 PM, Carlos Rodrigues wrote:
> Hello,
>
> After update the VirtIO drivers for Windows Server 2008 R2 64-bit, when
> i reboot virtual machine, the windows OS get stuck on loading bar.
>
> The VirtIO drivers is the latest stable that i made the download from
> http://alt.fedoraproject.org/pub/alt/virtio-win/stable/virtio-win-0.1-74.iso
>
> And i use version 1.2.1 of kvm and the OS of host is Centos 5.8.
>
> I try to install a fresh and clean version same Windows and same drivers
> and get the same problem. With virtio-win-0.1-52 version of drivers, the
> windows server works properly.
>
> I will use the oldest stable version of drivers, but anyone knows some
> issue with latest drivers?
>
[VR]
Hi Carlos,
Could you please post the QEMU command line as well as output
from 'info pci'
I have an issue that also existed with 0.65, on windows 7 64 bit: when I
have qxl enabled as well I get a crash shortly after initialization of
qxl (at the login screen) in a memory management function of the qxl
driver, indicating something overwrote parts of the allocators
accounting structures. When I disable the virtio driver (leaving the
virtio device) the problem goes away.
Vadim, is this a known problem? (sorry for hijacking the thread)
Does it crash into BSOD? Can you share the crash dump file?
Best regards,
Vadim.
> Regards,
>
next prev parent reply other threads:[~2013-12-10 2:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 14:45 Problem after update windows VirtIO drivers Carlos Rodrigues
2013-12-09 16:45 ` Alon Levy
2013-12-09 20:13 ` Cole Robinson
2013-12-10 2:24 ` Vadim Rozenfeld [this message]
2013-12-10 12:28 ` Carlos Rodrigues
2013-12-11 8:26 ` Vadim Rozenfeld
2013-12-11 9:46 ` Carlos Rodrigues
2013-12-11 10:07 ` Vadim Rozenfeld
2013-12-11 12:16 ` Carlos Rodrigues
2013-12-13 10:25 ` Vadim Rozenfeld
2013-12-13 14:35 ` Carlos Rodrigues
2013-12-13 21:30 ` Vadim Rozenfeld
2013-12-17 9:43 ` Carlos Rodrigues
2013-12-29 10:09 ` Vadim Rozenfeld
2013-12-10 13:29 ` Alon Levy
2013-12-11 9:27 ` Vadim Rozenfeld
2013-12-11 12:40 ` Alon Levy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1488140279.34434310.1386642242307.JavaMail.root@redhat.com \
--to=vrozenfe@redhat.com \
--cc=alevy@redhat.com \
--cc=cmar@eurotux.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox