G'day all,
I have a disk image here of Win2k-SP4 with AutoCAD installed.
It's a 4G QCOW filesystem. I have burned it on a DVD with QEMU and a few other bits and I carry it
around with me alongside a Knoppix disk so I always have my CAD system with me wherever I go.
Now this has worked great fo
These patches provide fixes/updates/enhancement to the native OS
X(COCOA) port.
Since the qemu CVS version of qemu has still a broken keyboard input and
lacks some features of it's SDL counterpart, I post two patches that
will add features similar to SDL and more. These patches contain only
f
On Mon, Oct 17, 2005 at 09:39:52PM +0200, Hetz Ben Hamo wrote:
> actually - the direct link now is simpler: http://qemu.dad-answers.com :)
>
> Thanks,
> Hetz
>
Fabrice still needs to update the link on the official qemu website.
> On 10/17/05, Nis Jorgensen <[EMAIL PROTECTED]> wrote:
> > The li
actually - the direct link now is simpler: http://qemu.dad-answers.com :)
Thanks,
Hetz
On 10/17/05, Nis Jorgensen <[EMAIL PROTECTED]> wrote:
> The link to the User Forum on
> http://fabrice.bellard.free.fr/qemu/lists.html is dead. It seems to
> have moved to here
>
> http://m2.dad-answers.com/qe
The link to the User Forum on
http://fabrice.bellard.free.fr/qemu/lists.html is dead. It seems to
have moved to here
http://m2.dad-answers.com/qemu-forum/
(I would have sent mail directly to the webmaster (Fabrice?), but I
couldn't find any contact information on the website)
--
Nis Jorgensen
On Sun, 2005-10-16 at 22:02 -0400, John Coiner wrote:
> It was a tiny bug...
>
> Windows does not like QEMU's DHCP server. Windows always issues
> DHCPDISCOVER and DHCPREQUEST packets in pairs: first the DHCPDISCOVER,
> followed by a DHCPREQUEST. The DHCPREQUEST is a sanity check. Windows
> wa
Henrik Nordstrom schrieb:
> On Fri, 14 Oct 2005, Alexander Skwar wrote:
>
>> QEMU Linux test distribution (based on Redhat 9)
>>
>> Type 'exit' to halt the system
>>
>> SIOCSIFADDR: No such device
>> eth0: unknown interface: No such device
>
> You are missing the correct network driver for the em
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,
>> argon:~/tmp # ./qemu-i386 /bin/ls
>> qemu: Unsupported syscall: 219
>> qemu: Unsupported syscall: 219
>> qemu: Unsupported syscall: 219
>> qemu: Unsupported syscall: 219
>> qemu: Unsupported syscall: 219
>> qemu: Unsupported syscall: 219
>> qemu: Unsupported syscall: 258
>> qemu: Unsupported sys
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
you didn't
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 -cdr
Hi
I am developing a
custom kernel using Qemu. I have an amd64 system, running an ia32 chroot in
which I build 32 bit kernels and run Qemu to test them. My kernel is a bare
minimum 2.6 and worked just fine until I added the suspend2 (software suspend)
patch and rebuilt.
Now when qemu sta
12 matches
Mail list logo