From: Dor Laor <dor.laor@qumranet.com>
To: "Jiang, Yunhong" <yunhong.jiang@intel.com>
Cc: kvm-devel@lists.sourceforge.net, Avi Kivity <avi@qumranet.com>
Subject: Re: Windows PV driver for KVM
Date: Wed, 14 May 2008 10:11:25 +0300 [thread overview]
Message-ID: <1210749085.24261.767.camel@localhost.localdomain> (raw)
In-Reply-To: <391BF3CDD2DC0848B40ACB72FA97AD59035AA574@pdsmsx413.ccr.corp.intel.com>
On Wed, 2008-05-14 at 08:55 +0800, Jiang, Yunhong wrote:
> Hi, Dor, I just checked the URL and seems it is not updated still,
> willyou update it?
Avi, since it passed regression, we can release it (also with the .pdb
file).
>
> -- Yunhong Jiang
>
> Dor Laor <mailto:dor.laor@qumranet.com> wrote:
> > On Wed, 2008-05-07 at 21:17 +0800, Jiang, Yunhong wrote:
> >> Avi Kivity <mailto:avi@qumranet.com> wrote:
> >>> Jiang, Yunhong wrote:
> >>>> I noticed there is a windows PV driver based on virtIO in
> >>>> http://sourceforge.net/project/showfiles.php?group_id=180599
> >>>>
> >>>> But when I enable the driver in guest, the guest will hang. I'm
> using
> >>>> changeset around April, 18. Since the driver is created in March, I
> >>>> assume the changeset in Apri should be ok.
> >>>>
> >>>> Are there any special action needed to enable the PV driver in
> windows?
> >>>> Have anyone tried it recently?
> >>>>
> >>>
> >>> We are using it in production. What HAL is the guest using? Are
> you
> >>> running with smp?
> >>
> >> The HAL is ACPI multipprocessor PC.
> >> It is a UP guest. But I do notice one thing strange. When I use
> device
> >> manager->Processors, I see a lot of CPU listed. But it is really a UP
> >> system and I can only get one cpu in the task manager->performance
> >> window. Not sure if that's the reason of the hang.
> >>
> >
> > We just fixed an smp bug for virtio (also triggered by single
> processor
> > with ACPI multiprocessor HAL). We'll publish a new binary tomorrow.
> >
> > The reason you see multiple cpus although there is only one is that we
> > expose the maximum number in the bios. The system is actually uses the
> > required number so this behavior is ok.
> >
> >
> >> -- Yunhong Jiang
> >>
> >>>
> >>> --
> >>> Any sufficiently difficult bug is indistinguishable from a feature.
> >>
> >>
> > ---------------------------------------------------------------
> > ----------
> >> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> >> Don't miss this year's exciting event. There's still time to save
> $100.
> >> Use priority code J8TL2D2.
> >>
> > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.
> > sun.com/javaone
> >> _______________________________________________
> >> kvm-devel mailing list
> >> kvm-devel@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/kvm-devel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-05-14 7:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 8:47 Windows PV driver for KVM Jiang, Yunhong
2008-04-30 20:04 ` Avi Kivity
2008-05-07 13:17 ` Jiang, Yunhong
2008-05-11 21:06 ` Dor Laor
2008-05-12 0:24 ` Jiang, Yunhong
2008-05-14 0:55 ` Jiang, Yunhong
2008-05-14 7:11 ` Dor Laor [this message]
2008-05-15 2:09 ` Jiang, Yunhong
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=1210749085.24261.767.camel@localhost.localdomain \
--to=dor.laor@qumranet.com \
--cc=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=yunhong.jiang@intel.com \
/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