Hi,
I was able to boot and install Soarlis 10 U4 but since upgraded the host,
I have issues.
Host:
Fedora 8 - 2.6.24.4-64.fc8PAE SMP
CPU AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
32 bit
Previously:
2.6.24.4-64.fc8
Running the standard F8 KVM kernel drivers, with either 65 or 66 userland.
Alexey Eremenko wrote:
> KVM-65/66 has some bugs on AMD. I suggest you to degrade to KVM-64 for
> stability.
Also crashes (userland kvm-64, kernel F8). It is Solaris 32bit.
Does the 32bit host running PAE cause any issues ?
---
Avi Kivity wrote:
> How much memory do you have? If you are blessed with 4GB or more, this
> is likely a truncation issue.
I have 4GB (just upgraded from 1GB), hence running PAE else Linux is only
enable to use ~3GB.
By mem=2000 I assume you mean on the Host?
If so, I might as well drop back t
Avi Kivity wrote:
> > If so, I might as well drop back to non-PAE and get to use 3GB.
>
> If it works, this provides a clue as to what goes wrong, and we can fix
> it.
>
> > Are these known issues? Can I do anything to help/test which might
> > make it work for other people?
>
> Just let us know i
Avi Kivity wrote:
> 1. Boot with 'noexec=off' on the host kernel command line
> 2. Loading the kernel modules that come with kvm-66
I'll have a go at no.2, I have not had much luck compiling the modules
within the constraints of a Fedora kernel.
No.1 I can do tomorrow when in the same buildi
Avi Kivity wrote:
> I do this regularly, basically you need to install kernel-devel and
> that's it.
Yes, that is very easy isn't it. Oops to my stupidity. I've got it built
and will give it a go tomorrow and report back on each test case.
Avi Kivity wrote:
> Actually kvm is affected by pae: it enables nx support. Please try
> (separately)
>
> 1. Boot with 'noexec=off' on the host kernel command line
2.6.24.4-64.fc8PAE noexec=off:
Using normal F8 modules
qemu-kvm dies in the same way
> 2. Loading the kernel modules that come
Avi Kivity wrote:
> > Yes, that is very easy isn't it. Oops to my stupidity. I've got it built
> > and will give it a go tomorrow and report back on each test case.
>
> Please don't flame on kvm-devel, even if the flames are self-directed.
Er, OK...
--
Ian Kirk wrote:
> 2.6.24.4-64.fc8PAE noexec=off:
>
> Using normal F8 modules
> qemu-kvm dies in the same way
>
> > 2. Loading the kernel modules that come with kvm-66
>
> Against 2.6.24.4-64.fc8 it works.
2.6.24.4-64.fc8PAE with kvm-66 module seems to work OK.
I gu
Avi Kivity wrote:
> For mass storage, we should follow the SCSI model with a single device
> serving multiple disks, similar to what you suggest. Not sure if the
> device should have a single queue or one queue per disk.
Don't you just end up re-implementing SCSI then, at which point you might
a
Hi,
I wanted to try running Vmware ESX without the effort of finding a
physical machine. Googling around I found that it is possible to run ESX
under other hypervisors/emulators, e.g. Vmware Workstation. So I thought
i'd give KVM a go.
Using kvm-66 on 2.6.24.4-64.fc8PAE, the (mostly text mode) in
Avi Kivity wrote:
> This is the first release of network drivers for Windows guests running
> on a kvm host.
Any plans for Windows Server and block support?
-
This SF.net email is sponsored by: Microsoft
Defy all challenges.
12 matches
Mail list logo
