Re: base format

On Thu, Apr 25, 2024 at 02:51:28PM +0200, lacsaP Patatetom wrote: > > > when using `qemu-img create`, why do I have to specify the > > > format of the base image ? can't `qemu-img` detect it itself ? > > > > Image format detection isn't 100% reliable. Notably, a 'raw' > > format image could in

Re: Can "throttle-group"(added by "object-add") be lively updated through QMP cmd?

On Tue, Jan 16, 2024 at 09:37:48AM +, Chun Feng Wu wrote: > * Is there any reason QEMU doesn’t provide QMP cmd like > “object-set” to update object? You can use qom-set for throttle-group, here's a simple example: https://github.com/qemu/qemu/blob/v8.2.0/tests/qemu-iotests/184#L108

Re: Directory does not fit in FAT16 (capacity 516.06 MB)

On Fri, Dec 15, 2023 at 09:15:22AM +0100, lacsaP Patatetom wrote: > here's a little script following the exchanges above. > perhaps it will be useful to others... If you want a full disk image with its partition table I don't know if you are aware that those tools can work with offsets, e.g.:

Re: Directory does not fit in FAT16 (capacity 516.06 MB)

On Wed, Dec 13, 2023 at 04:33:00PM +0100, lacsaP Patatetom wrote: > having said that, and if you respect the constraints ("what you > should never do..."), vvfat is a really nice way of performing and > repeating quick tests without having to go through the process of > building/creating/updating

Re: Directory does not fit in FAT16 (capacity 516.06 MB)

On Wed, Dec 13, 2023 at 01:27:49PM +0100, Narcis Garcia wrote: > A FAT16 partition (0x06) can be as large as 2 GiB That's why I say that there's probably a limitation in the QEMU vvfat driver. Berto

Re: Directory does not fit in FAT16 (capacity 516.06 MB)

On Wed, Dec 13, 2023 at 11:46:51AM +0100, lacsaP Patatetom wrote: > to quickly test my efi application `./esp/EFI/BOOT/BOOTX64.EFI`, I use the > following command `qemu-system-x86_64 -accel kvm -machine q35 -m 1024 -bios > /usr/share/edk2/x64/OVMF.fd -hda fat:./esp/ -snapshot` but it has recently

Re: swap

For non-Spanish speakers: he's asking about how memory swapping works on a VM. I'm answering his question and telling him to use English on this mailing list, or write me directly to continue using Spanish. Answer in Spanish below: Hola Pablo, esta es una lista de correo en inglés. Si necesitas

Re: Is it normal to get bigger qcow2 image after blockcopy?

On Tue, Nov 07, 2023 at 05:32:22PM +0800, Han Han wrote: > >>> Before blockcopy, check source image: ❓ > >>> > >> # qemu-img info -U > >>> /var/lib/avocado/data/avocado-vt/images/jeos-27-x86_64.qcow2 ❓ > >>> > >> > > Was this a compressed qcow2 image when you started? maybe you started with

Re: Performance Discrepancies and Limitations in Local Storage IOPS Testing

On Thu, Aug 24, 2023 at 12:29:43PM +0200, Jan Wasilewski wrote: > Ultimately, I discovered that the performance is significantly > enhanced when the hypervisor is deployed on top of Ubuntu > 22.04LTS. Under this setup, I was able to achieve around 100,000 > IOPS during my fio tests [1][2]. In

Re: Reopen qcow2 backing file from new location

On Fri, Jun 23, 2023 at 11:50:10AM +0200, Stanislav Datskevych wrote: > Unfortunately, change-backing-file only changes the string in the > image's metadata and doesn't cause QEMU to reopen it on the running > VM. So in order to fully migrate VM to its new storage, the VM must > be stopped and

Re: Using blockdev-mirror for Live Backup

On Wed, May 24, 2023 at 06:35:02PM +0330, Ali Gholami Rudi wrote: > If I prepare a patch, do you think it would be merged? I cannot say because I'm not working on the project at the moment, if you have an idea for an improvement I suggest that you write to the qemu-block mailing list describing

Re: Using blockdev-mirror for Live Backup

On Tue, May 16, 2023 at 11:58:30PM +0330, aliqr...@gmail.com wrote: > We are executing hundreds of VMs in our hosts (dual AMD EPYC 7002 > CPUs + 2TB memory + 8 NVMe disks). To cope with disk failures, we > tried different Linux software RAID mechanisms. At high disk usage, > all of them faced

Re: dropping 32-bit host support

On Fri, Mar 17, 2023 at 11:03:51AM +0300, Andrew Randrianasulu wrote: > To be honest after sleeping over problem I found situation beyond > ridiculous. In the course of this thread you have had some of the most active and knowledgeable QEMU developers explain you in a very reasonable way the

Re: Windows 98 ISO does not boot

On Wed, Jan 11, 2023 at 12:03:53PM +0100, timothylegg wrote: > I went to https://winworldpc.com/product/windows-98/98-second-edition and From that page: " Important: Only the OEM Full version is bootable. All others require an appropriate Windows 98 Boot Floppy. " Berto

Re: Detecting swapped images in backing chain via qemu-img

On Thu, Nov 24, 2022 at 01:04:17PM +0200, Plamen Dimitrov wrote: > I apologize in advance if I am missing something obvious but if I > have a backing chain like > > A <- B <- C > > and for some reason B is swapped with another very similar B layer, > can qemu-img detect this in some way? If

Re: how to use blockdev-add in hmp console

On Tue, Feb 22, 2022 at 07:13:24PM +0800, Jiatong Shen wrote: > I am reading > https://qemu.readthedocs.io/en/latest/interop/live-block-operations.html > and try to learn blockdev-add command. I boot a virtual machine with > -nographic option and entered hmp interactive console. but when I

Re: How to use SHA256 in a QEMU device

On Fri, Nov 20, 2020 at 09:33:18PM +, Weiss, Howard wrote: > I am writing a device which uses SHA256 [...] > I have tried > > #include You don't have to use openssl, QEMU already provides those algorithms, see include/crypto/hash.h Berto

Re: Purpose of stacking block devices

On Wed, Oct 21, 2020 at 08:23:17AM +0200, Raphael Pour wrote: > could someone explain me the purpose of stacking block devices on > top of each other? > > A block device with driver file or qcow2 "is usually" stacked on top of > a block device with driver raw as stated in the docs[1]. One of

Re: Large qcow2 performance

On Tue, Sep 24, 2019 at 02:45:10PM -0500, Andrew Martin wrote: > Hi Berto, > > Thank you for the detailed explanation! It is also worth noting that > I am planning on hosting this qcow2 on a ZFS dataset (and ZFS does > some in-memory caching with the ARC as well); does that have an > impact on

Re: Large qcow2 performance

On Mon, Sep 23, 2019 at 03:17:39PM -0500, Andrew Martin wrote: > I am considering creating a VM with a large qcow2, around 6TB in > size. This Linux VM will be reading and writing a lot of small > files to this very large qcow2 using the VirtIO driver. Are there > any concerns or guidance about

Re: [Qemu-discuss] Monitor mode with -display curses

On Tue, Aug 21, 2018 at 09:17:39PM +0200, Vincenzo Romano wrote: > But I would then get "just" the monitor. Not the console. > I need both. > Thanks anyway. I'm not sure if I'm following you... if you have '-display curses' you'll already have the guest console on the terminal emulator where

Re: [Qemu-discuss] Monitor mode with -display curses

On Mon, Aug 20, 2018 at 06:15:21PM +0200, Vincenzo Romano wrote: > Is there a way to get to the monitor commands when using the option > "-display curses"? Yes, you can use a socket, e.g: $QEMU -monitor unix:path=/path/to/socket,server,nowait and to connect to it: socat

Re: [Qemu-discuss]  qcow2 performanceimprove 

On Fri, Aug 17, 2018 at 10:28:49AM +0800, yang.bi...@zte.com.cn wrote: > > > > If there is no backing file or snapshot you still need to fill > > > > the cluster with zeroes, and that's going to be slower with > > > > larger clusters. > > > If not fill zeroes and only write guest data ,what`s

Re: [Qemu-discuss]  qcow2 performance improve 

On Thu 16 Aug 2018 10:20:12 AM CEST, yang.bi...@zte.com.cn wrote: >>If there is no backing file or snapshot you still need to fill the >>cluster with zeroes, and that's going to be slower with larger >>clusters. > > If not fill zeroes and only write guest data ,what`s wrong could > happen

Re: [Qemu-discuss] vga through qemu in arm

On Mon, May 14, 2018 at 02:40:42PM +0800, lizhuoyao wrote: > hi everyone: > currently, I meet a problem about qemu.Use virt-install order to create a > domain, return a failed: > order: virt-install -n centos-gg -r 1024 --disk > centos-gg.img,format=qcow2,size=10 --cdrom >

Re: [Qemu-discuss] QEMU make error

On Fri 27 Oct 2017 02:46:54 AM CEST, Akiv Jhirad wrote: > When running make in the qemu build, I get the error: > > /home/rtems/pc_rtems/qemu/replay/replay-internal.c: In function > 'replay_put_array': > > /home/rtems/pc_rtems/qemu/replay/replay-internal.c:65:15: error: > >

Re: [Qemu-discuss] QEMU caching modes

On Fri, Mar 17, 2017 at 09:52:27PM +0100, Jan Schermer wrote: > I'm trying to understand when/what IO is synchronous and why, and so > far what I'm seeing I can only describe as "weird". > > With cache=none, all IO should pass from the QEMU process to the device > as-is. Right? Here's the

Re: [Qemu-discuss] [Qemu-devel] Estimation of qcow2 image size converted from raw image

On Wed 15 Feb 2017 04:57:12 PM CET, Nir Soffer wrote: >>> Let's try this syntax: >>> >>> $ qemu-img query-max-size -f raw -O qcow2 input.raw >>> 1234678000 >>> >>> As John explained, it is only an estimate. But it will be a >>> conservative maximum. >> >> This forces you to have an input

Re: [Qemu-discuss] VGA choices

On Wed, Feb 01, 2017 at 01:25:17PM +0100, Vincenzo Romano wrote: > I've tried to start a previously created VM (running Ubuntu Server > 16.04) with just " -nographic -curses" as far as the console is > concerned. > So, no "-vga" and no "-vnc" option. And no -daemonize of course. > The PTY shows

Re: [Qemu-discuss] WinXP Guest: New hardware found - VGA controller

On Thu, Jan 26, 2017 at 12:18:53AM +0100, Joe wrote: > Anyway the issue was related to a misunderstanding of qemu man page: > > -vga type >Select type of VGA card to emulate. Valid values for type are > >cirrus >Cirrus Logic GD5446 Video card. All

Re: [Qemu-discuss] Multiple snapshots with one guest user

On Wed, Jan 25, 2017 at 04:16:22PM +0100, Gianni Costanzi wrote: > > > what's the purpose of specifying the size when you're creating > > > an image with a backing file? Is it simply ignored? > > > > The (virtual) sizes of the new image and the backing image can be > > different. If you don't

Re: [Qemu-discuss] Multiple snapshots with one guest user

On Wed, Jan 25, 2017 at 11:23:01AM +0100, Gianni Costanzi wrote: > what's the purpose of specifying the size when you're creating an > image with a backing file? Is it simply ignored? The (virtual) sizes of the new image and the backing image can be different. If you don't specify anything then

Re: [Qemu-discuss] Info about compressed images

On Fri, Jan 13, 2017 at 06:57:53PM +0100, Gianni Costanzi wrote: > Hi, > I'm new here and I've started using QEMU when I've started playing > with Unetlab/EVE Network simulator. > > I have some questions about compression and images with a compressed > backing file: I think there's some

Re: [Qemu-discuss] WinXP Guest: New hardware found - VGA controller

On Mon, Jan 23, 2017 at 01:00:26AM +0100, Joe wrote: > I'm trying Qemu (2.8.0) on Slackware GNU Linux 14.2 (64-bit) host. > I've a Windows XP (guest) raw image which was working with Qemu > times ago (I used it on an older Slackware version as host system). The default hardware emulated by QEMU

Re: [Qemu-discuss] Throttle in virtio-net

On Mon 05 Sep 2016 10:52:40 AM CEST, Pradeep Kiruvale wrote: >> > I am planning to implement throttling functionality for virtio-net >> > driver using the throttling APIs that exist inside qemu. >> >> the problem with implementing throttling for the network is that >> it's useless if you use the

Re: [Qemu-discuss] Throttle in virtio-net

On Fri, Sep 02, 2016 at 05:13:40PM +0200, Pradeep Kiruvale wrote: > I am planning to implement throttling functionality for virtio-net > driver using the throttling APIs that exist inside qemu. Hi Pradeep, the problem with implementing throttling for the network is that it's useless if you use

Re: [Qemu-discuss] SSD tuning

On Mon, Aug 08, 2016 at 04:12:06PM +, Tim Bell wrote: > Any suggestions for how to tune KVM for SSDs on the hypervisor ? > We’re seeing a significant drop (50%) of IOPS for random write > from guest to host. If you're using qcow2, you are doing random I/O and you have a sufficiently big

Re: [Qemu-discuss] [Qemu-devel] iolimits for virtio-9p

On Fri 06 May 2016 09:39:13 AM CEST, Pradeep Kiruvale wrote: >> The throttling API is currently only used by block devices, and the >> only documentation out-there is the code itself... > > Thanks, I will have a look and get back to you if I have any further > questions regarding this. As I said

Re: [Qemu-discuss] iolimits for virtio-9p

On Wed, Apr 27, 2016 at 09:29:02AM +0200, Pradeep Kiruvale wrote: > Thanks for the reply. I am still in the early phase, I will let you > know if any changes are needed for the APIs. > > We might also have to implement throttle-group.c for 9p devices, if > we want to apply throttle for group of

Re: [Qemu-discuss] iolimits for virtio-9p

On Tue 19 Apr 2016 02:09:24 PM CEST, Pradeep Kiruvale wrote: > We are planning to implement the io-limits for the virtio-9p driver > i.e for fsdev devices. > So, I am looking into the code base and how it has done for the block > io devices. > > I would like to know how difficult is this and is

Re: [Qemu-discuss] Cannot start qemu because of gtk version issue

On Tue, Mar 22, 2016 at 04:05:37PM +0800, Cao jin wrote: > Hi, > > I configured as following: > ./configure --target-list=x86_64-softmmu --enable-debug > > when run qemu, got following error: > (qemu-system-x86_64:3561): Gtk-ERROR **: GTK+ 2.x symbols detected. Using > GTK+ 2.x and GTK+ 3 in the

Re: [Qemu-discuss] about block_stream

On Mon, Mar 30, 2015 at 11:26:03AM +0800, yang.bi...@zte.com.cn wrote: Can block_stream merge any node to its direct leaf Or any other alternative? Thanks! I'm currently working on a patch that would allow block_stream to write to any intermediate layer: