Hello.
Yes but if I understood well, you can't boot on the SCSI device because
of BIOS limitations right?
So the problem remains ... :)
Maybe if you install GRUB and tell him to boot on SCSI.. :)
---
François.
Le mercredi 01 août 2007 à 10:55 -0500, [EMAIL PROTECTED] a écrit :
> on x86, qem
After some issues with qemu vnc I happened upon the patches xen carries
in xen-unstable.hg/tools/ioemu/patches/. After getting them to apply
cleanly they have vastly improved my experience with vnc.
I've taken these, omitted any that are xen specific or add extra
features to qemu, and made some pa
Hi guys,
I have had success using qemu + LinuxBIOS + ADLO to boot win2k and winXP
but with windows vista I have no idea what the problems are.
I have tried to use qemu with its normal bochs bios to boot VISTA
installation DVD. I get the initial loading screen followed by a black
screen ans th
> Management tools for QEMU will have come to rely on existing semantics
> of /usr/bin/qemu being i386.
How about just deprecating it? For example, we could make
/usr/bin/qemu be a script with:
#!/bin/bash
echo "warning: $0 is deprecated, use qemu-system-i386 instead"
exec qemu-system-i386 $@
The correct place for these questions would be the OpenBIOS list
(blatantly cross-posted).
On 7/30/07, Andreas Färber <[EMAIL PROTECTED]> wrote:
>
> Am 19.07.2007 um 09:23 schrieb Natalia Portillo:
>
> > El jue, 19-07-2007 a las 00:46 +0200, Andreas Färber escribió:
> >> Am 18.07.2007 um 18:26 sch
On Tue, Jul 31, 2007 at 08:54:09PM -0500, Anthony Liguori wrote:
> Daniel P. Berrange wrote:
> >This final code patch adds 4 new command line arguments to QEMU to allow
> >the
> >certificate files to be specified. The '-x509cacert', '-x509cert' and
> >'-x509key'
> >parameters are mandatory if the
On Tue, Jul 31, 2007 at 08:50:29PM -0500, Anthony Liguori wrote:
> Daniel P. Berrange wrote:
> >@@ -362,6 +365,7 @@ echo " --enable-alsaenable
> > echo " --enable-alsaenable ALSA audio driver"
> > echo " --enable-fmodenable FMOD audio driver"
> > echo " --en
On Tue, Jul 31, 2007 at 08:46:49PM -0500, Anthony Liguori wrote:
> Daniel P. Berrange wrote:
> >This patch introduces support for VNC protocols upto 3.8 and with
> >it, support for password based authentication. VNC's password based
> >authentication is not entirely secure, but it is a standard and
Bernhard Kauer wrote:
The boot_device is not communicated to the bochsbios
through the CMOS. The following patch allows to boot
via network on the newest bochsbios.
Bernhard Kauer
Index: vl.c
===
on x86, qemu by default does not emulate a scsi device.
if you look at my last set of postings, you will see a patch set for adding
scsi controllers on demand.
its got some code formatting issues, so i understand why it hasnt been merged
as of yet. i intend to publish a new version in the next
The boot_device is not communicated to the bochsbios
through the CMOS. The following patch allows to boot
via network on the newest bochsbios.
Bernhard Kauer
Index: vl.c
===
RCS file: /sources/qemu/qemu/vl.c,v
retrieving rev
The boot_device is not communicated to the bochsbios
through the CMOS. The following patch allows to boot
via network on the newest bochsbios.
Bernhard Kauer
Hello.
Micro$oft's 64bits OSes are known to be problematic w/ kvm.
I guess that the main problem w/ Qemu is that Microsoft Virtual Server
can emulate a SCSI controller and Qemu cannot... I havent checked but I
bet they installed their VM's with just SCSI drivers...
Try to install IDE drivers from
On Wednesday 01 August 2007, Dan Shearer wrote:
> On Wed, Aug 01, 2007 at 03:23:45PM +0100, Paul Brook wrote:
> > Some parts of this code effectively are a "special language" for
> > describing a CPU, that happen to be implemented using the C
> > preprocessor :-)
>
> Right, in the same way that QEM
On Wed, Aug 01, 2007 at 03:23:45PM +0100, Paul Brook wrote:
> Some parts of this code effectively are a "special language" for
> describing a CPU, that happen to be implemented using the C
> preprocessor :-)
Right, in the same way that QEMU devices written in C are in a device
language? :-)
--
On Wednesday 01 August 2007, Dan Shearer wrote:
> On Wed, Aug 01, 2007 at 02:02:13AM +0100, Paul Brook wrote:
> > I suspect making dyngen handle jump tables is not going to happen.
>
> Which brings up the question of dyngen. Very clever and a very good way
> of bootstrapping QEMU in the early days,
I have been playing around with the demonstration Windows images
downloadable from Microsoft just to see how hard it would be to use the
OSs they provide. The images are designed for Microsoft Virtual Server,
but can be successfully converted to qcow2 and vhdx using qemu-img. QEMU
won't boot the im
On Wed, Aug 01, 2007 at 02:02:13AM +0100, Paul Brook wrote:
> I suspect making dyngen handle jump tables is not going to happen.
Which brings up the question of dyngen. Very clever and a very good way
of bootstrapping QEMU in the early days, but too brittle going forwards
now the rest of QEMU wor
On Wednesday 01 August 2007 01:59, Thiemo Seufer wrote:
> > -AIOLIBS="-lrt"
> > +AIOLIBS="-lrt -lpthread"
>
> Why is this needed? Linux toolchains should add -lpthread implicitly.
Our SLES9 toolchain seems not to. It's a near-cosmetic change.
> > +#ifdef __s390__
> > +retaddr = (void*
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer 07/08/01 13:10:29
Modified files:
hw : rtl8139.c
Log message:
Fix rtl8139 checksum calculation, by Tim Deegan.
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/hw/rtl8139.c?cvs
20 matches
Mail list logo