On 25/1/20 16:52, Laurent Vivier wrote:
Le 25/01/2020 à 12:55, no-re...@patchew.org a écrit :
Patchew URL:
https://patchew.org/QEMU/20200125114753.61820-1-salva...@qindel.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Salvador,
you
From: Salvador Fandino
Under sparc and sparc64, both NetBSD and OpenSSH use two bits of the
syscall number as flags. Until now, those bits where only supported
for sparc64 when emulating OpenBSD.
This patch extends support for syscall flags to the sparc architecture
and NetBSD emulation. It had
From: Salvador Fandino
Under sparc and sparc64, both NetBSD and OpenSSH use two bits of the
syscall number as flags. Until now, those bits where only supported
for sparc64 when emulating OpenBSD.
This patch extends support for syscall flags to the sparc architecture
and NetBSD emulation. It had
On 24/1/20 20:44, no-re...@patchew.org wrote:
Patchew URL:
https://patchew.org/QEMU/20200124183113.58039-1-salva...@qindel.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
A new patch is coming fixing the errors found by patchew in bsd
From: Salvador Fandino
Under sparc and sparc64, both NetBSD and OpenSSH use two bits of the
syscall number as flags. Until now, those bits where only supported
for sparc64 when emulating OpenBSD.
This patch extends support for syscall flags to the sparc architecture
and NetBSD emulation. It had
From: Salvador Fandino
NULL is a valid log filename used to indicate we want to use stderr
but qemu_set_log_filename (which is called by bsd-user/main.c) was not
handling it correctly.
That also made redundant a couple of NULL checks in calling code which
have been removed.
Signed-off-by
From: Salvador Fandino
NULL is a valid log filename used to indicate we want to use stderr
but qemu_set_log_filename (which is called by bsd-user/main.c) was not
handling it correctly.
Signed-off-by: Salvador Fandino
---
util/log.c | 27 +++
1 file changed, 15
From: Salvador Fandino
NULL is a valid log filename used to indicate we want to use stderr
but qemu_set_log_filename (which is called by bsd-user/main.c) was not
handling it correctly.
Signed-off-by: Salvador Fandino
---
util/log.c | 27 +++
1 file changed, 15
I didnt understand properly the output, it only can use opengl es 3.0.
you should put that info because when i compile qemu it pass and it
should if doesnt support my opengl setup.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https
it shouldn't+
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1821839
Title:
qemu 4.0 doesnt support glsl 3.0 but yes older versions, that have no
sense IMO
Status in QEMU:
New
Bug description:
Public bug reported:
tested on qemu 4.0.rc1 on rpi3, mesa 19.x
maybe I am a bit confused, but why it can use and older version from my mesa
driver, it should pickup the right version instead of going to the latest.
pi@pi:~/Desktop/armbian/windows_95_vdi $ qemu-system-i386 -cpu qemu32 -m 32
-di
Hi,
The attached patch to qemu-img, adds support for multipart images (as
those used by VMWare) on the convert operation.
Now, the program accepts more than one input image arguments. For instance:
$ qemu-img convert -c -f vmdk \
foo-s001.vmdk foo-s002.vmdk foo-s00
Hi,
The -smb option doesn't work on Debian because of Samba bug #4105:
https://bugzilla.samba.org/show_bug.cgi?id=4105
Briefly, in Debian samba is configured with option --with-fhs that
causes smbd to ignore "private dir" directive on the config file.
Cheers,
- Salva
Jim C. Brown wrote:
>> yes, that's right, but it's not what lomount does. It parses the data on
>> the EBR in the same way as the MBR, reading 4 partition registers from them.
>>
>
> It only uses the first two. It reads in the rest but ignores them.
Could I be looking at an old version of lomoun
Jim C. Brown wrote:
> On Wed, Dec 13, 2006 at 08:03:13PM +0100, Salvador Fandino wrote:
>>> The code of lomount might be what you're looking for. Lomount allows one
>>> to mount partions (via loop) from a raw diskimage.
>> That was my intention, but I have found
Avi Kivity wrote:
> Martin Guy wrote:
>>> - write tons of data to nbd device, data ends up in pagecache
>>> - memory gets low, kswapd wakes up, calls nbd device to actually write
>>> the data
>>> - nbd issues a request, which ends up on the nbd server on the same
>>> machine
>>> - the nbd server al
Jan Marten Simons wrote:
> Salvador Fandino schrieb:
>> right now, you can use "-o offset" and "-s size" to serve a partition
>> inside a partitioned disk image. And you can use fdisk or a similar tool
>> to examine the partition table (they work on /de
Sylvain Petreolle wrote:
It's mostly intended to be used for accessing the files inside QEMU disk
images locally, without having to launch a virtual machine and accessing
then from there.
>>> mount -o loop does this.
>> How is everybody missing the point? :-) mount -o loop doesn't m
Daniel Jacobowitz wrote:
> On Tue, Dec 12, 2006 at 06:33:22PM +0100, Sylvain Petreolle wrote:
> It's mostly intended to be used for accessing the files inside QEMU disk
> images locally, without having to launch a virtual machine and accessing
> then from there.
mount -o loop does
Anthony Liguori wrote:
> Salvador Fandiño wrote:
>> Hi,
>>
>> The patch available from http://qemu-forum.ipi.fi/viewtopic.php?t=2718
>> adds a new utility, qemu-nbds, that implements a NBD server (see
>> http://nbd.sf.net) for QEMU images.
>>
>> Using
mu-nbds windows.qcow -p 8001 -o 32256 &
# modprobe nbd
# nbd-client localhost 8001 /dev/nbd0
# mount -o ro /dev/nbd0 /mnt/windows
$ cp /mnt/windows/FOO.txt ~/
Cheers,
- Salva
Cheers,
- Salvador.
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
works (locally) due to a limitation on the
Linux Kernel :-(
BTW, only tested on Linux!
Regards,
- Salvador
Cheap talk?
Check out Yahoo! Messenger's low PC-to-Phone call rates.
http://voice.yaho
22 matches
Mail list logo
