Daniel Qarras <[EMAIL PROTECTED]> writes:
>
> Hi Avi, all,
>
> > I tried it now, it's simple and it even works:
> >
> > 1. Add BRIDGE=sw0 to ifcfg-eth0
> > 2. Create a new ifcfg-sw0 that has TYPE=Bridge, and any dhcp/ip
> > configuration you previously had in ifcfg-eth0
>
> I've now managed t
Michael Riepe wrote:
> Avi Kivity wrote:
>
>> This is mostly to fix the 32-bit Linux guest breakage in kvm-17.
>>
>
> Well, almost. Knoppix 5.0 and 5.2 work now, but 5.1.1 still hangs with a
> black framebuffer (no penguin logo) and a load of 100%.
>
Do you have msr complaints in dmesg?
Avi Kivity wrote:
> This is mostly to fix the 32-bit Linux guest breakage in kvm-17.
Well, almost. Knoppix 5.0 and 5.2 work now, but 5.1.1 still hangs with a
black framebuffer (no penguin logo) and a load of 100%.
Everything else still works as fine as with kvm-17.
Great work!
--
Michael "Ti
Following patch adds back this functionality:
Signed-off-by: Sergey Kiselev <[EMAIL PROTECTED]>
--- kvm-18.orig/qemu/qemu-kvm.c 2007-03-21 17:55:11.0 +0200
+++ kvm-18/qemu/qemu-kvm.c 2007-03-25 20:42:53.0 +0200
@@ -693,6 +693,37 @@
if ((h_edx & 0x0010) == 0)
Hi,
In kvm-18 code that returned actual CPU vendor string was removed from
qemu-kvm.c (so kvm-18 running on Intel's CPU will return "AuthenticAMD"
vendor string).
Linux uses boot_cpu_data.x86_vendor (derived from vendor string) to
determine whenever to use syscall or sysenter instruction. It seem
Bugs item #1687803, was opened at 2007-03-25 14:45
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=1687803&group_id=180599
Please note that this message will contain a full copy
This is mostly to fix the 32-bit Linux guest breakage in kvm-17.
Changes from kvm-17:
- merged new userspace API
- revert the optimization which killed some 32-bit Linux guests
- reboot support on Intel hosts (AMD are already supported)
- better timekeeping under load (Uri Lublin)
- other minor f
DONGYAOZU wrote:
> When looking at the guest physical address space
> layout, I am confused by the rombios location. Besides
> normal bios position (0xE-1M), it seems the whole
> region 2 is for that purpose too (4G-12K--4G), and
> region 0 high end sapce also have a copy.
>
> What is the reaso
Michael Riepe wrote:
> Hi!
>
> Carsten Emde wrote:
>
>
>> Actually, the above line can be preserved, if we move the previous line
>> down by 1: Was it a simple race?
>>
>> --- kvm_main-17.c2007-03-24 02:09:00.0 +0100
>> +++ kvm_main.c 2007-03-24 04:10:59.0 +0100
>> @@
Michael Riepe wrote:
> Hi!
>
> Carsten Emde wrote:
>
>> Avi Kivity wrote:
>>
>>
>>> Michael Riepe wrote:
>>>
>>>
With respect to the Core Duo, this is the best release I've seen so far:
>> Unfortunately, kvm-17 was less successful here. FC6 did not boot any
>> lon
Carsten Emde wrote:
> Carsten Emde wrote:
>> I then reverted to kvm-16 and repeated all upgrade changes until the
>> problem occurred. The culprit was found to be
>> [..]
>> +#ifdef THIS_PREVENTS_FC6_FROM_BOOTING
>> emulate_instruction(vcpu, kvm_run, vcpu->mmio_fault_cr2, 0);
>> +#endif
Carsten Emde wrote:
> Avi Kivity wrote:
>> Michael Riepe wrote:
>>> With respect to the Core Duo, this is the best release I've seen so
>>> far:
> Unfortunately, kvm-17 was less successful here. FC6 did not boot any
> longer after I upgraded from kvm-16 to kvm-17, so I was rather
> surprised whe
12 matches
Mail list logo
