I notice that the "-boot n" etherboot support doesn't appear to work
when emulating x86_64 hardware (invocation as qemu-system-x86_64). Is
this intentional? A known issue?
Am 30.07.2007 um 22:37 schrieb Andreas Färber:
Maybe someone can shed some more light on what exactly needs to be
changed config-wise or is missing in OpenBIOS or qemu in order to
boot AIX 6 or any Linux.
Can't tell you much, but for sure, you won't need support for HFS or
HFS+. HFS supp
GUERRAZ Francois wrote:
> 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.. :)
GRUB uses BIOS...
Laurent
--
- [EMAIL PROTEC
Am 02.08.2007 um 09:51 schrieb Markus Hitter:
Am 30.07.2007 um 22:37 schrieb Andreas Färber:
Maybe someone can shed some more light on what exactly needs to be
changed config-wise or is missing in OpenBIOS or qemu in order to
boot AIX 6 or any Linux.
Can't tell you much, but for sure, y
Hi!
I get the newest version of kqemu (kqemu-1.3.0pre11), and it compiled fine
in various kernels up to 2.6.21.
But when I tried to compile it with 2.6.22, I get this error:
CC [M] /home/hc/tmp/kqemu-1.3.0pre11/kqemu-linux.o
/home/hc/tmp/kqemu-1.3.0pre11/kqemu-linux.c: In function
'kqemu_lock_use
Daniel P. Berrange wrote:
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 secur
SCSI is not the problem as VirtualPC does not emulate it (Virtual Server
does but not VPC up to 2007).
Basically the problem can be more related to ACPI.
Regards
En Wed, 01 Aug 2007 15:33:31 +0100, GUERRAZ Francois
<[EMAIL PROTECTED]> escribió:
Hello.
Micro$oft's 64bits OSes are known t
I'm trying to use qemu to test an install process which involves quite a
bit of downloading. Everything starts up fine (using either ne2k_pci or
rtl8139 hardware), but the multi-GB download typically stalls out about
100-400MB in. Is there anything I can do to prevent this?
There's a warning o
On Wed, Aug 01, 2007 at 01:32:00AM +0200, Juergen Lock wrote:
> On Tue, Jul 31, 2007 at 11:31:58PM +0200, andrzej zaborowski wrote:
> > can you try this change:
> > --- a/target-arm/helper.c
> > +++ b/target-arm/helper.c
> > @@ -840,7 +840,7 @@ void helper_set_cp15(CPUState *env, uint32_t insn,
>
Charles Duffy wrote:
> There's a warning on startup that the system can't set a 1024Hz timer,
> which persists even after I set /proc/sys/dev/rtc/max-user-freq to 1024,
> and I occasionally get warnings at runtime ("Your time source seems to
> be instable or some driver is hogging interrupts").
Th
This loss of connectivity is still happening; at least within my
environment, it's quite reproducible. While I've eliminated the message
about being unable to set the RTC to 1024Hz by recompiling my host
kernel without CONFIG_HPET_RTC_IRQ, the host's kernel is frequently
complaining "rtc: lost some
This appears to only happen with -net tap; I cannot reproduce the issue
with -net user.
12 matches
Mail list logo
