I use opensuse 10.3 and I tried to install it on a vm.
When I boot, it crashs.
So I downloaded gfxboot disable file and I tried to complile, but
pkg-config --cflags libiso9660
give me an error. I installed libiso9660-5 package.
-
Bugs item #1900228, was opened at 2008-02-23 11:26
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1900228group_id=180599
Please note that this message will contain a full copy of
Create large pages mappings if the guest PTE's are marked as such and
the underlying memory is hugetlbfs backed.
Gives a consistent 2% improvement for data copies on ram mounted
filesystem, without NPT/EPT.
Signed-off-by: Marcelo Tosatti [EMAIL PROTECTED]
Index:
Add an option so the user can specify the hugetlbfs mounted path, with
fallback to 4k pages on error.
Align the 4GB+ memslot on large page boundary.
Signed-off-by: Marcelo Tosatti [EMAIL PROTECTED]
Index: kvm-userspace.gitpara/qemu/hw/pc.c
This isn't mentioned on the guest status page.
I went ahead and tried it anyway (32-bit). It works fine if I don't
specify -smp 2.
But qemu rejects -m 2048. -m 1024 is fine. I had over 3GB available
memory (I presume all the memory is pae-fixed to avoid both host and
guest paging - if I'm wrong,
[EMAIL PROTECTED] wrote:
I use opensuse 10.3 and I tried to install it on a vm.
When I boot, it crashs.
So I downloaded gfxboot disable file and I tried to complile, but
pkg-config --cflags libiso9660
give me an error. I installed libiso9660-5 package.
You probably need the development
I looked for a gz o bz archive. Is there a tarball with gfxboot disable program
(URL)?
Thanks.
-
-
L'email della prossima generazione? Puoi averla con la nuova Yahoo!
Hi Marcelo,
Marcelo Tosatti wrote:
Add an option so the user can specify the hugetlbfs mounted path, with
fallback to 4k pages on error.
Align the 4GB+ memslot on large page boundary.
Signed-off-by: Marcelo Tosatti [EMAIL PROTECTED]
Index: kvm-userspace.gitpara/qemu/hw/pc.c
Marcelo Tosatti wrote:
Create large pages mappings if the guest PTE's are marked as such and
the underlying memory is hugetlbfs backed.
Gives a consistent 2% improvement for data copies on ram mounted
filesystem, without NPT/EPT.
FWIW, with NPT, I'm seeing kernbench get about a 4%
[EMAIL PROTECTED] wrote:
I looked for a gz o bz archive. Is there a tarball with gfxboot
disable program (URL)?
I'm not sure I understand your question but the only way to get
gfxboot-disable today is through mercurial.
Regards,
Anthony Liguori
Thanks.
Hi Anthony,
Thanks for your comments.
On Sat, Feb 23, 2008 at 12:29:27PM -0600, Anthony Liguori wrote:
In general, I don't think it causes any real harm if we always align the
ram address to a large page boundary. If we aren't on Linux (and can't
determine what the large page size is),
Marcelo Tosatti wrote:
I thought about doing that (gets rid of the 4GB+ special casing) but we
lose the ability to compact smaller allocations in a single largepage.
Right now the VGA BIOS and the BIOS fit in the same largepage, for
example.
Ah, good point. I was actually talking about
andrzej zaborowski wrote:
Oh, good question, and I think the answer be the reason why it's not
working here (*slaps self*). I'll apply the patch if you can confirm
that it works with some Ms Windows install.
I just tried with Windows XP and I have no problem detecting the card
with this
Marcelo Tosatti wrote:
Create large pages mappings if the guest PTE's are marked as such and
the underlying memory is hugetlbfs backed.
Gives a consistent 2% improvement for data copies on ram mounted
filesystem, without NPT/EPT.
Applied, thanks (as well as the qemu part).
--
error
Andreas Winkelbauer wrote:
hi,
the attached patch fixes the screen corruption issues which were
reported by others, see:
http://article.gmane.org/gmane.comp.emulators.kvm.devel/13543
http://article.gmane.org/gmane.comp.emulators.kvm.devel/13409
The bug is kvm specific and can only be
Anthony Liguori wrote:
Right now we set explict base addresses for the PCI IO regions in the VMware
VGA device. We don't register the second region at all and instead directly
map the physical memory.
The problem is, the addresses we're setting in the BAR is not taken into
account in the
Soren Hansen wrote:
vmware_vga.c uses functions in vga.c to do some things. They
need to agree on which parts of their state struct is common
and which aren't, otherwise they'll overwrite parts of each
other's state. This patch makes it so.
Applied, thanks.
--
error compiling
17 matches
Mail list logo
