On Thursday 12 April 2007 17:38, Avi Kivity wrote:
> > But wouldn't it also be possible to create a file in
> > userspace and pass its descriptor to kvm?
[...]
> swap, hugetlbfs, and maybe other nifty stuff. I think I know how to do
> this for the current mmu, but I'm worried that it will have a
Hello Folks
I am trying to get kvm going on my bleeding edge kubuntu system (feisty).
the normal apt-get install kvm does not work as the 2.6.20 kernel is missing
kvm-api-9
So I grabbed kvm-18 source from sourceforge together with the kernel
2.6.21-rc6
make etc works
but when starting kvm or
Bugs item #1699695, was opened at 2007-04-12 22:07
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1699695&group_id=180599
Please note that this message will contain a full copy
>Li, Xin B wrote:
>>> If the git: and svn: protocols are blocked for you, I can
>try to make them available through http.
>>>
>> That would be helpful, thanks!
>> -Xin
>>
>
>http://www.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git, branch
>avi/master
>
>Subversion is not yet available.
We al
On Thu, Apr 12, 2007 at 04:44:14PM -0400, Andrey Dmitriev wrote:
> A) (more of a comment); Windows 2000 server stalls on "installing
> devices", running with
> kvm -had vdisk.win2k -m 256 -cdrom win2k.iso -no-kvm (a restart of a
> previously hung setup)
I would suggest installing win2k with kqe
Info: running latest debian (kvm-modules-2.6.18-4-amd64)
A) (more of a comment); Windows 2000 server stalls on "installing
devices", running with
kvm -had vdisk.win2k -m 256 -cdrom win2k.iso -no-kvm (a restart of a
previously hung setup)
B) if Win2K worked, is there are a (easy) way to xfer my
Arjan van de Ven wrote:
> On Thu, 2007-04-12 at 10:05 -0500, Anthony Liguori wrote:
>
>> Why not drive the backend from userspace?
>>
>
> (nothing in the concept requires it to be in the kernel, it just makes
> things a lot easier)
>
> Because I think the trend forward is to reduce the use
On Thu, 2007-04-12 at 10:05 -0500, Anthony Liguori wrote:
> Arjan van de Ven wrote:
> >>> the pv block driver is in Ingo's -rt tree if you want to look at it.
> >>>
> >> Glad to know you made it to his tree :)
> >> When do you think it can be integrated to mainline kvm?
> >>
> >
> > the
>>> On Thu, Apr 12, 2007 at 10:14 AM, in message <[EMAIL PROTECTED]>,
Avi Kivity <[EMAIL PROTECTED]> wrote:
>
> It's really subtle.
>
> With respect to interrupts, VT^H^Hthe hardware provides an override over
> IF. If an interrupt happens while this override is enabled, we exit
> guest mode r
Laurent Vivier wrote:
> Avi Kivity wrote:
>
>> Michael Riepe wrote:
>>
>>> Hi!
>>>
>>> This is just a (probably silly) idea I had the other day. Currently, the
>>> guest's memory is allocated inside the kernel and exported to userspace
>>> via mmap(). But wouldn't it also be possible to cre
Avi Kivity wrote:
> Michael Riepe wrote:
>> Hi!
>>
>> This is just a (probably silly) idea I had the other day. Currently, the
>> guest's memory is allocated inside the kernel and exported to userspace
>> via mmap(). But wouldn't it also be possible to create a file in
>> userspace and pass its des
Michael Riepe wrote:
> Hi!
>
> This is just a (probably silly) idea I had the other day. Currently, the
> guest's memory is allocated inside the kernel and exported to userspace
> via mmap(). But wouldn't it also be possible to create a file in
> userspace and pass its descriptor to kvm? If we also
Hi!
This is just a (probably silly) idea I had the other day. Currently, the
guest's memory is allocated inside the kernel and exported to userspace
via mmap(). But wouldn't it also be possible to create a file in
userspace and pass its descriptor to kvm? If we also pass file offset
and length par
Arjan van de Ven wrote:
> the biggest gap left is how to associate the virtual file with the host.
> Once I've figured that it's ready to go imo.
>
You mean connecting the backend with the host file? Maybe an ioctl()
with an fd argument?
--
error compiling committee.c: too many arguments t
David Abrahams wrote:
> on Thu Apr 12 2007, Anthony Liguori
> wrote:
>
>
>> David Abrahams wrote:
>>
>>> No, this doesn't happen with -no-kvm
>>>
>>> X Error of failed request: BadValue (integer parameter out of range for
>>> operation)
>>> Major opcode of failed request: 136 (XFree8
Arjan van de Ven wrote:
>>> the pv block driver is in Ingo's -rt tree if you want to look at it.
>>>
>> Glad to know you made it to his tree :)
>> When do you think it can be integrated to mainline kvm?
>>
>
> the biggest gap left is how to associate the virtual file with the host.
>
on Thu Apr 12 2007, Anthony Liguori
wrote:
> David Abrahams wrote:
>> No, this doesn't happen with -no-kvm
>>
>> X Error of failed request: BadValue (integer parameter out of range for
>> operation)
>> Major opcode of failed request: 136 (XFree86-VidModeExtension)
>> Minor opcode of fail
on Thu Apr 12 2007, Avi Kivity
wrote:
> qemu is getting cpu time, but not calling into kvm.
>
> I'll try to reproduce this locally, right now I'm completely bewildered
> by this.
FYI, if I listen to the radio in windows media player, I don't see the
effect. KVM will take 18% or so of the CPU
> >
> >the pv block driver is in Ingo's -rt tree if you want to look at it.
>
> Glad to know you made it to his tree :)
> When do you think it can be integrated to mainline kvm?
the biggest gap left is how to associate the virtual file with the host.
Once I've figured that it's ready to go imo.
David Abrahams wrote:
> on Thu Apr 12 2007, Avi Kivity
> wrote:
>
>
>> There is a workaround:
>>
>> My Computer -> Properties -> Hardware -> Device Manager -> [Whatever's
>> under
>> Computer, unless it's "Standard PC"] -> Properties -> Update Driver ->
>> Not at this time -> Next -> Install
on Thu Apr 12 2007, Avi Kivity
wrote:
> There is a workaround:
>
> My Computer -> Properties -> Hardware -> Device Manager -> [Whatever's
> under
> Computer, unless it's "Standard PC"] -> Properties -> Update Driver ->
> Not at this time -> Next -> Install
> from a list -> Next -> Don't searc
David Abrahams wrote:
> No, this doesn't happen with -no-kvm
>
> X Error of failed request: BadValue (integer parameter out of range for
> operation)
> Major opcode of failed request: 136 (XFree86-VidModeExtension)
> Minor opcode of failed request: 10 (XF86VidModeSwitchToMode)
> Value in
on Thu Apr 12 2007, "Dor Laor"
wrote:
>>When I start my Windows VM with -no-kvm, it seems to boot much more
>>quickly than without. Also there's a long period, right after the VM
>>changes its screen resolution from the 640x480 used for Windows' boot
>>screen to 1280x1024, where the VM's scree
No, this doesn't happen with -no-kvm
X Error of failed request: BadValue (integer parameter out of range for
operation)
Major opcode of failed request: 136 (XFree86-VidModeExtension)
Minor opcode of failed request: 10 (XF86VidModeSwitchToMode)
Value in failed request: 0x363
Seria
David Abrahams wrote:
> on Thu Apr 12 2007, Avi Kivity
> wrote:
>
>
>> David Abrahams wrote:
>>
>>> When I start my Windows VM with -no-kvm, it seems to boot much more
>>> quickly than without.
>>>
>> You probably have acpi enabled in Windows. This causes massive
>> slowdowns i
on Thu Apr 12 2007, Avi Kivity
wrote:
> David Abrahams wrote:
>> When I start my Windows VM with -no-kvm, it seems to boot much more
>> quickly than without.
>
> You probably have acpi enabled in Windows. This causes massive
> slowdowns in kvm; the real fix will unfortunately require you to
Gregory Haskins wrote:
>
>> Ah, ok -- I misunderstood the whole thing. The way to avoid the race is
>> to disable interrupts before entering the guest. This way the IPI is
>> delayed until you enter guest mode:
>>
>> irq_disable();
>>
>> spin_lock();
>> vcpu- >guest_mode = 1;
>>
Tomasz Chmielewski wrote:
> As I understand, fully virtualized KVM guests (on Intel VT or AMD-V) can
> perform with near native speeds only when it comes to the CPU - because
> the things like network or block device are basically emulated.
>
>
> Among many changes, KVM in 2.6.21 has "Initial par
David Abrahams wrote:
> on Thu Apr 12 2007, Avi Kivity
> wrote:
>
>
>> David Abrahams wrote:
>>
>>
>>
>>
> Newsflash: yes, it does. The VM keeps using cycles at a normal rate
> even when not on a visible workspace. This problem appears to be
> KVM-specific.
>
>>>
David Abrahams wrote:
> When I start my Windows VM with -no-kvm, it seems to boot much more
> quickly than without.
You probably have acpi enabled in Windows. This causes massive
slowdowns in kvm; the real fix will unfortunately require you to upgrade
your hardware.
There is a workaround:
M
When I start my Windows VM with -no-kvm, it seems to boot much more
quickly than without. Also there's a long period, right after the VM
changes its screen resolution from the 640x480 used for Windows' boot
screen to 1280x1024, where the VM's screen goes all white. Is this
all normal?
--
Dave
>When I start my Windows VM with -no-kvm, it seems to boot much more
>quickly than without. Also there's a long period, right after the VM
>changes its screen resolution from the 640x480 used for Windows' boot
>screen to 1280x1024, where the VM's screen goes all white. Is this
>all normal?
I thi
I have attached a new version of the patch which eliminates the condition
variable (if only by name, anyway ;)
>>> On Thu, Apr 12, 2007 at 8:49 AM, in message <[EMAIL PROTECTED]>,
Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>
> Actually, I am in favor of having well- defined synchronization
> pri
Gregory Haskins wrote:
>>>
>>>
>> If you want condition variables, activate your cryogenically- cooled suit
>> and post on it on lkml. This cannot be added to the kernel via kvm.
>>
>
> Hehe. I wasn't aware of the contention surrounding them but that does
> explain why they are n
>> When the APIC/PIC will reside in the kernel we can pass to direct
mode
>> only.
>> Expect to publish the driver in the May.
>>
>> Arjan van de Ven from RedHat is working on pv block device.
>> Status is unknown.
>>
>
>I'm sorry but I'm from Intel, not Red Hat.
Opss, I thought you and Ingo work
> When the APIC/PIC will reside in the kernel we can pass to direct mode
> only.
> Expect to publish the driver in the May.
>
> Arjan van de Ven from RedHat is working on pv block device.
> Status is unknown.
>
I'm sorry but I'm from Intel, not Red Hat.
the pv block driver is in Ingo's -rt tre
>>> On Thu, Apr 12, 2007 at 4:02 AM, in message <[EMAIL PROTECTED]>,
Avi Kivity <[EMAIL PROTECTED]> wrote:
> Gregory Haskins wrote:
>> Hi All,
>> Attached are the first three patches in my queue. The first two you are
> likely familiar with at this point (though I have made some more of the
Tomasz Chmielewski wrote:
>>>
>>> What is the state of these PV drivers now? Is it usable on Linux now?
>>>
>>
>> We (Qumranet) have Linux paravirtual network support working, but not
>> ready for general consumption yet.
>
> Hmm, is the "general consumption" of the network support a matter of
David Abrahams wrote:
>>> Newsflash: yes, it does. The VM keeps using cycles at a normal rate
>>> even when not on a visible workspace. This problem appears to be
>>> KVM-specific.
>>>
>>>
>> Amazing.
>>
>> Can you strace a hung vm and post the log?
>>
>
> If you can tell me
on Wed Apr 11 2007, Avi Kivity wrote:
> David Abrahams wrote:
>> on Wed Apr 11 2007, David Abrahams
>> wrote:
>>
>>
Does qemu behave differently if you use -no-kvm?
>>> Haven't tried that one yet.
>>>
>>
>> Newsflash: yes, it does. The VM keeps using cycles at a norma
Tomasz Chmielewski wrote:
> Is it decided if these PV drivers will be open source/free, or rather
> have commercial model?
We are planning to open source all the drivers but we are still looking at the
legal aspects of opening a MS DDK based code, hopefully we'll have answers
shortly. The Windo
Avi Kivity schrieb:
> Tomasz Chmielewski wrote:
>> As I understand, fully virtualized KVM guests (on Intel VT or AMD-V)
>> can perform with near native speeds only when it comes to the CPU -
>> because the things like network or block device are basically emulated.
>>
>>
>> Among many changes, KV
>As I understand, fully virtualized KVM guests (on Intel VT or AMD-V)
can
>perform with near native speeds only when it comes to the CPU - because
>the things like network or block device are basically emulated.
>
>
>Among many changes, KVM in 2.6.21 has "Initial paravirtualization
>support, which
Tomasz Chmielewski wrote:
> As I understand, fully virtualized KVM guests (on Intel VT or AMD-V) can
> perform with near native speeds only when it comes to the CPU - because
> the things like network or block device are basically emulated.
>
>
> Among many changes, KVM in 2.6.21 has "Initial par
As I understand, fully virtualized KVM guests (on Intel VT or AMD-V) can
perform with near native speeds only when it comes to the CPU - because
the things like network or block device are basically emulated.
Among many changes, KVM in 2.6.21 has "Initial paravirtualization
support, which has
Leslie Mann wrote:
Avi Kivity <[EMAIL PROTECTED]> writes:
Please test the attached patch, against kvm-17. This is subversion
revision 4546 and git commit c01571ed56754dfea458cc37d553c360082411a1.
Fails.
I notice that a lot of new code is related to pio. Seeing that it locks up wh
On Thu, Apr 12, 2007 at 11:02:25AM +0300, Avi Kivity wrote:
> If you want condition variables, activate your cryogenically-cooled suit
> and post on it on lkml. This cannot be added to the kernel via kvm.
Better just rip it out. The code would be a lot simpler with opencoded
waitqueue use, and
Gregory Haskins wrote:
> Hi All,
> Attached are the first three patches in my queue. The first two you are
> likely familiar with at this point (though I have made some more of the
> requested changes to 02-irqdevice.patch). The last item
> (03-preemptible-cpu.patch) adds an implementation t
48 matches
Mail list logo
