Baruch Even wrote:
> * Dor Laor <[EMAIL PROTECTED]> [070402 00:43]:
>
>>> A user just submitted a bug report against the kvm-18 debian package.
>>> You can find the bug report at
>>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=417151
>>>
>>> The user has a default route with extra features
>Baruch Even wrote:
>> * Dor Laor <[EMAIL PROTECTED]> [070402 00:43]:
>>
A user just submitted a bug report against the kvm-18 debian
package.
You can find the bug report at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=417151
The user has a default route with extra feat
Leslie Mann wrote:
> Avi Kivity <[EMAIL PROTECTED]> writes:
>
>
>> The SIGIO means some I/O has occured, but what exactly, we don't know.
>> Can you generate a core, attach it with gdb, and generate a backtrace?
>>
>> Check the backtrace for signs of your password and delete them if
>> found.
On Fri, Mar 30, 2007 at 05:04:29PM +0300, Avi Kivity wrote:
> Joerg Roedel wrote:
> >From: Joerg Roedel <[EMAIL PROTECTED]>
> >
> >This patch enables the virtualization of the last branch record MSRs on
> >SVM if this feature is available in hardware. It also introduces a small
> >and simple check
Joerg Roedel wrote:
> Is struct svm_cpu_data a userspace data structure. I ask because in a
> previous version of the patch the svm_features variable was part of that
> struct. Thats why I used this type.
>
No, all userspace stuff is in include/linux/kvm*.h (which uses __u32;
uint32_t is for l
On Mon, Apr 02, 2007 at 12:39:46PM +0300, Avi Kivity wrote:
> Joerg Roedel wrote:
> >Is struct svm_cpu_data a userspace data structure. I ask because in a
> >previous version of the patch the svm_features variable was part of that
> >struct. Thats why I used this type.
> >
>
> No, all userspace
Joerg Roedel wrote:
>>> Is struct svm_cpu_data a userspace data structure. I ask because in a
>>> previous version of the patch the svm_features variable was part of that
>>> struct. Thats why I used this type.
>>>
>>>
>> No, all userspace stuff is in include/linux/kvm*.h (which uses __u32
Hi Dor,
Please find a patch attached for your review which adds support for dynamic
substitution of the PIC/APIC code to QEMU. This will allow us to selectively
chose the KVM in-kernel apic emulation vs the QEMU user-space apic emulation.
Support for both is key to allow "--no-kvm" type oper
Avi Kivity <[EMAIL PROTECTED]> writes:
>
> It's probably the aio thread. But wasn't there a segfault? That should
> get us a nice core.
>
No segfault. I don't believe that qemu has crashed, it just doesn't respond.
Only ill effect after killing the process is that the mouse dies.
>
> The
I've used the standard Belkin KVM before, so I'm familiar with regular
KVM. I'm excited about this, but I don't understand necessarily..
hopefully you'll chuckle and respond well to my ignorance.
My assumption is this: I have a keyboard, mouse, and a monitor and an
openkvm box(?) as well as s
10 matches
Mail list logo
