RE: [Qemu-devel] rtc: lost some interrupts at 1024Hz.

2006-07-10 Thread Armistead, Jason
Brad Campbell wrote: >The VM behaves perfectly until I do a suspend/resume of the host. When the machine comes back, most >of the time (not all the time however) it ends up flooding my logs with this message. > >Jul 8 17:26:03 localhost kernel: [43299223.91] rtc: lost some interrupts at 1024

[Qemu-devel] qemu/hw rtl8139.c

2006-07-10 Thread Fabrice Bellard
CVSROOT:/sources/qemu Module name:qemu Changes by: Fabrice Bellard06/07/10 21:38:17 Modified files: hw : rtl8139.c Log message: fixed for TCP segmentation offloading - removed dependency on slirp.h (Igor Kovalenko) CVSWeb URLs: http://cvs.sav

Re: [Qemu-devel] qemu/hw rtl8139.c

2006-07-10 Thread Igor Kovalenko
On 7/9/06, Igor Kovalenko wrote: Hi!This updated patch against current CVS implements TCP segmentation offloading for RTL8139 in C+ mode.I fixed a couple of problems in implementation (wrong sequence number calculation), and now TCP performance seem to be normal. Dependency on slirp.h header is now

Re: [Qemu-devel] rtc: lost some interrupts at 1024Hz.

2006-07-10 Thread Fabrice Bellard
It seems to be a host kernel problem. Regards, Fabrice. Brad Campbell wrote: G'day all, Just wonder if anyone else is seeing this. I've not had a chance to track it down or try to debug it yet. I'm running latest QEMU CVS with kqemu and the -no-tsc patch on a vanilla 2.6.17.3 kernel with

[Qemu-devel] qemu kqemu.c

2006-07-10 Thread Fabrice Bellard
CVSROOT:/sources/qemu Module name:qemu Changes by: Fabrice Bellard06/07/10 19:53:43 Modified files: . : kqemu.c Log message: monitor/mwait workaround CVSWeb URLs: http://cvs.savannah.gnu.org/viewcvs/qemu/kqemu.c?cvsroot=qemu&r1=1.11&r2=1.12

[Qemu-devel] qemu/target-i386 exec.h helper.c op.c translate.c

2006-07-10 Thread Fabrice Bellard
CVSROOT:/sources/qemu Module name:qemu Changes by: Fabrice Bellard06/07/10 19:53:04 Modified files: target-i386: exec.h helper.c op.c translate.c Log message: monitor/mwait support CVSWeb URLs: http://cvs.savannah.gnu.org/viewcvs/qemu/target-i386/exec

Re: [Qemu-devel] -kernel-kqemu Bug? Win2k reboots

2006-07-10 Thread my_trash
It crashes shorty after joining a table... > -Ursprüngliche Nachricht- > Von: qemu-devel@nongnu.org > Gesendet: 10.07.06 18:59:12 > An: qemu-devel@nongnu.org > Betreff: Re: [Qemu-devel] -kernel-kqemu Bug? Win2k reboots > [EMAIL PROTECTED] wrote: > > Ok, > > > >> How much ram are you al

Re: [Qemu-devel] -kernel-kqemu Bug? Win2k reboots

2006-07-10 Thread Brad Campbell
[EMAIL PROTECTED] wrote: Ok, How much ram are you allocating the guest? 256MB What is your host kernel version? Kernel 2.6.15 (Ubuntu Dapper) What is your qemu version? 0.8.1 with Mouse Wall and DHCP patch What is your kqemu version? 1.3.0pre09 How much ram does your host have? 1GB

Re: [Qemu-devel] -kernel-kqemu Bug? Win2k reboots

2006-07-10 Thread my_trash
Ok, > How much ram are you allocating the guest? 256MB > What is your host kernel version? Kernel 2.6.15 (Ubuntu Dapper) > What is your qemu version? 0.8.1 with Mouse Wall and DHCP patch > What is your kqemu version? 1.3.0pre09 > How much ram does your host have? 1GB > What command line optio

Re: [Qemu-devel] -kernel-kqemu Bug? Win2k reboots

2006-07-10 Thread Brad Campbell
[EMAIL PROTECTED] wrote: Hi all! I asked this already in user forum, with no replies :(( I have constantly win2k reboots when using -kernel-kqemu. No bluescreen, just reboot after a few seconds, for example when using PartyPoker software... Without -kernel-kqemu, it works fine. I expected win

[Qemu-devel] -kernel-kqemu Bug? Win2k reboots

2006-07-10 Thread my_trash
Hi all! I asked this already in user forum, with no replies :(( I have constantly win2k reboots when using -kernel-kqemu. No bluescreen, just reboot after a few seconds, for example when using PartyPoker software... Without -kernel-kqemu, it works fine. I expected win2k to work with this option

R: [Qemu-devel] PCI bridging

2006-07-10 Thread Palleni, F. - Franco -
> This has been discussed a coupe of times before[1]. > Short answer is that it requires either guest OS support (and corresponding > support in the guest OS drivers), or that the device does not use DMA. > Paul Tank you for the answer Regards Franco -Messaggio originale- Da: Paul Broo