tag found)
How to reproduce:
1) create a origin vm like:
/usr/local/autotest/tests/kvm/qemu -name 'vm1' -nodefaults -vga std
-monitor
unix:'/tmp/monitor-humanmonitor1-2004-200902-95j0',server,nowait
-qmp unix:'/tmp/monitor-qmpmonitor1-2004-200902-95j0',ser
Public bug reported:
Windows DVD starts loading and then stops with error 0x5d
MSDN tells us that 0x5d means unsupported_processor
The guest CPU is 64 bits though, the DVD fails early if booted on a
32bits CPU
Tested versions: 0.14.1, git (932eacc158)
qemu-system-x86_64 -m 1024 -boot d -cdrom w
I was using Windows 7 x86_64 DVD image: Ultimate N edition (french)
b89f76c3a1f9a15f2f583ce38d9740ea
fr_windows_7_ultimate_n_with_sp1_x64_dvd_u_677548.iso
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bug
On 4 November 2011 23:22, Jean-Christophe DUBOIS wrote:
> According to realview documentation [1], the bit used to reset the board
> is bit 2 and not bit 8.
True for PBA8 and PBXA9, but not true for PB1176, PB926 (where it
is bit 8) or Emulation Baseboard (which doesn't implement this
register at
According to realview documentation [1], the bit used to reset the board
is bit 2 and not bit 8.
This is also in sync with Linux source code [2].
[1]
http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0417d/BBACIGAD.html
[2]
http://lxr.free-electrons.com/source/arch/arm/mach-realvie
On Friday, November 4, 2011, 20:56:05, Gus Zernial wrote:
> Is this driver supported in QEMU 0.15.1, and if so how do I get it to work?
> If not,
> is there some alternative with the capability I mention?
The VMWare SVGA driver is reverse-engineered from the Linux/X VMWare
driver, and as such on
On 4 November 2011 20:50, Jean-Christophe DUBOIS wrote:
> During Xvisor development, it was noted that qemu did not return
> the correct domain value in the Cp15 [Data] FSR register (C5).
>
> This patch is a proposal to fix it.
> --- qemu-0.15.1.org/target-arm/helper.c 2011-10-12 18:41:43.
During Xvisor development, it was noted that qemu did not return
the correct domain value in the Cp15 [Data] FSR register (C5).
This patch is a proposal to fix it.
Signed-off-by: Jean-Christophe DUBOIS
---
--- qemu-0.15.1.org/target-arm/helper.c2011-10-12 18:41:43.0
+0200
+++ qem
Hi,
another showstopper appeared for DVD+RW.
After i disabled SET STREAMING, i was able to write a thoroughly formatted
DVD+RW. But when i inserted one that was never written up to its end, the
attempt failed to (re-)start background formatting (Format Type = 26h):
FORMAT UNIT
04 11 00 00 00
ode = tap
11/04 00:44:55 DEBUG| virt_test:0041| nic_model = virtio
Commented excerpt of the test log:
11/04 00:44:57 INFO |kvm_vm:0790| Running qemu command:
/usr/local/autotest/tests/kvm/qemu -name 'vm1' -nodefaults -vga std -monitor
unix:'/tmp/monitor-humanmon
First of all, thanks to Jernej Simon for the response which pointed out my
mistake
regards qemu vs qemu-kvm, and the pointer to the correct version. This solved
my
problem.
I have another question regards graphics driver for the Win7 client. I would
like to
use the VMware SVGA 3D (WDDM) drive
Am 04.11.2011 18:59, schrieb Peter Maydell:
> On 4 November 2011 17:56, Andreas Färber wrote:
>> --- a/vl.c
>> +++ b/vl.c
>> @@ -1484,7 +1484,7 @@ static void main_loop(void)
>>
>> static void version(void)
>> {
>> -printf("QEMU emulator version " QEMU_VERSION QEMU_PKGVERSION ",
>> Copyrigh
Stefan Hajnoczi writes:
> On Thu, Nov 03, 2011 at 10:35:28AM +0100, Fabien Chouteau wrote:
>> On 03/11/2011 08:44, Stefan Hajnoczi wrote:
>> > On Wed, Nov 2, 2011 at 5:39 PM, Fabien Chouteau
>> > wrote:
>> >> On 29/10/2011 15:52, Alexander Graf wrote:
>> > I took a quick peak at the qemu-trace.[
the test log:
11/04 00:44:57 INFO |kvm_vm:0790| Running qemu command:
/usr/local/autotest/tests/kvm/qemu -name 'vm1' -nodefaults -vga std -monitor
unix:'/tmp/monitor-humanmonitor1-2004-003602-LPJY',server,nowait -qmp
unix:'/tmp/monitor-qmpmonitor1-2004-003
u command:
/usr/local/autotest/tests/kvm/qemu -name 'vm1' -nodefaults -vga std -monitor
unix:'/tmp/monitor-humanmonitor1-2004-003602-LPJY',server,nowait -qmp
unix:'/tmp/monitor-qmpmonitor1-2004-003602-LPJY',server,nowait -serial
unix:'/tmp/serial-2004-0
On 4 November 2011 17:56, Andreas Färber wrote:
> --- a/vl.c
> +++ b/vl.c
> @@ -1484,7 +1484,7 @@ static void main_loop(void)
>
> static void version(void)
> {
> - printf("QEMU emulator version " QEMU_VERSION QEMU_PKGVERSION ",
> Copyright (c) 2003-2008 Fabrice Bellard\n");
> + printf("QE
Judging by -version output, one could get the impression that QEMU was
last modified in 2008. Therefore extend the copyright statement to
cover other contributors so that it can be updated to the current year.
Signed-off-by: Andreas Färber
---
vl.c |2 +-
1 files changed, 1 insertions(+), 1
me 'vm1' -nodefaults -vga std -monitor
unix:'/tmp/monitor-humanmonitor1-2004-003602-LPJY',server,nowait -qmp
unix:'/tmp/monitor-qmpmonitor1-2004-003602-LPJY',server,nowait -serial
unix:'/tmp/serial-2004-003602-LPJY',server,nowait -drive
file
nic_model = virtio
Commented excerpt of the test log:
11/04 00:44:57 INFO |kvm_vm:0790| Running qemu command:
/usr/local/autotest/tests/kvm/qemu -name 'vm1' -nodefaults -vga std -monitor
unix:'/tmp/monitor-humanmonitor1-2004-003602-LPJY',server,nowait -qmp
unix:
On 11/04/2011 02:56 PM, Anthony Liguori wrote:
On 11/04/2011 11:40 AM, Lucas Meneghel Rodrigues wrote:
Hi guys,
As we understand that qemu is approaching 1.0, we think it's a good
idea to
share the issues we have been seeing on recent qemu.git sanity jobs:
1) Some condition is consistently mak
> +static unsigned long get_value(HostPCIDevice *d, const char *name)
> +{
> +char path[PATH_MAX];
> +FILE *f;
> +unsigned long value;
> +
> +path_to(d, name, path, sizeof (path));
> +f = fopen(path, "r");
> +if (!f) {
> +fprintf(stderr, "Error: Can't open %s: %s\n",
** Changed in: qemu
Assignee: (unassigned) => Stefan Weil (ubuntu-weilnetz)
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/760060
Did you try compilation in a tree with old generated files from previous
compilations? If there are several qmp-commands.h in subdirectories,
you have such old files. There must be only one qmp-commands.h
in the build root.
The old files start with "{", the new files start with comment lines.
The
On Fri, 04 Nov 2011 11:53:53 +0100
Paolo Bonzini wrote:
> On 11/01/2011 06:03 AM, ShaoHe Feng wrote:
> > after the guest startups, then I right click mouse in the UI of the
> > guest, and select the Eject from the menu.
> > there comes an event in the qmp-monitor.
> > {"timestamp": {"seconds": 1
On Fri, 4 Nov 2011 14:03:47 +
Stefan Hajnoczi wrote:
> On Thu, Nov 3, 2011 at 6:36 PM, Luiz Capitulino
> wrote:
> > +Here's the implementation of the 'hello-world' HMP command:
> > +
> > +void hmp_hello_world(Monitor *mon, const QDict *qdict)
> > +{
> > + Error *errp = NULL;
> > + con
On Thu, 03 Nov 2011 16:25:58 -0500
Michael Roth wrote:
> On 11/03/2011 01:36 PM, Luiz Capitulino wrote:
> > Explains how to write QMP commands using the QAPI.
> >
> > TODO:
> > - write "returning lists" chapter
> > - review it
> >
> > Signed-off-by: Luiz Capitulino
> > ---
> >
> > This
On Fri 04 Nov 2011 02:56:30 PM BRST, Anthony Liguori wrote:
On 11/04/2011 11:40 AM, Lucas Meneghel Rodrigues wrote:
Hi guys,
As we understand that qemu is approaching 1.0, we think it's a good
idea to
share the issues we have been seeing on recent qemu.git sanity jobs:
1) Some condition is c
On 11/04/2011 11:40 AM, Lucas Meneghel Rodrigues wrote:
Hi guys,
As we understand that qemu is approaching 1.0, we think it's a good idea to
share the issues we have been seeing on recent qemu.git sanity jobs:
1) Some condition is consistently making a RHEL 6.1 linux guest not able to
bring up
On Fri 04 Nov 2011 02:50:53 PM BRST, Kevin Wolf wrote:
Am 04.11.2011 17:40, schrieb Lucas Meneghel Rodrigues:
2) The floppy regression problem which was reported some days ago on
this mailing list still happens, Kevin did post a patch that resolves it
[...]
But still wasn't integrated upstream
Am 04.11.2011 17:40, schrieb Lucas Meneghel Rodrigues:
> 2) The floppy regression problem which was reported some days ago on
> this mailing list still happens, Kevin did post a patch that resolves it
>
> [...]
>
> But still wasn't integrated upstream. As I understand, there are doubts
> whethe
On Thu, 3 Nov 2011 22:50:29 +0200
Alon Levy wrote:
> On Thu, Nov 03, 2011 at 04:36:03PM -0200, Luiz Capitulino wrote:
> > Explains how to write QMP commands using the QAPI.
> >
> > TODO:
> > - write "returning lists" chapter
> > - review it
> >
> > Signed-off-by: Luiz Capitulino
> > --
Hi guys,
As we understand that qemu is approaching 1.0, we think it's a good idea
to share the issues we have been seeing on recent qemu.git sanity jobs:
1) Some condition is consistently making a RHEL 6.1 linux guest not able
to bring up the network interface, causing login failures for all
Am 04.11.2011 17:21, schrieb Paolo Bonzini:
> First determine FAT12/16/32, then compute geometry from that for both
> FDD and HDD. For 1.44MB floppies, and 2.88MB floppies using FAT16,
> change to 1 sector/cluster. The default remains 2.88MB with FAT12
> and 2 sectors/cluster. Both DOS and mkdos
On Tue, 1 Nov 2011 17:20:19 -0200, Eduardo Habkost wrote:
> Summary of the problem:
>
> - qemu_fclose() calls qemu_fflush()
> - Writes done by qemu_fflush() can fail
> - Those errors are lost after qemu_fclose() returns
>
> So, this series change qemu_fclose() to return last_error. But to do th
First determine FAT12/16/32, then compute geometry from that for both
FDD and HDD. For 1.44MB floppies, and 2.88MB floppies using FAT16,
change to 1 sector/cluster. The default remains 2.88MB with FAT12
and 2 sectors/cluster. Both DOS and mkdosfs by default format a 2.88MB
floppy as FAT12.
Sign
I forgot to add that my configure flags are
./configure --enable-linux-aio --enable-kvm
and that my CFLAGS are
-O2 -W -Wformat=2 -Wswitch -Wshadow -Wwrite-strings -Wuninitialized
-Wall -pipe -mtune=native -march=native -fomit-frame-pointer -msse2
-msse -mmmx -mfpmath=sse -pedantic -D_FORTIFY_SOU
On Thu, Nov 3, 2011 at 2:14 PM, Jan Kiszka wrote:
> On 2011-11-03 19:59, Stuart Yoder wrote:
>> On Tue, Nov 1, 2011 at 9:22 AM, Jan Kiszka wrote:
>>> Hi there,
>>>
>>> I'm generating some slides on guest debugging via kvm. What's the
>>> current state for Book-E and Book-S? Works out of box, most
On 03.11.2011, at 01:36, Andreas Färber wrote:
> Am 03.11.2011 08:46, schrieb Markus Armbruster:
>> Anthony Liguori writes:
>>
>>> For the record, I'm opposed to ever having a stable plugin API.
>>>
>>> We aren't a closed source product. If people [don't] want to have to keep
>>> up
>>> with
In order to get nice error messages, keep the qemu-nbd process running
until before issuing NBD_DO_IT and connected to the daemon with a pipe.
This lets the qemu-nbd process relay error messages from the daemon and
exit with a nonzero status if appropriate.
Suggested-by: Kevin Wolf
Signed-off-by:
This is another approach to fixing the breakage of "qemu-nbd -c" due
to mixing fork with threads. It switches operation of qemu-nbd to
threads completely, with the exception of daemonization which is moved
as early as possible to avoid conflicts with threads.
Patches 1 and 2 are bugfixes to qemu-
Now that the client and server are in the same process, there is
no need to race on the creation of the socket. We can open the
listening socket before starting the client thread.
This avoids that "qemu-nbd -v -c" prints this once before connecting
successfully to the socket:
connect(unix:/v
Somehow, the read/write functions handle an offset that does not exist anymore.
Signed-off-by: Anthony PERARD
---
hw/xen_platform.c | 18 +-
1 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/hw/xen_platform.c b/hw/xen_platform.c
index 6e3ba8b..5e792f5 100644
--- a
It will be moved to a global variable by the next patch, and it
would conflict with the socket function.
Signed-off-by: Paolo Bonzini
---
qemu-nbd.c | 24 +++-
1 files changed, 11 insertions(+), 13 deletions(-)
diff --git a/qemu-nbd.c b/qemu-nbd.c
index d997bb0..ae504ec 10
This is cleaner, because we do not need to close the block device when
there is an error opening /dev/nbdX. It was done this way only to
print errors before daemonizing.
At the same time, use atexit to ensure that the block device is closed
whenever we exit.
Signed-off-by: Paolo Bonzini
---
qe
This avoids that qemu-nbd uses both forking and threads, which do
not behave well together.
qemu-nbd is already Unix only, and there is no qemu_thread_join,
so for now use pthreads.
Since the parent and child no longer have separate file descriptors,
we can open the NBD device before daemonizing,
The client process right now uses SIGTERM to interrupt the server side.
This does not affect the exit status of "qemu-nbd -v -c" because the
server is a child process. This will change when both sides will be
in the same process, and anyway cleaning up things nicely upon SIGTERM
is good practice.
This can be seen with "qemu-nbd -v -c", which returns 1 instead of 0
when you disconnect with "qemu-nbd -d".
Signed-off-by: Paolo Bonzini
---
I think this is a bug (because there would be no way to exit
qemu-nbd with zero status!), but the patch can be left out safely.
nbd.c |
Hi, all
While studying how QEMU handle self-modifying code I took [1] as an example.
Running QEMU under GDB I found tb_invalidate_phys_page is called in two
different call sequences:
1. do_syscall (linux-user/syscall.c) -> target_mprotect (linux-user/mmap.c)
-> page_set_flags (exec.c) -> tb
Anthony PERARD writes ("[Xen-devel] [PATCH V3 11/13] libxl: Use QMP to insert a
passthrough device when using upstream QEMU"):
> Also move the xenstore specific code to a new function and add a
> message if sscanf fails.
Thanks, following discussion I've applied 10,11 and will wait with 12
for th
Hi,
> We're about to release QEMU 1.0(-rc1) and you've just spotted a
> compilation issue...
Maybe one should consider to obtain the missing information
rather than crippling the debug message, like i did.
> You've solved this issue 50%! What's missing now is for you to put this
> fix into a se
Public bug reported:
Howdy Xubuntu users
How can I make a "starter program Icon on my desktop" with the mouse
command right key.
I do not seen the commands when I hit the right key of my mouse.
Hope to see some info in my pigeon-hole.
Spidey-Westland
** Affects: qemu
Importance: Undecide
On 04/11/2011 13:04, Stefan Hajnoczi wrote:
> On Fri, Nov 4, 2011 at 9:53 AM, Fabien Chouteau wrote:
>> On 04/11/2011 09:36, Stefan Hajnoczi wrote:
>>> On Thu, Nov 03, 2011 at 10:35:28AM +0100, Fabien Chouteau wrote:
On 03/11/2011 08:44, Stefan Hajnoczi wrote:
> On Wed, Nov 2, 2011 at 5:3
On Thu, Nov 3, 2011 at 6:36 PM, Luiz Capitulino wrote:
> +Here's the implementation of the 'hello-world' HMP command:
> +
> +void hmp_hello_world(Monitor *mon, const QDict *qdict)
> +{
> + Error *errp = NULL;
> + const char *message = qdict_get_str(qdict, "message");
Since message is option
Hi Thomas,
Am 03.11.2011 23:30, schrieb Thomas Schmitt:
> I tried to activate DPRINTF in hw/scsi-generic.c by removing the "//"
> before
> #define DEBUG_SCSI
>
> make yields:
> .../hw/scsi-generic.c: In function 'scsi_send_command':
> .../hw/scsi-generic.c:286: error: 'lun' undeclared (firs
Am 28.10.2011 18:03, schrieb Paolo Bonzini:
> Xen_disk.c has support for using synchronous I/O instead of asynchronous,
> but it is compiled out by default. Remove it.
>
> Signed-off-by: Paolo Bonzini
Thanks, applied for the block branch (for 1.1)
Kevin
On 4 November 2011 07:53, Paolo Bonzini wrote:
> On 11/04/2011 02:52 AM, Peter Maydell wrote:
>>
>> * the fixed address we mmap the code gen buffer to in system
>> mode tends to overlap the libc heap (at least on Ubuntu oneiric);
>> when this happens you typically get a sysmalloc abort
>
> Let's
Hi,
i wrote:
> > CD SAO gets stuck at SEND CUE SHEET.
Paolo Bonzini wrote:
> I wouldn't be surprised if they are bugs in either scsi-generic or the LSI
> emulation code. They seem to occur when commands return less data than the
> guest driver has asked; with master I get a guest oops in the LSI
After updating from the QEMU that came with Ubuntu 11.04 to
070411-1ubuntu2 version, I am seeing the bad ram offset error, also. If
I drop the memory for the guest (which is Windows 7 Pro 64-bit) from 4
GB to 3300MB, the error goes away.
Host machine has an AMD Opteron 6128 with 32GB RAM and is r
Anthony PERARD writes ("[Xen-devel] [PATCH V3 10/13] libxl: libxl_qmp:
Introduce libxl__qmp_pci_add."):
> This function insert a PCI passthrough device in qemu.
Thanks. I have applied 1-9 from this series. 13/13 had a conflict,
and I wasn't 100% sure that it was right to apply it without 10,11,
On Fri, Nov 4, 2011 at 9:53 AM, Fabien Chouteau wrote:
> On 04/11/2011 09:36, Stefan Hajnoczi wrote:
>> On Thu, Nov 03, 2011 at 10:35:28AM +0100, Fabien Chouteau wrote:
>>> On 03/11/2011 08:44, Stefan Hajnoczi wrote:
On Wed, Nov 2, 2011 at 5:39 PM, Fabien Chouteau
wrote:
> On 29/10
On 11/04/2011 12:09 PM, Thomas Schmitt wrote:
So there are still two show stoppers.
DVD+RW gets stuck at SET STREAMING.
(I will hack libburn to avoid this command and check whether
writing is possible then. Chances are good, as writing an
already formatted DVD+RW is quite artless.)
CD SAO g
On Fri, Nov 4, 2011 at 2:26 PM, Wen Congyang wrote:
> At 11/04/2011 10:48 AM, Zhi Yong Wu Write:
>> On Fri, Nov 4, 2011 at 10:45 AM, Wen Congyang wrote:
>>>
>>> We disable vm_clock when pausing all vcpus, but we forget to
>>> reenable it when resuming all vcpus. It will cause that the
>>> guest c
On 11/04/2011 12:22 PM, Kevin Wolf wrote:
>
> That's exactly what this series did. However, daemonization has also to
> be done before opening the image file. So the series has to support
> reporting errors to syslog, and also qemu-nbd will not give a nonzero
> exit status when errors occur
On Fri, Nov 4, 2011 at 10:48 AM, Stefan Hajnoczi wrote:
> Windows 7 32-bit guest blue screens when I shut it down properly with
> Start | Shut Down. The blue screen is only displayed for a split
> second before the guest reboots so I am not able to easily tell what
> it says. My guess is that Wi
Am 04.11.2011 12:10, schrieb Paolo Bonzini:
> On 11/04/2011 11:31 AM, Kevin Wolf wrote:
>>> I tried implementing this, but in general daemonization (which forks and
>>> leave only the children) breaks the threading.
>>>
>>> So we could either keep this series (which moves all errors to syslog,
>
On 11/04/2011 11:31 AM, Kevin Wolf wrote:
> I tried implementing this, but in general daemonization (which forks and
> leave only the children) breaks the threading.
>
> So we could either keep this series (which moves all errors to syslog,
> but doesn't otherwise change behavior), or I can f
On 11/04/2011 03:35 PM, Kevin Wolf wrote:
Am 30.10.2011 11:35, schrieb Supriya Kannery:
+struct BDRVReopenState {
+BlockDriverState *bs;
+int reopen_flags;
+
+/* For raw-posix */
+int reopen_fd;
+};
I think I commented the same on the previous version: BDRVReopenState
shouldn'
Hi,
i wrote:
> > Paolo:
> > May i ask for the favor that you try to add O_RDWR to the qemu_open()
> > call of passthrough devices ?
Paolo Bonzini wrote:
> I think the problem is that you're passing media=cdrom:
> Just do not do that when using scsi-generic.
The result looks promising, indeed. I
On 11/04/2011 03:30 PM, Kevin Wolf wrote:
Am 30.10.2011 11:34, schrieb Supriya Kannery:
+
+if (bdrv_is_inserted(bs)) {
+/* Reopen file with changed set of flags */
+return bdrv_reopen(bs, bdrv_flags);
+} else {
+/* Save hostcache change for future use */
+
On 11/03/2011 07:25 PM, Luiz Capitulino wrote:
On Sun, 30 Oct 2011 16:03:54 +0530
Supriya Kannery wrote:
+if (qdict_haskey(bs_dict, "hostcache")) {
+monitor_printf(mon, " hostcache=%d",
+ qdict_get_bool(bs_dict, "hostcache"));
+}
This series needs to be r
On 11/01/2011 06:03 AM, ShaoHe Feng wrote:
after the guest startups, then I right click mouse in the UI of the
guest, and select the Eject from the menu.
there comes an event in the qmp-monitor.
{"timestamp": {"seconds": 1320118137, "microseconds": 420150}, "event":
"TRAY_STATE_CHANGED", "data":
Am 04.11.2011 02:03, schrieb David Gibson:
> As a few people pointed out, my recent patch series introducing a new
> (stub) PCI DMA API added unnecessary casts in quite a few places. I
> think this was a hangover from early days of the patchese where the
> casts were necessary for some reason I've
Windows 7 32-bit guest blue screens when I shut it down properly with
Start | Shut Down. The blue screen is only displayed for a split
second before the guest reboots so I am not able to easily tell what
it says. My guess is that Windows is triple-faulting or soft
rebooting - note that I told Win
Am 04.11.2011 10:46, schrieb Paolo Bonzini:
> On 10/28/2011 02:17 PM, Paolo Bonzini wrote:
>>> Yes, it would be better if we could have error output on stderr. Now,
>>> "simple" errors such as a missing image file (or wrong path to the
>>> image) are reported to syslog instead. It could be the sour
Am 30.10.2011 11:35, schrieb Supriya Kannery:
> raw-posix driver changes for bdrv_reopen_xx functions to
> safely reopen image files. Reopening of image files while
> changing hostcache dynamically, is handled here.
>
> Signed-off-by: Supriya Kannery
>
> Index: qemu/block/raw.c
> ==
readline_hist_add() moves the history entry to the end of history. It
uses memmove() to move rs->history[idx + 1..] to rs->history[idx..].
However, its size argument is off by two array elements, so it writes
one element beyond rs->history[], and reads two.
On my system, this clobbers rs->hist_en
Am 30.10.2011 11:35, schrieb Supriya Kannery:
> Struct BDRVReopenState along with three reopen related functions
> introduced for handling reopen state of images safely. This can be
> extended by each of the block drivers to reopen respective
> image files.
>
> Signed-off-by: Supriya Kannery
> I
Am 30.10.2011 11:34, schrieb Supriya Kannery:
> New command "block_set_hostcache" added for dynamically changing
> host pagecache setting of a block device.
>
> Usage:
> block_set_hostcache
> = block device
> = on/off
>
> Example:
> (qemu) block_set_hostcache ide0-hd0 off
>
> Sign
On Fri, Nov 04, 2011 at 03:43:04PM +0800, Li Zhi Hui wrote:
> Since common file operation functions lack of error detection,
> so change them to bdrv series functions.
>
> Signed-off-by: Li Zhi Hui
> ---
> block/cow.c | 63 +-
> 1 files
On 04/11/2011 09:36, Stefan Hajnoczi wrote:
> On Thu, Nov 03, 2011 at 10:35:28AM +0100, Fabien Chouteau wrote:
>> On 03/11/2011 08:44, Stefan Hajnoczi wrote:
>>> On Wed, Nov 2, 2011 at 5:39 PM, Fabien Chouteau
>>> wrote:
On 29/10/2011 15:52, Alexander Graf wrote:
>>> I took a quick peak at t
On 10/28/2011 02:17 PM, Paolo Bonzini wrote:
Yes, it would be better if we could have error output on stderr. Now,
"simple" errors such as a missing image file (or wrong path to the
image) are reported to syslog instead. It could be the source of some
headaches...
Is there a way we could have th
Li Zhi Hui writes:
> Since common file operation functions lack of error detection,
> so change them to bdrv series functions.
Looks like a few indentation fixes crept in as well. Best to keep such
style cleanups well separated from functional changes.
On 11/04/2011 10:18 AM, Thomas Schmitt wrote:
Paolo:
May i ask for the favor that you try to add O_RDWR to the qemu_open()
call of passthrough devices ?
I think the problem is that you're passing media=cdrom:
if (media == MEDIA_CDROM) {
/* CDROM is fine for any interface, don't ch
vga_putcharxy()'s underline code sets font_data to 0x instead of
0xff. vga_putcharxy() then reads dmask16[0x >> 4] and
dmask4[0x >> 6]. In practice, these out-of-bounds subscripts
"only" put a few crap bits into the display surface.
For 32 bit pixels, there's no array access. font_d
Spotted by Coverity.
Signed-off-by: Markus Armbruster
---
hw/qxl.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/hw/qxl.c b/hw/qxl.c
index 84ffd45..c97bebe 100644
--- a/hw/qxl.c
+++ b/hw/qxl.c
@@ -1006,7 +1006,7 @@ void *qxl_phys2virt(PCIQXLDevice *qxl, QXLPHYSICAL pq
On 11/04/2011 10:27 AM, Fabien Chouteau wrote:
It's a huge assumption though, and I don't think it should be assumed anymore.
What can we do to improve that?
Remove the affinity change and see what breaks. :)
> With iothread the architecture of the QEMU main loop is anyway completely
diff
On 03/11/2011 12:50, Paolo Bonzini wrote:
> On 11/03/2011 11:29 AM, Avi Kivity wrote:
>> > It would ensure that two mutators wouldn't run concurrently. In some
>> > sense, signal-safe code could then be considered thread-safe too.
>>
>> How so? The scheduler can switch between the two threads o
Hi
i can prevent the EPERM failures of ioctl(SG_IO) by opening the
device file /dev/sg1 with O_RDWR rather than O_RDONLY.
In block/raw-posix.c:raw_open_common i implemented this hack:
printf("block/raw-posix.c: raw_open_common(\"%s\", %x)\n",
filename, s->open_flags);
if
On Thu, Nov 03, 2011 at 02:34:24PM -0200, Marcelo Tosatti wrote:
> On Wed, Nov 02, 2011 at 03:43:49PM +, Stefan Hajnoczi wrote:
> > On Tue, Nov 1, 2011 at 6:06 PM, Marcelo Tosatti wrote:
> > > On Thu, Oct 27, 2011 at 04:22:50PM +0100, Stefan Hajnoczi wrote:
> > >> +
> > >> + for (sector_num
On Thu, Nov 03, 2011 at 01:51:54PM -0200, Luiz Capitulino wrote:
> On Tue, 1 Nov 2011 18:08:16 +
> Stefan Hajnoczi wrote:
>
> > Move from plain HMP/QMP command implementation to QAPI. The
> > block_stream command takes arguments, returns nothing, may raise errors,
> > and will raise a QMP e
On Thu, Nov 03, 2011 at 10:35:28AM +0100, Fabien Chouteau wrote:
> On 03/11/2011 08:44, Stefan Hajnoczi wrote:
> > On Wed, Nov 2, 2011 at 5:39 PM, Fabien Chouteau
> > wrote:
> >> On 29/10/2011 15:52, Alexander Graf wrote:
> > I took a quick peak at the qemu-trace.[ch] from couverture and it
> > l
On 11/04/2011 02:52 AM, Peter Maydell wrote:
* the fixed address we mmap the code gen buffer to in system
mode tends to overlap the libc heap (at least on Ubuntu oneiric);
when this happens you typically get a sysmalloc abort
Let's change this to use the .bss code gen buffer. We can make it
Since common file operation functions lack of error detection,
so change them to bdrv series functions.
Signed-off-by: Li Zhi Hui
---
block/cow.c | 63 +-
1 files changed, 36 insertions(+), 27 deletions(-)
diff --git a/block/cow.c b/blo
On 11/04/2011 03:45 AM, Wen Congyang wrote:
We disable vm_clock when pausing all vcpus, but we forget to
reenable it when resuming all vcpus. It will cause that the
guest can not be rebooted.
Signed-off-by: Wen Congyang
---
cpus.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
d
Good catch.
This patch (and the next one 6/10) can be picked up independently
through qemu-trivial or pci-tree.
On Fri, Oct 28, 2011 at 04:07:31PM +0100, Anthony PERARD wrote:
> Value check in PCI Express Base Specification rev 1.1
>
> Signed-off-by: Anthony PERARD
> ---
> hw/pci_regs.h |2
Am 04.11.2011 03:56, schrieb Anthony Liguori:
On 11/03/2011 09:43 PM, Zhi Yong Wu wrote:
HI,
Just now i found that the mainpage of QEMU.org is hacked, right?
http://wiki.qemu.org/Main_Page
Not hacked, it's a wiki, so it's vulnerable to spam. Folks have been
doing a great job reverting the s
96 matches
Mail list logo
