Jan Kiszka wrote:
Farkas Levente wrote:
- guest fedora-9 latest kernel-2.6.26.6-79.fc9.i686 still not boot,
- guest centos-5 x86_64's kernel-2.6.18-92.1.17.el5 still gives the same
crash as kvm-78 (screenshot attached),
Those two should be fine with this patch [1]. You are welcome to test it
a
Farkas Levente wrote:
> Avi Kivity wrote:
>> This is the first release to fully support pci device assignment. You
>> can assign a pci device to qemu on the command line, or hot-plug it in
>> via the monitor. Note that at this time, Linux 2.6.28 is required on
>> the host.
>>
>> Upstream qemu rec
Avi Kivity wrote:
> This is the first release to fully support pci device assignment. You
> can assign a pci device to qemu on the command line, or hot-plug it in
> via the monitor. Note that at this time, Linux 2.6.28 is required on
> the host.
>
> Upstream qemu recently gained kvm support. At
Martin Vogt wrote:
Do I need git for this?
Is this something informal, does it need some special diff format?
Your patch is fine and I applied it. Thanks.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
Martin Vogt wrote:
Hello,
[...]
Notes:
If you use the modules bundled with kvm-79, you can use any version
of Linux from 2.6.16 upwards.
Nope.
I tested kvm-79 on a SLES 10 with 2.6.16,
in the hope that my previously reported bug:
"hrtimer_start: Unknown symbol in module"
was fixed.
Hello,
[...]
>Notes:
>If you use the modules bundled with kvm-79, you can use any version
>of Linux from 2.6.16 upwards.
Nope.
I tested kvm-79 on a SLES 10 with 2.6.16,
in the hope that my previously reported bug:
"hrtimer_start: Unknown symbol in module"
was fixed. (It wasnt)
Now I have thi
