QEMU on Linux hosting FreeDOS running an old DOS serial comm
application.
I want to redirect the guest's COM1 to ttyUSB0 which will have a real
device connected to it.
How is this done with QEMU?
I could use -serial stdio
but how do I get it connected to the usb port? I'm guessing netcat/socat
b
Has anyone been able to boot a Linux 2.6 kernel using
quemu-system-ppc? If so please explain how...
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
While tracking down a problem with getting X to work with the VNC
version of Qemu I discovered a problem in the way the Qemu mouse
emulation was handling mouse reset commands. Turns out, the emulation
code is a little over aggressive in dealing with reset commands for the
mouse. Since there are c
Okay, I finally got around looking at this a little longer and
came up with the port update below. Specifically, I tried to merge
the good parts of the old kqemu wrapper:
- device cloning support on 5.x (multiple vms can use kqemu, tested
and seems to work)
- 4.x support (untested, I'm not sure i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Better to have a architecture/machine pair.
Architecture: x86-64
Machine: PC
Architecture: PowerPC
Machine: Core99
To be coincident with the -M flag and having the possibility of
changing the qemu executable name (that should be in the GUI
conf
On Thu, Aug 04, 2005 at 02:25:05PM +0400, malc_ wrote:
> Since there is no default way to install FMOD on *nixes there is no
> default way to check for it's presence either.
Sounds like configure should be cowardly aborting if one attempts to enable
fmod without specifying the path to the include
On Tue, 12 Jul 2005, Jim C. Brown wrote:
I just tried this with libnet 1.1 (1.1.2.1 to be specific), and it doesn't
seem to work. Pings do not go through. I only handled the vde -> host case
though, do I need to do anything special for host -> vde packets?
Did you fake the ARP response to the
On Thu, 4 Aug 2005, Nardmann, Heiko wrote:
Am Donnerstag, 4. August 2005 11:38 schrieb malc:
On Thu, 4 Aug 2005, Nardmann, Heiko wrote:
Problem:
the current CVS is not compilable with audio enabled.
configure call:
./configure --prefix=/opt/qemu-20050804 --enable-adlib --enable-fmod
You
Am Donnerstag, 4. August 2005 11:38 schrieb malc:
> On Thu, 4 Aug 2005, Nardmann, Heiko wrote:
> > Problem:
> > the current CVS is not compilable with audio enabled.
> >
> > configure call:
> > ./configure --prefix=/opt/qemu-20050804 --enable-adlib --enable-fmo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This was discussed on the mailing list a long ago.
Just it have support for some instructions upper than Pentium II but
not all, so that is why developers decided to stay with CPUID saying
Pentium II.
Think itself like a steroid-Cyrix 5x86 (it
On Thu, 4 Aug 2005, Nardmann, Heiko wrote:
Problem:
the current CVS is not compilable with audio enabled.
configure call:
./configure --prefix=/opt/qemu-20050804 --enable-adlib --enable-fmod
You can not build with FMOD unless you specify paths to FMODs include
and library paths (--fmod-inc
Problem:
the current CVS is not compilable with audio enabled.
configure call:
./configure --prefix=/opt/qemu-20050804 --enable-adlib --enable-fmod
configure output:
Install prefix/opt/qemu-20050804
BIOS directory/opt/qemu-20050804/share/qemu
binary directory /opt/qemu-20050804/bin
Mike Kronenberg wrote:
I'm thinking of a new way to store the images and saved VMs, too.
Maybe we could make something like vpc: A package with the config,
disk-images and saved VMs, located in ~/Documents/QEMU PCs/
QEMU guest PC Format, a Proposal
This should serve as a base for the discuss
13 matches
Mail list logo
