Dong, Eddie wrote:
I think #2. Synchronization will be difficult; we'll need to send
signals to all other vcpus so that they drop the vcpu mutex.
How about add a new ABI KVM_RESET_KERNDEVS ?
We don't want to implement RESET ABIs for each kernel devices
especially when we move PIT down
Daniel P. Berrange wrote:
A Fedora user reported that Vista networking isn't working with KVM[1] and
pointed to the Wiki
http://kvm.qumranet.com/kvmwiki/Vista_Networking_Workaround
FYI, a patch from Xen was merged into upstream QEMU to fix this problem
with rtl8139 a week or two back
Dong, Eddie wrote:
Avi Kivity wrote:
Dong, Eddie wrote:
I think #2. Synchronization will be difficult; we'll need to send
signals to all other vcpus so that they drop the vcpu mutex.
How about add a new ABI KVM_RESET_KERNDEVS ?
We don't want to implement RESET ABIs for
Daniel P. Berrange wrote:
On Wed, Sep 26, 2007 at 06:02:21PM +0200, Laurent Vivier wrote:
Daniel P. Berrange wrote:
On Wed, Sep 26, 2007 at 05:47:20PM +0200, Laurent Vivier wrote:
Hi,
I think there is a bug in qemu RTL8139.
RTL8139 uses:
Haydn Solomon wrote:
I know I'm not crazy.. now my host and guest clocks are in sync. I'll
leave the guest running for a while and see if it eventually goes
ahead of host.
Please do this both with and without -no-kvm-irqchip. The code paths
are very different.
--
Do not meddle in the
Laurent Vivier wrote:
Remove unused variable introduced by commit
5ed6627ee96f0a6802d99e71879d98610ba17e01
(I missed it, sorry)
Applied, thanks.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
Avi Kivity wrote:
Farkas Levente wrote:
Daniel P. Berrange wrote:
A Fedora user reported that Vista networking isn't working with KVM[1] and
pointed to the Wiki
http://kvm.qumranet.com/kvmwiki/Vista_Networking_Workaround
FYI, a patch from Xen was merged into upstream QEMU to fix this
Farkas Levente wrote:
Avi Kivity wrote:
Haydn Solomon wrote:
I know I'm not crazy.. now my host and guest clocks are in sync. I'll
leave the guest running for a while and see if it eventually goes
ahead of host.
Please do this both with and without -no-kvm-irqchip. The
Laurent Vivier wrote:
Avi Kivity wrote:
Farkas Levente wrote:
Daniel P. Berrange wrote:
A Fedora user reported that Vista networking isn't working with KVM[1] and
pointed to the Wiki
http://kvm.qumranet.com/kvmwiki/Vista_Networking_Workaround
FYI, a patch from Xen
Avi Kivity wrote:
Farkas Levente wrote:
Avi Kivity wrote:
Haydn Solomon wrote:
I know I'm not crazy.. now my host and guest clocks are in sync. I'll
leave the guest running for a while and see if it eventually goes
ahead of host.
Please do this both with and without
Farkas Levente wrote:
Avi Kivity wrote:
Farkas Levente wrote:
Avi Kivity wrote:
Haydn Solomon wrote:
I know I'm not crazy.. now my host and guest clocks are in sync. I'll
leave the guest running for a while and see if it eventually goes
ahead of host.
I try to implement the guest reboot support, but I found there is an
stranger #PF VM Exit in guest real mode cs:ip=f000:1 which is
problemtic and current shadow won;t handle. I then try to
use -no-kvm-irqchip and get same error.
Can somebody give me more information if you ever
2007/9/27, Farkas Levente [EMAIL PROTECTED]:
Avi Kivity wrote:
Farkas Levente wrote:
Avi Kivity wrote:
Haydn Solomon wrote:
I know I'm not crazy.. now my host and guest clocks are in sync. I'll
leave the guest running for a while and see if it eventually goes
ahead of host.
[EMAIL PROTECTED] wrote:
I try to implement the guest reboot support, but I found there is an
stranger #PF VM Exit in guest real mode cs:ip=f000:1 which is
problemtic and current shadow won;t handle. I then try to
use -no-kvm-irqchip and get same error.
Can somebody give me more
Avi Kivity wrote:
this means it's better to run ntpd on all guests even if it's running on
the host:-((
I think there are issues with running ntp on the guest due to tsc being
very inaccurate on virtualized guests.
does this means itás not possible to run a guest with accurate time?
--
Farkas Levente wrote:
Avi Kivity wrote:
this means it's better to run ntpd on all guests even if it's running on
the host:-((
I think there are issues with running ntp on the guest due to tsc being
very inaccurate on virtualized guests.
does this means itás not
Dong, Eddie wrote:
[EMAIL PROTECTED] wrote:
I try to implement the guest reboot support, but I found there is an
stranger #PF VM Exit in guest real mode cs:ip=f000:1 which is
problemtic and current shadow won;t handle. I then try to
use -no-kvm-irqchip and get same error.
Can
Izik Eidus wrote:
Anthony Liguori wrote:
I think you forgot to include the patch?
Regards,
Anthony Liguori
yes i forgot :)
here it is...
Patch doesn't apply. Can you rebase to latest kvm.git?
Also, fix whitespace issues reported by 'git apply'.
Please repost with 'git
Avi Kivity wrote:
Izik Eidus wrote:
Anthony Liguori wrote:
I think you forgot to include the patch?
Regards,
Anthony Liguori
yes i forgot :)
here it is...
Patch doesn't apply. Can you rebase to latest kvm.git?
Also, fix whitespace issues reported by 'git apply'.
Correct me if I'm wrong, perhaps it's the bug Nitin is hunting.
There is always something wrong in the management in the REP prefix.
I think what is happen is:
- we have a REP prefix, we save ECX and EIP.
- we set c-dst to emulate a stos
- goto writeback
- writeback: we try a write_emulated()
Hi,
booting a FC6 on my intel box (xeon) with a kernel 2.6.22.5 and KVM git, I had
the following error (not reproducible):
# kvm-userspace/qemu/x86_64-softmmu/qemu-system-x86_64 -hda fc6.qcow2 -net nic
-net tap -serial stdio -smp 4
...
INIT: version 2.86 booting
Welcome to Fedora
Farkas Levente wrote:
Avi Kivity wrote:
this means it's better to run ntpd on all guests even if it's running on
the host:-((
I think there are issues with running ntp on the guest due to tsc being
very inaccurate on virtualized guests.
does this means itás not
Only for the week ending Sep 28, you will get a Directory for Nursing Homes,
Hospitals, Dentists and Chiropractors at no charge when you order the MD
Database
Licensed MDs in the USA
788,483 in total 17,400 emails
MDs in many different specialties
Sort by over a dozen different fields
This patch corrects some errors appearing when we have an emulation failure
on an operation using REP prefix.
When x86_emulate_insn() fails, saving EIP and ECX is not enough as emulation
should have modified other registers like RSI or RDI. Moreover, the emulation
can fail on the writeback, and
Avi Kivity wrote:
Dong, Eddie wrote:
[EMAIL PROTECTED] wrote:
I try to implement the guest reboot support, but I found there is an
stranger #PF VM Exit in guest real mode cs:ip=f000:1 which is
problemtic and current shadow won;t handle. I then try to
use -no-kvm-irqchip and get same
Hi Avi,
Sound good! But what can we do before the merge? You know, we have to
spend much effort maintaining our patches with sync with upstream tree. Do you
have an interim solution or proposal for merging IA64 code? Thanks.
Xiantao
-Original Message-
From: Avi Kivity
diff --git a/drivers/kvm/kvm_main.c b/drivers/kvm/kvm_main.c index
cecdb1b..0ebae4c 100644 --- a/drivers/kvm/kvm_main.c +++
b/drivers/kvm/kvm_main.c @@ -1080,14 +1080,19 @@ static int
emulator_read_emulated(unsigned long addr, memcpy(val,
vcpu-mmio_data, bytes); vcpu-mmio_read_completed = 0;
27 matches
Mail list logo
