It would be great if QEMU could emulate a 3D video card. We would all be able
to play our games in it. VirtualBox does have a GPL v2 implementation of a 2D
and 3D video card. If there any reason why we can't port their video card to
QEMU?
On Apr 25, 2015, at 12:56 AM, Kris zhang wrote:
> I have same question too, anybody know the reason?
>
>
> On Wednesday, April 8, 2015, Programmingkid wrote:
> > It would be great if QEMU could emulate a 3D video card. We would all be
> > able to play our games in it
On Apr 25, 2015, at 12:00 PM, qemu-discuss-requ...@nongnu.org wrote:
> Kris zhang writes:
>> On Wednesday, April 8, 2015, Programmingkid
>> wrote:
>>> It would be great if QEMU could emulate a 3D video card. We would all be
>> able to play our games in it.
On May 16, 2015, at 5:45 PM, Peter Maydell wrote:
> On 11 May 2015 at 16:18, Programmingkid wrote:
>> Adds any console that is available to the current emulator as a menu item
>> under the View menu.
>>
>> Signed-off-by: John Arbuckle
>
> Thanks; I think
Add Machine menu to the Macintosh interface with pause
and resume menu items. These items can either pause or
resume execution of the guest operating system.
Signed-off-by: John Arbuckle
---
Remove createMachineMenu() function.
Minor space issues fixed.
Patch created on top of cocoa.next branch.
Add "Reset" and "Power Down" menu items to Machine menu.
Signed-off-by: John Arbuckle
---
Changed text "Qemu" to "QEMU".
Moved menu insertion code into main() function.
Changed powerDown menu item's name to powerDownQEMU.
Replaced qemu_system_reset_request() with qmp_system_reset(NULL).
ui/coc
On May 17, 2015, at 5:37 PM, Peter Maydell wrote:
> On 17 May 2015 at 21:09, Programmingkid wrote:
>> You know how there's a "Zoom To Fit" menu item. What if we added a
>> mutually exclusive menu item called "Resize To Fit"? This menu item
>> would
Do we only support user interfaces in the english language, or are multiple
languages supported?
Add Machine menu to the Macintosh interface with pause
and resume menu items. These items can either pause or
resume execution of the guest operating system.
Signed-off-by: John Arbuckle
---
Disable the Resume menu item initially.
ui/cocoa.m | 67 +
Adds all removable devices to the Machine menu as a Change and Eject menu
item pair. ide-cd0 would have a "Change ide-cd0..." and "Eject ide-cd0"
menu items.
Signed-off-by: John Arbuckle
---
Replace NSRunAlertPanel() with QEMU_Alert().
Free currentDevice variable after finished using it.
Add "Re
Laptop users usually have keyboards that are missing the page up and page down
keys. This means they cannot scroll in the monitor. This patch gives laptop
users the ability to scroll in the monitor by having the user push the Control
+ Up/Down arrow keys to scroll one line at a time. Use ALT/Opt
On Mar 13, 2015, at 5:51 AM, Peter Maydell wrote:
> On 13 March 2015 at 04:35, Programmingkid wrote:
>> Laptop users usually have keyboards that are missing the page up and page
>> down keys. This means they cannot scroll in the monitor. This patch gives
>> laptop users
On Mar 13, 2015, at 1:31 PM, Paolo Bonzini wrote:
>
>
> On 13/03/2015 15:48, Programmingkid wrote:
>>
>> On Mar 13, 2015, at 5:51 AM, Peter Maydell wrote:
>>
>>> On 13 March 2015 at 04:35, Programmingkid wrote:
>>>> Laptop users usually have
On Mar 16, 2015, at 9:36 AM, Paolo Bonzini wrote:
>
>
> On 16/03/2015 14:35, Programmingkid wrote:
>> On Mar 16, 2015, at 8:19 AM, Paolo Bonzini wrote:
>>> On 13/03/2015 21:43, Programmingkid wrote:
>>>>> How do you do that in a terminal?
>>>&g
On Mar 16, 2015, at 8:19 AM, Paolo Bonzini wrote:
>
>
> On 13/03/2015 21:43, Programmingkid wrote:
>>> How do you do that in a terminal?
>>
>> I'm not sure what exactly you're asking. I will say past Apple laptop
>> did have the ability to page up
On Mar 16, 2015, at 10:00 AM, Peter Maydell wrote:
> On 16 March 2015 at 13:48, Daniel P. Berrange wrote:
>> The docs[1] still refer to fn+up/down as the way to achieve page up/down,
>> so perhaps your install has simply lost the shortcut mappings ?
>
> Works for me on a 2011 MacBook Air runnin
On Mar 16, 2015, at 9:48 AM, Daniel P. Berrange wrote:
> On Fri, Mar 13, 2015 at 04:43:54PM -0400, Programmingkid wrote:
>>
>> On Mar 13, 2015, at 1:31 PM, Paolo Bonzini wrote:
>>
>>>
>>>
>>> On 13/03/2015 15:48, Programmingkid wrote:
>&
On Mar 16, 2015, at 10:43 AM, Peter Maydell wrote:
> On 16 March 2015 at 14:38, Programmingkid wrote:
>>
>> On Mar 16, 2015, at 10:00 AM, Peter Maydell wrote:
>>
>>> On 16 March 2015 at 13:48, Daniel P. Berrange wrote:
>>>> The docs[1] still refer t
On Mar 16, 2015, at 10:47 AM, Paolo Bonzini wrote:
>
>
> On 16/03/2015 15:45, Programmingkid wrote:
>>>> Are you saying you are able to scroll up and down in QEMU's monitor
>>>> using your MacBook Air's keyboard?
>>>
>>> I haven&#
On Mar 16, 2015, at 10:52 AM, Paolo Bonzini wrote:
>
>
> On 16/03/2015 15:49, Programmingkid wrote:
>>
>> On Mar 16, 2015, at 10:47 AM, Paolo Bonzini wrote:
>>
>>>
>>>
>>> On 16/03/2015 15:45, Programmingkid wrote:
>>>>>
On Mar 16, 2015, at 10:59 AM, Peter Maydell wrote:
> On 16 March 2015 at 14:52, Paolo Bonzini wrote:
>>
>>
>> On 16/03/2015 15:49, Programmingkid wrote:
>>> Sorry but the GTK interface doesn't work on Mac OS X. We are all hoping
>>> this will cha
On Sep 25, 2015, at 12:09 PM, Peter Maydell wrote:
> On 23 September 2015 at 16:06, Programmingkid
> wrote:
>> Removes the open dialog code that runs when no arguments
>> are supplied with QEMU. Not everyone needs a hard drive
>> or cdrom to boot their target. A user m
On Sep 23, 2015, at 4:35 PM, Peter Maydell wrote:
> On 17 September 2015 at 21:17, Programmingkid
> wrote:
>> Add "Mount Image File..." and a "Eject Image File" menu items to
>> cocoa interface. This patch makes sharing files between the
>> host an
On Sep 25, 2015, at 11:42 AM, Markus Armbruster wrote:
> Programmingkid writes:
>
>> On Sep 24, 2015, at 2:57 AM, Markus Armbruster wrote:
>>
>>> Programmingkid writes:
>>>
>>>> On Sep 23, 2015, at 4:35 PM, Peter Maydell wrote:
>>&
Removes the open dialog code that runs when no arguments
are supplied with QEMU. Not everyone needs a hard drive
or cdrom to boot their target. A user might only need to
use their target's bios to do work. With that said,
this patch removes the unneeded open dialog code.
Signed-off-by: John Arbuck
On Sep 25, 2015, at 12:21 PM, Peter Maydell wrote:
> On 25 September 2015 at 09:12, Programmingkid
> wrote:
>>
>> On Sep 25, 2015, at 12:09 PM, Peter Maydell wrote:
>>> (Also, isn't a simple test on gArgc going to cause us to put up
>>> the dialog box
On Sep 25, 2015, at 2:53 PM, Peter Maydell wrote:
> On 25 September 2015 at 11:24, Programmingkid
> wrote:
>
>> I don't think Mac OS X adds the -psn argument anymore. It might have
>> in the past, but I don't see any sign of it on Mac OS 10.6. I made
>>
On Sep 25, 2015, at 4:14 PM, Peter Maydell wrote:
> On 25 September 2015 at 12:58, Programmingkid
> wrote:
>>
>> On Sep 25, 2015, at 2:53 PM, Peter Maydell wrote:
>>
>>> On 25 September 2015 at 11:24, Programmingkid
>>> wrote:
>>>
>>
Removes the open dialog code that runs when no arguments are supplied with QEMU.
Not everyone needs a hard drive or cdrom to boot their target. A user might only
need to use their target's bios to do work. With that said, this patch removes
the unneeded open dialog code.
Signed-off-by: John Arbuc
On Sep 25, 2015, at 6:00 PM, Peter Maydell wrote:
> On 25 September 2015 at 14:00, Programmingkid
> wrote:
>> Removes the open dialog code that runs when no arguments are supplied with
>> QEMU.
>> Not everyone needs a hard drive or cdrom to boot their target. A user m
Eliminate this warning associated with the setting of the normalWindow's title:
ui/cocoa.m: In function '-[QemuCocoaAppController init]':
ui/cocoa.m:888:9: warning: format not a string literal and no format arguments
[-Wformat-security]
[normalWindow setTitle:[NSString stringWithFormat:@
Eliminate this warning associated with the addRemovableDevicesMenuItems()
function:
ui/cocoa.m:1344:13: warning: function declaration isn't a prototype
[-Wstrict-prototypes]
static void addRemovableDevicesMenuItems()
^
ui/cocoa.m: In function 'addRemovableDevicesMenuItems':
ui/cocoa.
Add a menu item to the Machine menu called "Use Real CDROM". It gives the user
the ability to use a real CDROM disc with QEMU by simply selecting a menu item.
Signed-off-by: John Arbuckle
---
ui/cocoa.m | 87
1 files changed, 87 ins
On Sep 26, 2015, at 1:45 AM, Namsun Ch'o wrote:
>> Add a menu item to the Machine menu called "Use Real CDROM". It gives the
>> user the ability to use a real CDROM with QEMU by simply selecting a menu
>> item.
>
>> NSASCIIStringEncoding];
>> +qmp_change_blockdev(device, "/dev/cdrom", "raw",
On Sep 26, 2015, at 6:49 PM, Namsun Ch'o wrote:
>> Actually on Mac OS X, /dev/cdrom always points to the optical drive.
>> It is how QEMU is programmed.
>
> Is this only for Mac? I must have missed that.
Yes, it is for the Macintosh's cocoa interface.
The mouse cursor can become blinky when being moved a lot. This patch fixes that
problem by issuing the redraw sooner.
Signed-off-by: John Arbuckle
---
ui/cocoa.m |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/ui/cocoa.m b/ui/cocoa.m
index 334e6f6..cf372a4 100644
---
Would you be open to a feature that allows the user to select and run a custom
file that has commands in it that would run in the monitor?
Make the help menus actually work.
Signed-off-by: John Arbuckle
---
ui/cocoa.m | 20
1 files changed, 16 insertions(+), 4 deletions(-)
diff --git a/ui/cocoa.m b/ui/cocoa.m
index 334e6f6..2c81785 100644
--- a/ui/cocoa.m
+++ b/ui/cocoa.m
@@ -992,16 +992,28 @@ QemuCocoaVie
On Sep 27, 2015, at 2:53 PM, Peter Crosthwaite wrote:
> On Sun, Sep 27, 2015 at 3:13 AM, Peter Maydell
> wrote:
>> On 27 September 2015 at 04:39, Programmingkid
>> wrote:
>>> Would you be open to a feature that allows the user to select
>>> and run a cust
On Sep 27, 2015, at 10:30 PM, Michael Roth wrote:
> Quoting Programmingkid (2015-09-27 20:49:24)
>>
>> On Sep 27, 2015, at 2:53 PM, Peter Crosthwaite wrote:
>>
>>> On Sun, Sep 27, 2015 at 3:13 AM, Peter Maydell
>>> wrote:
>>>> On 27 S
Is there a reason why this patch hasn't been reviewed yet?
http://patchwork.ozlabs.org/patch/500498/
> Mac OS X can be picky when it comes to allowing the user to use physical
> devices
> in QEMU. Most mounted volumes appear to be off limits to QEMU. If an issue is
> detected, a message is displ
On Sep 28, 2015, at 3:29 AM, Markus Armbruster wrote:
> Programmingkid writes:
>
>> On Sep 27, 2015, at 10:30 PM, Michael Roth wrote:
>>
>>> Quoting Programmingkid (2015-09-27 20:49:24)
>>>>
>>>> On Sep 27, 2015, at 2:53 PM, Peter Crosthwa
On Sep 28, 2015, at 3:44 PM, Peter Maydell wrote:
> On 28 September 2015 at 20:43, Programmingkid
> wrote:
>>
>> On Sep 28, 2015, at 3:29 AM, Markus Armbruster wrote:
>>
>>> Programmingkid writes:
>>>>
On Sep 28, 2015, at 4:09 PM, Markus Armbruster wrote:
> Programmingkid writes:
>
>> On Sep 25, 2015, at 11:42 AM, Markus Armbruster wrote:
>>
>>> Programmingkid writes:
>>>
>>>> On Sep 24, 2015, at 2:57 AM, Markus Armbruster wrote:
>>>
On Sep 29, 2015, at 9:11 AM, Dr. David Alan Gilbert wrote:
> * Peter Maydell (peter.mayd...@linaro.org) wrote:
>> On 28 September 2015 at 20:43, Programmingkid
>> wrote:
>>>
>>> On Sep 28, 2015, at 3:29 AM, Markus Armbruster wrote:
On Sep 29, 2015, at 1:18 PM, Peter Maydell wrote:
> On 29 September 2015 at 18:03, Programmingkid
> wrote:
>> Allow the user the ability to run a custom script file.
>> This patch adds a menu item called "Run Custom Script".
>> When the user selects it,
Allow the user the ability to run a custom script file.
This patch adds a menu item called "Run Custom Script".
When the user selects it, a open-file dialog has the
user select a text file with the custom scripts to run.
This allows for virtually unlimited expandability. All
monitor commands should
On Sep 29, 2015, at 2:00 PM, Peter Maydell wrote:
> On 29 September 2015 at 18:53, Programmingkid
> wrote:
>>
>> On Sep 29, 2015, at 1:18 PM, Peter Maydell wrote:
>>
>>> On 29 September 2015 at 18:03, Programmingkid
>>> wrote:
>>>>
On Sep 30, 2015, at 6:53 AM, Peter Maydell wrote:
> On 30 September 2015 at 09:14, Dr. David Alan Gilbert
> wrote:
>> * Markus Armbruster (arm...@redhat.com) wrote:
>>> In my opinion, QEMU should leave them to separate GUI shells, because
>>> doing everything in QEMU distracts from our core miss
On Oct 1, 2015, at 9:23 AM, Stefan Hajnoczi wrote:
> On Sat, Sep 26, 2015 at 10:24:31AM -0400, Programmingkid wrote:
>> I was looking at the commit history for sd.c and noticed your patch. Would
>> you know how to make the SD card reader work for a guest like Windows,
>&g
On Oct 2, 2015, at 8:33 AM, Daniel P. Berrange wrote:
> On Wed, Sep 30, 2015 at 11:53:50AM +0100, Peter Maydell wrote:
>> On 30 September 2015 at 09:14, Dr. David Alan Gilbert
>> wrote:
>>> * Markus Armbruster (arm...@redhat.com) wrote:
In my opinion, QEMU should leave them to separate GUI
On Oct 2, 2015, at 10:28 AM, Daniel P. Berrange wrote:
> On Fri, Oct 02, 2015 at 02:33:22PM +0100, Dr. David Alan Gilbert wrote:
>> * Daniel P. Berrange (berra...@redhat.com) wrote:
>>> On Wed, Sep 30, 2015 at 09:48:25AM +0200, Markus Armbruster wrote:
"Dr. David Alan Gilbert" writes:
>>
>
On Oct 2, 2015, at 12:21 PM, Eric Blake wrote:
> On 10/02/2015 08:37 AM, Programmingkid wrote:
>>> Even if it were a fancier GUI, I don't think it would really go very far to
>>> providing users a solution which is on a par with VirtualBox or VMWare
>>> Deskt
On Oct 28, 2015, at 6:58 AM, Stefan Hajnoczi wrote:
> On Mon, Oct 26, 2015 at 01:24:00PM +0100, Gerd Hoffmann wrote:
>>> So this change would make real-time audio feel laggy.
>>
>> That is secondary if the sound quality is bad due to constant overruns
>> and underruns ...
>
> This is like sweep
On Oct 29, 2015, at 11:08 AM, Stefan Hajnoczi wrote:
> On Wed, Oct 28, 2015 at 09:59:32AM -0400, Programmingkid wrote:
>>
>> On Oct 28, 2015, at 6:58 AM, Stefan Hajnoczi wrote:
>>
>>> On Mon, Oct 26, 2015 at 01:24:00PM +0100, Gerd Hoffmann wrote:
>>>>&
Apple has custom PCI bridge registers that are not a part of any known
standard. This patch implements register 0x48. With this patch the
AppleMacRiscPCI kernel extension no longer prints these error messages for the
mac99 target:
AppleMacRiscPCI: bad range 2(8000:0100)
AppleMacRiscPCI:
On Jan 22, 2016, at 11:46 AM, Mark Cave-Ayland wrote:
> On 22/01/16 16:09, Programmingkid wrote:
>
>> Apple has custom PCI bridge registers that are not a part of any known
>> standard. This patch implements register 0x48. With this patch the
>> AppleMacRiscPCI ke
On Jan 23, 2016, at 3:41 PM, qemu-ppc-requ...@nongnu.org wrote:
> Message: 6
> Date: Sat, 23 Jan 2016 21:40:02 +0100
> From: Herv? Poussineau
> To: qemu-devel@nongnu.org
> Cc: Alyssa Milburn , Herv? Poussineau
> , qemu-...@nongnu.org, David Gibson
>
> Subject: [Qemu-ppc] [PATCH 05/1
https://patchwork.ozlabs.org/patch/570128/
Mac OS X can be picky when it comes to allowing the user
to use physical devices in QEMU. Most mounted volumes
appear to be off limits to QEMU. If an issue is detected,
a message is displayed showing the user how to unmount a
volume. Now QEMU uses both CD
On Feb 2, 2016, at 12:16 PM, Daniel P. Berrange wrote:
> On Tue, Feb 02, 2016 at 12:08:31PM -0500, Programmingkid wrote:
>> https://patchwork.ozlabs.org/patch/570128/
>>
>> Mac OS X can be picky when it comes to allowing the user
>> to use physical devices in
On Feb 2, 2016, at 12:31 PM, Daniel P. Berrange wrote:
> On Tue, Feb 02, 2016 at 12:28:24PM -0500, Programmingkid wrote:
>>
>> On Feb 2, 2016, at 12:16 PM, Daniel P. Berrange wrote:
>>
>>> On Tue, Feb 02, 2016 at 12:08:31PM -0500, Programmingkid wrote:
>>&
On Feb 2, 2016, at 2:24 PM, Eric Blake wrote:
> On 02/02/2016 12:10 PM, Programmingkid wrote:
>
>>> There was/is no leak because it qdict_get_str() returns 'const char *' and
>>> so nothing needs freeing. So your change is still a backwards steps IMH
On Feb 2, 2016, at 2:24 PM, Eric Blake wrote:
> On 02/02/2016 12:10 PM, Programmingkid wrote:
>
>>> There was/is no leak because it qdict_get_str() returns 'const char *' and
>>> so nothing needs freeing. So your change is still a backwards steps IMH
On Feb 2, 2016, at 5:04 PM, Eric Blake wrote:
> On 02/02/2016 02:23 PM, Programmingkid wrote:
>
>>> And why isn't bsd_path usable for that purpose?
>>
>> After trying it out, I found out why bsd_path isn't usable for that purpose.
>> It is because
On Feb 2, 2016, at 9:30 PM, Eric Blake wrote:
> On 02/02/2016 06:15 PM, Programmingkid wrote:
>
>>> No, keep filename as a const char * pointer. It's easy to avoid use of
>>> uninitialized memory. Try this:
>>>
>>> const char *filename;
>
On Feb 2, 2016, at 11:36 PM, Eric Blake wrote:
> On 02/02/2016 09:21 PM, Programmingkid wrote:
>
>>>> #if defined(__APPLE__) && defined(__MACH__)
>>>> /* if a physical device experienced an error while being opened */
>>>> if (str
I built Cormac O'Brien's QEMU repo for Mac OS 9 and tried to boot my Mac OS
10.4 boot cd. Mac OS 10.4's kernel panics because of a CUDA problem. I did use
the mac99 target. Here is the error message:
panic(cpu 0 caller 0x16E786CC): CUDA - TODO CHECK FOR TRANSACTION TYPE AND ERROR
This is the c
On Nov 11, 2015, at 12:54 PM, Mark Cave-Ayland wrote:
> On 11/11/15 15:15, Programmingkid wrote:
>
>> I built Cormac O'Brien's QEMU repo for Mac OS 9 and tried to boot my Mac OS
>> 10.4 boot cd. Mac OS 10.4's kernel panics because of a CUDA problem. I did
>
On Nov 11, 2015, at 4:32 PM, Andreas Tobler wrote:
> On 11.11.15 19:55, Programmingkid wrote:
>>
>> On Nov 11, 2015, at 12:54 PM, Mark Cave-Ayland wrote:
>>
>>> On 11/11/15 15:15, Programmingkid wrote:
>>>
>>>> I built Cormac O'Brien&#x
On Nov 11, 2015, at 6:05 PM, Mark Cave-Ayland wrote:
> On 11/11/15 21:32, Andreas Tobler wrote:
>
>> On 11.11.15 19:55, Programmingkid wrote:
>>>
>>> On Nov 11, 2015, at 12:54 PM, Mark Cave-Ayland wrote:
>>>
>>>> On 11/11/15 15:15, Program
On Nov 11, 2015, at 6:05 PM, Mark Cave-Ayland wrote:
> On 11/11/15 21:32, Andreas Tobler wrote:
>
>> On 11.11.15 19:55, Programmingkid wrote:
>>>
>>> On Nov 11, 2015, at 12:54 PM, Mark Cave-Ayland wrote:
>>>
>>>> On 11/11/15 15:15, Program
On Nov 11, 2015, at 6:14 PM, BALATON Zoltan wrote:
> On Wed, 11 Nov 2015, Programmingkid wrote:
>> On Nov 11, 2015, at 4:32 PM, Andreas Tobler wrote:
>>>> It looks like you are saying you wish to keep the CUDA device. Mac OS 9 is
>>>> most
>>>> likel
On Nov 12, 2015, at 11:04 PM, qemu-ppc-requ...@nongnu.org wrote:
> Message: 3
> Date: Thu, 12 Nov 2015 22:24:08 +0100
> From: Herv? Poussineau
> To: qemu-devel@nongnu.org
> Cc: "open list:Old World" , Herv? Poussineau
>
> Subject: [Qemu-ppc] [PATCH for-2.5] mac_dbdma: always initialize
>
On Nov 20, 2015, at 8:39 AM, BALATON Zoltan wrote:
> On Thu, 19 Nov 2015, Segher Boessenkool wrote:
>> Some mac99/pmu99 hardware has an ADB keyboard, fwiw (tibook, for example).
>> The do have built-in USB; that, and being newworld, are not directly
>> related things.
>
> Maybe, but the PowerMac
Add support for caching options that can be specified from
the command line.
Signed-off-by: John Arbuckle
---
Only location of code has been changed.
block/raw-posix.c | 15 +--
1 files changed, 9 insertions(+), 6 deletions(-)
diff --git a/block/raw-posix.c b/block/raw-posix.c
Mac OS X can be picky when it comes to allowing the user
to use physical devices in QEMU. Most mounted volumes
appear to be off limits to QEMU. If an issue is detected,
a message is displayed showing the user how to unmount a
volume.
Signed-off-by: John Arbuckle
---
This patch depends on the Get
On Nov 20, 2015, at 11:26 AM, Kevin Wolf wrote:
> Am 27.07.2015 um 19:05 hat Programmingkid geschrieben:
>> Mac OS X can be picky when it comes to allowing the user to use physical
>> devices
>> in QEMU. Most mounted volumes appear to be off limits to QEMU. If an issue is
&
On Nov 21, 2015, at 7:32 AM, Mark Cave-Ayland wrote:
> On 20/11/15 17:06, Alfonso Gamboa wrote:
>
>> booting into MacOS9 with qemu to the Desktop is now possible, see:
>>
>> http://www.emaculation.com/forum/viewtopic.php?f=34&t=7047&start=250
>>
>> Some issues, remain, certain extensions cra
On Nov 21, 2015, at 7:32 AM, Mark Cave-Ayland wrote:
> On 20/11/15 17:06, Alfonso Gamboa wrote:
>
>> booting into MacOS9 with qemu to the Desktop is now possible, see:
>>
>> http://www.emaculation.com/forum/viewtopic.php?f=34&t=7047&start=250
>>
>> Some issues, remain, certain extensions cra
When QEMU is brought to the foreground, the click event that activates QEMU
should not go to the guest. Accidents happen when they do go to the guest
without giving the user a change to handle them. Buttons are clicked accidently.
Windows are closed accidently. Volumes are unmounted accidently. Thi
On Nov 22, 2015, at 6:58 AM, Mark Cave-Ayland wrote:
> On 21/11/15 22:59, Programmingkid wrote:
>
>> On Nov 21, 2015, at 7:32 AM, Mark Cave-Ayland wrote:
>>
>>> On 20/11/15 17:06, Alfonso Gamboa wrote:
>>>
>>>> booting into MacOS9 with qemu to t
On Nov 23, 2015, at 11:06 AM, Peter Maydell wrote:
> On 22 November 2015 at 01:43, Programmingkid
> wrote:
>> When QEMU is brought to the foreground, the click event that activates QEMU
>> should not go to the guest. Accidents happen when they do go to the guest
>> w
On Nov 23, 2015, at 11:06 AM, Peter Maydell wrote:
> On 22 November 2015 at 01:43, Programmingkid
> wrote:
>> When QEMU is brought to the foreground, the click event that activates QEMU
>> should not go to the guest. Accidents happen when they do go to the guest
>> w
On Nov 23, 2015, at 4:00 PM, Mark Cave-Ayland wrote:
> On 22/11/15 17:39, Programmingkid wrote:
>
>>>>> Hi Alfonso,
>>>>>
>>>>> Has there been any progress at all as to which extensions may be causing
>>>>> the crashes?
>>
On Nov 23, 2015, at 4:00 PM, Mark Cave-Ayland wrote:
> On 22/11/15 17:39, Programmingkid wrote:
>
>>>>> Hi Alfonso,
>>>>>
>>>>> Has there been any progress at all as to which extensions may be causing
>>>>> the crashes?
>>
On Nov 24, 2015, at 3:56 AM, Peter Maydell wrote:
> On 24 November 2015 at 03:25, Programmingkid
> wrote:
>>
>> On Nov 23, 2015, at 11:06 AM, Peter Maydell wrote:
>>
>>> On 22 November 2015 at 01:43, Programmingkid
>>> wrote:
>>>> W
On Nov 24, 2015, at 9:38 AM, Kevin Wolf wrote:
>
>
>> +/* If using a physical device */
>> +if (strstart(filename, "/dev/", NULL)) {
>> +char bsdPath[MAXPATHLEN];
>> +
>> +/* If the physical device is a cdrom */
>> +if (strcmp(filename, "/dev/cdrom") == 0) {
>
>
Mac OS X can be picky when it comes to allowing the user
to use physical devices in QEMU. Most mounted volumes
appear to be off limits to QEMU. If an issue is detected,
a message is displayed showing the user how to unmount a
volume.
Signed-off-by: John Arbuckle
---
Changed cdromOK variable to c
Is there any platform where a guest in QEMU can play an audio cd? If not, is
this a feature that you would allow into QEMU?
Mac OS X can be picky when it comes to allowing the user
to use physical devices in QEMU. Most mounted volumes
appear to be off limits to QEMU. If an issue is detected,
a message is displayed showing the user how to unmount a
volume.
Signed-off-by: John Arbuckle
---
block/raw-posix.c | 98 +++
When QEMU is brought to the foreground, the click event that activates QEMU
should not go to the guest. Accidents happen when they do go to the guest
without giving the user a change to handle them. Buttons are clicked accidently.
Windows are closed accidently. Volumes are unmounted accidently. Thi
Mac OS X can be picky when it comes to allowing the user
to use physical devices in QEMU. Most mounted volumes
appear to be off limits to QEMU. If an issue is detected,
a message is displayed showing the user how to unmount a
volume.
Signed-off-by: John Arbuckle
---
Added DVD support - real DVD
Mac OS X can be picky when it comes to allowing the user
to use physical devices in QEMU. Most mounted volumes
appear to be off limits to QEMU. If an issue is detected,
a message is displayed showing the user how to unmount a
volume. Now QEMU uses both CD and DVD media.
Signed-off-by: John Arbuckl
https://patchwork.ozlabs.org/patch/579325/
Mac OS X can be picky when it comes to allowing the user
to use physical devices in QEMU. Most mounted volumes
appear to be off limits to QEMU. If an issue is detected,
a message is displayed showing the user how to unmount a
volume. Now QEMU uses both CD
On Nov 26, 2015, at 6:45 AM, Peter Maydell wrote:
> On 26 November 2015 at 01:14, Programmingkid
> wrote:
>> When QEMU is brought to the foreground, the click event that activates QEMU
>> should not go to the guest. Accidents happen when they do go to the guest
>> w
On Nov 25, 2015, at 11:23 PM, Eric Blake wrote:
> On 11/25/2015 09:10 PM, Programmingkid wrote:
>> Mac OS X can be picky when it comes to allowing the user
>> to use physical devices in QEMU. Most mounted volumes
>> appear to be off limits to QEMU. If an issue is dete
On Nov 25, 2015, at 11:29 PM, Eric Blake wrote:
> On 11/25/2015 09:23 PM, Eric Blake wrote:
>
>>> +static kern_return_t FindEjectableOpticalMedia(io_iterator_t
>>> *mediaIterator,
>>> +char
>>> *mediaType)
>>
>> Unusual indentati
Mac OS X can be picky when it comes to allowing the user
to use physical devices in QEMU. Most mounted volumes
appear to be off limits to QEMU. If an issue is detected,
a message is displayed showing the user how to unmount a
volume.
Signed-off-by: John Arbuckle
---
Fixed some spacing issues.
R
On Nov 30, 2015, at 11:26 AM, Kevin Wolf wrote:
> Am 30.11.2015 um 17:19 hat Eric Blake geschrieben:
>> On 11/27/2015 12:35 PM, Programmingkid wrote:
>>
>>>> Unusual indentation; more typical is:
>>>>
>>>> | static kern_return_t FindEjec
On Nov 30, 2015, at 11:26 AM, Eric Blake wrote:
> On 11/27/2015 02:49 PM, Programmingkid wrote:
>> Mac OS X can be picky when it comes to allowing the user
>> to use physical devices in QEMU. Most mounted volumes
>> appear to be off limits to QEMU. If an issue is dete
101 - 200 of 1022 matches
Mail list logo
