Yes, VirtualBox provides fairly decent performance for non-VT CPUs,
almost the equivalent to kqemu. If your guest is a Windows XP machine,
ensure you deactivate the ACPI in the VirtualBox launch parameters, and
then you'll have to reactivate your Windows XP.
Prior to doing that, you have to conver
I can only point you to VirtualBox for non-VT virtualization in ubuntu.
I'm sorry.
--
kqemu mode not compiled for karmic
https://bugs.launchpad.net/bugs/426497
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Yep, I too have a new ASUS U50V laptop with Intel Dual Core but no VT
and now no kqemu. I have either compile from source or use non-open
source alternatives. It would be better if qemu could support ordinary
CPUs like before.
--
kqemu mode not compiled for karmic
https://bugs.launchpad.net/bug
* PauLoX wrote, On 08/11/09 12:22:
> I'm agree with Julien Aubin, please provide a package of qemu with kqemu
> enabled for everyone.
Please allow launchpad to accept bounty offers so users can influence
and contribute to the fixing of bugs.
Sam
--
kqemu mode not compiled for karmic
https://bu
I'm agree with Julien Aubin, please provide a package of qemu with kqemu
enabled for everyone.
--
kqemu mode not compiled for karmic
https://bugs.launchpad.net/bugs/426497
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
Am 28.10.2009 um 18:21 schrieb Nigel Pallett:
> The problem occurs when I'm using virt-manager or virsh to run the
> Virtual Machines under kqemu.
I can't help here as I use qemu without any "managers". Typical
strategy here is to try find out which commands these managers try to
launch an
>> /usr/bin/qemu: invalid option -- '-domid'
>
>That's odd, as qemu doesn't have a feature "domid". Even the
>unavailable options are listed with "qemu -help".
>
>Are you sure to use the newly compiled qemu? "which qemu" will tell you.
>
>Which sources are you using? I'm using the plain sources fr
> /usr/bin/qemu: invalid option -- '-domid'
That's odd, as qemu doesn't have a feature "domid". Even the
unavailable options are listed with "qemu -help".
Are you sure to use the newly compiled qemu? "which qemu" will tell you.
Which sources are you using? I'm using the plain sources from
w
Current situation is unbearable for all the users of Intel multicore
CPUs that do not have VT, i.e. half of them. kqemu provided quite decent
performance with those CPUs, but without kqemu performance drops
dramatically !!!
--
kqemu mode not compiled for karmic
https://bugs.launchpad.net/bugs/426
I've compiled qemu from source, but when I try to use it with kqemu, I
get the following error:
/usr/bin/qemu: invalid option -- '-domid'
--
kqemu mode not compiled for karmic
https://bugs.launchpad.net/bugs/426497
You received this bug notification because you are a member of Ubuntu
Bugs, which
Perhaps the way froward is to make qemu-source a dependency of the kqemu
packages
--
kqemu mode not compiled for karmic
https://bugs.launchpad.net/bugs/426497
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
Shht. The kqemu packages still work great in combination with qemu built
from source.
--
kqemu mode not compiled for karmic
https://bugs.launchpad.net/bugs/426497
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
If kqemu support is disabled in karmic, why are the kqemu-source and
kqemu-common packages available in the karmic repositories ?
I agree with Traumflug's comments - there are MANY multicore processors
shipping today that do not support KVM, plus of course, all of the lower
end processors.
The re
About half of Intel's Core 2 Duo processor models shipping today do
_not_ support KVM, much less lower end processors like Celeron, Atom,
etc.. There are quite reasons to run qemu on such lower-spec'd machines.
--
kqemu mode not compiled for karmic
https://bugs.launchpad.net/bugs/426497
You recei
Can we have two packages.
One that works with CPUs that support kvm, and one that works with CPUs that do
not support kvm, e.g. with kqemu instead.
I think it is sensible to assume that all new CPUs will support kvm, so that
handles the physical memory >3.5GB issue.
But, for older CPUs, that do n
Thanks for the report. We've gotten a few requests about this over the
last few weeks. I need to respond to all of those here.
Upstream QEMU has configured kqemu off by default for 0.11, and has
completely removed the code from the tree for 0.12. This is upstream's
acknowledgement that kqemu is
** Package changed: qemu (Ubuntu) => qemu-kvm (Ubuntu)
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: qemu-kvm (Ubuntu)
Status: New => Confirmed
--
kqemu mode not compiled for karmic
https://bugs.launchpad.net/bugs/426497
You received this bug notifi
17 matches
Mail list logo