It is likely that guest stops to receive interrupt. I met this issue in
debuging
in kernel PIC patch. The normal reason is that a previous irq injection
fails (IDT_Vectoring valid). It seems currnet KVM handling to
IDT_Vectoring
doesn't cover all situation.
(The in Kernel PIC patch will try to
On Mon, 2007-06-18 at 12:09 +0300, Avi Kivity wrote:
Rusty Russell wrote:
On Sun, 2007-06-17 at 17:25 +0300, Avi Kivity wrote:
Rusty Russell wrote:
+ /* Set up for reply. */
+ vblk-sg[0].page = virt_to_page(vbr-in_hdr);
+ vblk-sg[0].offset = offset_in_page(vbr-in_hdr);
+
Bugs item #1739503, was opened at 2007-06-19 10:27
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1739503group_id=180599
Please note that this message will contain a full copy of
Baruch Even wrote:
I'm using KVM 28 and when I'm trying to reboot the guest vm kvm fails
with the following message:
Can you be more specific as to what you're doing? what host cpu,
bitness, guest OS, bitness, actions to reproduce?
--
error compiling committee.c: too many arguments to
Anthony Liguori wrote:
In debugging a virtbench bug on KVM, I seemed to uncover some weird
behaviors with gettimeofday() and KVM with newer kernels.
The attached program will run a tight loop of code a certain number of
times and measure it's duration with gettimeofday(). With a stock
Anthony Liguori wrote:
How are you doing clockevents?
Right now, I'm relying on the PIT but it would be nice to eliminate
that. I'd like to move to something PV so that I can make use of
tickless guest kernels. I'm very open to suggestion and even more open
to reusing other
David Brown wrote:
Okay there's another centrino duo issue I've run across.
Also, finally got a setup where I can get console dumps from kvm :) so
I should be able to provide much better debugging information.
This happens when I try to tftpboot from and etherboot image and
install either
Richard Hughes wrote:
On Sun, 2007-06-17 at 11:10 +0300, Avi Kivity wrote:
I posted a patchset which does just that, when the F kernel
integrates
it (through inclusion of 2.6.23 or by patching the current kernel),
Fedora will be able to suspend/resume just fine.
I've tried the
Kamble, Nitin A wrote:
Hi Avi,
Attached is a small patch to emit little bit more information when
emulcation reaches cannot_emulate:.
The patch looks fine to the scripts/checkpatch.pl. It show not look to
you in the DOS format, unless something in between us is changing the
format of
Kamble, Nitin A wrote:
Hi Avi,
Patch implementing the pop reg, opcodes 0x58-0x5f attached. It
has passed the checkpatch.pl test. And you should not see any CRLF
characters in the attachment.
I did get it in dos format. I guess I'll just have to live with it.
Applied thanks.
--
Kamble, Nitin A wrote:
The patch attached to this email.
Hi Avi,
Attached is a patch implementing the instruction ret opcode 0xc3.
Please Comment/Apply.
Applied, thanks.
--
error compiling committee.c: too many arguments to function
On Tue, 2007-06-19 at 10:44 +0300, Avi Kivity wrote:
Anthony Liguori wrote:
How are you doing clockevents?
Right now, I'm relying on the PIT but it would be nice to eliminate
that. I'd like to move to something PV so that I can make use of
tickless guest kernels. I'm
Rusty Russell wrote:
On Mon, 2007-06-18 at 12:09 +0300, Avi Kivity wrote:
Rusty Russell wrote:
On Sun, 2007-06-17 at 17:25 +0300, Avi Kivity wrote:
Rusty Russell wrote:
+ /* Set up for reply. */
+ vblk-sg[0].page = virt_to_page(vbr-in_hdr);
+
Adam Monsen wrote:
I had just installed a Windows XP guest and left it running for a few
hours with no users logged in. The machine appears to have crashed.
Avi requested that I send this bug(?) report to kvm-devel, so here
'tis...
REPRO STEPS:
1. Install Fedora 7
2. Install KVM
3.
- rebased to latest master
- added latest 6 patches from Gregory
the smp patches gave birth to a nice lockless inter-vcpu signalling
system, I'll try to reuse that for lapic.
--
error compiling committee.c: too many arguments to function
Avi Kivity wrote:
Baruch Even wrote:
I'm using KVM 28 and when I'm trying to reboot the guest vm kvm fails
with the following message:
Can you be more specific as to what you're doing? what host cpu,
bitness, guest OS, bitness, actions to reproduce?
The host CPU is Intel Core Duo,
Avi Kivity wrote:
- rebased to latest master
- added latest 6 patches from Gregory
My AMD machine seems happy with it. I'll start picking stuff into mainline.
--
error compiling committee.c: too many arguments to function
Avi Kivity wrote:
Avi Kivity wrote:
- rebased to latest master
- added latest 6 patches from Gregory
My AMD machine seems happy with it. I'll start picking stuff into
mainline.
Spoke too soon. Things are broken.
--
error compiling committee.c: too many arguments to function
On Tue, 2007-06-19 at 13:29 +0300, Avi Kivity wrote:
Avi Kivity wrote:
Avi Kivity wrote:
- rebased to latest master
- added latest 6 patches from Gregory
My AMD machine seems happy with it. I'll start picking stuff into
mainline.
Spoke too soon. Things are broken.
Do you
Gregory Haskins wrote:
On Tue, 2007-06-19 at 13:29 +0300, Avi Kivity wrote:
Avi Kivity wrote:
Avi Kivity wrote:
- rebased to latest master
- added latest 6 patches from Gregory
My AMD machine seems happy with it. I'll start picking stuff into
mainline.
On Tue, 2007-06-19 at 11:05 +0300, Avi Kivity wrote:
Richard Hughes wrote:
On Sun, 2007-06-17 at 11:10 +0300, Avi Kivity wrote:
I posted a patchset which does just that, when the F kernel
integrates
it (through inclusion of 2.6.23 or by patching the current kernel),
Fedora will be
On Tue, 2007-06-19 at 08:33 -0400, Jeremy Katz wrote:
On Tue, 2007-06-19 at 11:05 +0300, Avi Kivity wrote:
Richard Hughes wrote:
On Sun, 2007-06-17 at 11:10 +0300, Avi Kivity wrote:
I posted a patchset which does just that, when the F kernel
integrates
it (through inclusion of
Hi all,
I am a newbie for KVM testing.
Now I meet a problem in testing, that it seems there isn't a simple and
effective way to judge if a Qemu is using KVM modules or doing pure Qemu
operations.
Checking how many reference of kvm.ko by lsmod is a way, but would meet trouble
when creating
Avi Kivity wrote:
Anthony Liguori wrote:
It's pretty erratic. If I run if a few times at any rate, sometimes
I get 0.0 and sometimes I get a more sane result.
I expect the newer kernel is sometimes disqualifying the timestamp
counter from being used as a clocksource. Running pinned to a
You, Yongkang wrote:
Hi all,
I am a newbie for KVM testing.
Now I meet a problem in testing, that it seems there isn't a simple and
effective way to judge if a Qemu is using KVM modules or doing pure Qemu
operations.
Checking how many reference of kvm.ko by lsmod is a way, but would
A non-programmatic way is to look at the SDL banner window (assuming you
are using SDL and not VNC or gfx disabled). When you are using KVM it
will say QEMU/KVM.
(WARNING: hack alert) A programmatic way would be to check the /proc
filesystem for the pid of the QEMU process for open references
to
Anthony Liguori wrote:
Avi Kivity wrote:
Anthony Liguori wrote:
It's pretty erratic. If I run if a few times at any rate, sometimes
I get 0.0 and sometimes I get a more sane result.
I expect the newer kernel is sometimes disqualifying the timestamp
counter from being used as a
I am a newbie for KVM testing.
Now I meet a problem in testing, that it seems there isn't a simple and
effective way to judge if a Qemu is using KVM modules or doing pure Qemu
operations.
Checking how many reference of kvm.ko by lsmod is a way, but would meet
trouble when creating multi KVM
A non-programmatic way is to look at the SDL banner window (assuming you
are using SDL and not VNC or gfx disabled). When you are using KVM it
will say QEMU/KVM.
It would be troublesome if doing auto testing. :)
(WARNING: hack alert) A programmatic way would be to check the /proc
filesystem
Gregory Haskins wrote:
Halting in userspace requires a relatively cumbersome mechanism to signal the
halted VCPU. Implementing halt in kernel should be relatively straight
forward and it eliminates the need for the signaling
Merging this one in, found some nits:
+/*
* This function
Anthony Liguori wrote:
It's less stable then I thought.
less stable? less unstable?
You were right btw, the guest is deciding the TSC is too unreliable.
It happens every once and while (although the taskset/no pm timer
combination helps a whole lot).
Well, the guest is right too.
Avi Kivity wrote:
Anthony Liguori wrote:
It's less stable then I thought.
less stable? less unstable?
It didn't fix the problem :-)
You were right btw, the guest is deciding the TSC is too unreliable.
It happens every once and while (although the taskset/no pm timer
combination
On Tue, 2007-06-19 at 17:48 +0300, Avi Kivity wrote:
Gregory Haskins wrote:
Halting in userspace requires a relatively cumbersome mechanism to signal
the
halted VCPU. Implementing halt in kernel should be relatively straight
forward and it eliminates the need for the signaling
Hello,
I've tried to diff kvm-28 qemu directory with qemu 0.9.0 and I see that
some files in the kvm sources have the content of the file duplicated,
f.ex. qemu/hw/mips_int.c has it's own content twice in the kvm tree, it
only has it once in qemu as it should be. Look for the include
Jeremy Fitzhardinge wrote:
+.read = read_hyper,
+.mask = CLOCKSOURCE_MASK(64),
+.mult = 1,
+.shift = 0,
It would be better to use a scale and shift here, so that adjtime has
something to work
When the old value and new one are the same the emulator skips the
write; this is undesiderable when the destination is a MMIO area and the
write shall be performed regardless of the previous value. This
optimization breaks e.g. a Linux guest APIC compiled without
X86_GOOD_APIC.
Remove the check
Il Mon, Jun 18, 2007 at 02:32:39PM +0300, Avi Kivity ha scritto:
Unfortunately, this kills Windows XP (first run with a guest crash,
second with a host oops), so I reverted it. I'd guess some operation
which doesn't need writeback ends up in the modified code.
Previously, the check
On 6/19/07, Baruch Even [EMAIL PROTECTED] wrote:
Hello,
I've tried to diff kvm-28 qemu directory with qemu 0.9.0 and I see that
some files in the kvm sources have the content of the file duplicated,
f.ex. qemu/hw/mips_int.c has it's own content twice in the kvm tree, it
only has it once in
Luca wrote:
On 6/19/07, Baruch Even [EMAIL PROTECTED] wrote:
Hello,
I've tried to diff kvm-28 qemu directory with qemu 0.9.0 and I see that
some files in the kvm sources have the content of the file duplicated,
f.ex. qemu/hw/mips_int.c has it's own content twice in the kvm tree, it
only has
Anthony Liguori wrote:
I've updated this patch and switched to using a scale/shift like Xen
is doing, but I must admit, I don't understand how it helps adjtime.
I poked around a bit and it wasn't obvious.
Why is having {mult=122, shift=22} better for adjtime than {mult=1,
shift=0}?
I don't
Jeremy Fitzhardinge wrote:
Anthony Liguori wrote:
I've updated this patch and switched to using a scale/shift like Xen
is doing, but I must admit, I don't understand how it helps adjtime.
I poked around a bit and it wasn't obvious.
Why is having {mult=122, shift=22} better for adjtime
Avi Kivity wrote:
+static void kvm_pte_clear(struct mm_struct *mm,
+ unsigned long addr, pte_t *ptep)
+{
+pte_t pte = {0};
Surely there's a nice macro for creating a pte from an int?
Perhaps my grep'ing skills are weak, but I don't seem to see any. Were
you thinking of
Anthony Liguori wrote:
Perhaps my grep'ing skills are weak, but I don't seem to see any.
Were you thinking of something in particular?
__pte(), of course. Sheesh. ;)
J
-
This SF.net email is sponsored by DB2
Jeremy Fitzhardinge wrote:
Anthony Liguori wrote:
Perhaps my grep'ing skills are weak, but I don't seem to see any.
Were you thinking of something in particular?
__pte(), of course. Sheesh. ;)
How could I have missed something that is so clearly named! :-)
Regards,
Anthony Liguori wrote:
I don't see a compelling reason to paravirtualize earlier although I
also don't see a compelling reason not too. I noticed that VMI hooks
setup.c. It wasn't immediately obvious why it was hooking there but
perhaps it worthwhile to have a common hook? I suspect VMI
Jeremy Fitzhardinge wrote:
Well, I was suggesting we could print the banner later rather than
forcing an earlier init.
The important part is that you set your pv_ops before patching occurs,
since that will bake the function calls into the rest of the kernel, and
it will ignore any further
On 6/19/07, Avi Kivity [EMAIL PROTECTED] wrote:
[...]
The virtual machine has spontaneously rebooted, then failed because
Windows has (legitimately) overwritten the real-mode task state segment
located at the end of memory. The emulation failure is for an 'out'
instruction, which will trap if
47 matches
Mail list logo
