em0 requested-size 0
(qemu) device_del vmem0
Tested-by: Mario Casquero
On Tue, Jan 28, 2025 at 7:57 PM David Hildenbrand wrote:
>
> This is based-on [1], which adds MSI-X support to virtio-balloon-pci,
> but can be applied independently.
>
> Turns out it is fairly easy to get
: [70] Vendor Specific Information: VirtIO: Notify
Capabilities: [60] Vendor Specific Information: VirtIO: DeviceCfg
Capabilities: [50] Vendor Specific Information: VirtIO: ISR
Capabilities: [40] Vendor Specific Information: VirtIO: CommonCfg
Kernel driver in use: virtio-pci
Tested-by: Mario
On 15.12.2024 22:37, Yanfeng Liu wrote:
This adds virtualization mode (V bit) as bit(2) of register `priv`
per RiscV debug spec v1.0.0-rc4. Checked with gdb-multiarch v12.1.
Note that GDB may display `INVALID` tag for `priv` reg when V bit
is set, this doesn't affect actual access to the bit
Hi,
apologies for the delayed review; I've just gotten to it now.
On 06.12.2024 01:14, Yanfeng Liu wrote:
This adds virtualization mode (V bit) as bit(2) of register `priv`
per RiscV debug spec v1.0.0-rc3. Checked with gdb-multiarch v12.1.
Note that GDB may display `INVALID` tag for the value
Hi everyone,
I'd like to chime in here because we are sitting on a similar patch
which I wanted to send to the mailing list as soon as riscv-debug-spec
v1.0.0 becomes ratified.
For hypervisor support, `(qemu) info registers` isn't enough. We need to
have both read and write access to the V-b
0-
Tested-by: Mario Casquero
On Tue, Oct 8, 2024 at 12:57 PM David Hildenbrand wrote:
>
> Based on current master.
>
> There is really not much left to do on s390x, because virtio-mem already
> implements most things we need today (e.g., early-migration,
> u
-id=1,core-id=0
-numa cpu,node-id=0,socket-id=1,core-id=1,thread-id=0 -numa
cpu,node-id=1,socket-id=1,core-id=1,thread-id=1 -accel qtest
Tested-by: Mario Casquero
On Tue, Jun 4, 2024 at 8:24 AM Ani Sinha wrote:
>
> 'pentium' cpu is old and obsolete and should be avoided for
Tested-by: Mario Casquero
On Wed, Jun 5, 2024 at 12:45 PM Michal Privoznik wrote:
>
> If memory-backend-{file,ram} has a size that's not aligned to
> underlying page size it is not only wasteful, but also may lead
> to hard to debug behaviour. For instance, in case
> memory-backe
This patch has been successfully tested by QE. After allocating some
hugepages in the host, try to boot up a VM with the memory backed by a
file and the size unaligned, check now the message displayed by QEMU:
qemu-system-x86_64: backend memory size must be multiple of 0x20
Tested-by: Mario
This series has been successfully tested in x86. Execute the cpu help
command and check in the list the x86 prefix is no longer present.
Tested-by: Mario Casquero
On Sat, Apr 20, 2024 at 7:47 AM Thomas Huth wrote:
>
> Printing an architecture prefix in front of each CPU name is not h
plugged
Tested-by: Mario Casquero
On Tue, Apr 16, 2024 at 4:14 PM David Hildenbrand wrote:
>
> The error message is actually expressive, considering QEMU only. But
> when called from Libvirt, talking about "size" can be confusing, because
> in Libvirt "size" translat
e memslots.
Tested-by: Mario Casquero
On Mon, Mar 11, 2024 at 9:00 PM Mario Casquero wrote:
>
> This series has been successfully tested by QE. Start the
> qemu-storage-daemon in the background with a rhel 9.5 image and
> vhost-user-blk. After that, boot up a VM with virtio-mem and
>
This series has been successfully tested by QE. Start the
qemu-storage-daemon in the background with a rhel 9.5 image and
vhost-user-blk. After that, boot up a VM with virtio-mem and
vhost-user-blk-pci. Check with the HMP command 'info mtree' that
virtio-mem is making use of multiple memslots.
On
aphic
-monitor stdio
QEMU 8.2.50 monitor - type 'help' for more information
qemu-system-x86_64: cannot use stdio by multiple character devices
qemu-system-x86_64: could not connect serial device to character backend 'stdio'
real 0m0.012s
user 0m0.006s
sys 0m0.007s
Tested-by: Mar
This series has also been successfully tested in x86_64.
Tested-by: Mario Casquero
On Thu, Jan 18, 2024 at 4:08 AM Zhenyu Zhang wrote:
>
> [PATCH v1 2/2] memory-device: reintroduce memory region size check
>
> Test on 64k basic page size aarch64
> The patches work well on my Amp
This patch has been successfully tested by QE. Start a VM with a
virtio-balloon device and resize it to an invalid value. Check in the
expected error message that now makes reference to 'value' instead of
'target'.
Tested-by: Mario Casquero
On Tue, Oct 31, 2023 at 12:12
This patch has been successfully tested by QE. With a debug QEMU
build, start a VM with a virtio-mem device and 'dynamic-memslots=off',
this one can be resized seamlessly, no floating point exception found.
Tested-by: Mario Casquero
On Mon, Oct 23, 2023 at 1:13 PM David Hildenbr
This series has been successfully tested by QE. Specify a directory
for the mem-path of a memory-backend-file object. Check the error
message has been improved without referring to a device, which can
lead to confusion.
Tested-by: Mario Casquero
On Wed, Sep 6, 2023 at 2:07 PM David
This series has been successfully tested by QE. Start a vm using
pc.ram id but specifying a different memory-backend from the default
one. Check the error message has been improved.
Tested-by: Mario Casquero
On Wed, Aug 23, 2023 at 5:38 PM David Hildenbrand wrote:
>
> For migration pu
This series has been successfully tested by QE. Start a VM, plug a
virtio-mem device, resize the device (adding memory) and verify that
the virtio-mem device cannot be unplugged. Finally, resize the device
(removing all the memory) and check that it can be unplugged
seamlessly.
Tested-by: Mario
This series has been tested successfully by QE. Start a VM with a 8G
virtio-mem device and start memtester on it. Enable x-ignore-shared
capability and then do migration. Migration was successful and
virtio-mem can be resized as usual.
Tested-by: Mario Casquero
BR,
Mario
On Tue, Jun 20
On Thu, Jul 22, 2021 at 3:14 PM Dr. David Alan Gilbert
wrote:
> * Richard Henderson (richard.hender...@linaro.org) wrote:
> > On 7/22/21 12:02 AM, Dr. David Alan Gilbert wrote:
> > > Hi Richard,
> > >I think you were the last person to fiddle with the prefetching
> > > in buffer_zero_avx2 and
The issue is resolved in the current release
C:\tmp>"C:\Program Files\qemu\\qemu-system-i386.exe" --version
QEMU emulator version 5.1.92 (v5.2.0-rc2-11843-gf571c4ffb5-dirty)
Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers
** Changed in: qemu
Status: Incomplete => Fi
having the guest name enables identify of owner and customer.
Signed-off-by: Mario Smarduch
---
Test verification summary:
a) qemu-system-x86_64 -msg help
guest-name= - Prepends guest name for error messages but only
if -name is set otherwise option is ignored
timestamp=
b) qemu-system-x86_64
On 10/09/2019 02:19 PM, Paolo Bonzini wrote:
> On 09/10/19 18:44, Mario Smarduch wrote:
>> In a large VPC environment we want to log memory error occurrences
>> and log them with guest name and type - there are few use cases
>>
>>
>> - if VM crashes on AR mce
3d6f5000 addr of type BUS_MCEERR_AR
injected qemu-system-x86_64 amsNams3node
The first log had a corresponding mce log entry, the second didnt (logging
thresholds) we can infer from second entry same PA and mce type.
Signed-off-by: Mario Smarduch
---
target/i386/kvm.c | 29
Signed-off-by: Mario Smarduch
---
include/qemu/error-report.h | 1 +
qemu-options.hx | 10 ++
util/qemu-error.c | 31 +++
vl.c| 5 +
4 files changed, 43 insertions(+), 4 deletions(-)
diff --git a/include/qemu
type BUS_MCEERR_AR injected
with enterprise logging environment we can to take further actions.
v1 -> v2:
- split into two patches one to get the gustname second to log MCEs
- addressed comments for MCE logging
Mario Smarduch (2):
util/qemu-error: add guest name helper with -msg opti
On 10/07/2019 03:27 AM, Philippe Mathieu-Daudé wrote:
> Hi Mario,
>
> On 10/5/19 1:53 AM, Mario Smarduch wrote:
>> In a large VPC environment we want to log memory error occurrences
>> and log them with guest name and type - there are few use cases
>>
>>
>&g
On 10/06/2019 09:11 AM, Paolo Bonzini wrote:
> On 05/10/19 01:53, Mario Smarduch wrote:
>> Guest [Droplet-12345678] 2019-08-02T05:00:11.940270Z qemu-system-x86_64:
>> Guest MCE Memory Error at qemu addr 0x7f3c7622f000 and guest 78e42f000
>> addr of type BUS_MCEERR_A
type BUS_MCEERR_AR injected
with enterprise logging environment we can to take further actions.
Signed-off-by: Mario Smarduch
---
target/i386/kvm.c | 27 ++-
util/qemu-error.c | 24
2 files changed, 46 insertions(+), 5 deletions(-)
diff --git a
o have a reference implmentation for the integrated keyboard layout switching.
What are your thoughts about this kind of improvement?
Thanks,
Mario
Fixed issue by switching boot from d to c. I found the solution by just
seeing if it would work, and it does.
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.ne
Public bug reported:
When I try to install Mac OS X 10.5, it gives this error, "Mac OS X
cannot be installed on your computer." Command ran in the command-line:
"C:\Program Files\qemu\qemu-system-ppc" -L pc-bios -boot d -M
mac99,via=pmu -m 512 -hda
"C:\Users\*\Downloads\macosx105\MacOSHDD.qcow
I have a similar bug: 1674114
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1745312
Title:
Regression report: Disk subsystem I/O failures/issues surfacing in
DOS/early Windows [two separate issue
It is working now without the parameters "-machine isapc" and "-cpu
486".
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1674114
Title:
Bad sectors when using MS-DOS 6.22
Status in QEMU:
New
Bug
Public bug reported:
When I try to install DOS 6.22 in QEMU, I get many disk errors when the
virtual disk is beeing partionized and formatted. When I later do a
SCANDISK, I can see many bad sectors and file errors.
I have tested this with the following disk formats: qcow2, vmdk, raw.
I tested th
On 05/25/2015 10:11 AM, Andrew Jones wrote:
> On Fri, May 22, 2015 at 06:08:30PM -0700, Mario Smarduch wrote:
>> On 05/18/2015 08:53 AM, Catalin Marinas wrote:
>>> On Thu, May 14, 2015 at 02:46:44PM +0100, Andrew Jones wrote:
>>>> On Thu, May 14, 2015 at 01:05:09PM
asic loadable driver
that allocates non-cachable/pinned pages for QEMU to mmap()
may provide a reference point to build on. If that covers
all the cases then perhaps move to more generic solution. This
should be quicker to implement and test.
I wonder if kernel mm will ever have a reason
to create
_region_set_uncached() added to QEMU, and if it does not, some
>> vague idea why that falls outside of the scope of this patch set. After
>> all, adding a USB controller to a VM is not that an esoteric use case,
>> is it?
>
> I'll pull together a new version addressing all your comments, and also
> put some more time into making sure it'll work...
>
> Jeremy, can you give me the qemu command line you're using for your tests?
> I'll do some experimenting with it.
>
> Thanks,
> drew
>
Hi Drew,
I just recently looked at these patches and little confused.
Where or how are the QEMU page tables changed to
non-cacheable?
I noticed the logical pfn is changed to non-cacheable.
- Mario
erates error on the following:
./configure --enable-rbd
> ERROR: User requested feature rados block device
>configure was not able to find it.
>Install librbd/ceph devel
which I don't know what to do as i could not able to find librbd library.
Hope someone can helps.
Thanks,
Mario
@serge, what version would I need to upgrade to be able to use the
external snapshots? that sounds like it would solve my problems
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1025244
Title:
qcow2
@michael, so you do that once, after some time the machine keeps
growing, and growing and growing... and you have to redo that every so
often... I have a machine that should be taking up 30 gb yet is taking
600+ GB with 4 snapshots... but yeah... I'll just plug in another 1tb
hard drive so that i
Is anyone even looking at this? been years and the problem still
persists!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1025244
Title:
qcow2 image increasing disk size above the virtual limit
Sta
you may see issues like that.
- Mario
On 03/20/2014 08:45 AM, Michael Tokarev wrote:
> 19.03.2014 21:24, Mario Smarduch wrote:
>>
>> Fix return condition check from kvm_vm_ioctl(s, KVM_GET_DIRTY_LOG, &d) to
>> handle internal failures or no support for memory slot dirty
Fix return condition check from kvm_vm_ioctl(s, KVM_GET_DIRTY_LOG, &d) to
handle internal failures or no support for memory slot dirty bitmap.
Otherwise the ioctl succeeds and continues with migration.
Addresses BUG# 1294227
Signed-off-by: Mario Smarduch
---
kvm-all.c |2 +-
1 file cha
Public bug reported:
In the code below kvm_vm_ioctl(...) can return --errno != -1 from ioctl call,
but return only checks for -1.
Found during KVM-ARM migration which apperead to go through but was actually
failing getting
memslot dirty bitmap.
static int kvm_physical_sync_dirty_bitmap()
evice' option and see what happens.
Yes I did check the options on host after device is plugged and guest after
features
are probed, only the MAC feature is set.
Thanks,
- Mario
-Original Message-
From: qemu-devel-bounces+m.smarduch=samsung@nongnu.org
[mailto:qemu-devel-bounc
Public bug reported:
When using indpendent transport and backend in this case virtio-net-
device transport, none of the acceleration features are set after guest
probes the transport the backend is plugged into. For virtio-net this
leads to low throughput/performance. This holds true for virtio-
irtio-mmio
transport is addressed in this patch with few backends to see if
this is acceptable by virtio maintainers.
One issue on applying properties this late is they can't be added to the
object - none of property accessor functions work at this point. This
is something I'm not sure h
with the
back-end device when it's plugged in.
Thanks,
Mario.
Signed-off-by: Mario Smarduch
---
hw/virtio/virtio-bus.c |5 +
hw/virtio/virtio-mmio.c| 46
include/hw/virtio/virtio-bus.h |4
3 files change
On 02/20/2014 02:47 PM, Peter Maydell wrote:
> On 20 February 2014 22:36, Mario Smarduch wrote:
>> On 02/20/2014 02:10 PM, Peter Maydell wrote:
>>> On 20 February 2014 21:59, Mario Smarduch wrote:
>>>> On 02/20/2014 11:35 AM, Peter Maydell wrote:
>>>>&
On 02/20/2014 02:10 PM, Peter Maydell wrote:
> On 20 February 2014 21:59, Mario Smarduch wrote:
>> On 02/20/2014 11:35 AM, Peter Maydell wrote:
>>> On 20 February 2014 19:09, Mario Smarduch wrote:
>>>> host features since you don't know what virtio device will
On 02/20/2014 11:35 AM, Peter Maydell wrote:
> On 20 February 2014 19:09, Mario Smarduch wrote:
>> host features since you don't know what virtio device will be plugged
>> in later.
>
> I think this function is the right place to set these properties,
> yes. What I
;s instantiated. I think the proper way would
be to refactor virtio-mmio to similar structure PCI version uses then
one virtio_net_properties[] can be used selecting PCI or virtio-mmio at
compile time. But right now it's unclear to me how pci and virtio-mmio
versions intend to co-exist. I'm
e
of qemu, especially virtio stuff.
- Mario
On 02/14/2014 03:49 PM, Peter Maydell wrote:
> CCing the virtio maintainers.
>
> thanks
> -- PMM
>
> On 13 February 2014 21:13, Mario Smarduch wrote:
>> virtio: set virtio-net/virtio-mmio host features
>>
>> Patch s
write to VIRTIO_PCI_QUEUE_NUM.
You might be able to try something like that adjusting max value.
- Mario
virtio: set virtio-net/virtio-mmio host features
Patch sets 'virtio-net/virtio-mmio' host features to enable network
features based on peer capabilities. Currently host features turn
of all features by default.
Signed-off-by: Mario Smarduch
---
hw/virtio/virtio-mmi
ier but at the time 'virtio-mmio'
is created the device to be plugged in is unknown.
Signed-off-by: Mario Smarduch
---
hw/virtio/virtio-mmio.c | 29 +
1 file changed, 29 insertions(+)
diff --git a/hw/virtio/virtio-mmio.c b/hw/virtio/virtio-mmio.c
index 882
: off
tx-vlan-offload: off
ntuple-filters: off
receive-hashing: off
Debugview logs are attached end are always the same (now with debug level
set to 4)
Please tell me how I can further give information. The issue is very
annoying.
Mario
2013-12-12 ing. Mario De Chenno :
> Hi all, it happe
will have some debug data to report to the list. In the
meantime if you have some configuration advises, feel free to post them.
Thanks,
Mario
2013/11/24 Yan Vugenfirer
> Hi Mario,
>
> Can you check the offload settings of the tap device that is connected to
> guest?
>
> Run “
Hi all.
We are facing some network issues on some Windows Server 2003 machines.
In short, network seems to lock up and stops responding even to ping
requests. From TCPdump on the tap interface on the server I only see arp
request to the gateway, without replies. Increased tx overruns on the some
in
-k it -usbdevice tablet -name solari -daemonize
We tried also the following options without result
,vhost=off,vnet_hdr=on
,ioeventfd=on,event_idx=off
How can we troubleshoot the issue?
Thanks
Mario De Chenno
0x76c2ed6b in start_thread () from /lib64/libpthread.so.0
#6 0x76966abd in clone () from /lib64/libc.so.6
See you again
Mario
-Messaggio originale-
Da: Stefan Hajnoczi [mailto:stefa...@gmail.com]
Inviato: mer 18/09/2013 14.50
A: Mario DE CHENNO
Cc: qemu-devel@nongnu.org
ut.
Let me know If I can help.
Mario
-
sendmsg(8, {msg_name(0)=NULL,
msg_iov(1)=[{"gDf\230\0\0\0\0\30\325\243\203\0\210\377\377", 16}],
msg_controllen=0, msg_flags=0}, 0) = 16
write(4, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=8, events=POLLIN|POLL
vhdx are transparent to
qemu-img?
Regards,
Mario
can I do it?
I have configured the guest with virt-manager.
Thanks you very much in advance.
Mario
It could be possible to add a sort of "ifname=" option to the
qemu-bridge-helper program, so qemu could give a recognizable name to
the tap interface the helper creates?
Thanks all,
Mairo De Chenno
tests and what other infos you need.
Ciao!
--
Mario 'Reliant' Pascucci
http://ilpettegolo.altervista.org/
Chiacchiera con i tuoi amici in tempo reale!
http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
___
Qemu-devel mailing
mu including the snapshot from 29.03. and all without kqemu). No matter
if you specify a hd or not (for the boot.lvm test).
The tests are ok on AMD Athlon64 and AMD Opteron machines.
Are there any more information needed?
Mario.
___
Qemu-deve
Hi,
i have some trouble with qemu-system-x86_64. Neither SuSE92-64 nor Ubuntu
5.10-64 will install.
Here my env:
Host OS: SuSE10 (i586)
Kernel: 2.6.13-15.8-smp
qemu: snapshot20060315 (without kqemu )
./configure --prefix=/usr --cc=/opt/gcc33/bin/gcc-3.3
--interp-prefix=/usr/share/qemu/qemu-%M
Am Montag, 13. März 2006 10:19 schrieb Jens Axboe:
> On Mon, Mar 13 2006, Mario Goppold wrote:
> > Am Samstag, 11. März 2006 13:31 schrieb Jens Axboe:
> > > On Fri, Mar 10 2006, Mario Goppold wrote:
> > > > Hi,
> > > >
> > > >
Am Samstag, 11. März 2006 13:31 schrieb Jens Axboe:
> On Fri, Mar 10 2006, Mario Goppold wrote:
> > Hi,
> >
> > I try to install SuSE92-64 on an 400G HD but it fails:
> >
> > hda: max request size: 128KiB
> > hda: cannot use LBA48 - full capacity 838860800
p,vlan=0 \
-hda test.img -cdrom /dev/dvd -boot d
If I reduce the image-size it won't better.
Yust now I try it without "-smp 2" and see what I want "unkown partition
table ..."
So my question is : Is lba48 not smp save or is smp support broken (or
incomplete)?
Hi Lace,
see my thread "32bit emulation in x86_64 System emulation" (27.10.2005).
perhaps it helps you too.
bye,
Mario.
Am Donnerstag, 15. Dezember 2005 08:56 schrieb Jan Kratochvil:
> Hi,
>
> I could not find anywhere - is the current QEMU CVS snapshot GNU/Linux
> x8
ldconfig
Mario.
Am Donnerstag, 27. Oktober 2005 08:37 schrieb Mario Goppold:
> Hi list,
>
> I've tried to install SuSE92 x68_64 as guest (qemu 0.7.2 with and without
> kqemu). During the install grub terminates with core. But not only grub
> terminates:
>
> #include
>
installation).
And again, any suggestions?
Mario
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
Today I found out that the output of nm and ldd for both are identical. The
binaries are exchangeable. In other words the compiler produces the same
output. And here are the diffs between the strace calls (as attachment).
What else can I do? Any suggestions?
Mario
Am Donnerstag, 27
$1
/sbin/ifconfig $1 0.0.0.0 promisc up
fi
) >> /var/log/qemu-ifup.log 2>&1
This adds the tun? devices to qbridge. You can communicate form host to guest
and between the guests but you MUST set the mac-sdress at the commandline:
qemu -macaddr 00:01:01:01:01:01 -hda /localho
time i've found out that's not (only) a SuSE problem:
SuSE92, SuSE93, SuSE10, FC4 fails but Ubuntu 5.10 works fine (all in x86_64).
Have anyone see this behaviour. What can i do?
Mario
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http:
80 matches
Mail list logo
