On 6/9/19 4:49 pm, Brad Campbell wrote:
On 2/9/19 6:23 pm, Brad Campbell wrote:
Here is the holdup :
11725@1567416625.003504:qxl_ring_command_check 0 native
11725@1567416625.102653:qxl_io_write 0 native addr=0
(QXL_IO_NOTIFY_CMD) val=0 size=1 async=0
~100ms delay prior to each logged
On 9/9/19 11:22 pm, Dr. David Alan Gilbert wrote:
Oh, hmm.
Sorry I don't know too much where to look then; you have any of:
a) Windows
b) guest graphics drivers
c) spice server in qemu
and probalby some more.
So I think it's going to be a case of profiling on the two different
On 7/9/19 03:03, Dr. David Alan Gilbert wrote:
* Brad Campbell (lists2...@fnarfbargle.com) wrote:
On 2/9/19 6:23 pm, Brad Campbell wrote:
Here is the holdup :
11725@1567416625.003504:qxl_ring_command_check 0 native
11725@1567416625.102653:qxl_io_write 0 native addr=0 (QXL_IO_NOTIFY_CMD
On 6/9/19 21:38, Brad Campbell wrote:
7022@1567775824.002106:kvm_vm_ioctl type 0xc008ae67, arg 0x7ffe13b0c970
7022@1567775824.002115:kvm_vm_ioctl type 0xc008ae67, arg 0x7ffe13b0c980
7022@1567775824.003122:kvm_vm_ioctl type 0xc008ae67, arg 0x7ffe13b0c970
Does this look familiar to anyone
On 6/9/19 16:49, Brad Campbell wrote:
On 2/9/19 6:23 pm, Brad Campbell wrote:
Here is the holdup :
11725@1567416625.003504:qxl_ring_command_check 0 native
11725@1567416625.102653:qxl_io_write 0 native addr=0 (QXL_IO_NOTIFY_CMD) val=0
size=1 async=0
~100ms delay prior to each logged
On 2/9/19 6:23 pm, Brad Campbell wrote:
Here is the holdup :
11725@1567416625.003504:qxl_ring_command_check 0 native
11725@1567416625.102653:qxl_io_write 0 native addr=0 (QXL_IO_NOTIFY_CMD)
val=0 size=1 async=0
~100ms delay prior to each logged QXL_IO_NOTIFY_CMD on the AMD box which
On 03/02/17 01:14, Brian Rak wrote:
We recently upgraded to qemu 2.8.0, and noticed a bunch of issues with
various non-linux operating systems.
I was able to bisect this down to
83d768b5640946b7da55ce8335509df297e2c7cd being the commit that breaks
things
On 18/01/17 10:21, Brad Campbell wrote:
G'day all,
Upgrading from 2.7.1 to 2.8 on my machines here leaves the guests
without networking. All guests are using a vanilla self-compiled 4.8.12
kernel. The host is using a 4.9.3 kernel.
Guests are using virtio networking into a bridge on the host
G'day all,
Upgrading from 2.7.1 to 2.8 on my machines here leaves the guests
without networking. All guests are using a vanilla self-compiled 4.8.12
kernel. The host is using a 4.9.3 kernel.
Guests are using virtio networking into a bridge on the host.
tcpdump on the bridge shows the guests
a displaychangelistener in the first place for secondary cards.
Remove it.
Reported-by: Brad Campbell lists2...@fnarfbargle.com
Signed-off-by: Gerd Hoffmann kra...@redhat.com
Tested-by: Brad Campbell lists2...@fnarfbargle.com
---
hw/display/qxl.c | 1 -
1 file changed, 1 deletion(-)
diff --git
G'day all,
I've had an annoying problem on a test box and I've only just got around
to bisecting it.
Host is a Debian ~7(ish) system. Fairly stock. Spice and qemu are both
tracking git head. This problem reared its ugly head for me just after
christmas when I updated the qemu tree. I worked
On 30/11/12 23:29, Gerd Hoffmann wrote:
Hi,
This pull updates seabios to current master. The seabios q35 patches
didn't land upstream yet so they miss the boat unfortunaly. As this
update brings an important regression fix we can't wait for them and
risk to not update seabios for 1.3. So
On 05/12/12 20:47, Gerd Hoffmann wrote:
On 12/05/12 11:49, Brad Campbell wrote:
On 30/11/12 23:29, Gerd Hoffmann wrote:
Hi,
This pull updates seabios to current master. The seabios q35 patches
didn't land upstream yet so they miss the boat unfortunaly. As this
update brings
or extends data
already in the supplied backing file.
Signed-off-by: Brad Campbell b...@fnarfbargle.com
---
qemu-img.c | 74 ++-
1 files changed, 57 insertions(+), 17 deletions(-)
diff --git a/qemu-img.c b/qemu-img.c
index c8a70ff..3fb6cbf
On 03/09/12 22:23, Andreas Färber wrote:
Am 03.09.2012 09:46, schrieb Brad Campbell:
Converting to an image with an output backing file would write out the
contents
of the source image whether or not it was already contained in the new backing
file. This commit ensures that the source
On 28/04/11 14:36, Kevin Wolf wrote:
Am 28.04.2011 04:06, schrieb Brad Campbell:
On 27/04/11 22:02, Brad Campbell wrote:
On 27/04/11 21:56, Kevin Wolf wrote:
When you don't have a backing file, leaving an cluster unallocated means
that it's zero. When you have a backing file, it could
G'day all,
This patch makes qemu-img properly consider the contents of the output
backing file when performing a convert operation. All things considered
it would also perform similar to rebase, where you could specify a
completely different backing file and it would just de-dup.
I've poked
On 27/04/11 16:10, Stefan Hajnoczi wrote:
On Wed, Apr 27, 2011 at 4:05 AM, Brad Campbell
lists2...@fnarfbargle.com wrote:
I see there is a bug raised about the behaviour of qemu-img when used to
convert using an output backing file. It allocates every sector whether or not
it already exists
On 27/04/11 18:06, Kevin Wolf wrote:
Am 27.04.2011 10:56, schrieb Brad Campbell:
On 27/04/11 16:10, Stefan Hajnoczi wrote:
On Wed, Apr 27, 2011 at 4:05 AM, Brad Campbell
lists2...@fnarfbargle.com wrote:
I see there is a bug raised about the behaviour of qemu-img when used to
convert using
On 27/04/11 21:56, Kevin Wolf wrote:
When you don't have a backing file, leaving an cluster unallocated means
that it's zero. When you have a backing file, it could be anything. So
if qemu-img convert wanted to save this space, it would have to read
from the backing file and leave the cluster
On 27/04/11 22:02, Brad Campbell wrote:
On 27/04/11 21:56, Kevin Wolf wrote:
When you don't have a backing file, leaving an cluster unallocated means
that it's zero. When you have a backing file, it could be anything. So
if qemu-img convert wanted to save this space, it would have to read
from
G'day all,
I see there is a bug raised about the behaviour of qemu-img when used to
convert using an output backing file. It allocates every sector whether
or not it already exists in the output backing file.
I'm walking my way through the block driver to try and get a handle on
why this is
Resent as I've not seen a trace of the first one in 12 hours..
I'm running git (as of 5 minutes ago) on an AMD Phenom 97xx. Debian stable, 64
bit self compiled kernel.
I've got qemu-system-x86_64 symlinked to qemu
My minimal test case is ...
qemu -drive if=virtio,file=xp_base.qcow2 -cdrom
Carlo Marcelo Arenas Belon wrote:
On Sun, Jan 27, 2008 at 06:01:22PM +, Stefano Stabellini wrote:
I can confirm this, I have the same problem on Kubuntu 7.10 i386 using
either gcc-3.4 or gcc-3.3.
architectural limitation for x86 triggered by cpu-exec.c version 1.131,
reverting to 1.130
Stefano Stabellini wrote:
Brad Campbell wrote:
Carlo Marcelo Arenas Belon wrote:
On Sun, Jan 27, 2008 at 06:01:22PM +, Stefano Stabellini wrote:
I can confirm this, I have the same problem on Kubuntu 7.10 i386
using either gcc-3.4 or gcc-3.3.
architectural limitation for x86 triggered
G'day all,
Getting this on my two development machines with up-to-date CVS as of now..
I did a complete directory removal and fresh CVS checkout just to be sure.
Configured with..
./configure --target-list=i386-softmmu --enable-alsa
gcc-3.4 -Wall -O2 -g -fno-strict-aliasing
Laurent Vivier wrote:
Le mardi 11 décembre 2007 à 10:10 +0100, Fabrice Bellard a écrit :
Hi,
Hi,
At this point I am not interested in integrating it into QEMU as it is
one more API level to maintain in addition to the command line monitor.
However, I can change my mind if several projects
Halim Sahin wrote:
Hello list,
I experienced several problems with qemu under linux using kernel
2.6.18.
The guest system is a debian testing, the host a debian unstable.
kqemu is the newest version from www.qemu.org.
The guest can not start if I give -kernel-kqemu.
The last message is kernel
Halim Sahin wrote:
Hello,
Is the cvs-repo of qemu down?
cvs -z3 -d:pserver:[EMAIL PROTECTED]:/sources/qemu co
qemu
gives me a timeout after a few minutes.
The qemu release 0.9.0 does not work for me.
1. DMA not activable in guest
2. kernel-kqemu causes kernel panic (not the debian package)
3.
This is not a real patch, it's been hand edited and badly whitespace damaged to remove some of my
braindamaged/commented out debugging code that just muddies things up.
Simply posted for comment. I've tested it with WinXP and Ubuntu 6.06 and it appears to do what it's
supposed to with no ill
G'day all.
Has anyone managed to get Win2k or XP reliably running with acpi and kqemu?
I get random errors usually related to memory access according to the blue
screens.
Without ACPI it runs ok.. and without kqemu it runs ok.
I can not (and I've been trying hard) managed to reproduce any
This was working about 4 weeks ago or thereabouts. I just upgraded qemu from cvs and now it won't
boot a stock kernel with -kernel-qemu. (no -kernel-kqemu seems to work just fine)
Qemu Version:
CVS as of 30 mins ago
Host kernel:
Linux bklaptop2 2.6.18-rc4-bkc1 #3 Wed Aug 9 12:01:18 GST 2006
Brad Campbell wrote:
This works: (It was one I had handy in my backup - current as of about
August sometime I think)
$Revision: 1.160 $ $Date: 2006/01/25 17:51:49 $
sigh
But of course that bios.bin on a recent cvs qemu refuses to detect the disks.
I knew I kept rotating incremental rsync
Fabrice Bellard wrote:
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Fabrice Bellard bellard 06/10/01 16:08:15
Modified files:
pc-bios: bios.diff bios.bin
Log message:
synced to Bochs BIOS - use 32 bit pushf/popf in 32 bit PCI bios - moved
some useful
Alessandro Corradi wrote:
Hi all,
I use Debian host os with debian guest os. The problem is that I must to
reinstall kqemu every time I boot my host system.
When I try to load qemu it tells me that it can't open kqemu (first I
load kqemu with modprobe naturallyand it is ok), I chmod 777
G'day all,
I'm developing a series of automated tests for win2k and winxp installs with varying features
enabled/disabled. One thing I've found *really* handy is the ability to stop qemu rebooting and just
have it exit every time the vm tries to reboot. (Enables me to use different command
Fabrice Bellard wrote:
This is a PCI save/restore issue. I am working on it. In between you can
boot and wait until the VGA is initialized by the guest OS and then do
the loadvm.
If you did this, I would have thought you were letting the guest alter the state of the disk image,
you then
Steve Ellenoff wrote:
Is it possible to run a real time OS under qemu? What changes would need
to be made?
Can it even be done?
The guest OS I'm trying to run sets the RTC System Timer 0 to a 0.25ms
interval (~4000Hz)!! The program I'm trying to run on it, expects this
time to be accurate,
andrzej zaborowski wrote:
I don't know if you mean just zeroing unused parts or reordering the
data and stuff like defragmentation. If you mean the former, there's a
universal method:
dd if=/dev/zero of=xxx; rm xxx
where xxx is a path to a new file on the filesystem, which must be
mounted. It
G'day all,
Been playing with multiple vm's on linux and hacking around my suspend/resume
dropped interrupt issues.
I just noticed the /dev/rtc interface appears to be very single use oriented.
If I run multiple vm's
simultaneously on the same machine, the 1st one picks up the interrupt driven
ZIGLIO, Frediano, VF-IT wrote:
Hi,
well, this is not a definitive patch but it works. The aim is to be
able to wipe the disk without allocating entire space. When you wipe a
disk the program fill disk with zero bytes so disk image increase to
allocate all space. This just patch detect null
Avi Kivity wrote:
This _looks_ like it would severely impact cpu load during a write.
Have you done any testing to determine if this is likely to impact a
normal usage scenario?
Why would it? In most cases, the zero test would terminate quickly,
without accessing the entire cluster.
ZIGLIO, Frediano, VF-IT wrote:
I use the patch to reduce image size. I use a RIP (repair is possible)
ISO image to boot a small Linux system where I can issue ntfswipe (or
any other wipe command). Than I can recompress image with qemu-img.
Yes, I do similar at the moment.
I just boot the
Lonnie Mendez wrote:
Perhaps tweaking the value of ep_bInterval for the tablet's status
change endpoint would help? The endpoint descriptor for the tablet
currently has this at 3 milliseconds. The hid mouse reports a 10
millisecond polling interval.
Indeed. I'm not quite sure how or why
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 suspend2.
The VM behaves perfectly until I do a suspend/resume of the host.
[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?
G'day all,
I just attempted a clean Win2k-SP4 install with CVS from today..
Just a couple of gotchas I noticed..
Windows has a couple of install stages the first of which is the old blue screen text mode
format/copy stage which will not work with -kernel-kqemu. So I boot and do that stage
Mikhail Ramendik wrote:
I wrote:
There seems to be an issue with guest Windows 98 SE on qemu 0.8.1 and kqemu
1.3.0pre7, on a Linux host.
Windows 98 SE is visibly very slow; and when qemu is run with -no-kqemu, it
is actually faster.
I forgot to mention that the CPU use as per top is
Christian MICHON wrote:
thanks for the tips.
unfortunately, rh72 means xfree86 4.1.0 (event with updates)
xfree86 4.2 means at least rh73
I read somewhere that evtouch driver is actually for kernel 2.6
and at least xorg (not xfree 4.x). I tried to fiddle with the usb
tablet in rh72, but no luck
Brad Campbell wrote:
Also I can't access the monitor (which I can with the other vnc patch)
... again, when I get a chance.
Oh how I wish I'd read the todo carefully.. thumps head on desk
--
Human beings, who are almost unique in having the ability
to learn from the experience of others
Troy Benjegerdes wrote:
Now, does anyone have instructions on how to get Win2k installed and
updated to the latest set of security patches? I can get service pack 4
installed, but running windowsupdate seems to never work right.
If I run it up with -win2k-hack then windowsupdate works fine..
Troy Benjegerdes wrote:
On Wed, Apr 26, 2006 at 12:50:16AM +0200, Fabrice Bellard wrote:
Well, there is a change log in the archive and here it is:
version 1.3.0pre6:
- compile fix for Linux kernel version = 2.6.16
- better null LDT handling (aka Plan9 and ReactOS bug)
- moved monitor code to
Troy Benjegerdes wrote:
On Thu, Feb 09, 2006 at 04:01:34PM -0600, Anthony Liguori wrote:
Jim C. Brown wrote:
-kernel-kqemu virtualizes ring 0 code.
So it basically makes qemu do what VMware does.
IIRC someone reported a 33% speedup with the new option.
That was me. That was a 33% speedup
Troy Benjegerdes wrote:
On Mon, Apr 10, 2006 at 12:23:05PM +0400, Brad Campbell wrote:
Anthony Liguori wrote:
I spent some time cleaning this all up. The following integrates Brad's
patches and the patch from
http://gnome.dnsalias.net/patches/qemu-hidmousexp.patch
It adds a new emulated
Auke Kok wrote:
no matter how you turn Linus' arguments, he doesn't like anything else
than ports from windows driver objects linked, and I can really agree
I think you best re-read anything from Linus on that subject.
What he has said is something derivative of the kernel.
Now we have
Leonardo E. Reiter wrote:
Sorry about that... Brad, very well done!
Ta :)
Anthony did a great job doing the stuff I'm knaff at (making clean and mergable code) and the sdl
hookups.
I just hacked the hid stuff (about 150 win2k reboots in there).
It works with Win98 also, but Win98 seems to
Hetz Ben Hamo wrote:
I'm sorry to bring this issues back from the dead:
* Full disk issues
* Service pack issues
I Do know that both these issues have been dealt before, but yet,
there is no fix from the QEMU application itself, compared to the
competitors..
One thing that I don't understand
Juergen Pfennig wrote:
Hello ...
Please note: I will send the Async IO stuff later, see below.
This Patch: Here is a very simple patch to ide.c that does not change
the controller type and that lets an existing win2003 in-
stallation use multi-sector IO and/or DMA.
Brad Campbell wrote:
The wheel works in SDL although there is currently a bug where it steps
by 2 instead of 1.. so it's ok for scrolling, but scrolling through a
selection box causes it to skip every second selection.
I've not tested the wheel with the vnc patch yet. I'll get to those
Lonnie Mendez wrote:
Please see the patch posted yesterday to this mailing list:
http://gnome.dnsalias.net/patches/qemu-hidmousexp.patch
Ta for that.. not sure how I missed it.
Now to try and get it to work..
Sprinkling printf's around the place it inits the usb controller and mouse,
Brad Campbell wrote:
Lonnie Mendez wrote:
Please see the patch posted yesterday to this mailing list:
http://gnome.dnsalias.net/patches/qemu-hidmousexp.patch
Ta for that.. not sure how I missed it.
Now to try and get it to work..
Ok.. 1st cut.. it's not great, and it's not hooked up
Anthony Liguori wrote:
+kbd_mouse_abs_event(dx * 0x7FFF / width,
+ dy * 0x7FFF / height,
I had just made that same mod to my tree.. solved the tracking problem
perfectly.
Now if only it would work under win98 without modification..
Look what I just stumbled
Anthony Liguori wrote:
I wonder.. does windows switch over from ps2 to hid or just react to
both and given hid is more positive about where it wants the mouse to
go it wins ?
I'm sure I've used a ps2 mouse and a usb mouse on windows before.. I'm
thought they both worked at the same time.
I
Anthony Liguori wrote:
Final one of the night. This patch disables relative mouse reporting
and disables grab automatically the first time SDL detects that the
absolute mouse was enabled. Needs a lot of cleanup but I'm very happy
with the user experience on this one.
Perfect with a
Anthony Liguori wrote:
Final one of the night. This patch disables relative mouse reporting
and disables grab automatically the first time SDL detects that the
absolute mouse was enabled. Needs a lot of cleanup but I'm very happy
with the user experience on this one.
Wish I'd just gone
Leonardo E. Reiter wrote:
The mouse sync solution we have in Win4Lin Pro is okay, but it's a bit
slow and I'd like to do something much cleaner. Of course if I do the
wacom tablet implementation, it will be open source and part of QEMU
itself.
This link might or might not be intersting
Andrew Barr wrote:
Hi again. I'm still working on my Windows 2000 SP4 VM, and I've discovered
that running Windows Update (Internet Explorer 6) causes behavior similar to
the disk full bug encountered during Windows 2000 setup. When it gets to
the part where it's looking for updates (the green
Leonardo E. Reiter wrote:
This is by no means a complete patch (do not apply it as it will break
usb-hid.c), but it adjusts the report descriptor in usb-hid.c to provide
position in 16-bits, and in absolute coordinates:
Index: usb-hid.c
Andrew Barr wrote:
I'm running a Windows 2000 SP4 guest on a Linux 2.6.16 host with Qemu CVS and
kqemu 1.3.0pre3. I am trying to use -kernel-kqemu. I have been allocating 256
MB of RAM to my guest (out of 768 MB total) and I have found that using that
amount of memory with -kernel-kqemu causes
Fabrice Bellard wrote:
Hi,
I just released a new version of kqemu which fixes some recently
discovered issues. The fixes are the following:
- Support for guest Linux kernels compiled with gcc = 3.3
Tested with 2.4.26 2.6.16 - gcc-3.2, gcc-3.3, gcc-3.4 gcc-4.0.2
Win2k-SP3, Win2k-SP4,
Kazu wrote:
I tested Linux guest/WinXP host but the host OS crashed.
I believe -kernel-kqemu is still somewhat experimental on Windows host.
Redhat 7.2 guest/Fedora Core 4 host with normal kqemu is slower
than -no-kqemu. Why ?
Have you got your tmpfs set up correctly so qemu can place its
Ed Swierk wrote:
I'm still getting a kernel panic running a Linux guest kernel with
-kernel-qemu. I'm using kqemu-1.3.0pre5 and
qemu-snapshot-2006-03-27_23.
The guest kernel is a precompiled Fedora Core 4 kernel, version
2.6.14-1.1656_FC4. It works fine with kqemu in non-kernel-kqemu mode.
Any
Andrew Barr wrote:
I'm running a Windows 2000 SP4 guest on a Linux 2.6.16 host with Qemu CVS and
kqemu 1.3.0pre3. I am trying to use -kernel-kqemu. I have been allocating 256
MB of RAM to my guest (out of 768 MB total) and I have found that using that
amount of memory with -kernel-kqemu causes
G'day all,
The -kernel-kqemu with linux guest bug is still at large, however it appears if you compile your
kernel with gcc-3.2.2 it will work. (yay!). Further investigation continues.
I've posted a monolithic 2.6.16 kernel compiled with gcc-3.2.2 at
http://fnarfbargle.dyndns.org:81/qemu/
--Resend-- Not sure why but this did not make the list the 1st time around
G'day all,
The -kernel-kqemu with linux guest bug is still at large, however it appears if
you compile your
kernel with gcc-3.2.2 it will work. (yay!). Further investigation continues.
I've posted a monolithic 2.6.16
--RESEND-- Can someone let me know if this comes through twice? I'm having huge problems getting
through to the list it would appear.
Andrew Barr wrote:
I'm running a Windows 2000 SP4 guest on a Linux 2.6.16 host with Qemu CVS and
kqemu 1.3.0pre3. I am trying to use -kernel-kqemu. I have been
Brad Campbell wrote:
Fabrice Bellard wrote:
Try the following patch:
diff -u -w -r1.39 helper2.c
--- helper2.c 4 Dec 2005 18:46:06 - 1.39
+++ helper2.c 20 Mar 2006 23:38:51 -
@@ -110,6 +110,7 @@
env-pat = 0x0007040600070406ULL;
env-cpuid_ext_features = 0
Fabrice Bellard wrote:
Try the following patch:
diff -u -w -r1.39 helper2.c
--- helper2.c 4 Dec 2005 18:46:06 - 1.39
+++ helper2.c 20 Mar 2006 23:38:51 -
@@ -110,6 +110,7 @@
env-pat = 0x0007040600070406ULL;
env-cpuid_ext_features = 0;
G'day all,
I've had *great* results running win2k and xp with -kernel-kqemu on an Athlon
host under linux 2.6,
however my experiments using a linux guest have resulted in complete kernel
bombs..
Is there anything I should be doing/thinking about when compiling a linux kernel for use as a guest
Brad Campbell wrote:
G'day all,
I've had *great* results running win2k and xp with -kernel-kqemu on an
Athlon host under linux 2.6,
however my experiments using a linux guest have resulted in complete
kernel bombs..
Is there anything I should be doing/thinking about when compiling a
linux
malc wrote:
At http://www.boblycat.org/~malc/code/patches/qemu/1_mqemu.tgz you will
find two patches and binary XFree86 module that allows grabless mouse
operation.
Steps:
a. patch QEMU with 1_mqemu.patch
b. in the guest copy mouse_drv.o to /usr/X11R6/lib/modules/input
Binary mouse_drv.o
Emmanuel Pellereau wrote:
Le Mardi 18 Octobre 2005 23:17, Brad Campbell a écrit :
John R. Hogerhuis wrote:
And it was all a bogus trail.. It's *timer* related!
I made start_rtc_timer() fail (return -1) unconditionally, and voila it
boots first time every time, and any Image I throw at it..
So
John R. Hogerhuis wrote:
Anyway everything seems to be fitting your theory about Athlon
extensions. It would be nice to catch it in the act of trying to run an
Athlon instruction on a Pentium.
And it was all a bogus trail.. It's *timer* related!
I made start_rtc_timer() fail (return -1)
G'day all,
Have discovered a minor hitch with the non-blocking IO patch.
when changing cdrom devices in the console it dies with
qemu: /home/brad/src/qemu/block.c:425: bdrv_cancel_nonblock_io: Assertion `nbst-state ==
STATE_READ_DONE' failed.
Aborted
I start qemu with qemu -hda test.img
John Coiner wrote:
I can't reproduce this. Please check two things:
1. In block.c, the first two lines of the bdrv_cancel_nonblock_io
function should read:
if( bs-nbst.booted
bs-nbst.state != STATE_IDLE ) {
There was a bugfix here, in the most recent version of the patch, and if
Troy Benjegerdes wrote:
Furthermore, the main problem still prevails: There is no sane way to get
the mouse running yet. I played around with a tablet patch someone sent
me, but could not get it to run with a Win98 guest. Since this is my main
use for qemu+vnc, I need a solution for this case.
Kazu wrote:
This patch might help..
http://ebisa.hp.infoseek.co.jp/qemu/arcs/qemu-piix4-udma-20050514.zip
Interesting.. after applying that patch both my win2k and winxp installs
refused to boot.
Winxp gets as far as the safe mode selection screen, select safe mode and it goes straight back
Christian Bourque wrote:
Hi Jim!
Could you send a new Makefile.diff (the old one is not working with
the latest cvs version of QEMU), I would like to test this code too...
I had huge rejects in Makefile.target, configure and vl.h. I merged them by hand and used the latest
gtk2.c and xid_fs.c
88 matches
Mail list logo
