Re: "Instant clone" with Qemu?

Hello Stefan, Am 15.12.23 um 16:21 schrieb Stefan Hajnoczi: Am 05.12.23 um 15:44 schrieb Stefan Hajnoczi: On Tue, 5 Dec 2023 at 04:53, Philipp Hahn wrote: > by accident I stumbled over "VMware Instant Clone" ¹, which allows cloning of running VMs by copy-on-write-sharing th

Re: "Instant clone" with Qemu?

Hello Stefan, thank you for your kind reply. Am 05.12.23 um 15:44 schrieb Stefan Hajnoczi: On Tue, 5 Dec 2023 at 04:53, Philipp Hahn wrote: > by accident I stumbled over "VMware Instant Clone" ¹, which allows cloning of running VMs by copy-on-write-sharing the disk images and m

"Instant clone" with Qemu?

to allow running flaky tests multiple times from a clean clone again ¹<https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-853B1E2B-76CE-4240-A654-3806912820EB.html> -- Philipp Hahn Open Source Software Engineer Univention GmbH Mary-Somerville-Str. 1 2835

Re: VNC clipboard support

Hello, Am 29.04.23 um 17:29 schrieb octavef...@outlook.fr: I'm trying to use the copy/paste with VNC. I'm launching qemu with: $ qemu-system-x86_64 -hda debiandisk.img vnc :1 I'm using tightvncviewer which has support for copy/paste. I try to copy text between guest and host. It doesn't

Re: [Qemu-devel] storing machine data in qcow images?

Hi, Am 18.05.2018 um 17:30 schrieb Michael S. Tsirkin: > Unfortunately this means that it's no longer possible > to more or less reliably boot a VM just given a disk image, > even if you select the correct QEMU binary: ... > Would it be reasonable to support storing this information in the qcow >

Re: [Qemu-devel] [PATCH 1/2] docs: Add image locking subsection

Hello, Am 23.11.2017 um 14:59 schrieb Fam Zheng: > diff --git a/docs/qemu-block-drivers.texi b/docs/qemu-block-drivers.texi > index 1cb1e55686..fa2e90d15f 100644 > --- a/docs/qemu-block-drivers.texi > +++ b/docs/qemu-block-drivers.texi > @@ -785,6 +785,42 @@ warning: ssh server

Re: [Qemu-devel] [libvirt] How to best handle the reoccurring of rom changes breaking cross version migrations?

Hello Am 03.11.2017 um 08:30 schrieb Christian Ehrhardt: > On Thu, Nov 2, 2017 at 4:34 PM, Daniel P. Berrange > wrote: >> >> On Thu, Nov 02, 2017 at 04:14:06PM +0100, Christian Ehrhardt wrote: >>> Ping - since there wasn't any reply so far - any best practices one could >>>

Re: [Qemu-devel] Why got no response of vnc?

Hello, Am 25.08.2017 um 08:31 schrieb Sam: > I'm starting vm using: > > kvm]$ sudo /usr/local/bin/qemu-system-x86_64 -m 256 -hda test.qcow2 -cdrom >> CentOS-7-x86_64-DVD-1503-01.iso -boot d >> VNC server running on '127.0.0.1:5900' ^ This a a *local* host

Re: [Qemu-devel] RFH: difference in read-only mapped bios.bin - memory corruption?

Hello, Am 15.08.2017 um 13:25 schrieb Laszlo Ersek: > On 08/14/17 20:39, Dr. David Alan Gilbert wrote: >> * Philipp Hahn (h...@univention.de) wrote: >>> I'm currently investigating a problem, were a Linux VM does not reboot >>> and gets stuck in the SeaBIOS reboot code

[Qemu-devel] RFH: difference in read-only mapped bios.bin - memory corruption?

03940.html>, which I "solved" by upgrading the OVMF version: I have not seen the problem there since than, but this problems looks very similar. 1. How can it be, that the low-mem ROM mapping is modified? 2. Can I tell QEMU or gdb to trap any modification of that 128 KiB area? I'll try t

Re: [Qemu-devel] [PATCH 01/11] qemu.py: Pylint/style fixes

Hi, Am 20.07.2017 um 18:28 schrieb Lukáš Doktor: > --- a/scripts/qemu.py > +++ b/scripts/qemu.py ... > @@ -64,16 +79,16 @@ class QEMUMachine(object): > if self._socket_scm_helper is None: > print >>sys.stderr, "No path to socket_scm_helper set" > return -1 > -

Re: [Qemu-devel] [RFH] qemu-2.6 memory corruption with OVMF and linux-4.9

Hello, Am 18.06.2017 um 20:22 schrieb Philipp Hahn: > Am 17.06.2017 um 18:51 schrieb Laszlo Ersek: >> (I also recommend using the "vbindiff" tool for such problems, it is >> great for picking out patterns.) >> >> ** ** ** **

Re: [Qemu-devel] [RFH] qemu-2.6 memory corruption with OVMF and linux-4.9

Am 18.06.2017 um 20:27 schrieb Dr. David Alan Gilbert: > * Philipp Hahn (h...@univention.de) wrote: >> Hello, >> >> Am 17.06.2017 um 18:51 schrieb Laszlo Ersek: >>> (I also recommend using the "vbindiff" tool for such problems,

Re: [Qemu-devel] [RFH] qemu-2.6 memory corruption with OVMF and linux-4.9

Hello, Am 17.06.2017 um 18:51 schrieb Laszlo Ersek: > (I also recommend using the "vbindiff" tool for such problems, it is > great for picking out patterns.) > > ** ** ** ** ** ** ** ** 8 9 ** ** ** 13 14 15 > -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 01

[Qemu-devel] [RFH] qemu-2.6 memory corruption with OVMF and linux-4.9

1:0 -device > cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device > intel-hda,id=sound0,bus=pci.0,addr=0x4 -device > hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device > virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -global > isa-debugcon.iobase=0x402 -debugcon file:/tmp/

Re: [Qemu-devel] [PATCH 1/2] acpi_piix4: fix migration of gpe fields

Hello Marcelo, Am 21.03.2017 um 00:20 schrieb Marcelo Tosatti: > On Mon, Mar 20, 2017 at 01:02:10PM +0100, Philipp Hahn wrote: >> Hello Marcelo, cc:qemu, >> >> Sorry for re-using this old thread, but I have a problem loading some >> saved state from qemu-kvm-1.1.

Re: [Qemu-devel] [PATCH 1/2] acpi_piix4: fix migration of gpe fields

ivention.de> From: Philipp Hahn <h...@univention.de> Date: Mon, 20 Mar 2017 12:36:53 +0100 Subject: [PATCH 2/2] 0007-Bug-38877-fix-qemu-kvm-1.1-piix4_pm-incompatibility Organization: Univention GmbH, Bremen, Germany To: qemu-devel@nongnu.org qemu-kvm-1.1 only saves 2*uint16, but qemu-2

[Qemu-devel] RFC: Qemu/SeaBIOS/VGA/PXE upgrades vs. longterm-snapshot/migration

s) 3. How do others handle long-term snapshots? Just say "good-bye" to your old snapshots when upgrading to a newer Qemu version or keeping the old, probably unmaintained and vulnerable Qemu/BIOS binaries until the end-of-time? Thanks in advance Philipp -- Philipp Hahn Open Source Soft

[Qemu-devel] virnet: page allocation failure: order:0

Hello, this Sunday one of our virtual servers running linux-4.1.16 inside OpenStack using qemu "crashed" while doing a backup using rsync to a slow NFS server. Crash here means that the server became unresponsive to network traffic: - it was no longer able to contact the two LDAP servers - no ssh

Re: [Qemu-devel] [libvirt] [PATCH v2 3/8] Add support for fetching statistics of completed jobs

uot;active", it is a json-object with the > following RAM information (in bytes): but the example some lines below is wrong: > 2. Migration is done and has succeeded > > -> { "execute": "query-migrate" } > <- { "return": { > "st

Re: [Qemu-devel] how to setup a watchdog?

Hi, Am 18.01.2016 um 12:43 schrieb lejeczek: > I'm trying Qemu's watchdog. > My understanding was that hardware (here qemu's watchdog) would take > action, eg. cold reboot the system if there is no ping from the OS > watchdog, so I > thought stopping watchdog service in VM should be a quick test,

Re: [Qemu-devel] VirtIO windows driver: viostor.sys not post-installable

Hello, On 31.05.2015 12:58, Vadim Rozenfeld wrote: On Sun, 2015-05-31 at 11:26 +0300, Yan Vugenfirer wrote: On May 29, 2015, at 5:43 PM, Philipp Hahn h...@univention.de wrote: ... we tried to migrate some Windows 2008 and 2012 VMs from Xen to KVM, but installing the VirtIO viostor.sys

[Qemu-devel] VirtIO windows driver: viostor.sys not post-installable

data, just ask. Thanks in advance Philipp Hahn PS: data was copied by hand from Windows, so it might contains copy-paste-errors. -- Philipp Hahn Open Source Software Engineer Univention GmbH be open. Mary-Somerville-Str. 1 D-28359 Bremen Tel.: +49 421 22232-0 Fax : +49 421 22232-99 h

Re: [Qemu-devel] [PATCH v10] Support vhd type VHD_DIFFERENCING

Hello, On 11.03.2015 07:22, Xiaodong Gong wrote: Hope that clarified things. ... first，your patch is very clear，a good sample. store ascii code in kernel that I said before is a mistake，I mean the glibc need the input of arguments of fuction such as fopen（path）is ascii code No: ASCII =

Re: [Qemu-devel] [PATCH v10] Support vhd type VHD_DIFFERENCING

Hello, On 08.03.2015 02:53, Xiaodong Gong wrote: the encoding type of parent location is must be utf 8，utf16e，according to the draft Yes, the SPEC for VPC/VHD specifies the character encoding to use, which is good for being portable. ascii is the encoding type to store the string of parent

Re: [Qemu-devel] [PATCH v10] Support vhd type VHD_DIFFERENCING

Hi, On 04.03.2015 15:18, Xiaodong Gong wrote: @@ -157,6 +178,224 @@ static int vpc_probe(const uint8_t *buf, int buf_size, const char *filename) .. +static int vpc_decode_maxc_loc(BlockDriverState *bs, uint32_t data_length) ... +cd = g_iconv_open(ASCII, UTF8); ... +static int

[Qemu-devel] [PATCH v2] hw/dma/i8257: Silence phony error message

Convert into trace event. Otherwise the message dma: unregistered DMA channel used nchan=0 dma_pos=0 dma_len=1 gets printed every time and fills up the log-file with 50 MiB / minute. Signed-off-by: Philipp Hahn h...@univention.de --- v2: Convert into trace event instead of tracking

[Qemu-devel] [PATCH] hw/dma: Print error message only once

otherwise the message dma: unregistered DMA channel used nchan=0 dma_pos=0 dma_len=1 gets printed every time and fills up the log-file with 50 MiB / minute. Signed-off-by: Philipp Hahn h...@univention.de --- hw/dma/i8257.c | 10 -- 1 file changed, 8 insertions(+), 2 deletions

Re: [Qemu-devel] [PATCH v2] Support vhd type VHD_DIFFERENCING

Hello, I'm no qemu-devel expert, but as I tried myself at adding VHD_DIFF support some time ago, here are some comments: On 08.09.2014 16:41, Xiaodong Gong wrote: diff --git a/block/vpc.c b/block/vpc.c ... +/* Read backing file location from dyn header table */ +if

Re: [Qemu-devel] Differential VHD

Hello, On 15.05.2014 13:54, Ankur Srivastava wrote: What all steps to be taken for differential vhd image? i created one differential image using vhd-util Last time I checked it it wass not implemented in QEMU. I started working on it in my spare time, but never completed it. Sincerely

[Qemu-devel] [BUG] 50MB/min logspam: dma: unregistered DMA channel used nchan=0 dma_pos=0 dma_len=1

/* qemu_get_8s (f, d-status); */ 1. Might it be that 'status' is uninitialized after migration? 2. Has someone other seen that message? 3. Could the rate of the message please be limited? See attached patch. 4. Some other ideas or comments? Sincerely Philipp -- Philipp Hahn Open Source Software Engineer

[Qemu-devel] VHD suport in QEMU?

then. Sincerely Philipp -- Philipp Hahn Open Source Software Engineer h...@univention.de Univention GmbHbe open. fon: +49 421 22 232- 0 Mary-Somerville-Str.1 D-28359 Bremen fax: +49 421 22 232-99

Re: [Qemu-devel] Qemu Boot failure with /dev/ram0

to be large enougth to contain the uncompressed file-system. If the size is too small, you will have a corrupt FS where you also get the error you mention above. Sincerely Philipp -- Philipp Hahn Open Source Software Engineer h...@univention.de Univention GmbHbe open

[Qemu-devel] backing file support for vpc/vhd ?

) tools/blktap2/vhd/vhd-update.c: BSD (3 clause) tools/blktap2/vhd/vhd-util.c: BSD (3 clause) Is the lack of support for backing files in vpc/vjd in qemu just a question of time / interest, are there technical problems, or are there some political issues? Sincerely Philipp -- Philipp Hahn

[Qemu-devel] RFH: boot from virtio cdrom?

on when Linux is installed, the CDROM works fine through virtio. Sincerely Philipp -- Philipp Hahn Open Source Software Engineer h...@univention.de Univention GmbHbe open. fon: +49 421 22 232- 0 Mary-Somerville-Str.1 D-28359 Bremen

Re: [Qemu-devel] [PATCH for-1.4 0/2] fix migration failure from 1.3 due to SeaBIOS size change

with the PXE-BIOSs, because Debian provides it's own compilation of etherboot and iPXE. As each upgrade threatens to break all your previous snapshots, would it help to include the BIOSs within the saved state instead of letting qemu pickup the current external file? Sincerely Philipp -- Philipp

[Qemu-devel] [PATCH] vmdk: Allow space in file name

-by: Philipp Hahn h...@univention.de --- block/vmdk.c | 10 +- 1 files changed, 1 insertions(+), 9 deletions(-) [V2] Also remove striping code. Add \n\r to stop character set. diff --git a/block/vmdk.c b/block/vmdk.c index 19298c2..20ad646 100644 --- a/block/vmdk.c +++ b/block/vmdk.c

Re: [Qemu-devel] [BUG, RFC] block/vmdk.c: File name with space fails to open

.vmdk\. That's because you change sscanf() to ignore the double-quotes without dropping the quote stripping code below. I'll remove the stripping code. Care to post a fixed up patch? Will do so. Sincerely Philipp -- Philipp Hahn Open Source Software Engineer h...@univention.de

Re: [Qemu-devel] [PATCH] vmdk: Allow space in file name

Hello, On Tuesday 29 January 2013 22:50:31 Philipp Hahn wrote: The previous scanf() format string stopped parsing the file name on the first white white space, which seems to be allowed at least by VMware Wokrstation. Change the format string to collect everything between the first

[Qemu-devel] [BUG, RFC] block/vmdk.c: File name with space fails to open

. Sincerely Philipp -- Philipp Hahn Open Source Software Engineer h...@univention.de Univention GmbHbe open. fon: +49 421 22 232- 0 Mary-Somerville-Str.1 D-28359 Bremen fax: +49 421 22 232-99

Re: [Qemu-devel] [BUG] qemu-1.1.2 [FIXED-BY] qcow2: Fix avail_sectors in cluster allocation code

Hello Kevin, hello Michael, On Wednesday 12 December 2012 17:54:58 Kevin Wolf wrote: Am 12.12.2012 15:09, schrieb Philipp Hahn: Am Mittwoch 12 Dezember 2012 14:41:49 schrieb Kevin Wolf: As you can see in the commit message of that patch I was convinced that no bug did exist in practice

Re: [Qemu-devel] [BUG] qemu-1.1.2 [FIXED-BY] qcow2: Fix avail_sectors in cluster allocation code

Hello Kevin, On Wednesday 12 December 2012 18:29:48 Philipp Hahn wrote: I just re-run my git bisect run ~/bisect.sh case, but it again arrived at that patch. I just queued another run for tonight so make sure the test is reliable: The run from last night again arrived at the refecenced patch

[Qemu-devel] [BUG] qemu-1.1.2 [FIXED-BY] qcow2: Fix avail_sectors in cluster allocation code

for 1.1. Thanks in advance. Sincerely Philipp -- Philipp Hahn Open Source Software Engineer h...@univention.de Univention GmbHbe open. fon: +49 421 22 232- 0 Mary-Somerville-Str.1 D-28359 Bremen fax: +49 421 22 232-99

Re: [Qemu-devel] [BUG] qemu-1.1.2 [FIXED-BY] qcow2: Fix avail_sectors in cluster allocation code

it: After a reboot the md5sums are still invalid, so I guess the data is corrupted on writeout. Sincerely Philipp -- Philipp Hahn Open Source Software Engineer h...@univention.de Univention GmbHbe open. fon: +49 421 22 232- 0 Mary-Somerville-Str.1 D-28359

Re: [Qemu-devel] [BUG] qemu-1.1.2 [FIXED-BY] qcow2: Fix avail_sectors in cluster allocation code

Hello Kevin, Am Mittwoch 12 Dezember 2012 17:54:58 schrieb Kevin Wolf: Am 12.12.2012 15:09, schrieb Philipp Hahn: Am Mittwoch 12 Dezember 2012 14:41:49 schrieb Kevin Wolf: As you can see in the commit message of that patch I was convinced that no bug did exist in practice and this was only

[Qemu-devel] [BUG?] vvfat vs. pc-1.1 isa-fdc.check_media_rate=off

-- Philipp Hahn Open Source Software Engineer h...@univention.de Univention GmbHbe open. fon: +49 421 22 232- 0 Mary-Somerville-Str.1 D-28359 Bremen fax: +49 421 22 232-99 http

Re: [Qemu-devel] 1.1.1 - 1.1.2 migrate /managedsave issue

an implicit multifinction=off. (https://forge.univention.org/bugzilla/show_bug.cgi?id=22877#c6 in our German BZ) Sincerely Philipp Hahn -- Philipp Hahn Open Source Software Engineer h...@univention.de Univention GmbHbe open. fon: +49 421 22 232- 0 Mary

Re: [Qemu-devel] [PATCH] e1000: Don't set the Capabilities List bit

somebody an idea how to fix this issue? Sincerely Philipp Hahn PS: It would be nice if the error message could indicate an error because of an incompatible PCI configuration. I had a very similar problem with the rtl8139 card, where the ROM size was changed due to the upgrade from etherboot to iPXE

Re: [Qemu-devel] [PATCH] e1000: Don't set the Capabilities List bit

Hello, On Friday 19 October 2012 11:59:24 Philipp Hahn wrote: On Wednesday 21 September 2011 22:06:25 dann frazier wrote: ... -/* TODO: we have no capabilities, so why is this bit set? */ -pci_set_word(pci_conf + PCI_STATUS, PCI_STATUS_CAP_LIST); ... Since cmask[PCI_STATUS=6

[Qemu-devel] [PATCH] Rate limit vnc_write_pixels_generic

Only print the error message once per change and also include the actual unsupported color depth in bytes per pixel in the error message. Signed-off-by: Philipp Hahn h...@univention.de --- ui/vnc.c |8 +++- 1 files changed, 7 insertions(+), 1 deletions(-) diff --git a/ui/vnc.c b/ui

Re: [Qemu-devel] [PATCH] Rate limit vnc_write_pixels_generic

Hello Anthony, Am Montag 07 Mai 2012 16:19:57 schrieb Anthony Liguori: On 05/07/2012 08:58 AM, Philipp Hahn wrote: Only print the error message once per change and also include the actual unsupported color depth in bytes per pixel in the error message. Signed-off-by: Philipp Hahnh

Re: [Qemu-devel] [PATCH 35/46] qemu-iotests: qcow2.py

with future backwards compatible extensions. Cool. I wrote a very similar tool to dump qcow2 data some time ago when I tried to debug a ref-count corruption bug. I'll attach it just FYI. BYtE Philipp -- Philipp Hahn Open Source Software Engineer h...@univention.de Univention GmbH

Re: [Qemu-devel] Keysymbol interpretation missing in QEMU's VNC server?

-- Philipp Hahn Open Source Software Engineer h...@univention.de Univention GmbHLinux for Your Businessfon: +49 421 22 232- 0 Mary-Somerville-Str.1 D-28359 Bremen fax: +49 421 22 232-99 http

Re: [Qemu-devel] [PATCH 3/3] stop the periodic RTC update timer

hypervisor for example (that is the one I have been looking at at the past few hours), which explicitliy waits for the falling edge of UIP to get sub-second precision. This would break if you no longer simulate UIP. Sincerely Philipp -- Philipp Hahn Open Source Software Engineer h

Re: [Qemu-devel] Correct syntax for named snapshots

your have to manage. Deleting one file from the middle of such a chain breaks all following snapshots, so be careful when you do delete files. And yes, both are still supported. Sincerely Philipp -- Philipp Hahn Open Source Software Engineer h...@univention.de Univention GmbH

Re: [Qemu-devel] Question on kvm_clock working ...

the value of /sys/devices/system/clocksource/clocksource0/current_clocksource in your guest. If it is somethong other than kvmclock, you should if using hwclock --hctosys --utc re-synchronizes your guest clock to the host. Sincerely Philipp -- Philipp Hahn Open Source Software

[Qemu-devel] [BUG] Qcow2 corruption on snapshot revert

=e11480db7ff15a9e878f6b3cc1199b439bf7c825 http://git.kernel.org/?p=virt/kvm/qemu-kvm.git;a=commit;h=f0aa7a8b2d518c54430e4382309281b93e51981a http://lists.gnu.org/archive/html/qemu-devel/2011-04/msg01376.html https://forge.univention.org/bugzilla/show_bug.cgi?id=1 Any help is appreciated. Sincerely Philipp Hahn -- Philipp

Re: [Qemu-devel] [PATCH v2 0.15.0] qcow2: Fix L1 table size after bdrv_snapshot_goto

and eventuelly to image corruption. Instead of writing the new L1 size to disk, this simply retains the bigger L1 size that is currently in use and makes sure that the unused part is zeroed. Signed-off-by: Kevin Wolf kw...@redhat.com Tested-by: Philipp Hahn h...@univention.de Philipp, I think

[Qemu-devel] [PATCH] Fix DEBUG_* compilation of qcow2.

By introducing BlockDriverState compiling qcow2 with DEBUG_ALLOC and DEBUG_EXT defined got broken. Define a BdrvCheckResult structure locally which is now needed as the second argument. Also fix qcow2_read_extensions() needing BDRVQcowState. Signed-off-by: Philipp Hahn h...@univention.de

Re: [Qemu-devel] [Request for Help] QEMU 0.15.0 change log

Sincerely Philipp -- Philipp Hahn Open Source Software Engineer h...@univention.de Univention GmbHLinux for Your Businessfon: +49 421 22 232- 0 Mary-Somerville-Str.1 D-28359 Bremen fax: +49 421 22 232

Re: [Qemu-devel] [PATCH 00/13] QED image streaming

have few changed relative to the master, so we don't want the copying to happen there. If haven't looked at QED yet, so thanks in advance for your answer. Sincerely Philipp Hahn -- Philipp Hahn Open Source Software Engineer h...@univention.de Univention GmbHLinux for Your

[Qemu-devel] [BUG] Re: [2/6] loadvm: improve tests before bdrv_snapshot_goto()

be adapted to this new behavior. I found the Bug also reported with Ubuntu and created a Bug in our own German bugtracker: https://bugs.launchpad.net/qemu/+bug/726619 https://forge.univention.org/bugzilla/show_bug.cgi?id=1 Sincerely Philipp Hahn -- Philipp Hahn Open Source Software