ok,
patched kvm-33, compile, install
i started qemu-system-x86_64 with "-no-rtc -use-hpet" and ... well the
time drift is unchanged. ok, the warning for "dev.rtc..." has gone.
doing a date (guest) gives me (for example):
8:08:59
after 10 (real!) seconds, date (guest) gives me
8:09:04
--> 10
On Tue, Aug 07, 2007 at 02:53:01PM -0700, Dor Laor wrote:
> Actually we're in the middle of developing pci pass through support
> for enabling physical device pass through for guests. It's work in
> progress but eventually we'll post the code to the list.
Cool. Are you relying on an isolation-ca
[EMAIL PROTECTED] wrote:
> Hello Dor,
>
> Thank you so much for the quick reply.
>
> My project is to run a qnx4.4 legacy application (which talks
> to custom made hardware) on virtualized environment. I am
> using KVM for that and am able to read and write to the actual
> hardware. I used serial
Avi Kivity wrote:
> Daniel P. Berrange wrote:
>> On Tue, Aug 07, 2007 at 07:10:17AM +0300, Avi Kivity wrote:
>>
>>> Anthony Liguori wrote:
>>>
I don't think adding annotations as snapshots is the right
approach. I think proper support should be added in the header. I
wouldn
Hello Dor,
Thank you so much for the quick reply.
My project is to run a qnx4.4 legacy application (which talks to custom made
hardware) on virtualized environment. I am using KVM for that and am able to
read and write to the actual hardware. I used serial driver in qemu as a
reference to dev
Daniel P. Berrange wrote:
> On Tue, Aug 07, 2007 at 07:10:17AM +0300, Avi Kivity wrote:
>
>> Anthony Liguori wrote:
>>
>>> I don't think adding annotations as snapshots is the right approach. I
>>> think proper support should be added in the header. I wouldn't be too
>>> concerned with
Daniel Paquet wrote:
> Hello Devs!
>
> On my haste to try new patches and stuff I got this error message
> looping and using 100% cpu when starting vista as guest.
>
> My host is a linux 2.6.22.1-cfs-v19 #1 SMP
>
> So I have the cfs scheduler patchs in.
>
> I have build kvm-33 on this new kernel.
>Hello Dor,
>
>Can you please point to an example that injects interrupts via
userspace
>?
>
>I am running QNX as Guest and Linux as Host. One of my QNX application
>(Guest application), expects an interrupt from the Hardware.
>
>Now as I understand this, I need to write a driver on the host side t
Hello Dor,
Can you please point to an example that injects interrupts via userspace ?
I am running QNX as Guest and Linux as Host. One of my QNX application (Guest
application), expects an interrupt from the Hardware.
Now as I understand this, I need to write a driver on the host side to get t
Il Tue, Aug 07, 2007 at 02:08:08PM +0200, Luca ha scritto:
> On 8/7/07, Dor Laor <[EMAIL PROTECTED]> wrote:
> > Luca claims the HPET intefer the RTC. Can it be disabled? ( I know some
> > new chipsets implement rtc using HPET).
>
> Basically HPET can operate in legacy mode - where it uses the sam
I wrote:
> It's almost as if migrate_write() is being called after
> migrate_finish() ??
Yes, I'm definitely seeing this -- migrate_finish followed by
migrate_write, which causes a segfault (and explains my truncated
images). Unfortunately I'm not at all familiar with this code, and
all the qemu
Hello Devs!
On my haste to try new patches and stuff I got this error message looping
and using 100% cpu when starting vista as guest.
My host is a linux 2.6.22.1-cfs-v19 #1 SMP
So I have the cfs scheduler patchs in.
I have build kvm-33 on this new kernel.
I dont get this get_dirty_pages retur
>>> Basically HPET can operate in legacy mode - where it uses the same
>>> IRQ as the RTC (and RTC won't deliver any interrupt) - or in
>>> "standard" mode where the IO-APIC can be configured to deliver the
>>> interrupt on any line. ATM Linux can only use the legacy mode.
>>> You can of course dis
[EMAIL PROTECTED] wrote:
>>> Luca claims the HPET intefer the RTC. Can it be disabled? ( I know
>>> some new chipsets implement rtc using HPET).
>>
>> Basically HPET can operate in legacy mode - where it uses the same
>> IRQ as the RTC (and RTC won't deliver any interrupt) - or in
>> "standard" mo
On Tue, Aug 07, 2007 at 07:10:17AM +0300, Avi Kivity wrote:
> Anthony Liguori wrote:
> > I don't think adding annotations as snapshots is the right approach. I
> > think proper support should be added in the header. I wouldn't be too
> > concerned with breaking compatibility in qcow2. That's w
> We're experiencing guest clock drifts even when the host is running with
> HZ=1000.
> But so far there were no performance problmes around it.
> It's worth a shot anyway.
>
are there any benchmarkings (and tools) which i can run inside the
guest? are there any official results with which i ca
>> Luca claims the HPET intefer the RTC. Can it be disabled? ( I know
>some
>> new chipsets implement rtc using HPET).
>
>Basically HPET can operate in legacy mode - where it uses the same IRQ
>as the RTC (and RTC won't deliver any interrupt) - or in "standard"
>mode where the IO-APIC can be config
well there are running some "default F7 daemons".
yum-updatesd (python)
setroubleshootd (python)
hald
...
but no process is really running, when doing a "htop" i the processor
has a load of 0.7%
what is the "efer_reload"?
while i'm writing this email i have kvm_stat in another shell in the
back
On 8/7/07, Dor Laor <[EMAIL PROTECTED]> wrote:
> Luca claims the HPET intefer the RTC. Can it be disabled? ( I know some
> new chipsets implement rtc using HPET).
Basically HPET can operate in legacy mode - where it uses the same IRQ
as the RTC (and RTC won't deliver any interrupt) - or in "standa
>today morning i compiled kvm-33 and the output of kvm-stat is much
>better now (guest in idle):
>
>kvm statistics
>
> efer_reload 109442736504
> exits137226886967
> halt_exits1084344 935
> invlpg 0 0
> io_exits 76689145070
> irq_exits 2788
On 8/7/07, Ulrich Schreiner <[EMAIL PROTECTED]> wrote:
> Could not configure '/dev/rtc' to have a 1024 Hz timer. This is not a
> fatal
> error, but for better emulation accuracy either use a 2.6 host Linux
> kernel or
> type 'echo 1024 > /proc/sys/dev/rtc/max-user-freq' as root.
>
> well i HAVE a 2
today morning i compiled kvm-33 and the output of kvm-stat is much
better now (guest in idle):
kvm statistics
efer_reload 109442736504
exits137226886967
halt_exits1084344 935
invlpg 0 0
io_exits 76689145070
irq_exits 27886 2
kvm: qemu: add qemu command line option -no-kvm-irqchip
This option disables in-kernel irqchip (PIC/IOAPIC/LAPIC) and uses
qemu interrupt controllers in userspace instead.
Signed-off-by: Qing He <[EMAIL PROTECTED]>
---
qemu/qemu-kvm.c |4
qemu/vl.c |5 +
kvm: libkvm: export a new function to disable irqchip creation
Signed-off-by: Qing He <[EMAIL PROTECTED]>
Signed-off-by: Yaozu (Eddie) Dong <[EMAIL PROTECTED]>
---
user/kvmctl.c | 25 ++---
user/kvmctl.h | 10 ++
2 files changed, 28 insertions(+), 7
He, Qing wrote:
> kvm: qemu: fix a possible deadlock situation in save/restore
>
> If a VM using userspace irqchip is saved when it's in HLT state,
> and is restored to use the in-kernel irqchip, the HLT state flag
> is also restored. This HLT flag in userspace HLT handling pre
>no ideas what can be done? why it is so slow?
Let's try to catch the cause for the 74k ioexits per second.
Please add #define DEBUG_IOPORT in qemu/vl.c and qemu/exec.c and
recompile.
After that when the guest runs and does 74k ioexits on idle, enter the
qemu's monitor (ctrl-alt-1)
enter 'log iopo
no ideas what can be done? why it is so slow?
i've tried the "-L /usr/shar/kvm" to use the kvm-bios but no better
performance ...
Am Donnerstag, den 02.08.2007, 11:24 +0300 schrieb Avi Kivity:
> Ulrich Schreiner wrote:
> > dmesg|grep kvm
> >
> > SELinux: initialized (dev kvmfs, type kvmfs), uses
27 matches
Mail list logo
