Well done Carlo.
The patch works perfectly with my OpenSolaris and kvm-53.
Thx!
El lun, 26-11-2007 a las 19:31 -0600, Carlo Marcelo Arenas Belon
escribió:
> On Wed, Oct 10, 2007 at 03:53:10PM +0200, magicboiz wrote:
> > Sun Solaris Express(9/07), does not detect the hard disk..I attach
> > a
Neo Jia wrote:
>>>
>>> Do we need to add a "default" in x86 emulator switch statement?
>>>
>>>
>>>
>> Take a look at the code. That path is already covered.
>>
>
> Avi,
>
> I just checkout the latest kvm.git. Please correct me if I am wrong.
>
> I don't see the explicit "default" in sw
Sheng Yang wrote:
> From c050ed6225f314b86a0dabf11c7f677de097c39f Mon Sep 17 00:00:00 2001
> From: Sheng Yang <[EMAIL PROTECTED]>
> Date: Tue, 27 Nov 2007 14:41:06 +0800
> Subject: [PATCH] KVM: Fix compile error caused by no defined CONFIG_X86
>
> For was included by qemu, which didn't define CONF
Sheng Yang wrote:
> From 5a3ca0556bb3f8b9e18d392535312c370c2dd2f7 Mon Sep 17 00:00:00 2001
> From: Sheng Yang <[EMAIL PROTECTED]>
> Date: Tue, 27 Nov 2007 14:51:44 +0800
> Subject: [PATCH] kvm: qemu: Fix compile error in non-x86 arch
>
> This patch disable PIC/IOAPIC live migration support for non-
Neo Jia wrote:
> >From 2d054cce30ae2e837b24144195b9785a20e08c4a Mon Sep 17 00:00:00 2001
> From: Neo Jia <[EMAIL PROTECTED]>
> Date: Mon, 26 Nov 2007 23:29:53 -0800
> Subject: [PATCH] Remove build output file in user/test/x86/lib.
>
> This patch will remove the generated files (.*.d, *.o) in direct
Anthony Liguori wrote:
>> Another point is that virtio still has a lot of leading zeros in its
>> mileage counter. We need to keep things flexible and learn from
>> others as much as possible, especially when talking about the ABI.
>
> Yes, after thinking about it over holiday, I agree that we sh
Avi Kivity wrote:
> No, definitely not define a hypercall ABI. The feature bit should say
> "this device understands a hypervisor-specific way of kicking. consult
> your hypervisor manual and cpuid bits for further details. should you
> not be satisfied with this method, port io is still avai
Carsten Otte wrote:
> Avi Kivity wrote:
>
>> No, definitely not define a hypercall ABI. The feature bit should say
>> "this device understands a hypervisor-specific way of kicking. consult
>> your hypervisor manual and cpuid bits for further details. should you
>> not be satisfied with thi
On Tuesday 27 November 2007, Avi Kivity wrote:
> > :-) Do you know if there is a hard limit on the number of devices on
> > a PCI bus? My concern was that it was limited by something stupid
> > like an 8-bit identifier.
>
> IIRC pci slots are 8-bit, but you can have multiple buses, so
> effec
>Perhaps we could just move the declaration of kvm_irqchip to an arch
>specific header instead of introducing #ifdef's?
>Does ia64 have a i8259a?
Hi Anthony,
IA64 doesn't need to keep i8259 for platform virtualization, but
we still need ioapic, so I also don't think we can
use #i
Rusty Russell wrote:
> On Tuesday 13 November 2007 10:25:54 Anthony Liguori wrote:
>
>> Dor Laor wrote:
>>
>>> Anthony Liguori wrote:
>>>
Dor Laor wrote:
> In general I think we need to add another feature or even version
> number ( I know you guys hate it)
Avi Kivity wrote:
> Unfortunately, we have to care for platform differences, subarch
> differences (vmx/svm), hypervisor differences (with virtio), and guest
> differences (Linux/Windows/pvLinux, 32/64). Much care is needed when
> designing the ABI here.
Yea, I agree.
> [actually thinking a bi
Carsten Otte wrote:
>
>> [actually thinking a bit, this is specific to the virtio pci binding;
>> s390 will never see any of it]
> You remember that we've lost the big debate around virtio in Tucson?
I was in the embedded BOF.
> We intend to bind our virtio devices to PCI too, so that they look
Avi Kivity wrote:
>> We intend to bind our virtio devices to PCI too, so that they look the
>> same in Linux userland across architectures.
>
> Ouch.
That was my initial opinion too, but HPA has come up with a lean and
clean PCI binding for lguest. I think we should seriously consider
using tha
Minor improvements all around.
Changes from kvm-53:
- fix fpu leak on AMD (Amit Shah)
- (on kvm-53, lazy fpu was disabled, so this just improves performance)
- prefetch instruction bytes when emulating
- implement guest page fault bypass on nonpae
- should speed up some 32-bit guests
- add a
Hi Jerone,
On Monday 26 November 2007, Jerone Young wrote:
> On Mon, 2007-11-26 at 11:57 +0100, Gerd Koenig wrote:
> > hello,
> > Which is the first version of kvm, which is considered to be able to
> > cross compile?
>
> It would be one of the newer versions. I started to sending cross
> compile
Anthony Liguori wrote:
> I don't think there's any plans for this driver to every be used seriously as
> virtio seems like the agreed upon layer. So let's remove the code from the
> tree so I can use the drivers/ directory for something else.
>
>
Applied, thanks.
--
error compiling committee.
Anthony Liguori wrote:
> This provides a make sync within the drivers/ directory to allow virtio
> drivers
> to be built as third-party modules much as we do with the KVM driver.
>
>
We will want to ship and build guest drivers as a separate package
(that's not to say that this patch is wrong
When using VNC Server build into qemu the AltGr-Key seems to be ignored.
The alternative Ctrl-Alt seems to work but it is less comfortable to
press three keys.
Any idea how to fix it?
Elmar
-
This SF.net email is sponsored
Carsten Otte wrote:
Avi Kivity wrote:
We intend to bind our virtio devices to PCI too, so that they look the
same in Linux userland across architectures.
Ouch.
That was my initial opinion too, but HPA has come up with a lean and
clean PCI binding for lguest. I think we should se
Zhao, Yunfeng wrote:
>>
>> https://sourceforge.net/tracker/?funcÞtail&atid‰3831&aid36905&group_id05
>> 99
>>
>> Internal testing here confirms, but this is not a recent regression.
>> When was the last time Vista x64 installed reliably for you? (here, it
>> works, but not 100% of the time).
Linus,
Please pull the the kvm updates in
git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git for-linus
fixing some x86 emulator and AMD FPU handling regressions.
Amit Shah (2):
KVM: x86 emulator: Use emulator_write_emulated and not emulator_write_std
KVM: SVM: Fix FPU leak
>> One regression:
>> 1. Cannot install 64bit vista guests.
>>
>https://sourceforge.net/tracker/?funcÞtail&atid3831&aid36905&group_id05
>99
>>
>
>Internal testing here confirms, but this is not a recent regression.
>When was the last time Vista x64 installed reliably for you? (here, it
>works,
magicboiz wrote:
> Well done Carlo.
>
> The patch works perfectly with my OpenSolaris and kvm-53.
>
>
Good to know.
> Thx!
>
> El lun, 26-11-2007 a las 19:31 -0600, Carlo Marcelo Arenas Belon
> escribió:
>
>> On Wed, Oct 10, 2007 at 03:53:10PM +0200, magicboiz wrote:
>>
>>> Sun Solaris
On Tue, Nov 27, 2007 at 10:22:57PM +0200, Avi Kivity wrote:
> magicboiz wrote:
> > Well done Carlo.
> >
> > The patch works perfectly with my OpenSolaris and kvm-53.
>
> Good to know.
Also tested it with Nexenta alpha 7, and Indiana and had it added as part
of my gentoo package for kvm-54
> >> a
Hi,
Apologies for this not being a specific KVM issue. I cannot get
vde/dnsmasq working with KVM on CentOS 5.0. It works fine on FC6
basically following the instructions here
https://help.ubuntu.com/community/KVM.
However, when I move to CentOS 5, I constantly get the "Sendto: bad file
des
Hi Avi,
I am noticing that with SL 10.1 The QEMU process memory consumption
steadily increases, up the the guest memory size and then the guest dies
with unhandled vmexit. If I change the guest memory size I can see the
qemu process dies accordingly, after reaching the size of allotted guest
memor
>-Original Message-
>From: Kamble, Nitin A
>Sent: Tuesday, November 27, 2007 5:05 PM
>To: 'Avi Kivity'
>Cc: kvm-devel
>Subject: real mode emulation and memory consumption
>
>Hi Avi,
> I am noticing that with SL 10.1 The QEMU process memory consumption
>steadily increases, up the the guest m
Kamble, Nitin A wrote:
> Hi Avi,
> I am noticing that with SL 10.1 The QEMU process memory consumption
> steadily increases, up the the guest memory size and then the guest dies
> with unhandled vmexit. If I change the guest memory size I can see the
> qemu process dies accordingly, after reaching
Hi, Avi
Since IA64's irqchip is always in kernel side, so we don't need
kvm_vcpu_ioctl_interrupt for irq delivery. Should we moved it to arch?
Otherwise, we have to define two unnecessary fields(irq_summary and
irq_pending) for vcpu structure for compile pass.
Xiantao
-
30 matches
Mail list logo
