Are you running smp or ht hardware?
Nicholas A. Schembri
> > My feeling is that config files are outdated. When used with a gui,
> > you end up writing silly parsers and stuff and still wrecking things
> > horribly when the the gui writer's expectations don't match reality.
> > When used without a gui, they increase the amount of details one has
> > to
Hi,
I experience a roblem when running qemu on Fedora 7.
I've got CentOS5 installed as a qemu image. When I boot guest OS _without_
kqemu module - it works.
But when booting with kqemu _loaded_ - guest system hangs on early stage (just
after loading initrd.img).
software versions:
* qemu-0.9.0-
On 8/10/07, Anthony Liguori <[EMAIL PROTECTED]> wrote:
> I suspect our best long term bet is a new paravirtual graphics driver
> that's also a standard VESA device and the hope that someone writes a
> proper Windows driver for it.
>
> Regards,
>
> Anthony Liguori
>
Too bad we don't know of any op
Linux operates the HPET timer in legacy replacement mode, which means that the
periodic interrupt of the CMOS RTC is not delivered (qemu won't be able to use
/dev/rtc). Add support for HPET (/dev/hpet) as a replacement for the RTC; the
periodic interrupt is delivered via SIGIO and is handled in the
Avi Kivity wrote:
Anthony Liguori wrote:
Avi Kivity wrote:
This is a big effort but a config file is the right long term
solution.
For which use case? management-full or management-less?
Both. A config file will be useful not just for expressing the
functionality we have today,
Anthony Liguori wrote:
Avi Kivity wrote:
This is a big effort but a config file is the right long term solution.
For which use case? management-full or management-less?
Both. A config file will be useful not just for expressing the
functionality we have today, but also for describ
Jeremy Katz wrote:
On Fri, 2007-08-10 at 17:28 +0100, Paul Brook wrote:
On Thursday 09 August 2007, Jeremy Katz wrote:
The attached adds a PCI subsystem vendor ID of 0x514D (QM ascii->hex)
for the Cirrus emulation so that you can tell that the system is running
under qemu. This will ma
Avi Kivity wrote:
This is a big effort but a config file is the right long term solution.
For which use case? management-full or management-less?
Both. A config file will be useful not just for expressing the
functionality we have today, but also for describing the guest's
environ
On Friday 10 August 2007, Jeremy Katz wrote:
> On Fri, 2007-08-10 at 17:28 +0100, Paul Brook wrote:
> > On Thursday 09 August 2007, Jeremy Katz wrote:
> > > The attached adds a PCI subsystem vendor ID of 0x514D (QM ascii->hex)
> > > for the Cirrus emulation so that you can tell that the system is
>
On Fri, 2007-08-10 at 17:28 +0100, Paul Brook wrote:
> On Thursday 09 August 2007, Jeremy Katz wrote:
> > The attached adds a PCI subsystem vendor ID of 0x514D (QM ascii->hex)
> > for the Cirrus emulation so that you can tell that the system is running
> > under qemu. This will make it so that, eg
Anthony Liguori wrote:
Jorge Lucángeli Obes wrote:
Hi all,
>From what I've gathered, it seems that we have basically four options
at hand. I think it's important to notice, however, that whatever
comes out of this will probably be, as Avi said, a "low-end" solution.
IMHO there's room to have bo
On Thursday 09 August 2007, Jeremy Katz wrote:
> The attached adds a PCI subsystem vendor ID of 0x514D (QM ascii->hex)
> for the Cirrus emulation so that you can tell that the system is running
> under qemu. This will make it so that, eg, we can detect that in X and
> know that resolutions > 800x6
Jorge Lucángeli Obes wrote:
Hi all,
>From what I've gathered, it seems that we have basically four options
at hand. I think it's important to notice, however, that whatever
comes out of this will probably be, as Avi said, a "low-end" solution.
IMHO there's room to have both the high-end libvirt-
On 8/10/07, dmc <[EMAIL PROTECTED]> wrote:
> Brian Wheeler wrote:
> > On Thu, 2007-08-09 at 15:32 -0500, Anthony Liguori wrote:
> >> Avi Kivity wrote:
> >>> Anthony Liguori wrote:
> If you're looking for a low-end solution, another possibility would
> be having a "new" file format which c
> Hi, I am using slack11, kernel 2.6.22, after ./compile; make, I had the
> errors:
...
> To fix it, I included in the kqemu-linux.c file.
I had the same problem, your solution worked for me too. Thanks!
Hugo Segovia
__
Correo Yahoo!
Espacio
16 matches
Mail list logo
