Commit 618ba removed parameter puc, fix it in fake-exec.c.
Signed-off-by: Bernhard Held bh...@mgpi.de
---
target-i386/fake-exec.c |4 +---
target-ia64/fake-exec.c |4 +---
2 files changed, 2 insertions(+), 6 deletions(-)
diff --git a/target-i386/fake-exec.c b/target-i386/fake-exec.c
Am 04.07.2011 12:37, schrieb Michael S. Tsirkin:
On Sun, Jul 03, 2011 at 08:31:11PM +0200, Bernhard Held wrote:
SYS_eventfd2 is not defined on systems with old glibc. These numbers
are working for me, for 32 and 64 bit linux. What means
__NR_eventfd2 does seem to exit?
My system seems to have
Am 28.06.2011 13:09, schrieb Michael S. Tsirkin:
On Mon, Jun 27, 2011 at 08:19:47PM +0200, Jan Kiszka wrote:
From: Jan Kiszkajan.kis...@siemens.com
No longer used.
Signed-off-by: Jan Kiszkajan.kis...@siemens.com
I think it's actually handy to build on old systems which have
a recent enough
Am 03.07.2011 11:57, schrieb Michael S. Tsirkin:
On Sun, Jul 03, 2011 at 12:54:06PM +0300, Michael S. Tsirkin wrote:
On Sun, Jul 03, 2011 at 11:46:51AM +0200, Bernhard Held wrote:
#ifndef _COMPAT_SYS_EVENTFD
#define _COMPAT_SYS_EVENTFD
#includeunistd.h
#includesyscall.h
/* Flags for signalfd
Am 03.06.2011 15:38, schrieb Brad Campbell:
On 02/06/11 07:03, CaT wrote:
On Wed, Jun 01, 2011 at 07:52:33PM +0800, Brad Campbell wrote:
Unfortunately the only interface that is mentioned by name anywhere
in my firewall is $DMZ (which is ppp0 and not part of any bridge).
All of the nat/dnat
I've switched from -0.11.0 to -0.12 and from 2.6.31.6 to 2.6.32.2 to try
the new virtio-memory-API introduced in latest libvirt from git. I can
start VMs f.e. by kvm -cdrom $someiso --enable-kvm but my domain configs
to not work anymore.
Just found the other bug report about this
Fix compile without eventfd.
Signed-off-by: Bernhard Held bh...@mgpi.de
---
compatfd.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- qemu-kvm-0.12.0-rc2/compatfd.c
+++ qemu-kvm-0.12.0-rc2/compatfd.c
@@ -118,9 +118,9 @@
int qemu_eventfd(int *fds)
{
-#if defined(CONFIG_EVENTFD
Hi Arun!
send_cmd() {
QEMU_MONITOR_COMMAND=$1
echo ${QEMU_MONITOR_COMMAND} | socat - UNIX-CONNECT:${FILE_MONITOR}
}
which sends the exit command to the qemu process via a socket file.
Just send system_powerdown, and your guest will receive an ACPI shutdown
request.
Bernhard
There are two more typos:
+echo --disable-cap-device-assignmentdisable KVM device assignemnt
^
+echo --enable-cap-device-assignment enable KVM device assignemnt
Hi Daniel!
Aug 4 17:38:39 ss03 kernel: [4.750023] bnx2 :03:00.0: firmware:
requesting bnx2/bnx2-mips-06-4.6.16.fw
Aug 4 17:38:39 ss03 kernel: [4.751070] bnx2: Can't load firmware file
bnx2/bnx2-mips-06-4.6.16.fw
Aug 4 17:38:39 ss03 kernel: [4.751141] bnx2 :03:00.0: PCI
Hi Daniel!
I've set in the kernel config:
CONFIG_FIRMWARE_IN_KERNEL=y
And what happened? Are you sure you recompiled and booted the new kernel with
CONFIG_FIRMWARE_IN_KERNEL=y?
Although I don't see the asked file in initramfs. The file with full
path is
--- cache-utils.h.orig 2009-04-21 10:46:04.0 +0200
+++ cache-utils.h 2009-04-22 08:39:20.0 +0200
@@ -47,6 +47,8 @@
}
#else
static inline void qemu_sync_idcache(unsigned long start, unsigned long
stop)
+{
+}
#endif
#define qemu_cache_utils_init(envp) do { (void)
does not boot, BIOS complains Boot failed: could not read the boot disk:
-drive file=/dev/VolGroup00/testpart,if=virtio,index=0 \
O.k., this doesn't work on my box too.
Please try with:
-drive file=/dev/VolGroup00/testpart,if=virtio,index=0,boot=on \
Anthony wrote index doesn't have meaning
After an upgrade from kvm-84 to kvm-85 all my guests won't start because
no boot device could be found.
[...]
A rollback to kvm-84 OR changing the hdd from vda to ide for the guests
and everything is OK again
I'm having the same problem and repored it to the list just some hours ago.
No
After an upgrade from kvm-84 to kvm-85 all my guests won't start because
no boot device could be found.
No problem here, my guests run fine with kvm-85 and 2.6.29.1:
-drive file=$IMG,format=raw,cache=none
Are you sure you are using a virtio blockdevice and not a regular ide one?
IIRC,
When updating to kernel 2.6.29.1, I'm unable to boot my Windows XP Pro 32bit
guest. The problem is consistent (actually on both of my laptops, with two
different WinXP guests) and it is fixed immediately when downgrading to
kernel 2.6.28.8 or an older kernel version.
Works for me with
Hi,
this happens on CentOS 5.3:
# cd kvm-85/qemu
# make
CCqemu-nbd.o
CCqemu-tool.o
CCosdep.o
CCcutils.o
In file included from cutils.c:27:
/usr/include/assert.h: In function ‘qemu_sync_idcache’:
/usr/include/assert.h:70: error: storage class specified for parameter
Avi Kivity schrieb:
Bernhard Held wrote:
Windows XP Prof. freezes few seconds after booting on kvm-81 with
hugepages. The cpu load stays at 200% (on 2 cores), the screen is black.
The process can't be killed, a reboot is required.
The same guest runs fine
- without hugepages or
- with kvm-79
Can you check kvm-80? This will help pinpointing the evil commit.
WXP works with kvm-80 and hugepages. There are no problems with kvm-80
and all three guests.
kvm-80 isn't that bad ;-)
Works here. Since there's an mmu fix queued, please try kvm-82 when
it's released.
Of course I will try
The invlpg and sync walkers lack knowledge of large host sptes,
descending to non-existant pagetable level.
Stop at directory level in such case.
Fixes SMP Windows XP with hugepages.
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
I happily confirm that with Marcelo's patch applied
Using this patch on a vanilla 2.6.27 kernel, I get this when I try to
compile it:
arch/x86/kvm/mmu.c: In function ‘kvm_pv_mmu_flush_tlb’:
arch/x86/kvm/mmu.c:2241: error: ‘KVM_REQ_MMU_SYNC’ undeclared (first use
in this function)
arch/x86/kvm/mmu.c:2241: error: (Each undeclared identifier is
21 matches
Mail list logo
