Penned by Paolo Bonzini on 20130316 3:14.29, we have:
| Il 15/03/2013 20:21, Todd T. Fries ha scritto:
| > PID USERNAME PRI NICE SIZE RES STATE WAIT TIMECPU COMMAND
| > 28818 todd 640 1142M 53M onproc/0 - 2:01 17.24% cc1
| >
| > For systems with lower limits
Penned by Paolo Bonzini on 20130316 3:14.29, we have:
| Il 15/03/2013 20:21, Todd T. Fries ha scritto:
| > PID USERNAME PRI NICE SIZE RES STATE WAIT TIMECPU COMMAND
| > 28818 todd 640 1142M 53M onproc/0 - 2:01 17.24% cc1
| >
| > For systems with lower limits
Penned by Paolo Bonzini on 20130321 3:25.51, we have:
| Il 21/03/2013 08:53, qemu-de...@email.fries.net ha scritto:
| > load averages: 6.74, 6.23, 5.17leveno.fries.net
02:42:23
| > 201 processes: 200 idle, 1 on processor
| > CPU0 states: 0.4% user, 0.0% nice, 33.3% system
Penned by ? (Wei-Ren Chen) on 20130322 2:30.14, we have:
| > Still no joy:
| >
| > PID USERNAME PRI NICE SIZE RES STATE WAIT TIMECPU COMMAND
| > 21212 todd -5 20 1142M 118M sleep/0 - 1:03 37.30% cc1
| >
| > cc -I. -I/home/todd/git/sw/3rdParty/qemu
-I/
Hi List,
This morning I ran across a thread on this list from Oct'11 about slow
booting with large initrd images. Reading through that thread, I didn't
really see any sort of definitive resolution to the problem.
Also, this morning, I upgraded Qemu-KVM to latest git master
(9d636ae7488edfa9c7f03
06:57:59 -0600, Dyweni - Qemu-Devel wrote:
Hi,
I am unable to boot KVM using a usb flash drive. I'm using QEMU-KVM
built
from GIT MASTER as of this morning.
Here's my QEMU-KVM startup options:
qemu-system-x86_64
-curses
-m 512
-snapshot
-device piix3-usb-uhci
-drive id=usbflash,file=fl
Hi All,
In QEMU-KVM 0.14, I was able to simulate booting from a USB Flash drive
with
these options:
qemu-system-x86_64 \
-curses \
-m 512 \
-snapshot \
-device piix3-usb-uhci \
-drive id=usbflash,file=flash.img,if=none,boot=on,cache=writeback \
Hi,
I am unable to boot KVM using a usb flash drive. I'm using QEMU-KVM
built
from GIT MASTER as of this morning.
Here's my QEMU-KVM startup options:
qemu-system-x86_64 \
-curses \
-m 512 \
-snapshot \
-device piix3-usb-uhci \
-drive id=usbflash,file=
from ca00:0372
In resume (status=0)
In 32bit resume
Attempting a hard reboot
---
Thanks,
Dyweni
On Thu, 19 Jan 2012 06:21:36 -0600, Dyweni - Qemu-Devel wrote:
Hi All,
In QEMU-KVM 0.14, I was able to simulate booting from a USB Flash
drive
with
these options:
qemu-system-x86_64
-curses
-m 512
20:57:11 -0500, Kevin O'Connor wrote:
On Thu, Jan 19, 2012 at 06:57:59AM -0600, Dyweni - Qemu-Devel wrote:
Hi, I am unable to boot KVM using a usb flash drive. I'm using
QEMU-KVM
built from GIT MASTER as of this morning. Here's my QEMU-KVM startup
options: qemu-system-x86
sitory hosted on git.kernel.org:
[Qemu-devel] [PATCH v3 0/4] rbd improvements
http://lists.gnu.org/archive/html/qemu-devel/2011-04/msg01211.html
Before I attempt to apply Josh's patchset, I'd like to know if anyone
else on the list has ran across this before.
Thanks,
Dyweni
x27;s patches use the newer librbd from ceph 0.27. With this library
> the qemu driver gets a lot simpler and avoids code duplication in ceph
> and qemu. - It's the future, but I don't think it will solve your
> problem.
>
> Christian
>
> 2011/5/4 Dyweni - Qemu-Devel <
bd improvements" patchset
(http://lists.gnu.org/archive/html/qemu-devel/2011-04/msg01211.html)
The GDB Backtrace is:
#0 0x7f7733c2a495 in raise (sig=) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1 0x7f7733c2b81f in abort () at abort.c:92
#2 0x7f7733175a25 in __gnu_cxx::__v
6.37-gentoo-r4
> Ceph 0.27
> QEMU-KVM (commit 28262112181f27f302b5186f0df6428df6b513e7)
> Pulled from: git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git
> And patched with Josh Durgin's "rbd improvements" patchset
> (http://lists.gnu.org/archive/html/qemu-devel
Hi Josh/Lists!
463 ::decode(*data_bl, iter);
(gdb) print r
$1 = 0
(gdb) print data_bl
$2 = (ceph::bufferlist *) 0x7f16f40d6060
(gdb) print data_bl->_len
$3 = 0
(gdb) print iter->off
$4 = 20
Thanks,
Dyweni
> CCing the ceph list.
>
> On 05/06/2011 12:23 PM, Dywe
0, _off = 0, _len = 0}, last_p = {
bl = 0x7f16f40d6170, ls = 0x7f16f40d6170, off = 0, p = {_M_node =
0x7f16f40d6170}, p_off = 0}}, pbl = 0x0, buf = 0x0, maxlen = 0}
Thanks,
Dyweni
> On Fri, 6 May 2011, Dyweni - Qemu-Devel wrote:
>> Hi Josh/Lists!
>>
>> 463 ::de
Thanks,
Dyweni
> f 9 (or 8?)
> p n
> p s
>
> (BTW this might be faster over irc, #ceph on irc.oftc.net)
>
> Thanks!
> sage
>
>
> On Fri, 6 May 2011, Dyweni - Qemu-Devel wrote:
>
>> Hi Sage/Lists!
>>
>>
>> (gdb) print c->bl._len
>
Hi Sage/Lists!
Yes! The entire Ceph cluster (1 Mon, 1 MSD, 3 OSD) are 32bit linux.
The machine running Qemu is 64bit linux.
Thanks,
Dyweni
> On Fri, 6 May 2011, Dyweni - Qemu-Devel wrote:
>> Hi Sage/Lists!
>>
>>
>> (gdb) f 8
>> #8 0x7f170174198
From: yuchenlin
Due to too early RCT0 interrput, win10x32 may hang on booting.
This problem can be reproduced by doing power cycle on win10x32 guest.
In our environment, we have 10 win10x32 and stress power cycle.
The problem will happen about 20 rounds.
Below shows some log with comment:
The n
Original Message
Subject: Re: [Qemu-devel] [PATCH RFC v19 11/13] target-avr: Put all translation
code into one compilation unit
Local Time: June 13, 2017 10:07 PM
UTC Time: June 13, 2017 8:07 PM
From: th...@redhat.com
To: Michael Rolnik , qemu-devel@nongnu.org
Richard Henderson
Hello.
I have forgot about this. I even unable to remember what I have done.
Unfortunately I can't help you. Sorry.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1169049
Title:
do not st
Anyone can explain what is the blocking problem for this target to be pulled
upstream?
I apologize for bothering but I don't have the workflow clear in my mind.
thanks,
Anichang
> Original Message
> Subject: Re: [PATCH RFC v19 00/13] QEMU AVR 8 bit cores
> Local Time: June 22, 2
Hi all,
I just resurrected the target-avr patchset from Michael Rolnik. Following the
details:
commit f2bca179dbfc3f378b131ed619d07db946bae598
Merge: 43771d5 ed250c0
Author: Ani Chang
Date: Fri Jun 2 01:17:34 2017 +0200
target/avr: resurrected (see mailing list qemu-devel, Richard Henderson
When the guest OS needs to send the mouse commands it will at least in
the case
of Windows 10 set the KBD_MODE_DISABLE_MOUSE bit to prevent interrupts
from
causing stream desynchronisation.
Here is Windows 10 attempting to issue a PS/2 mouse reset without this
fix where
you can see the mouse p
Hi All,
I am writing some code that needs to share a block of ram between a
Windows guest and Linux host. For this I am using the ivshmem device and
I have written a very primitive driver for windows that allows a single
application to request to memory map the pci bar (shared memory) into
th
Hi,
A .qcow file was deleted by mistake. No recovery or backup is available.
Hard disk was plugged out from the NAS after half a hour to prevent
Synology OS operations writing over desallocated stockage. The file
system on the virtual disk was ntfs. Virtualisation OS is Proxmox.
Ease Us Data
I just updated to the latest build and applied this patch set, now on VM
reset the qemu crashes with the following assert:
ivshmem.c:467: ivshmem_add_kvm_msi_virq: Assertion
`!s->msi_vectors[vector].pdev' failed.
On 2017-11-15 18:31, Ladi Prosek wrote:
Fixes bugs in the ivshmem device implem
t TBD. Thanks,
Alex
[1] https://lists.gnu.org/archive/html/qemu-devel/2018-10/msg03086.html
---
Alex Williamson (7):
pcie: Create enums for link speed and width
pci: Sync PCIe downstream port LNKSTA on read
qapi: Define PCIe link speed and width properties
pcie: Add li
On 2018-10-08 10:38, Fam Zheng wrote:
On Fri, 10/05 10:00, yuchenlin wrote:
Ping?
Hi,
This was merged as 51b3c6b73acae1e3fd3c7d441fc86dd17356695f.
Fam
Hi,
Thank you for your information.
yuchenlin
On 2018-09-13 16:34, Fam Zheng wrote:
> On Thu, 09/13 16:29, yuchen...@synology.com wro
From: yuchenlin
There are 3 virtqueues (ctrl, event and cmd) for virtio scsi device,
but seabios will only set the physical address for the 3rd one (cmd).
Then in vhost_virtqueue_start(), virtio_queue_get_desc_addr()
will be 0 for ctrl and event vq.
In this case, ctrl and event vq are not initia
Ping?
On 2018-10-12 17:07, yuchen...@synology.com wrote:
From: yuchenlin
There are 3 virtqueues (ctrl, event and cmd) for virtio scsi device,
but seabios will only set the physical address for the 3rd one (cmd).
Then in vhost_virtqueue_start(), virtio_queue_get_desc_addr()
will be 0 for ctrl a
From: yuchenlin
Signed-off-by: yuchenlin
---
hw/display/vga_int.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/hw/display/vga_int.h b/hw/display/vga_int.h
index 6e4fa48a79..55c418eab5 100644
--- a/hw/display/vga_int.h
+++ b/hw/display/vga_int.h
@@ -166,7 +166,6 @@ MemoryRegion *vga_init_i
(VGACommonState *s);
void vga_dirty_log_start(VGACommonState *s);
void vga_dirty_log_stop(VGACommonState *s);
Added to vga queue.
thanks,
Gerd
Hi, Gerd
Laurent has sent a pull request for this trivial commit.
See:
http://lists.nongnu.org/archive/html/qemu-devel/2018-10/msg05896.html
Thanks
Ping?
On 2018-09-13 16:34, Fam Zheng wrote:
On Thu, 09/13 16:29, yuchen...@synology.com wrote:
From: yuchenlin
There is a rare case which the size of last compressed cluster
is larger than the cluster size, which will cause the file is
not aligned at the sector boundary.
There are three reas
On 2018-12-28 22:50, Julio Faracco wrote:
This is a trivial patch to fix a wrong value for block terminator.
The old value was 0x7fff which is wrong. It was not affecting the
code because QEMU dmg block is not handling block terminator right now.
Neverthless, it should be fixed.
Signed-off-b
From: yuchenlin
There is a rare case which the size of last compressed cluster
is larger than the cluster size, which will cause the file is
not aligned at the sector boundary.
Signed-off-by: yuchenlin
---
block/vmdk.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/blo
64" ] || [ "$host_family" != "$family" ] ;
then
and running it with the --systemd ALL parameter causes a x86_64 config
file to be created. it still doesnt work but that might have different
causes.
--
You received this bug notification because you are a member of
Ping!
yuchen...@synology.com 於 2018-08-28 11:18 寫道：
> From: yuchenlin There is a rare case which the size
> of last compressed cluster is larger than the cluster size, which will cause
> the file is not aligned at the sector boundary. Signed-off-by: yuchenlin
> --- block/vmdk.c | 18 +
Fam Zheng 於 2018-09-12 17:34 寫道：
> On Tue, 08/28 11:17, yuchen...@synology.com wrote: > From: yuchenlin
> > > There is a rare case which the size of last
> compressed cluster > is larger than the cluster size, which will cause the
> file is > not aligned at the sector boundary. I don't under
On 2018-09-12 19:54, Fam Zheng wrote:
On Tue, 08/28 11:17, yuchen...@synology.com wrote:
From: yuchenlin
There is a rare case which the size of last compressed cluster
is larger than the cluster size, which will cause the file is
not aligned at the sector boundary.
Signed-off-by: yuchenlin
-
From: yuchenlin
There is a rare case which the size of last compressed cluster
is larger than the cluster size, which will cause the file is
not aligned at the sector boundary.
Signed-off-by: yuchenlin
---
v1 -> v2:
* Add more detail comment.
* Add QEMU_ALIGN_UP to show the intention more clear
On 2018-09-13 10:54, Fam Zheng wrote:
On Thu, 09/13 10:31, yuchen...@synology.com wrote:
From: yuchenlin
There is a rare case which the size of last compressed cluster
is larger than the cluster size, which will cause the file is
not aligned at the sector boundary.
The code looks good to me.
From: yuchenlin
There is a rare case which the size of last compressed cluster
is larger than the cluster size, which will cause the file is
not aligned at the sector boundary.
There are three reasons to do it. First, if vmdk doesn't align at
the sector boundary, there may be many undefined beha
ndows
** Attachment added: "2018-07-11_15-49-15.png"
https://bugs.launchpad.net/bugs/1781211/+attachment/5162388/+files/2018-07-11_15-49-15.png
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1781211
qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1781211
Title:
HAXM acceleration does not work at all.
Status in QEMU:
New
Bug description:
I have qemu windows build 2.12.90, haxm 7.2.0. Ubuntu, nor arch linux does
not works when i turn on hax acceleration
main_loop_err = 0x0
err = 0x0
list_data_dirs =
dirs =
bdo_queue = {sqh_first = 0x0, sqh_last = 0xb918}
__func__ = "main"
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a
follow-up to IRC discussions with stsquad and danpb : the problem is
"-machine none" which prevents all the data structures from being
initialized properly.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.lau
Works well for me, thanks!
Tested-by: Geoffrey McRae
On 2018-04-27 02:26, Babu Moger wrote:
This series enables the TOPOEXT feature for AMD CPUs. This is required
to
support hyperthreading on kvm guests.
This addresses the issues reported in these bugs:
https://bugzilla.redhat.com/show_bug.c
From: Andrew Oates
On Linux, SOCK_DGRAM+IPPROTO_ICMP sockets give only the ICMP packet when
read from. On macOS, however, the socket acts like a SOCK_RAW socket
and includes the IP header as well.
This change strips the extra IP header from the received packet on macOS
before sending it to the
From: Andrew Oates
On Linux, SOCK_DGRAM+IPPROTO_ICMP sockets give only the ICMP packet when
read from. On macOS, however, the socket acts like a SOCK_RAW socket
and includes the IP header as well.
This change strips the extra IP header from the received packet on macOS
before sending it to the
From: yuchenlin
When the condition of each if or else if is true,
the code flow will goto fail. Which means we can decouple
if else if chain to get some readability.
Signed-off-by: yuchenlin
---
block/vdi.c | 27 ++-
1 file changed, 18 insertions(+), 9 deletions(-)
dif
From: yuchenlin
This series refine some code in vdi.c, includes:
* Remvoe CONFIG_VDI_WRITE because there is no reason to leave an always on
and cannot configure option in the code-side.
* decouple if else if chain to get more readability.
Thanks,
yuchenlin
yuchenlin (2):
vdi: remove CONFIG
From: yuchenlin
The CONFIG_VDI_WRITE is here when the first time vdi is added.
But there is no reason to leave an always on and cannot configure option
in the code-side.
Signed-off-by: yuchenlin
---
block/vdi.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/block/vdi.c b/block/vdi.c
i
Hi, Stefan
I agree that redundancy of If else may helps people to understand the code.
However, CONFIG_VDI_WRITE only contributes:
#if defined(CONFIG_VDI_WRITE)
.bdrv_co_pwritev = vdi_co_pwritev,
#endif
I think we don't need CONFIG_VDI_WRITE to document the code.
As its name implies, vdi_co_pwr
ards,
Yan.
On 15 Oct 2017, at 12:32, geoff--- via Qemu-devel
wrote:
Hi All,
I am writing some code that needs to share a block of ram between a
Windows guest and Linux host. For this I am using the ivshmem
device and I have written a very primitive driver for windows that
allows a single appli
On 2017-10-18 16:31, Ladi Prosek wrote:
Hi Geoff,
On Mon, Oct 16, 2017 at 8:31 PM, wrote:
Hi Yan & Ladi.
I have written an initial implementation that supports just the shared
memory
mapping at this time. I plan to add events also but before I go
further I
would
like some feedback if possi
On 2017-10-18 17:50, Ladi Prosek wrote:
On Wed, Oct 18, 2017 at 7:50 AM, wrote:
On 2017-10-18 16:31, Ladi Prosek wrote:
Hi Geoff,
On Mon, Oct 16, 2017 at 8:31 PM, wrote:
Hi Yan & Ladi.
I have written an initial implementation that supports just the
shared
memory
mapping at this time.
Hi Ladi & Yan,
I am pleased to present the completed driver for review, please see:
https://github.com/gnif/kvm-guest-drivers-windows
All issues previously mentioned have been addressed and all missing
functionality has been added.
Please note that this work has exposed a bug in the qemu ivshm
On 2017-10-19 19:35, Ladi Prosek wrote:
On Wed, Oct 18, 2017 at 5:04 PM, wrote:
Hi Ladi & Yan,
I am pleased to present the completed driver for review, please see:
https://github.com/gnif/kvm-guest-drivers-windows
Awesome!
Feel free to open pull request, it should be easier to comment on.
On 2017-10-19 20:01, Ladi Prosek wrote:
On Thu, Oct 19, 2017 at 10:44 AM, wrote:
On 2017-10-19 19:35, Ladi Prosek wrote:
On Wed, Oct 18, 2017 at 5:04 PM, wrote:
Hi Ladi & Yan,
I am pleased to present the completed driver for review, please see:
https://github.com/gnif/kvm-guest-drivers
On 2017-10-19 20:07, ge...@hostfission.com wrote:
On 2017-10-19 20:01, Ladi Prosek wrote:
On Thu, Oct 19, 2017 at 10:44 AM, wrote:
On 2017-10-19 19:35, Ladi Prosek wrote:
On Wed, Oct 18, 2017 at 5:04 PM, wrote:
Hi Ladi & Yan,
I am pleased to present the completed driver for review, ple
On 2017-10-19 20:51, Ladi Prosek wrote:
On Thu, Oct 19, 2017 at 11:41 AM, wrote:
On 2017-10-19 20:07, ge...@hostfission.com wrote:
On 2017-10-19 20:01, Ladi Prosek wrote:
On Thu, Oct 19, 2017 at 10:44 AM, wrote:
On 2017-10-19 19:35, Ladi Prosek wrote:
On Wed, Oct 18, 2017 at 5:04 PM
Hi All,
I have started to dig into why ntp seems to slow down graphics
performance on
AMD systems using PCI passthrough and figured I would report what I have
so far
discovered. I have noted the primary point of failure seems to be
specifically
with PhysX. This is why people only see a slow do
>Could you please try to replace the -virtfs option with these two options:
>
>-fsdev local,id=shared,path=/home/mahmood/Downloads \
>-device virtio-9p-pci,fsdev=shared,mount_tag=Downloads
Still get the same error!
mahmood@cluster:qemu-vm$ qemu-system-x86_64 -m 4000 -cpu Opteron_G5 -smp 2 -h
The security_model=none also doesn't work and get the same error.
mahmood@cluster:qemu-vm$ qemu-system-x86_64 -version
QEMU emulator version 1.7.0, Copyright (c) 2003-2008 Fabrice Bellard
I know it is old but I think I installed this version three years ago due to
the Rocks-6 version old libra
Hello again,I installed 2.5.0 quickly and it was pretty straight forward!
Here is the error message I get regarding the 'virtio-9p-pci'
mahmood@cluster:qemu-vm$ qemu-system-x86_64 -m 4000 -cpu Opteron_G5 -smp 2 -hda
centos7.img -boot c -usbdevice tablet -enable-kvm -device
e1000,netdev=host_
OK. I reconfigured 2.9.0 with --enable-virtfs. Please note:
1- If I use -virtfs option, I get
qemu-option.c:547: opt_set: Assertion `opt->str' failed
2- If I use -fsdev and -device, then I *must* use security_model
3- If I use -fsdev and -device and security_model, then the guest boots
nor
Hello again,
For the command
mount -t 9p -o trans=virtio Downloads /media/Downloads
inside the Centos-7 guest, I get this error
mount: unknown filesystem type '9p'
Any thought?
Regards,
Mahmood
Thanks Ladi, I had not yet had time to dig into these, this patch set
resolves all issues I was aware of.
Tested-by: Geoffrey McRae
On 2017-11-11 04:34, Ladi Prosek wrote:
As of commit 660c97eef6f8 ("ivshmem: use kvm irqfd for msi
notifications"),
QEMU crashes with:
kvm_irqchip_commit_rou
On 2017-11-14 04:27, Markus Armbruster wrote:
Ladi Prosek writes:
Adds a rollback path to ivshmem_enable_irqfd() and fixes
ivshmem_disable_irqfd() to bail if irqfd has not been enabled.
Signed-off-by: Ladi Prosek
Is this a theoretical bug, or can you trigger it?
It is reproducible, I can
Public bug reported:
This would be a useful feature. Many kernels, particularly hobbyist
kernels, have support for ATAGS.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
if I wait around 30 minutes to an hour I can
restart and it will boot fine again with iommu=pt (I get a kernel panic
if i don't use iommu=pt)
Hardware
Ryzen R5 1600
asrock ab350m pro4
32gb ram
Host gpu RX580
Guest gpu GTX1070
--
You received this bug notification because you are a member of
From: yuchenlin
VMDK has a hard limitation of extent size, which is due to the size of grain
table entry is 32 bits. It means it can only point to a grain located at
offset = 2^32. To prevent offset overflow and record a useless offset
in grain table. We should return un-support here.
Signed-off
From: yuchenlin
VMDK has a hard limitation of extent size, which is due to the size of grain
table entry is 32 bits. It means it can only point to a grain located at
offset = 2^32. To avoid writing the user data beyond limitation and record a
useless offset
in grain table. We should return ERROR
From: yuchenlin
VMDK has a hard limitation of extent size, which is due to the size of grain
table entry is 32 bits. It means it can only point to a grain located at
offset = 2^32. To avoid writing the user data beyond limitation and record a
useless offset
in grain table. We should return ERROR
Bacherov
-Исходное сообщение-
From: Stafford Horne
Sent: Saturday, May 05, 2018 8:19 AM
To: Richard Henderson
Cc: qemu-devel@nongnu.org ; Richard Henderson ; band...@mail.ru
Subject: Re: [PATCH 01/13] target-openrisc: Write back result before FPE
exception
On Thu, May 03, 2018 at 10:40:1
This allows guest's to correctly reinitialize and identify the mouse
should the guest decide to re-scan or reset during mouse input events.
Signed-off-by: Geoffrey McRae
---
hw/input/ps2.c | 4
1 file changed, 4 insertions(+)
diff --git a/hw/input/ps2.c b/hw/input/ps2.c
index 06f5d2ac4a..
This fixes an issue by adding bounds checking to multi-byte packets
where the PS/2 mouse data stream may become corrupted due to data
being discarded when the PS/2 ringbuffer is full.
Interrupts for Multi-byte responses are postponed until the final
byte has been queued.
These changes fix a bug
On 2018-05-07 22:21, Gerd Hoffmann wrote:
On Mon, May 07, 2018 at 10:00:22PM +1000, geoff--- via Qemu-devel
wrote:
This allows guest's to correctly reinitialize and identify the mouse
should the guest decide to re-scan or reset during mouse input events.
Signed-off-by: Geoffrey McRae
--
On 2018-05-07 22:34, Gerd Hoffmann wrote:
diff --git a/hw/input/ps2.c b/hw/input/ps2.c
index 6edf046820..011290920f 100644
--- a/hw/input/ps2.c
+++ b/hw/input/ps2.c
@@ -192,12 +192,50 @@ void ps2_queue(PS2State *s, int b)
{
PS2Queue *q = &s->queue;
-if (q->count >= PS2_QUEUE_SIZE - 1)
On 2018-05-07 22:41, Gerd Hoffmann wrote:
On Mon, May 07, 2018 at 10:26:24PM +1000, geoff--- via Qemu-devel
wrote:
On 2018-05-07 22:21, Gerd Hoffmann wrote:
> On Mon, May 07, 2018 at 10:00:22PM +1000, geoff--- via Qemu-devel wrote:
> > This allows guest's to correctly reinitializ
From: Andrew Wood
Signed-off-by: Andrew Wood
---
os-posix.c | 1 +
vl.c | 13 +++--
2 files changed, 12 insertions(+), 2 deletions(-)
diff --git a/os-posix.c b/os-posix.c
index b9c2343b1e..68d70f269b 100644
--- a/os-posix.c
+++ b/os-posix.c
@@ -70,6 +70,7 @@ void os_setup_signal
Hi All,
I am having some very strange issues with Qemu and memory copy
performance. It seems that when performing buffer -> buffer copies of
8MB or lower the performance is horrid.
Test program:
#include
#include
#include
#include
#include
static inline uint64_t nanotime()
{
struct t
(wrong bug, sorry!)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1350435
Title:
tcg.c:1693: tcg fatal error
Status in launchpad-buildd:
Won't Fix
Status in QEMU:
Fix Released
Status in
QEMU
utilities
to reproduce: pbuilder-dist bionic arm64 create
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1350435
Title:
tcg.c:1693: tcg fatal error
Status in launchpad-buildd:
Won&#
If Windows 10 guests have enabled 'turn off hard disk after idle'
option in power settings, and the guest has a SATA disk plugged in,
the SATA disk will be turned off after a specified idle time.
If the guest is live migrated or saved/loaded with its SATA disk
turned off, the following error will o
-- Best regards, Andy Chiu John Snow 於 2019-09-10 02:13 寫道：
> > > > On 9/9/19 1:18 PM, andychiu via Qemu-devel wrote: > > If Windows 10
guests have enabled 'turn off hard disk after idle' > > option in power
settings, and the guest has a SATA disk plugged in,
[reg:PxIS] @ 0x10:
0x0002
ahci_mem_write_host ahci(0x7fcc4e19b4a0) write4 [reg:IS] @ 0x8:
0x0001
---
--
Best regards,
Andy Chiu
On 2019/9/10 上午2:13, John Snow wrote:
On 9/9/19 1:18 PM, andychiu via Qemu-devel wrote:
If
Text from "docs/nvdimm.txt" says:
Guest Data Persistence
--
Though QEMU supports multiple types of vNVDIMM backends on Linux,
currently the only one that can guarantee the guest write persistence
is the device DAX on the real NVDIMM device (e.g., /dev/dax0.0), to
which all gues
Raphael Norwitz 於 2019-08-23 04:16 寫道： > > Same
rational as: e6cc11d64fc998c11a4dfcde8fda3fc33a74d844 > > Of the 3 virtqueues,
seabios only sets cmd, leaving ctrl > and event without a physical address.
This can cause > vhost_verify_ring_part_mapping to return ENOMEM, causing > the
following l
: New
** Tags: ppc
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1824744
Title:
ivshmem device PCI device exposes wrong endianness on ppc64le
Status in QEMU:
New
Bug description:
On a pp
** Summary changed:
- ivshmem device PCI device exposes wrong endianness on ppc64le
+ ivshmem PCI device exposes wrong endianness on ppc64le
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1824744
Hello,
I'm sorry to waste your time.
Now I have a question and i can't find answer by google.
I need to use qemu to run different router,switch,and different
type(example:cisco,netgear,forti and more) and use openstack vm to connect
these equipment.
I found these equipment with different type,for
From: yuchenlin
In vmdk_co_create_opts, when it finds hw_version is undefined, it will
set it to 4, which misleading the compat6 and hwversion in
vmdk_co_do_create. Simply set hw_version to NULL after free, let
the logic in vmdk_co_do_create to decide the value of hw_version.
This bug can be rep
this bug while still applicable can be closed.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1759338
Title:
qemu-system-sparc w/ SS-20 ROM does not add processors
Status in QEMU:
New
Bug desc
On 2019-04-24 15:49, Sam Eiderman wrote:
Commit b0651b8c246d ("vmdk: Move l1_size check into vmdk_add_extent")
extended the l1_size check from VMDK4 to VMDK3 but did not update the
default coverage in the moved comment.
The previous vmdk4 calculation:
(512 * 1024 * 1024) * 512(l2 entries) *
Ping?
On 2019-03-13 14:56, yuchen...@synology.com wrote:
From: yuchenlin
Due to too early RCT0 interrput, win10x32 may hang on booting.
This problem can be reproduced by doing power cycle on win10x32 guest.
In our environment, we have 10 win10x32 and stress power cycle.
The problem will happen
On 2019-03-25 12:26, Jason Wang wrote:
On 2019/3/21 上午9:35, yuchenlin wrote:
Ping?
On 2019-03-13 14:56, yuchen...@synology.com wrote:
From: yuchenlin
Due to too early RCT0 interrput, win10x32 may hang on booting.
This problem can be reproduced by doing power cycle on win10x32
guest.
In our
From: Roman Kiryanov
VMSTATE_OPAQUE allows passing user defined functions to save
and load vmstate for cases when data structures do not fit
into int/struct/array terms.
Signed-off-by: Roman Kiryanov
---
include/migration/vmstate.h | 13 +
1 file changed, 13 insertions(+)
diff --g
Hi!
This is v2 of a proposed patch set for fixing file ID collisions with 9pfs.
Patch 1 to 3 are identical to the previous version. New in this v2 is patch 4
which introduces variable length suffixes for inode mapping instead of fixed
length prefixes.
Also: patch 4 disables file ID persistency a
1 - 100 of 845 matches
Mail list logo
