ote:
> On Sat, Nov 10, 2007 at 01:22:06PM -0500, John Clemens wrote:
> > It appears the qemu in KVM-51 has a weird glitch where it will ignore
> > the '-m' memory parameter if it's the first parameter on the command
> > line (the case 'QEMU_OPTION_m' sta
It appears the qemu in KVM-51 has a weird glitch where it will ignore
the '-m' memory parameter if it's the first parameter on the command
line (the case 'QEMU_OPTION_m' stanza never gets called in
qemu/hw/vl.c:main()). A quick look at the code doesn't reveal anything
obvious to me as to why. Put
For what it's worth, -no-kvm completed the install successfully.
And I am able to boot the resulting installed system with KVM-51
enabled. Only been running for a few minutes though.
john.c
On Fri, 2007-11-09 at 15:01 -0500, John Clemens wrote:
> I'm having the same issues a
I'm having the same issues as Werner, and using the kvm userspace from
kvm-44 and the kernel modules from kvm-51 does not help. Same issue at
the same place in the install. AMD turion X2 1.6Ghz, gutsy
2.6.22-14-generic host kernel.
It always fails, with either the IRQL_... error, or I've also s
Not much detail here but I'll post all I can.
KVM-46 (from tarball, using kvm-46 modules), ubuntu gutsy
2.6.22-14-generic amd64, Turion X2 with SVM, 1GB total memory on
laptop.
Was in the middle of an windows xp pro sp2 install using this command
line:
sudo ~/kvm46/bin/qemu-system-x86_64 -m
On Fri, 2007-10-05 at 07:52 -0500, Anthony Liguori wrote:
> http://hg.codemonkey.ws/qemu-nbd/
>
> This will let you expose a qcow file (or an individual partition within
> a qcow file) as an NBD server which you can then mount on your host. A
> bit round-about but it gets the job done.
You j
