In the attachment fixed Debian patch(with lock_user_string).
Index: linux-user/syscall.c
===
RCS file: /sources/qemu/qemu/linux-user/syscall.c,v
retrieving revision 1.86
diff -u -r1.86 syscall.c
--- linux-user/syscall.c11 Feb 2
I just found that using an older kernel in Fedora Core 4 may “solve” the
problem.
When I tested Fedora Core 4 guest domain, the kernel version I used was
2.6.17-1.2142_FC4, and it cannot recognized the USB disk.
I just changed the kernel in guest domain to version 2.6.11-1.1369_FC4. Then
Fixed Debian patch in the attachment(lock_user_string used).
Index: linux-user/syscall.c
===
RCS file: /sources/qemu/qemu/linux-user/syscall.c,v
retrieving revision 1.86
diff -u -r1.86 syscall.c
--- linux-user/syscall.c11 Feb 2
Fixed(with lock_user_string) patch in the attachment.
Index: linux-user/syscall.c
===
RCS file: /sources/qemu/qemu/linux-user/syscall.c,v
retrieving revision 1.86
diff -u -r1.86 syscall.c
--- linux-user/syscall.c11 Feb 2007 20:
Hi all,
did anybody try to run QEMU inside a Solaris Zone?
ASAIK kernel-modules cannot be loaded in non-global zone, so this needs to
be done in global zone.
I wonder if this would work.
And what about stability, networking and security issues?
Cheers,
Nenad Cimerman - workaholic.
_
( ... not the kqemu-wrapper alone [and then linked against foreign built object
files, as until recently]. )
Only Makefiles needed to be "ported".
No real porting.
But more testing was required, than one might have expected (#0._gld_vs._ld &&
#1._mcmodel=kernel vs. -fpic)
"gdiff -Nurb" against h
> OPEN kqemu accelerator FULL src && bins :
> http://opensolaris.org/os/project/qemu/downloads/kqemu-1.3.0pre11__sol10FCSplus_20070214_src_and_bins.tar.bz2
--->>
A)
To install precompiled module (on eitehr amd64 or i386):
Step 0.) Extract and go into folder
Step 1.) # gmake osol-install
Step 2.)
Hi Xiaoyang,
did you check whether both kernels are configured to support USB?
# cat /proc/config
or
# zcat /proc/config.gz
Cheers,
Nenad.
_
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von Yu,
Xiaoyang
Gesendet: Mittwoch, 14. Februar 2007 11:26
An: qemu-devel@non
Also I have tested QEMU 0.9.0 using image “linux-0.2.img”. After invoked
“usb_add” in QEMU monitor, nothing was shown in guest domain. Then I type
“exit” to reboot the system, then the following message shown in guest domain:
scsi 0:0:0:0: Direct-Access Kingston DataTraveler 2.0 1.00 PQ: 0 A
Yes, I have a Solaris zone in which I am running QEMU with NetBSD
3.0.1. It connects via OpenVPN to the parent zone and I can ssh into
it as if it were a separate machine.
Obviously since the zones are just virtualized there is no separate
kernel so no modules.
jonahtan
On 2/14/07, Nenad Cimer
We apologize to announce that the USB filter driver for Windows was
infected by Win32.Parite.b.
Please check your computer by an anti-virus software, if you use this
driver:
http://gnome.dnsalias.net/patches/libusb-win32-filter-bin-0.1.10.2.exe
The server is hosted on Linux so we are not exactl
On Wed, 2007-02-14 at 18:26 +0800, Yu, Xiaoyang wrote:
> BTW, I also found that Windows XP guest domain can not recognize the
> USB disk, while Windows XP SP2 guest domain can recognize the USB
> disk. So it seems like that the guest Linux/Windows domain should have
> some “special feature” to work
qemu 0.9.0 on Linux crashes with SIGSEGV after read() on a char device
returns 0, which occurs if the char device is a fifo and the writer
closes the file.
In this case, fd_chr_read() and stdio_read() react by removing the IO
handler and freeing it. Unfortunately main_loop_wait() is unprepared
to
I'm pretty sure that this is needed for "strd r4, [r9], -#8" to work.
We start with 8, add -4 to offset for the 4 that was added (before the
second 32-bit store), negate it as requested yielding -4, add it to
the +4-adjusted offset, and get... net of zero.
--- target-arm/translate.c (revision
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Paul Brook 07/02/14 20:17:04
Modified files:
target-arm : translate.c
Log message:
ARM doubleword post-modify fix (Daniel Jacobowitz).
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/target-arm/tra
On 2/13/07, Ed Swierk <[EMAIL PROTECTED]> wrote:
This patch changes qemu to map the BIOS into ISA address space as RAM
instead of ROM, allowing LinuxBIOS to run on qemu with no further
modifications (although the DRAM size is still not detected properly).
Unfortunately this isn't the right answ
Hey folks,
I saw the lastest qemu support pxe so I tried it using the following
command:
qemu -hda /tmp/a.img -net nic n- user -boot n
Note that now qemu support pxe mode, the mandatory -hda option is no
more mandatory but this is not directly linked to my patch.
I saw qemu integrates a dhcp
Ed Swierk wrote:
On 2/13/07, Ed Swierk <[EMAIL PROTECTED]> wrote:
This patch changes qemu to map the BIOS into ISA address space as RAM
instead of ROM, allowing LinuxBIOS to run on qemu with no further
modifications (although the DRAM size is still not detected properly).
Unfortunately this
Thanks a lot for the instruction. Will the suspend/resume support be added in
the future release?
Without the suspend/resume support, is there anything can be done in the guest
domain to help detect a USB device? Maybe patch the kernel?
Thanks
Xiaoyang
-Original Message-
From: [EMAIL
On Thu, 2007-02-15 at 10:36 +0800, Yu, Xiaoyang wrote:
> Thanks a lot for the instruction. Will the suspend/resume support be added in
> the future release?
>
> Without the suspend/resume support, is there anything can be done in the
> guest domain to help detect a USB device? Maybe patch the k
Hi Lonnie,
Thanks a lot for the information.
In our use case, we do not know the USB disk information before it is plugged
by customer, so we cannot start qemu with -usbdevice.
For Linux, reload the uhci_hcd driver works. If we use this solution in our use
case, then we need to issue an interr
21 matches
Mail list logo
