Hollis Blanchard wrote:
On Mon, 2008-07-07 at 15:56 +0200, [EMAIL PROTECTED] wrote:
From: Christian Ehrhardt <[EMAIL PROTECTED]>
The current implementation of kvmtrace uses always a 64 bit cycle variable,
but get_cycles() which is used to fill it is "unsigned long" which might be 32
bit.
Thi
Bugs item #2014059, was opened at 2008-07-09 10:30
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=2014059&group_id=180599
Please note that this message will contain a full copy
Hi,
I more or less accidently stumbled across a problem when compiling KVM
on the VMI-enabled kernel. Even though that's pretty much useless right
now, I think there might be a day, VMware will emulate VM extensions, in
VMs, so we should probably not keep KVM from running under VMI.
The prob
Hollis Blanchard wrote:
On Mon, 2008-07-07 at 15:56 +0200, [EMAIL PROTECTED] wrote:
From: Christian Ehrhardt <[EMAIL PROTECTED]>
The current implementation of kvmtrace uses always a 64 bit cycle variable,
but get_cycles() which is used to fill it is "unsigned long" which might be 32
bit.
Thi
Avi Kivity wrote:
Alexander Graf wrote:
Netware writes and reads to the DEBUGCTL and LAST*IP MSRs without
further checks and is really confused to receive a #GP during that.
To make it happy we should just make them stubs, which is exactly
what SVM already does.
To support VMX too, I put the
Zhao, Yunfeng wrote:
>> 2. vista auto-unattended installation failed on kvm guests
>>
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1991653&group_id=180599
>>
>
> Is this a duplicate of
>
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1967368&group_id=1
Bugs item #1991653, was opened at 2008-06-12 16:05
Message generated for change (Comment added) made by yunfeng
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1991653&group_id=180599
Please note that this message will contain a full copy of the comment t
On Wed, 2008-07-09 at 11:17 +0200, Christian Ehrhardt wrote:
>
> So the question that is left before changing that is, if the original
> author had something special in mind chosing cycles here.
> I added Eric on CC for that.
>
> I wait with my resubmission of the patch series until all
> archit
jd wrote:
hi
1. It there away to know various states of a VM via console (or any other
means?) ?
-- Running
-- Paused
-- Booting/Shutting down
-- crashed
etc ?
I cant find any console command that can tell that. If this is not
available, is there a plan
On Sun, Jul 06, 2008 at 01:16:13PM +0300, Uri Lublin wrote:
> Hello,
>
> We are happy to announce the availability of kvm-autotest, a test
> framework for KVM based on autotest. Naturally, the purpose is to make
> KVM stable, find/fix bugs faster and prevent regressions. It is to serve
> dev
Ben-Ami Yassour wrote:
From: Kay, Allen M <[EMAIL PROTECTED]>
This patch includes the functions to support VT-d for passthrough
devices.
[Ben: fixed memory pinning]
Signed-off-by: Kay, Allen M <[EMAIL PROTECTED]>
Signed-off-by: Weidong Han <[EMAIL PROTECTED]>
Signed-off-by: Ben-Ami Yassour <[E
Chris Lalancette wrote:
Mike Snitzer wrote:
I've taken to using a bridge (or in virt-manager speak "shared
physical device"). The 'network-bridge' script (and supporting
xen-network-common.sh and xen-script-common.sh) that are provided with
xen rpms (e.g. xen-3.1.0-13.fc8.x86_64.rpm) make this
On Tue, Jul 08, 2008 at 08:08:22PM -0500, Anthony Liguori wrote:
> john cooper wrote:
>> I like it even less. MAP_POPULATE does not fault in physical
>> hpages to the map. Again this was a qemu-side interim bandaid.
>
> Really? That would seem like a bug in hugetlbfs to me.
This is Linux's beha
Marcelo Tosatti wrote:
On Tue, Jul 08, 2008 at 08:08:22PM -0500, Anthony Liguori wrote:
john cooper wrote:
I like it even less. MAP_POPULATE does not fault in physical
hpages to the map. Again this was a qemu-side interim bandaid.
Really? That would seem like a bug in hugetlb
On Wed, Jul 9, 2008 at 11:28 AM, Bill Davidsen <[EMAIL PROTECTED]> wrote:
> A bit of the original problem seems to have been clipped before you read it,
> or I stated it poorly.
i think you're very confused. maybe you got it working the hard way,
but it's really simple to do the easy way.
first,
On Tue, Jul 8, 2008 at 5:16 PM, David S. Ahern <[EMAIL PROTECTED]> wrote:
> There's a bug opened for the network lockups -- see
> http://sourceforge.net/tracker/index.php?func=detail&aid=1802082&group_id=180599&atid=893831
>
> Based on my testing I've found that the e1000 has the lowest overhead
>
On Tue, Jul 8, 2008 at 3:52 AM, Mohammed Gamal <[EMAIL PROTECTED]> wrote:
> On Mon, Jul 7, 2008 at 6:29 PM, Anthony Liguori <[EMAIL PROTECTED]> wrote:
>> Avi Kivity wrote:
>>>
>>> Mohammed Gamal wrote:
>>>
>>> I think they're fine. Can you check the vmentry patch now, with Anthony's
>>> testcase?
This patch, based on an earlier patch by Alexander Graf, adds HPET
emulation to qemu. I am sending out a separate patch to kvm with the
required bios changes.
This work is incomplete.
Currently working (at least generally):
- linux 2.6.25.9 guest
Todo:
- other guest support (i.e. adding whate
This patch, written by Ryan Harper, adds HPET support to BIOS.
Signed-off-by: Beth Kon <[EMAIL PROTECTED]>
diff --git a/bios/Makefile b/bios/Makefile
index 48022ea..3e73fb5 100644
--- a/bios/Makefile
+++ b/bios/Makefile
@@ -40,7 +40,7 @@ LIBS = -lm
RANLIB = ranlib
BCC = bcc
-GCC = gcc -m32
+
I originally sent this to [EMAIL PROTECTED] because
http://kvm.qumranet.com/kvmwiki/Bugs told me so, but then I noticed on
the lists page this email address is used, so I am sending it here again.
(I am not subscribed)
CPU: AMD Phenom X4
KVM version: kvm_62+dfsg-0ubuntu7
Host kernel version: 2.6.
Hi,
I've downloaded and compiled/installed kvm-70 on an AMD-64 box with
linux 2.6.22-14 (ubuntu 7.10). Is it ok to use this combination or
could there be some issues (the old kvm I was using was kvm-64)?
(I started the guest and so far everything seems to be working but I
wanted to double check)
Beth Kon wrote:
This patch, based on an earlier patch by Alexander Graf, adds HPET
emulation to qemu. I am sending out a separate patch to kvm with the
required bios changes.
This work is incomplete.
Currently working (at least generally):
- linux 2.6.25.9 guest
Todo:
- other guest support
Hi,
I'd like to know what happens when the guest kernel or process in the
guest tries to get timing information. For example if a userspace
process in the guest calls nanotime(), getnanotime() or gettimeofday()
functions, then where is the time info read from ?
I had a look thru the latest 2.6.25
23 matches
Mail list logo
