[kvm-devel] gfxboot disable

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. - --

[kvm-devel] [ kvm-Bugs-1900228 ] Time on guest slows down sometimes...

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=detail&atid=893831&aid=1900228&group_id=180599 Please note that this message will contain a full copy

[kvm-devel] [PATCH] KVM: large page support

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: kvm.paravirt3/arch/x86/kvm/mmu

[kvm-devel] [PATCH] QEMU/KVM: large page support

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 =

Re: [kvm-devel] The SMP RHEL 5.1 PAE guest can't boot up issue

Avi Kivity wrote: > [copying Thomas for a question about CONSTANT_TSC, below] > > Yang, Sheng wrote: >> I believe I have found the root cause of SMP RHEL5.1 PAE guest can't boot up >> issue. The problem was caused by >> kvm:6685637b211ad67bdce21bfd9f91bc888b3acb4f >> "KVM: VMX: Ensure vcpu time

[kvm-devel] Status of FreeBSD 6.3 as a guest

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,

Re: [kvm-devel] gfxboot disable

[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 p

Re: [kvm-devel] gfxboot disable

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! Mail---

Re: [kvm-devel] [PATCH] QEMU/KVM: large page support

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 > ===

Re: [kvm-devel] [PATCH] KVM: large page support

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% i

Re: [kvm-devel] gfxboot disable

[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. > > >

Re: [kvm-devel] [PATCH] QEMU/KVM: large page support

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),

Re: [kvm-devel] [PATCH] QEMU/KVM: large page support

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 a

Re: [kvm-devel] [PATCH] Don't explicitly set BAR values for VMware VGA

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 pa

Re: [kvm-devel] [PATCH] KVM: large page support

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). -- er

Re: [kvm-devel] [PATCH] fix screen corruption bug in vga_draw_graphic()

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 onl

Re: [kvm-devel] [PATCH] Don't explicitly set BAR values for VMware VGA

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 t

Re: [kvm-devel] [PATCH] Move common VGAState attributes to VGA_STATE_COMMON

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 comm