Anthony Liguori wrote:
> This patch attempts to clean up kvmctl so that it can be more easily made to
> work for multiple architectures and to support more emulation.
>
> It introduces a io dispatch mechanism. This mechanism supports subpage
> granularity but is optimized to efficiently cover regi
Jim Paris wrote:
> If I stop KVM in the monitor with "stop", wait a minute, and do
> "cont", a Linux guest gives me a "BUG: soft lockup detected on CPU#0".
> Is that expected behavior?
No.
> What isn't virtualized that allows it to
> detect that? The host is a core 2 duo.
>
>
It may be tha
If I stop KVM in the monitor with "stop", wait a minute, and do
"cont", a Linux guest gives me a "BUG: soft lockup detected on CPU#0".
Is that expected behavior? What isn't virtualized that allows it to
detect that? The host is a core 2 duo.
I have bigger problems in the guest after migrating to
We've now switched to allocating guest memory in userspace rather than
in the kernel. This is important if you have a mainframe, but also if
you want to share memory between guests and implement nice features like
swapping.
Changes since kvm-45:
- fix host oops on bad guest ioapic accesses
- hand
Avi Kivity wrote:
> Small, reviewable, posted patches are definitely the best way forward.
Very well, will go that direction.
>
>> -case KVM_CHECK_EXTENSION: {
>> -int ext = (long)argp;
>> -
>> -switch (ext) {
>> -case KVM_CAP_IRQCHIP:
>> -case KVM_CAP_HLT:
>> -
Avi Kivity wrote:
> What's the motivation for the new header? So we have a list of
> arch-dependent functions? Compiler-wise it could just as well remain in
> kvm.h.
The motivation for a new header, is that it contains definitions
specific to an architecture. These prototypes should go to kvm.
Hi,
On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> We've now switched to allocating guest memory in userspace rather than
> in the kernel. This is important if you have a mainframe, but also if
> you want to share memory between guests and implement nice features like
> swapping.
This is i
Jun Koi wrote:
> Hi,
>
> On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>> We've now switched to allocating guest memory in userspace rather than
>> in the kernel. This is important if you have a mainframe, but also if
>> you want to share memory between guests and implement nice features
[EMAIL PROTECTED] wrote:
>
> It may be that the timer correction code detects that zillions of
> timer interrupts have not been serviced by the guest so it floods the
> guest with these interrupts. Does -no-kvm-irqchip help?
>
In Xen, we decide to froze the guest time after save/restore. In this
Calin Brabandt wrote:
> I'm a KVM newb and can't find any information or
> associated FAQ about KVM guest firewire support
Unfourtantly kvm have no firewire support
-
This SF.net email is sponsored by: Splunk Inc.
Still grepp
On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> Jun Koi wrote:
> > Hi,
> >
> > On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> >
> >> We've now switched to allocating guest memory in userspace rather than
> >> in the kernel. This is important if you have a mainframe, but also if
> >> you
Jun Koi wrote:
> On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>> Jun Koi wrote:
>>
>>> Hi,
>>>
>>> On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
>>>
>>>
We've now switched to allocating guest memory in userspace rather than
in the kernel. This is important if
Dong, Eddie wrote:
> [EMAIL PROTECTED] wrote:
>
>> It may be that the timer correction code detects that zillions of
>> timer interrupts have not been serviced by the guest so it floods the
>> guest with these interrupts. Does -no-kvm-irqchip help?
>>
>>
> In Xen, we decide to froze the gu
Avi Kivity wrote:
> Dong, Eddie wrote:
>> [EMAIL PROTECTED] wrote:
>>
>>> It may be that the timer correction code detects that zillions of
>>> timer interrupts have not been serviced by the guest so it floods
>>> the guest with these interrupts. Does -no-kvm-irqchip help?
>>>
>>>
>> In Xen, we
Dong, Eddie wrote:
> Avi Kivity wrote:
>
>> Dong, Eddie wrote:
>>
>>> [EMAIL PROTECTED] wrote:
>>>
>>>
It may be that the timer correction code detects that zillions of
timer interrupts have not been serviced by the guest so it floods
the guest with these interrupts.
Avi Kivity wrote:
> We've now switched to allocating guest memory in userspace rather than
> in the kernel. This is important if you have a mainframe, but also if
> you want to share memory between guests and implement nice features like
> swapping.
>
> Changes since kvm-45:
> - fix host oops on
Dong, Eddie wrote:
>> Or is the timer saved in absolute time? if so you are right, and yes,
>> your solution is needed.
>>
>>
> Looks like current live migration, also save/restore, doesn't migrate
> guest time. (do I miss something?) So the new guest will
> see a totally different TSC and
Dong, Eddie wrote:
> Avi Kivity wrote:
>
>> Dong, Eddie wrote:
>>
>>> This one is a preparation for kernel devices reset support.
>>>
>>>
>>>
>>>Split ioapic reset API and export PIC reset API
>>>
>>>
>> Please split into two patches, I need to fold them into the pic patch
>>
>Or is the timer saved in absolute time? if so you are right, and yes,
>your solution is needed.
>
Looks like current live migration, also save/restore, doesn't migrate
guest time. (do I miss something?) So the new guest will
see a totally different TSC and OS feel stranger or
many lost ticks
Farkas Levente wrote:
> Avi Kivity wrote:
>
>> We've now switched to allocating guest memory in userspace rather than
>> in the kernel. This is important if you have a mainframe, but also if
>> you want to share memory between guests and implement nice features like
>> swapping.
>>
>> Changes s
2007/10/10, Calin Brabandt <[EMAIL PROTECTED]>:
> I'm a KVM newb and can't find any information or
> associated FAQ about KVM guest firewire support. If
> there's no KVM support, I'm seeking alternative
> recommendations, if KVM list members are so inclined.
>
> My goal is to boot a dedicated and
Farkas Levente wrote:
> Avi Kivity wrote:
>> We've now switched to allocating guest memory in userspace rather than
>> in the kernel. This is important if you have a mainframe, but also if
>> you want to share memory between guests and implement nice features like
>> swapping.
>>
>> Changes since
Avi Kivity wrote:
> Farkas Levente wrote:
>> Avi Kivity wrote:
>>
>>> We've now switched to allocating guest memory in userspace rather than
>>> in the kernel. This is important if you have a mainframe, but also if
>>> you want to share memory between guests and implement nice features like
>>>
Dong, Eddie wrote:
> Avi Kivity wrote:
>
>> Dong, Eddie wrote:
>>
>>> Avi Kivity wrote:
>>>
>>>
But, for an ungraceful reset, nothing prevents an AP from
issuing a reset?
>>> Mmm, Yes, but I think current architecture can't handle this.
>>> The thread whe
Elmar Haneke wrote:
> Hi,
>
> is there any option to reenable virtualisation support (AMD-CPU) if it
> is disabled by bios (and Bios does not show an option to enable
> virtualisation support)?
>
Look for a bios update, that may help.
--
error compiling committee.c: too many arguments to fun
Dong, Eddie wrote:
> SMP reboot failed with various phenomena such as user level
> "unhandled vm exit: 0x8021 ..." when rebooting SMP RHEL5U
> or "execption 8 (0)..." when rebooting XP etc. The reason is that
> we are not correctly reset VCPU. create_vcpu does some initialization
> work which
Hi,
is there any option to reenable virtualisation support (AMD-CPU) if it
is disabled by bios (and Bios does not show an option to enable
virtualisation support)?
Elmar
-
This SF.net email is sponsored by: Splunk Inc.
Stil
Oliver Kowalke wrote:
> Hi,
> I've Debian/Lenny (amd64) with kernel 2.6.22-9 (kvm-support build in) with
> kvm-45 running.
> WinXP, FreeBSD-6.2 (i386) and NetBSD-3.1 (i386) are working.
> I've only a problem running OpenBSD-4.1 (i386). The installation succeeded,
> but if I start OpenBSD I get fo
Aurelien Jarno wrote:
>>> I also confirm that using -no-acpi fixes the problem. However, I have
>>> seen strange data corruption, even on Intel.
>>>
>>> Basically, booting a recently installed FreeBSD leads to the following
>>> message from the bootloader: "No kernel found". And the next time, I ge
Hi,
I've Debian/Lenny (amd64) with kernel 2.6.22-9 (kvm-support build in) with
kvm-45 running.
WinXP, FreeBSD-6.2 (i386) and NetBSD-3.1 (i386) are working.
I've only a problem running OpenBSD-4.1 (i386). The installation succeeded,
but if I start OpenBSD I get following error:
cpu0: QEMU Virtual
Avi Kivity wrote:
> Zhao, Yunfeng wrote:
>> This fix cannot resolve this issue.
>> Against latest kvm commits, SMP linux with 4 vcpus still cannot boot up.
>> But the issue will not happen , if adding "-smp4 -no-acpi".
>>
>
> Can you try the attached patch?
>
>
>
>
>
>
> -
Avi Kivity wrote:
> We've now switched to allocating guest memory in userspace rather than
> in the kernel. This is important if you have a mainframe, but also if
> you want to share memory between guests and implement nice features like
> swapping.
we did a quick test against this version and it
Avi Kivity a écrit :
> Aurelien Jarno wrote:
I also confirm that using -no-acpi fixes the problem. However, I have
seen strange data corruption, even on Intel.
Basically, booting a recently installed FreeBSD leads to the following
message from the bootloader: "No kernel fou
Farkas Levente wrote:
> Avi Kivity wrote:
>
>> We've now switched to allocating guest memory in userspace rather than
>> in the kernel. This is important if you have a mainframe, but also if
>> you want to share memory between guests and implement nice features like
>> swapping.
>>
>
> we
Aurelien Jarno wrote:
> Avi Kivity a écrit :
>
>> Aurelien Jarno wrote:
>>
> I also confirm that using -no-acpi fixes the problem. However, I have
> seen strange data corruption, even on Intel.
>
> Basically, booting a recently installed FreeBSD leads to the following
>
Zhao, Yunfeng wrote:
> This fix cannot resolve this issue.
> Against latest kvm commits, SMP linux with 4 vcpus still cannot boot up.
> But the issue will not happen , if adding "-smp4 -no-acpi".
>
Can you try the attached patch?
--
error compiling committee.c: too many arguments to functi
Avi Kivity wrote:
> Farkas Levente wrote:
>> Avi Kivity wrote:
>>
>>> We've now switched to allocating guest memory in userspace rather than
>>> in the kernel. This is important if you have a mainframe, but also if
>>> you want to share memory between guests and implement nice features like
>>>
On 10/10/07, Izik Eidus <[EMAIL PROTECTED]> wrote:
> Oliver Kowalke wrote:
> > Hi,
> > I've Debian/Lenny (amd64) with kernel 2.6.22-9 (kvm-support build in) with
> > kvm-45 running.
> > WinXP, FreeBSD-6.2 (i386) and NetBSD-3.1 (i386) are working.
> > I've only a problem running OpenBSD-4.1 (i386).
Farkas Levente wrote:
>>> we did a quick test against this version and it's turn out the smp
>>> guests are still not working. even if we start only one linux guest with
>>> 4cpu on 4cpu host the guest kernel hangs at random stages of the kernel
>>> loading process (if we run more smp guests then t
Thanks to Avis review, this is an updated version of the patch that
splits kvm_dev_ioctl into architecture dependent and architecture
independent parts. I've changed everything Avi noted in his review
feedback. It is also rebased to fit on today's git with all that
reindentation.
KVM_CHECK_EXTENSI
Christian Borntraeger pointed out that Avi requested to rename kvm_x86.c
to x86.c. The patch below is the same as V2, but the files kvm_x86.[ch]
have been renamed to x86.[ch], and the #includes have been updated.
signed-off-by: Carsten Otte <[EMAIL PROTECTED]>
---
Index: kvm/drivers/kvm/kvm.h
Avi Kivity wrote:
> Farkas Levente wrote:
we did a quick test against this version and it's turn out the smp
guests are still not working. even if we start only one linux guest
with
4cpu on 4cpu host the guest kernel hangs at random stages of the kernel
loading process (if
On Wed, Oct 10, 2007 at 12:56:18PM +0200, Izik Eidus wrote:
> Oliver Kowalke wrote:
> > Hi,
> > I've Debian/Lenny (amd64) with kernel 2.6.22-9 (kvm-support build in) with
> > kvm-45 running.
> > WinXP, FreeBSD-6.2 (i386) and NetBSD-3.1 (i386) are working.
> > I've only a problem running OpenBSD-4.
Avi Kivity a écrit :
> Aurelien Jarno wrote:
I also confirm that using -no-acpi fixes the problem. However, I have
seen strange data corruption, even on Intel.
Basically, booting a recently installed FreeBSD leads to the following
message from the bootloader: "No kernel fou
Carsten Otte wrote:
> Christian Borntraeger pointed out that Avi requested to rename kvm_x86.c
> to x86.c. The patch below is the same as V2, but the files kvm_x86.[ch]
> have been renamed to x86.[ch], and the #includes have been updated.
>
> signed-off-by: Carsten Otte <[EMAIL PROTECTED]>
> ---
>
On Wed, Oct 10, 2007 at 10:28:24AM +0200, Avi Kivity wrote:
> We've now switched to allocating guest memory in userspace rather than
> in the kernel. This is important if you have a mainframe, but also if
> you want to share memory between guests and implement nice features like
> swapping.
Is th
Daniel P. Berrange wrote:
> On Wed, Oct 10, 2007 at 10:28:24AM +0200, Avi Kivity wrote:
>
>> We've now switched to allocating guest memory in userspace rather than
>> in the kernel. This is important if you have a mainframe, but also if
>> you want to share memory between guests and implement n
Avi Kivity wrote:
> Anthony Liguori wrote:
>> Avi Kivity wrote:
>>> Anthony Liguori wrote:
>>>
This patch attempts to clean up kvmctl so that it can be more
easily made to
work for multiple architectures and to support more emulation.
It introduces a io dispatch mechanis
Avi Kivity a écrit :
> Aurelien Jarno wrote:
>> Avi Kivity a écrit :
>>
>>> Aurelien Jarno wrote:
>>>
>> I also confirm that using -no-acpi fixes the problem. However, I have
>> seen strange data corruption, even on Intel.
>>
>> Basically, booting a recently installed FreeBS
Anthony Liguori wrote:
>>
>>>
>>> QEMU uses an array for PIO but a table for MMIO. I figured it would
>>> be best to just use the same table.
>>
>> Or the same array?
>
> Indexed by the address or just sorted and searchable? MMIO addresses
> are rather sparse so the former seems like the only s
Should we be seeing a mmap file when running guests now or do we have to use
a special flag when running kvm?
On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
>
> Daniel P. Berrange wrote:
> > On Wed, Oct 10, 2007 at 10:28:24AM +0200, Avi Kivity wrote:
> >
> >> We've now switched to allocating g
Avi Kivity wrote:
> Anthony Liguori wrote:
>
>> This patch attempts to clean up kvmctl so that it can be more easily made to
>> work for multiple architectures and to support more emulation.
>>
>> It introduces a io dispatch mechanism. This mechanism supports subpage
>> granularity but is optim
Aurelien Jarno wrote:
> Avi Kivity a écrit :
>
>> Aurelien Jarno wrote:
>>
> I also confirm that using -no-acpi fixes the problem. However, I have
> seen strange data corruption, even on Intel.
>
> Basically, booting a recently installed FreeBSD leads to the following
>
Anthony Liguori wrote:
> Avi Kivity wrote:
>> Anthony Liguori wrote:
>>
>>> This patch attempts to clean up kvmctl so that it can be more easily
>>> made to
>>> work for multiple architectures and to support more emulation.
>>>
>>> It introduces a io dispatch mechanism. This mechanism supports
Hi list,
you I always report OS that do not start with kvm :))
Sun Solaris Express(9/07), does not detect the hard disk..I attach
an screenshot.
Kernel:2.6.23
kvm: 45 and 46
CPU: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz
<>---
Avi Kivity wrote:
> Anthony Liguori wrote:
>>>
QEMU uses an array for PIO but a table for MMIO. I figured it
would be best to just use the same table.
>>>
>>> Or the same array?
>>
>> Indexed by the address or just sorted and searchable? MMIO addresses
>> are rather sparse so the
Avi Kivity wrote:
> Argument names in prototypes please.
Will do that.
>> case KVM_CHECK_EXTENSION: {
>> int ext = (long)argp;
>>
>> -switch (ext) {
>> -case KVM_CAP_IRQCHIP:
>> -case KVM_CAP_HLT:
>> -case KVM_CAP_MMU_SHADOW_CACHE
Haydn Solomon wrote:
> Should we be seeing a mmap file when running guests now or do we have
> to use a special flag when running kvm?
>
Nope, the default is user space allocation were a regular malloc is used
for allocating the guest ram from userspace.
The mmap is for future shared memory imple
Thanks to Avi's continued review, we've got even more common code this
time: KVM_CHECK_EXTENSION ioctl is now completely handled in kvm_main.c
instead of having arch callbacks to check extensions. The architectures
are expected to setup a bit mask named KVM_ARCH_EXTENSIONS with
information about ca
Thanks for clearing that up.
On 10/10/07, Dor Laor <[EMAIL PROTECTED]> wrote:
>
> Haydn Solomon wrote:
> > Should we be seeing a mmap file when running guests now or do we have
> > to use a special flag when running kvm?
> >
> Nope, the default is user space allocation were a regular malloc is us
Am Mittwoch, 10. Oktober 2007 14:17:56 schrieb Alexey Eremenko:
> On 10/10/07, Izik Eidus <[EMAIL PROTECTED]> wrote:
> > Oliver Kowalke wrote:
> > > Hi,
> > > I've Debian/Lenny (amd64) with kernel 2.6.22-9 (kvm-support build in)
> > > with kvm-45 running.
> > > WinXP, FreeBSD-6.2 (i386) and NetBSD-
Oliver Kowalke wrote:
> Am Mittwoch, 10. Oktober 2007 14:17:56 schrieb Alexey Eremenko:
>
>> On 10/10/07, Izik Eidus <[EMAIL PROTECTED]> wrote:
>>
>>> Oliver Kowalke wrote:
>>>
Hi,
I've Debian/Lenny (amd64) with kernel 2.6.22-9 (kvm-support build in)
with kvm-45 runnin
Hi,
I'm interested in working on one of the entry-level projects on the TODO
list to get my feet wet with the code. My preference is allowing CPU
features to be passed to the guest. So I two things: I want to check
if anyone is working on these already and if not can someone please
expand
Cam Macdonell wrote:
> Hi,
>
> I'm interested in working on one of the entry-level projects on the TODO
> list to get my feet wet with the code. My preference is allowing CPU
> features to be passed to the guest. So I two things: I want to check
> if anyone is working on these already and if
Izik Eidus wrote:
> Cam Macdonell wrote:
>> Hi,
>>
>>
> sorry, but patch for that feature was already wrote by someone.
>
> but you are more than welcome to try/ask about something else.
Ah, I should've searched the list. Is there another project of similar
scope that would be of use?
Thank
Bugs item #1811073, was opened at 2007-10-10 18:19
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1811073&group_id=180599
Please note that this message will contain a full copy
Avi Kivity wrote:
> Jim Paris wrote:
> > If I stop KVM in the monitor with "stop", wait a minute, and do
> > "cont", a Linux guest gives me a "BUG: soft lockup detected on CPU#0".
> > Is that expected behavior?
>
> No.
>
> > What isn't virtualized that allows it to
> > detect that? The host is
This patch attempts to clean up kvmctl so that it can be more easily made to
work for multiple architectures and to support more emulation.
For dispatch, it's using a simple array as suggested by Avi.
For x86, we'll have two tables, a pio_table and an mmio_table. For PPC we can
just have a singl
The memory size is currently hardcoded into the linker script (end_of_memory).
This prevents the memory size from being specified dynamically in kvmctl.
This patch adds a PIO port that can be used to query the memory size in the
tests.
Signed-off-by: Anthony Liguori <[EMAIL PROTECTED]>
diff --git
This patch adds a --memory option to kvmctl to allow the memory size of the
guest to be specified.
Since v1, I added more checks for bad input as suggested by Muli.
Signed-off-by: Anthony Liguori <[EMAIL PROTECTED]>
diff --git a/user/main.c b/user/main.c
index 9a57a24..a08e0a7 100644
--- a/user/
On Tue, Oct 02, 2007 at 02:38:19PM +0200, Avi Kivity wrote:
> Aurelien Jarno wrote:
> > Avi Kivity a écrit :
> >
> >> Aurelien Jarno wrote:
> >>
> >>> Hi all,
> >>>
> >>> That's not something new, but I never seen the problem mentioned here.
> >>> FreeBSD does not work on KVM, approximately
Some of the MMU functions take a struct kvm_vcpu even though they effect all
VCPUs. This patch cleans up some of them to instead take a struct kvm. This
makes things a bit more clear.
The main thing that was confusing me was whether certain functions need to be
called on all VCPUs.
Signed-off-b
Sorry, I didn't guilt refresh before sending. I'll have to modify my patchbomb
script to check for that to avoid this in the future.
Some of the MMU functions take a struct kvm_vcpu even though they effect all
VCPUs. This patch cleans up some of them to instead take a struct kvm. This
makes thi
This time, the biggest change is gpa_to_hpa. The translation of GPA to HPA does
not depend on the VCPU state unlike GVA to GPA so there's no need to pass in
the kvm_vcpu.
Signed-off-by: Anthony Liguori <[EMAIL PROTECTED]>
diff --git a/drivers/kvm/kvm.h b/drivers/kvm/kvm.h
index 4ab487c..8859a92 1
Jun Koi wrote:
> On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>> Jun Koi wrote:
>>
>>> On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
>>>
>>>
Jun Koi wrote:
> Hi,
>
> On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>
>
Avi Kivity wrote:
> cpu_save (qemu/hw/pc.c) has this:
>
> #ifdef USE_KVM
>if (kvm_allowed) {
>for (i = 0; i < NR_IRQ_WORDS ; i++) {
>qemu_put_be32s(f, &env->kvm_interrupt_bitmap[i]);}
>qemu_put_be64s(f, &env->tsc);
>}
> #endif
Mmm, so this is not the ro
On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> Jun Koi wrote:
> > On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> >
> >> Jun Koi wrote:
> >>
> >>> Hi,
> >>>
> >>> On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> >>>
> >>>
> We've now switched to allocating guest memory in usersp
Anthony Liguori wrote:
> Some of the MMU functions take a struct kvm_vcpu even though they effect all
> VCPUs. This patch cleans up some of them to instead take a struct kvm. This
> makes things a bit more clear.
>
> The main thing that was confusing me was whether certain functions need to be
>
Avi Kivity wrote:
> Dong, Eddie wrote:
>> Avi Kivity wrote:
>>
>
> It's just like the guest kernel executing hlt. Why is there a
> difference?
Current VP wake up logic thru INIT/SIPI doesn't support this when
irqchip in kernel.
>
>>
>> Yes, halt all APs and let BSP do reset ops in user le
I meet following error while compile latest kvm source code.
..
make -C qemu
make[1]: Entering directory
`/workspace/ia32e/nightly/kvm-master-2.6.22-rc4-20071010190122210/kvm-us
erspace/qemu'
Makefile:3: config-host.mak: No such file or directory
make[1]: *** No rule to make target
Avi:
Time to time, I see this error message, any typo exist?
thx,eddie
slab error in kmem_cache_destroy(): cache `kvm_rmap_desc': Can't free
all objects
Call Trace:
[] kmem_cache_destroy+0x93/0xdc
[] :kvm:kvm_mmu_module_exit+0x23/0x37
[] :kvm:kvm_exit+0x26/0x31
[] sys_delete_module+0
I was curious if anyone thinks that it may be possible to get a
KVM-patched QEMU to use a real video card? For example, let's say I had
a second video card. Is QEMU/kvm a codebase which would support hacking
in the ability to utilize this second video card (one not utilized by
the host Linux)?
Dong, Eddie wrote:
> Avi:
> Time to time, I see this error message, any typo exist?
> thx,eddie
>
>
> slab error in kmem_cache_destroy(): cache `kvm_rmap_desc': Can't free
> all objects
>
> Call Trace:
> [] kmem_cache_destroy+0x93/0xdc
> [] :kvm:kvm_mmu_module_exit+0x23/0x37
> [] :kvm:kvm_
83 matches
Mail list logo
