I used QEMU 0.9.0 to do the testing. All the seven USB disks can work properly
in host OS (Linux 2.6), so the USB devices and its interaction with the kernel
drivers should be okay. So the problem must be in QEMU USB code.
Thanks
Xiaoyang
-Original Message-
From: [EMAIL PROTECTED] [ma
Hi Anthony,
On Thursday 29 March 2007 04:07, you wrote:
> Axel Zeuner wrote:
> > Hi Anthony,
> >
> > On Monday 26 March 2007 01:44, you wrote:
> >> Axel Zeuner wrote:
> >>> On Saturday 24 March 2007 21:15, Anthony Liguori wrote:
> The tricky thing I still can't figure out is how to get ASM_SO
Hi,
On 3/29/2007 11:49 AM, Yu, Xiaoyang wrote:
I found that some USB disks do not work in QEMU.
I don't quite understand. In which way? As I understand it, QEMU just
uses the I/O layer provided by the host operating system. In my
experience, if there has been any USB problem, it is either wi
Hi guys,
I found that some USB disks do not work in QEMU.
I collected seven types of USB disks, and tested them in QEMU. Four of
them can work properly, but other three do not work. I compared their
information in /proc/bus/usb/devices, and found that the four "good"
disks all use endpoint
Hi guys,
I found that some USB disks do not work in QEMU.
I collected seven types of USB disks, and tested them in QEMU. Four of
them can work properly, but other three do not work. I compared their
information in /proc/bus/usb/devices, and found that the four "good"
disks all use endpoint
Axel Zeuner wrote:
Hi Anthony,
On Monday 26 March 2007 01:44, you wrote:
Axel Zeuner wrote:
On Saturday 24 March 2007 21:15, Anthony Liguori wrote:
The tricky thing I still can't figure out is how to get ASM_SOFTMMU
working. The problem is GLUE(st, SUFFIX) function. First GCC
Good question. I stumbled about this, too, when I looked
at the code how I could apply your patch. Some months
had past since I wrote it :-)
The code writes to a serial EEPROM, so the 16 bits are
sent using only a clock and a single data bit. The
EEPROM emulation then takes the single bits and put
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Jocelyn Mayer 07/03/28 20:43:46
Modified files:
target-ppc : cpu.h
Log message:
Solaris host compilation fix by Shaddy Baddah.
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/target-ppc/cpu.h?cvsroot=q
On Saturday 24 March 2007 8:32 am, Sunil Amitkumar Janki wrote:
> Anyhow, I expect 32-bit hardware to gradually die because of wear and
> tear in the next few years and the replacement will be 64-bit hardware so
> the problem will solve itself that way.
Specifically, in 2008 32-bit x86 hardware b
On 3/28/07, Rick Vernam <[EMAIL PROTECTED]> wrote:
On Tuesday 27 March 2007 08:53:42 pm Rick Vernam wrote:
> On Tuesday 27 March 2007 06:34:04 pm Kyle Hubert wrote:
> > I've been looking online, but I can't say that I have found the answer
> > to this yet.
> >
> > When using QEMU, I've noticed th
On Tuesday 27 March 2007 08:53:42 pm Rick Vernam wrote:
> On Tuesday 27 March 2007 06:34:04 pm Kyle Hubert wrote:
> > I've been looking online, but I can't say that I have found the answer
> > to this yet.
> >
> > When using QEMU, I've noticed that if I switch away to a different
> > virtual deskto
On 3/27/07, andrzej zaborowski <[EMAIL PROTECTED]> wrote:
On 28/03/07, Kyle Hubert <[EMAIL PROTECTED]> wrote:
> I've been looking online, but I can't say that I have found the answer
> to this yet.
>
> When using QEMU, I've noticed that if I switch away to a different
> virtual desktop on the hos
On 3/28/07, WaxDragon <[EMAIL PROTECTED]> wrote:
On 3/27/07, Kyle Hubert <[EMAIL PROTECTED]> wrote:
> Also, I have noticed that when using the ondemand governor for the
> host OS (AMD PowerNow) that QEMU doesn't register for some reason. My
> host CPU stays running at 1GHz, when it is capable of
Hi,
This is a cross-post from
http://qemu-forum.ipi.fi/viewtopic.php?p=10639#10639.
Continuing on from http://qemu-forum.ipi.fi/viewtopic.php?p=10487#10487,
I am being continually frustrated in bringing up my Debian i386
installation on my external USB drive.
I have tried both the 0.8.2 ve
Hi,
Recent changes to qemu/target-ppc/cpu.h have broken Solaris 8 builds.
Specifically, the insertion of a insertion, which is not part
of the Solaris C development library.
[SNIP]
make[1]: Entering directory `/var/home/shaddy/src/qemu/qemu/ppc-softmmu'
gcc -Wall -O2 -g -fno-strict-aliasing -I.
On 3/27/07, Kyle Hubert <[EMAIL PROTECTED]> wrote:
Also, I have noticed that when using the ondemand governor for the
host OS (AMD PowerNow) that QEMU doesn't register for some reason. My
host CPU stays running at 1GHz, when it is capable of 2.6GHz. I can
run anything on the host OS, and I see t
On Wednesday 28 March 2007 03:21, Daniel Jacobowitz wrote:
> On Wed, Mar 28, 2007 at 12:35:18AM +0100, Thiemo Seufer wrote:
> > Right, a piggyback-style loader would likely fail in that case.
>
> Which is exactly the interesting case for x86_64. So, since Paul's
> verified that grub and lilo just
On Wed, Mar 28, 2007 at 10:13:49AM +0200, Sebastian Kaliszewski wrote:
> Bernhard Kauer wrote:
> >Qemu does not generate a double fault (DBF) on x86, if a general protection
> >fault could not be delivered. Instead it hangs in a loop.
> >
> >The patch fix this bug by checking whether we are already
Bernhard Kauer wrote:
Qemu does not generate a double fault (DBF) on x86, if a general protection
fault could not be delivered. Instead it hangs in a loop.
The patch fix this bug by checking whether we are already in a GPF exception.
If you're at it, maybe add triple fault handling (ie excepti
19 matches
Mail list logo
