Hollis Blanchard wrote:
> There are a bunch of x86-specific fields in struct kvm_run:
> /* in */
> __u8 request_interrupt_window;
> __u8 padding1[7];
>
> /* out */
> __u8 if_flag;
> __u8 padding2[2];
>
> /* in (pre_kvm_run), out (post_kvm_run) */
>
Zhang, Xiantao wrote:
> Hollis Blanchard wrote:
>
>> There are a bunch of x86-specific fields in struct kvm_run:
>> /* in */
>> __u8 request_interrupt_window;
>> __u8 padding1[7];
>>
>> /* out */
>> __u8 if_flag;
>> __u8 padding2[2];
>>
>> /* in (pre_kvm_run),
Hollis Blanchard wrote:
> On Wed, 2008-01-09 at 10:39 +0200, Avi Kivity wrote:
>
>> Zhao, Yunfeng wrote:
>>
>>> Today's tip fails to compile with following error messages:
>>>
>>>
>> [...]
>>
>> Fixed now. Hollis, I had to revert your asm symlink patch to fix this,
>> so we need
Christian Ehrhardt wrote:
> This includes the comments from Jerone. Moving the targets back into the
> Makefile e.g. easen things for people looking at the Makefile for the first
> time and looking for targets. So here v2 of the patch.
> changes to v1:
> - defining per arch targets via variables i
Hello,
When a vmentry failure occurs, where is it caught? I see that
VMX_EXIT_REASONS_FAILED_VMENTRY is defined but I don't see where it is
used. Shouldn't there be something in handle_excetion() like:
static int handle_exception(struct kvm_vcpu *vcpu, struct kvm_run
*kvm_run) {
struct
Dan Kenigsberg wrote:
> On Wed, Jan 09, 2008 at 07:46:04PM +0100, Alexander Graf wrote:
>
>> Darwin requires SSSE3 in 64-bit mode, so KVM needs to reveal the
>> appropriate CPUID flag. I could not find a proper define in the kernel
>> headers, so I just added the specific bit number.
>>
>
>
On Wed, 2008-01-09 at 23:08 -0500, Javier Guerra Giraldez wrote:
> On Wednesday 09 January 2008, Dor Laor wrote:
> > Some figures: Linux rx 350Mbps, tx 150bps, Windows rx 700mbps, tx 100 mbps.
>
> very nice!
>
> in a related note, the VMWare tools package, which is supposed to 'enhance
> perfor
Christoph Lameter wrote:
> On Wed, 9 Jan 2008, Andrea Arcangeli wrote:
>
>
>> This patch is a first basic implementation of the mmu notifiers. More
>> methods can be added in the future.
>>
>> In short when the linux VM decides to free a page, it will unmap it
>> from the linux pagetables. Howev
On Thu, Jan 10, 2008 at 04:11:51PM +0900, Akio Takebe wrote:
> Hi, Marcelo
>
> >+struct balloon_buf *alloc_balloon_buf(struct virtio_device *vdev, gfp_t
> >flags)
> >+{
> >+struct balloon_buf *buf;
> >+
> >+buf = kzalloc(sizeof(struct balloon_buf), flags);
> >+if (!buf)
> >+
Am Dienstag, 18. Dezember 2007 schrieb Rusty Russell:
> To me this points to doing interrupt suppression a different way. If we
> have a ->disable_cb() virtio function, and call it before we call
> netif_rx_schedule, does that fix it?
The fix looks good and I agree with it.
There is one problem
On Sat, Jan 05, 2008 at 07:53:03PM -0600, Carlo Marcelo Arenas Belon <[EMAIL
PROTECTED]> wrote:
> there has to be something wrong with your build system as from the log it
> seems you are using "-I /include " which most likely doesn't exist
right, that was the problem.
for the record, i needed .
Hi, Marcelo
>> >+static int kvm_balloon_inflate(struct virtballoon *v, int32_t npages)
>> >+{
>> >+ LIST_HEAD(tmp_list);
>> >+ struct page *page, *tmp;
>> >+ struct balloon_buf *buf;
>> >+ u32 *pfn;
>> >+ int allocated = 0;
>> >+ int i, r = -ENOMEM;
>> >+
>> >+ buf = alloc_balloon_bu
On Thu, Jan 10, 2008 at 01:44:18PM +0200, Avi Kivity wrote:
> Christoph Lameter wrote:
>> On Wed, 9 Jan 2008, Andrea Arcangeli wrote:
>>
>>
>>> This patch is a first basic implementation of the mmu notifiers. More
>>> methods can be added in the future.
>>>
>>> In short when the linux VM decides
On Thu, 2008-01-10 at 21:27 +0900, Akio Takebe wrote:
> Hi, Marcelo
>
> >> >+static int kvm_balloon_inflate(struct virtballoon *v, int32_t npages)
> >> >+{
> >> >+ LIST_HEAD(tmp_list);
> >> >+ struct page *page, *tmp;
> >> >+ struct balloon_buf *buf;
> >> >+ u32 *pfn;
> >> >+ int allocated = 0;
>
Robin Holt wrote:
>
>> The patch does enable some nifty things; one example you may be familiar
>> with is using page migration to move a guest from one numa node to another.
>>
>
> xpmem allows one MPI rank to "export" his address space, a different
> MPI rank to "import" that address space,
On Thu, 10 Jan 2008 11:19:58 +0100
Guillaume Thouvenin <[EMAIL PROTECTED]> wrote:
> I tried but it didn't catch any vmentry failures (and I know that
> there is at least one during the test).
I think that there is a vmentry failure because qemu-system-x86_64
crashes with following error:
"exc
On Thu, Jan 10, 2008 at 03:27:24PM +0200, Avi Kivity wrote:
> Robin Holt wrote:
>>
>>> The patch does enable some nifty things; one example you may be familiar
>>> with is using page migration to move a guest from one numa node to
>>> another.
>>>
>>
>> xpmem allows one MPI rank to "export"
On Thu, 2008-01-10 at 08:56 +0200, Avi Kivity wrote:
>
> IIRC endianness is a per-page attribute on ppc, no? Otherwise you'd
> have a global attribute instead of per-access.
The MMU in some PowerPC can have per-page endianness, but not all. On a
processor that supports this attribute, I expect
Guillaume Thouvenin wrote:
> On Thu, 10 Jan 2008 11:19:58 +0100
> Guillaume Thouvenin <[EMAIL PROTECTED]> wrote:
>
>
>> I tried but it didn't catch any vmentry failures (and I know that
>> there is at least one during the test).
>>
>
> I think that there is a vmentry failure because qem
Hollis Blanchard wrote:
> On Thu, 2008-01-10 at 08:56 +0200, Avi Kivity wrote:
>
>> IIRC endianness is a per-page attribute on ppc, no? Otherwise you'd
>> have a global attribute instead of per-access.
>>
>
> The MMU in some PowerPC can have per-page endianness, but not all. On a
> proces
> the next step would be to emulate LSI SCSI chips, eh?
Qemu already does.
Paul
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doub
Am Donnerstag, 10. Januar 2008 schrieb Christian Borntraeger:
> Am Dienstag, 18. Dezember 2007 schrieb Rusty Russell:
> > To me this points to doing interrupt suppression a different way. If we
> > have a ->disable_cb() virtio function, and call it before we call
> > netif_rx_schedule, does that f
Am Donnerstag, 10. Januar 2008 schrieb Christian Borntraeger:
> Am Donnerstag, 10. Januar 2008 schrieb Christian Borntraeger:
> > Am Dienstag, 18. Dezember 2007 schrieb Rusty Russell:
> > > To me this points to doing interrupt suppression a different way. If
we
> > > have a ->disable_cb() virtio
On Jan 10, 2008, at 10:23 AM, Hollis Blanchard wrote:
> On Thu, 2008-01-10 at 08:56 +0200, Avi Kivity wrote:
>>
>> IIRC endianness is a per-page attribute on ppc, no? Otherwise you'd
>> have a global attribute instead of per-access.
>
> The MMU in some PowerPC can have per-page endianness, but n
Hello All,
I was trying to get Vista 64-bit to boot off QEMU and was pointed to this
list from the QEMU developers list. From the guest compatibility page I
could gather that KVM with Intel host is able to boot a Vista 64-bit guest,
however the stand-alone version of QEMU does not (yet) support bo
This includes the comments from Avi to "[PATCH] portability: add top level
config-$arch files v2". Putting the arch dependencies into if's saves us 4
config-$arch files which are not essential to fix the current issue.
Since this is copy&paste from Avis response to v2 I added him to the From list
Hi,
On 09/01/2008, Dor Laor <[EMAIL PROTECTED]> wrote:
> It which supports TCP/UDP and IP transmit checksum, as well as TSO.
> It has been tested with Linux (2.6.18|22|23|24)++ and Windows XP (using
> the driver supplied at the intel download site).
> Windows Vista recognizes it but there is no tr
On Thu, Jan 10, 2008 at 03:36:19PM +, Paul Brook wrote:
> > the next step would be to emulate LSI SCSI chips, eh?
>
> Qemu already does.
Quite a different one from vmware, though :)
-
Check out the new SourceForge.net M
On Thu, 10 Jan 2008, Avi Kivity wrote:
> So this is yet another instance of hardware that has a tlb that needs to be
> kept in sync with the page tables, yes?
Correct.
> Excellent, the more users the patch has, the easier it will be to justify it.
We'd like to make sure though that we can slee
On Thu, 10 Jan 2008, Avi Kivity wrote:
> Actually sharing memory is possible even without this patch; one simply
> mmap()s a file into the address space of both guests. Or are you referring to
> something else?
A file from where? If a file is read by two guests then they will have
distinct page
Here is the package deal we're running for this week
Currently Practicing Medical Doctors in America
788,614 in total * 17,576 emails
34 primary and secondary specialties
Sort by over a dozen different fields
American Pharmaceutical Company Contact List
47,000 personal emails and names of
On Thu, 2008-01-10 at 17:28 +0200, Avi Kivity wrote:
> I'll apply that patch (with a #ifdef CONFIG_PPC so other archs don't
> use it by mistake).
I don't think that's the right ifdef. For example, I believe IA64 can
run in BE mode and so will have the same issue, and there are certainly
other arch
Bugs item #1868937, was opened at 2008-01-11 00:08
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=1868937&group_id=180599
Please note that this message will contain a full copy
andrzej zaborowski wrote:
> Hi,
>
> On 09/01/2008, Dor Laor <[EMAIL PROTECTED]> wrote:
>
>> It which supports TCP/UDP and IP transmit checksum, as well as TSO.
>> It has been tested with Linux (2.6.18|22|23|24)++ and Windows XP (using
>> the driver supplied at the intel download site).
>> Window
On 11/01/2008, Dor Laor <[EMAIL PROTECTED]> wrote:
> andrzej zaborowski wrote:
> > Would it be possible to pick only the useful stuff from the header and
> > put it into the same file, rather than maintaining a copy of a linux
> > header (which is 3.5 bigger than the actual emulation in kLoC)? Qemu
Hello,
I've noticed this strange networking behavior while running kvm-59 modules and
qemu on a custom-compiled 2.6.24-rc5 kernel on x86_64 (2 x Opteron 2210).
When I ping a VM from the host it's running on, I get the following result:
talithaA ~ # ping 10.0.1.1
PING 10.0.1.1 (10.0.1.1) 56(84)
Can hardware breakpoints be set (and trapped, and handled) inside a guest
OS (specifially Windows XP2)?
I noticed the other day that software (malicious code, in fact) packed with
the EXE compressor PELock won't run under QEMU+KVM. I guessed that this was
because h/w breakpoints aren't being trap
Peter Osuchowski wrote:
> talithaA ~ # ping 10.0.1.1
> PING 10.0.1.1 (10.0.1.1) 56(84) bytes of data.
> 64 bytes from 10.0.1.1: icmp_seq=1 ttl=64 time=850 ms
> 64 bytes from 10.0.1.1: icmp_seq=2 ttl=64 time=389 ms
> 64 bytes from 10.0.1.1: icmp_seq=3 ttl=64 time=0.353 ms
> 64 bytes from 10.0.1.1: i
Hi all,
That's a good start to consider BE.
Yes, IA64 support BE and LE.
I have below comments.
What does is_bigendian mean?
Host is runing with BE or guest is running with BE.
Who will set is_bigendian?
For supporing BE,
We need to consider host BE and guest BE.
For IA64, most OS is running w
On Thu, 10 Jan 2008 17:32:35 +0200
Avi Kivity <[EMAIL PROTECTED]> wrote:
> I think 33 is the error code, which means we got a general protection
> fault while accessing segment 0x33.
>
> What guest code is running when this happens? The dump sometimes
> includes the current code.
When it happ
40 matches
Mail list logo
