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 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;
+ int i, r = -ENOMEM;
+
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:
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 his address space, a
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
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 not all.
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
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 copypaste from Avis response to v2 I added him to the From list
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
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 sleep
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
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
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=detailatid=893831aid=1868937group_id=180599
Please note that this message will contain a full copy of
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).
Windows Vista
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
has
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
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:
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
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 happened I
21 matches
Mail list logo
