On Wed, Dec 19, 2012 at 03:18:43PM -0500, Jason Baron wrote:
I think you are missing:
-acpitable file=seabios/out/q35-acpi-dsdt.aml
Indeed, that made all the difference !
Thanks much,
--Gabriel
On Wed, Dec 05, 2012 at 07:50:17AM +0100, Gerd Hoffmann wrote:
Ok, so no IRQ declared for the RTC. We have IRQ 8 for both rtc and
hpet, which most likely is the root cause for the issue. You can try
simply dropping the line for testing. I'll try to come up with
something more clever as the
On Tue, 04 Dec 2012 08:40:27 +0100 Gerd Hoffmann wrote:
On Mon, 3 Dec 2012 13:47:04 -0500, Jason Baron wrote:
2) HPET ACPI error
This line: 'IRQNoFlags () {2, 8}' in the HPET acpi table is causing the
folloing ACPI message (removing it makes it go away):
Hmm. That was added to make macos x
On Tue, Dec 04, 2012 at 10:11:38AM -0500, jba...@redhat.com wrote:
I don't have an XP install image anymore, but does replacing 2,8 with
0,8 help ?
no.
On a few of my machines, this is actually coded as
IRQNoFlags ()
{0}
On Tue, Dec 04, 2012 at 05:56:55PM +0100, Gerd Hoffmann wrote:
Ok, and how does the RTC look like on your MacPro?
Device (RTC)
{
Name (_HID, EisaId (PNP0B00))
Name (_CRS, ResourceTemplate ()
{
IO (Decode16,
0x0070, // Range Minimum
0x0070,
Gerd,
On Tue, Nov 13, 2012 at 09:48:10AM +0100, Gerd Hoffmann wrote:
below is what I got running the -usb -device usb-kbd -device usb-mouse
command line with EHCI_DEBUG set to 1.
This isn't what I ment. See docs/tracing.txt for how tracepoint work.
Wildcards (i.e. 'ehci_*') work on
On Tue, Nov 13, 2012 at 05:31:42PM +0100, Gerd Hoffmann wrote:
The last lines of the log are more useful, which is more than 650
lines like this:
usb_ehci_opreg_read 4.767 addr=0x2c str=FRINDEX val=0x0
So macos seems to expect the frame index updating, and probably frame
list rollover
This patch fixes a few debugging print statements whose arguments fell
out of sync over time with changes being made to the active code base.
Signed-off-by: Gabriel Somlo so...@cmu.edu
---
On Mon, Nov 12, 2012 at 11:26:18AM +0100, Gerd Hoffmann wrote:
Seems macos doesn't like something in our
Gerd,
On Mon, Nov 12, 2012 at 11:26:18AM +0100, Gerd Hoffmann wrote:
Seems macos doesn't like something in our ehci emulation ...
Can you send a trace with all ehci tracepoints enabled?
For brevity, I replaced each cluster of six Port X not enabled
lines with one Port 0..5 not enabled, but
Hi,
I'm testing OS X on the q35 tree, and it seems to work quite nicely
so far.
However, with the addition of usb-ehci1 in the latest round of
updates, I've started experiencing hangs during OS X boot.
First, what works:
With the following command line (usb items on the last line):
Paolo,
On current git master, if I do:
./configure --prefix=/home/somlo/KVM-OSX/SCRATCH --target-list=x86_64-softmmu
make clean
make
I end up with:
CCqemu-timer.o
qemu-timer.c: In function `init_timer_alarm':
qemu-timer.c:780:5: error: implicit declaration of function `pthread_atfork'
Jan,
After my most recent pull from qemu git master, I realized I can no
longer use '-monitor stdio' together with '-enable-kvm'. They each
work separately, but when used together, qemu dies with the following
error:
$ bin/qemu-system-x86_64 -enable-kvm -monitor stdio
failed to initialize KVM:
Some guest operating systems' drivers (Mac OS X in particular) fail to
properly initialize the Receive Address registers (probably expecting
them to be pre-initialized by an earlier component, such as a specific
proprietary BIOS). This patch pre-initializes the RA registers, allowing
OS X
Some guest operating systems' drivers (Mac OS X in particular) fail to
properly initialize the Receive Address registers (probably expecting
them to be pre-initialized by an earlier component, such as a proprietary
BIOS). This patch pre-initializes the RA registers, allowing OS X
networking to
On Fri, Oct 26, 2012 at 04:24:44PM -0400, Jason Baron wrote:
Thanks for the bug report! What OS are you running? I'm not seeing any
issue with -usbdevice keyboard on Fedora.
I was using this:
bin/qemu-system-x86_64 \
-M pc_q35 -L q35-seabios/out \
-usbdevice keyboard \
-hdd
Jason,
Commit d8b0dbdba325773469733222a167b54aca74de55 in the q35 tree breaks
'-usbdevice keyboard' for me. Instead of being able to type at the VM,
none of the keypresses make it through, and qemu stderr soon starts
logging this error: usb-kbd: warning: key event queue full.
Specifically, it's
701 - 716 of 716 matches
Mail list logo
