On Wednesday 05 March 2008 19:35:40 Yang, Sheng wrote:
> On Wednesday 05 March 2008 17:15:29 Ingo Molnar wrote:
> > * Yang, Sheng <[EMAIL PROTECTED]> wrote:
> > > + val &= 0xff;
> > > + addr &= 3;
> >
> > magic constants.
>
> I will update these constants. :) In fact, I have thought of these befor
Yang, Sheng wrote:
> Here is the updated patch. I kept 0xff because I think it's OK for understand
> easily. :)
>
>
Any news on the regression with older Linux guests? That's the only
thing keeping my from applying the patchset.
--
Do not meddle in the internals of kernels, for they are s
> Very Nice. Must be KVM-63.
>
>
>> - merge qemu-cvs
>>- new curses display option
>>
>qemu -curses
I'm Sorry, but it doesn't works.
[EMAIL PROTECTED]:~> /usr/local/bin/qemu-system-x86_64 -curses
/usr/local/bin/qemu-system-x86_64: invalid option -- '-curses'
Alexey Eremenko wrote:
>
> > Very Nice. Must be KVM-63.
> >
> >
> >> - merge qemu-cvs
> >>- new curses display option
> >>
> >qemu -curses
>
> I'm Sorry, but it doesn't works.
>
> [EMAIL PROTECTED]:~> /usr/local/bin/qemu-system-x86_64 -curses
>
> /usr/local/bin/qemu-system-x86_64: invali
>It probably wasn't configured. Do you have the devel package installed?
You are correct - it wasn't configured.
The problem is - I have the package (ncurses-devel) installed, but it is not
detected.
KVM's "./configure" scripts skips it.
But it works on my Fedora machine.
I have a big problem
On Thursday 06 March 2008 16:06:51 Avi Kivity wrote:
> Yang, Sheng wrote:
> > Here is the updated patch. I kept 0xff because I think it's OK for
> > understand easily. :)
>
> Any news on the regression with older Linux guests? That's the only
> thing keeping my from applying the patchset.
Not muc
Fix a bug when using "--no-kvm-irqchip".
---
libkvm/libkvm-x86.c |9 +
qemu/hw/i8254.c | 12
qemu/qemu-kvm.c |4
qemu/qemu-kvm.h |2 ++
qemu/vl.c | 11 ++-
5 files changed, 33 insertions(+), 5 deletions(-)
diff --git a/libkv
Hi all,
we are running an winxp client as kvm guest (with vnc option) all day long
(license management software). So automatic windows updates are activated.
On MS patch days steadily the guest hangs on automatic reboot, until one
connect with vnc to it. Instantly and without any user action the
On Thu, Mar 06, 2008 at 12:32:58AM -0800, Alexey Eremenko wrote:
>
>I have a big problem with ncurses - once the VM enters Graphics Mode, it
>cannot be killed
>with start Linux command: "ctrl+C" - tried from KDE Konsole. It can be
>killed only using "kill".
using xterm over pekwm
>using xterm over pekwm (which traps "alt+2") I can use for that "esc+2"
> qemu> quit
>konsole probably works with the default key bindings for the qemu console
under curses which is "alt+2".
Yes, Thanks Carlo, that worked.
Another problem, is that most standard OSes (including most Linux dist
* Yang, Sheng <[EMAIL PROTECTED]> wrote:
> + /* Though spec said the state of 8254 is undefined after power-up,
> + * seems some tricky OS like Windows XP depends on IRQ0 interrupt
> + * when booting up.
> + * So here setting initialize rate for it, and not a specific number */
> * We only need to hook operations that are MMU writes. We hook these so
> that
> * we can use lazy MMU mode to batch these operations. We could probably
> * improve the performance of the host code if we used some of the
> information
> @@ -219,6 +359,9 @@ static void paravirt_ops_setup(void)
> p
On Thursday 06 March 2008 17:14:34 Ingo Molnar wrote:
> * Yang, Sheng <[EMAIL PROTECTED]> wrote:
> > + /* Though spec said the state of 8254 is undefined after power-up,
> > +* seems some tricky OS like Windows XP depends on IRQ0 interrupt
> > +* when booting up.
> > +* So here settin
This is the first release of block and network drivers for Linux guests
running on a kvm host. The drivers are intended for guest kernels
2.6.18-2.6.24. Newer kernels include the drivers; older kernels may not
work. kvm-61 or later is needed in the host.
Network throughput is around 1 Gbit/s
Zhao Forrest wrote:
>> * We only need to hook operations that are MMU writes. We hook these so
>> that
>> * we can use lazy MMU mode to batch these operations. We could probably
>> * improve the performance of the host code if we used some of the
>> information
>> @@ -219,6 +359,9 @@ static void pa
Thomas Besser wrote:
> Hi all,
>
> we are running an winxp client as kvm guest (with vnc option) all day long
> (license management software). So automatic windows updates are activated.
>
> On MS patch days steadily the guest hangs on automatic reboot, until one
> connect with vnc to it. Instantly
Hi Anthony.
> The attached patch implements AIO support for the virtio backend so if this
> is the case, you should see the proper proportions.
First, thank you very much for making the patch.
I ran the same test program on KVM with the patch but I wasn't able to
get good results.
I checked the
* Yang, Sheng <[EMAIL PROTECTED]> wrote:
> > another silly style nit, the canonical comment style is:
> > > + /*
> > > + * Though spec said the state of 8254 is undefined after power-up,
> > > + * seems some tricky OS like Windows XP depends on IRQ0 interrupt
> > > + * when booting up.
> > > +
Avi Kivity wrote:
> Glauber Costa wrote:
>> Use the lower 3 lower bits of the system time msr to turn off the clock.
>> This means that all clock registration has to be aligned in a 4-byte
>> boundary
>>
>>
>
> 3 bits -> 8 bytes.
dohh!! true
/me ashamed.
> How about just using just bit 0 as a
"H. Peter Anvin" <[EMAIL PROTECTED]> writes:
> Avi Kivity wrote:
>> H. Peter Anvin wrote:
>>> Just for fun, I tried to boot OS/2 Warp 4.0 under KVM (KVM-59 with the
>>> latest git kernel from Linus as of yesterday, slightly post
>>> 2.6.24-rc8.)I found that it crashes very early, apparently b
Avi Kivity wrote:
> Glauber Costa wrote:
>> Apart from the fact that it will break every single guest out there,
>> that's ok. As I said: these things are so early, that maybe we can pay
>> this price. Your call.
>>
>
> Which guests? kvmclock is only in kvm.git, and I don't think any distro
Thomas Besser wrote:
> Avi Kivity wrote:
>
>> Thomas Besser wrote:
>>
>>> Is that a feature or a bug? Any hints to solve this problem?
>>>
>> Strange.
>>
>> What kvm version are you using?
>>
>
> Ups, sorry for forgetting this: I am using kvm-52 in a productive
> environment. Ho
On 3/6/08, Avi Kivity <[EMAIL PROTECTED]> wrote:
> This is the first release of block and network drivers for Linux guests
> running on a kvm host. The drivers are intended for guest kernels
> 2.6.18-2.6.24. Newer kernels include the drivers; older kernels may not
> work. kvm-61 or later is n
Dor Laor wrote:
> On Wed, 2008-03-05 at 17:10 -0600, Anthony Liguori wrote:
>
>> Dor Laor wrote:
>>
>>> Seems to work reliably with kvm, should do the same trick for lguest.
>>> You can download it from
>>> git://kvm.qumranet.com/home/dor/src/kvm-guest-drivers-linux
>>>
>>> Anthony, you can
Very nice !
1. How about releasing those in ISO format instead (or in addition
to...) tarballs?
2. I have a problem compiling it.
"make sync LINUX=." fails.
I have read the README:
"Where /path/to/kernel is the path to a recent kernel tree containing virtio
drivers. At the moment, this must be
On Thursday 06 March 2008 16:43:18 Yang, Sheng wrote:
> On Thursday 06 March 2008 16:06:51 Avi Kivity wrote:
> > Yang, Sheng wrote:
> > > Here is the updated patch. I kept 0xff because I think it's OK for
> > > understand easily. :)
> >
> > Any news on the regression with older Linux guests? That'
Be a dream lover simply by clicking here-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
> On 3/6/08, Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>> This is the first release of block and network drivers for Linux guests
>> running on a kvm host. The drivers are intended for guest kernels
>> 2.6.18-2.6.24. Newer kernels include the drivers; older kernels may not
>> work. kvm-61 o
Avi Kivity wrote:
> Thomas Besser wrote:
>> Is that a feature or a bug? Any hints to solve this problem?
>
> Strange.
>
> What kvm version are you using?
Ups, sorry for forgetting this: I am using kvm-52 in a productive
environment. Host ist Debian etch, debs are self backported from unstable.
K
Glauber Costa wrote:
> Apart from the fact that it will break every single guest out there,
> that's ok. As I said: these things are so early, that maybe we can pay
> this price. Your call.
>
Which guests? kvmclock is only in kvm.git, and I don't think any distro
is based on that.
--
Do n
> @@ -1219,53 +1229,75 @@ static void nonpaging_prefetch_page(struct kvm_vcpu
> *vcpu,
>
> static void mmu_free_roots(struct kvm_vcpu *vcpu)
> {
> - int i;
> + int i, j;
>struct kvm_mmu_page *sp;
>
> - if (!VALID_PAGE(vcpu->arch.mmu.root_hpa))
> - return;
Hi Zhao,
On Thu, Mar 06, 2008 at 09:15:59PM +0800, Zhao Forrest wrote:
> > @@ -1219,53 +1229,75 @@ static void nonpaging_prefetch_page(struct kvm_vcpu
> > *vcpu,
> >
> > static void mmu_free_roots(struct kvm_vcpu *vcpu)
> > {
> > - int i;
> > + int i, j;
> >struct kvm_mmu_pa
On Thursday 06 March 2008 04:01:53 pm Jun Koi wrote:
> On 3/6/08, Avi Kivity <[EMAIL PROTECTED]> wrote:
> > This is the first release of block and network drivers for Linux guests
> > running on a kvm host. The drivers are intended for guest kernels
> > 2.6.18-2.6.24. Newer kernels include the
Marcelo Tosatti wrote:
>>
>> Here CR3_TARGET_VALUEx is written.
>> My question is:
>> 1 why is vmcs_writel(CR3_TARGET_VALUE0 + idx*2, cr3); called by
>> vmx_set_cr3(), but not called by mmu_free_roots()?
>>
>
> By clearing guest_cr3 entry of the shared area we avoid the guest from
> using it.
Use LSB of the address passed through the msr to enable/disable
the clock. Setting it to 1 enables it, setting it to 0 disables it.
As the guest data structures are aligned anyway, this
won't be a problem, as this bit is free.
Guest is changed accordingly
Signed-off-by: Glauber Costa <[EMAIL PRO
Avi,
Hope this is better
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
_
replace hv_clock vector in kvmclock with a percpu variable
that is cacheline aligned.
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
arch/x86/kernel/kvmclock.c |9 +
1 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/arch/x86/kernel/kvmclock.c b/arch/x86/kernel/kvmcl
On Wed, Feb 27, 2008 at 03:42:42PM -0800, Roland Dreier wrote:
> >
> http://git.kernel.org/?p=linux/kernel/git/viro/vfs-2.6.git;a=commit;h=49be4f8114e6ff0efdab10ebba2493fb67bc3034
>
> Actually, looking closer at the kvm changes here, I think that
> create_vcpu_fd() needs the same treatment as kv
On Wed, Feb 27, 2008 at 11:16:02AM -0800, Roland Dreier wrote:
> The anonymous inodes interface anon_inode_getfd() calls fd_install()
> for the newly created fd, which does not work for some use cases where
> the caller must do futher initialization before exposing the file to
> userspace. This is
Alexey Eremenko wrote:
> Very nice !
>
> 1. How about releasing those in ISO format instead (or in addition
> to...) tarballs?
>
It's not a bad idea. What we really need is for people to submit
spec/deb files for older distros. Then it's a matter of compiling those
RPMs/debs and putting the
Balaji Rao wrote:
>> Excellent, thanks!
>>
>> Just 1 question: Above is the instruction for guest. How about the
>> host? Dont we need to install anything??
>>
>> I suppose that qemu in the latest kvm package already supported
>> virtio, but I think we need some support from host kernel as well?
>>
Ryo Tsuruta wrote:
> Hi Anthony.
>
>
>> The attached patch implements AIO support for the virtio backend so if this
>> is the case, you should see the proper proportions.
>>
>
> First, thank you very much for making the patch.
> I ran the same test program on KVM with the patch but I wasn
Anthony Liguori wrote:
> Cam Macdonell wrote:
>> Hello,
>>
>> Is it possible to share a memory (a page perhaps) between the host and
>> guest?
>
> Yes, the host always has access to all of the guests memory. All of the
> virtio drivers depend on this fact. With KVM, the userspace (in this
> c
This patch writes 0 (actually, what really matters is that the
LSB is cleared) to the system time msr before rebooting/shutting down
the machine.
Without it, we can have a random memory location being written
when the guest comes back
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
arch/x86
Hi greg,
When I remove only the kvm-intel module without removing the kvm module itself,
I get an error saying that a kobject is
trying to be reinitialized. Its because of the fact that kvm reuses a kobject
in kvm_init when calling sysdev_register.
This patch fixes kobject_cleanup by marking t
On Thu, Mar 06, 2008 at 10:23:18PM +0530, Balaji Rao wrote:
> Hi greg,
>
> When I remove only the kvm-intel module without removing the kvm
> module itself, I get an error saying that a kobject is trying to be
> reinitialized. Its because of the fact that kvm reuses a kobject in
> kvm_init when ca
On Thursday 06 March 2008 10:35:14 pm Greg KH wrote:
> Where exactly in the code does that happen? kobjects should not be
> "reused" as that implies that they are static, and not dynamically
> allocated, right?
>
> Which kobject is this?
Yes, its static. Here's the code from virt/kvm_main.c:1269
On Thu, Mar 06, 2008 at 11:20:50PM +0530, Balaji Rao wrote:
> On Thursday 06 March 2008 10:35:14 pm Greg KH wrote:
>
> > Where exactly in the code does that happen? kobjects should not be
> > "reused" as that implies that they are static, and not dynamically
> > allocated, right?
> >
> > Which ko
I will be off-line (and sometimes off-piste) from March 8 through March
15. I may have sporadic Internet access.
Andrew, should kvm.git not play nicely with the rest of the children,
have it stand in the corner.
--
error compiling committee.c: too many arguments to function
This is a note to let you know that I've just added the patch titled
Subject: kobjects: mark cleaned up kobjects as unitialized
to my gregkh-2.6 tree. Its filename is
kobjects-mark-cleaned-up-kobjects-as-unitialized.patch
This tree can be found at
http://www.kernel.org/pub/linu
Greetings,
I'm running vanilla-sources-2.6.24.3 with KVM-63 on a Thinkpad T61p running
Gentoo Linux. I'm having some trouble with a corporate rollout of WinXP into
a KVM image. My company uses WinPE in order to do the rollout, after firing
up KVM (via command: kvm -hda $HOME/winxp.img -boot c -std
Avi Kivity wrote:
>
>> The thing I'm trying to get at is a quantitative statement about why
>> moving the pit into the kernel is the right thing. I'll try to give
>> the patches a try myself in the next couple of days. I don't think
>> it's obvious that it's the right thing to do without some
On Thu, 2008-03-06 at 14:56 -0600, Anthony Liguori wrote:
> Avi Kivity wrote:
> >
> >> The thing I'm trying to get at is a quantitative statement about why
> >> moving the pit into the kernel is the right thing. I'll try to give
> >> the patches a try myself in the next couple of days. I don't
On Thu, 2008-03-06 at 14:17 -0500, [EMAIL PROTECTED] wrote:
> Greetings,
>
> I'm running vanilla-sources-2.6.24.3 with KVM-63 on a Thinkpad T61p
> running Gentoo Linux. I'm having some trouble with a corporate rollout
> of WinXP into a KVM image. My company uses WinPE in order to do the
> rollout
On Thu, Mar 6, 2008 at 4:43 PM, Dor Laor <[EMAIL PROTECTED]> wrote:
>
> How did you got the winxp.img? Is it by installing cd over kvm or
> v2v /p2v?
>
My company has a Linux livecd which they use to prime the laptop with, as
the company offers the choice of a Linux installation. I chose WinXP an
Avi Kivity wrote:
> > This is the first release of block and network drivers for Linux guests
> > running on a kvm host. The drivers are intended for guest kernels
> > 2.6.18-2.6.24. Newer kernels include the drivers; older kernels may not
> > work. kvm-61 or later is needed in the host.
Tr
>
> Can you try -no-kvm just to see if qemu succeeds?
> >
>
>
Ok, I've recompiled with gcc-3 and I used the -no-kvm option. I got the same
result, but in 5x the amount of time. No joy. How do I get at that kvm_stat?
Thanks!
-jesse
---
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2008-03-06 16:53]:
> >
> > Can you try -no-kvm just to see if qemu succeeds?
> > >
> >
> >
> Ok, I've recompiled with gcc-3 and I used the -no-kvm option. I got the same
> result, but in 5x the amount of time. No joy. How do I get at that kvm_stat?
> Thanks!
On Thu, Mar 06, 2008 at 04:44:26PM +0200, Avi Kivity wrote:
> Marcelo Tosatti wrote:
> >>
> >>Here CR3_TARGET_VALUEx is written.
> >>My question is:
> >>1 why is vmcs_writel(CR3_TARGET_VALUE0 + idx*2, cr3); called by
> >>vmx_set_cr3(), but not called by mmu_free_roots()?
> >>
> >
> >By clearing
On Thu, Mar 6, 2008 at 6:19 PM, Ryan Harper <[EMAIL PROTECTED]> wrote:
>
> (dethklok) kvm-63 % ./kvm_stat
> Please mount debugfs ('mount -t debugfs debugfs /sys/kernel/debug')
> and ensure the kvm modules are loaded
> (dethklok) kvm-61 % sudo mount -t debugfs debugfs /sys/kernel/debug
>
> then run
Iain Paton <[EMAIL PROTECTED]> writes:
> Trying to build against 2.6.24 gives the following:
>
> CC [M] /root/kvm/kvm-guest-drivers-linux-1/virtio_net.o
> /root/kvm/kvm-guest-drivers-linux-1/virtio_net.c: In function 'receive_skb':
> /root/kvm/kvm-guest-drivers-linux-1/virtio_net.c:101: error
61 matches
Mail list logo