Re: [pve-devel] backup RFC preview
Hi, I'm trying to build qemu with your patchs (I'm a bit late,I didn't have time last week) I have errors on missing glib.h, softfloat.h, but files exists /root/qemu/fpu/softfloat.h /usr/include/glib-2.0/glib.h any idea ? maybe some missing envvars ? #./configure --prefix=/usr --datadir=/usr/share --docdir=/usr/share/doc/pve-qemu-kvm --sysconfdir=/etc --disable-xen --enable-vnc-tls --enable-sdl --enable-uuid --enable-linux-aio --enable-rbd --enable-libiscsi --audio-drv-list=alsa # make gcc -O2 -D_FORTIFY_SOURCE=2 -g -Wl,--warn-common -Wl,-z,relro -Wl,-z,now -pie -m64 -g vma.c -o vma vma.c:22:18: error: glib.h: No such file or directory In file included from qemu-common.h:125, from vma.c:24: bswap.h:7:23: error: softfloat.h: No such file or directory In file included from qemu-common.h:125, from vma.c:24: bswap.h:242: error: expected specifier-qualifier-list before ‘float32’ bswap.h:247: error: expected specifier-qualifier-list before ‘float64’ bswap.h:263: error: expected specifier-qualifier-list before ‘floatx80’ bswap.h:271: error: expected specifier-qualifier-list before ‘float128’ bswap.h:502: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘ldfl_le_p’ bswap.h:507: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘ldfq_le_p’ bswap.h:512: error: expected declaration specifiers or ‘...’ before ‘float32’ bswap.h: In function ‘stfl_le_p’: bswap.h:514: error: ‘float32’ undeclared (first use in this function) bswap.h:514: error: (Each undeclared identifier is reported only once bswap.h:514: error: for each function it appears in.) bswap.h:514: error: expected expression before ‘)’ token bswap.h: At top level: bswap.h:517: error: expected declaration specifiers or ‘...’ before ‘float64’ bswap.h: In function ‘stfq_le_p’: bswap.h:519: error: ‘float64’ undeclared (first use in this function) bswap.h:519: error: expected expression before ‘)’ token bswap.h: At top level: bswap.h:616: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘ldfl_be_p’ bswap.h:626: error: expected declaration specifiers or ‘...’ before ‘float32’ bswap.h: In function ‘stfl_be_p’: bswap.h:629: error: expected specifier-qualifier-list before ‘float32’ bswap.h:632: error: ‘union anonymous’ has no member named ‘f’ bswap.h:632: error: ‘v’ undeclared (first use in this function) bswap.h:633: error: ‘union anonymous’ has no member named ‘i’ bswap.h: At top level: bswap.h:636: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘ldfq_be_p’ bswap.h:644: error: expected declaration specifiers or ‘...’ before ‘float64’ bswap.h: In function ‘stfq_be_p’: bswap.h:647: error: ‘CPU_DoubleU’ has no member named ‘d’ bswap.h:647: error: ‘v’ undeclared (first use in this function) bswap.h:648: error: ‘CPU_DoubleU’ has no member named ‘l’ bswap.h:649: error: ‘CPU_DoubleU’ has no member named ‘l’ In file included from main-loop.h:28, from qemu-timer.h:5, from sysemu.h:8, from vma.c:28: qemu-aio.h: At top level: qemu-aio.h:47: error: expected specifier-qualifier-list before ‘GSource’ qemu-aio.h:229: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token In file included from vma.c:31: vma.h:115: error: expected declaration specifiers or ‘...’ before ‘gpointer’ vma.h:131: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token vma.h:132: error: expected declaration specifiers or ‘...’ before ‘guint8’ vma.h:133: error: expected declaration specifiers or ‘...’ before ‘guint8’ vma.c: In function ‘extract_devname’: vma.c:54: warning: assignment makes pointer from integer without a cast vma.c:58: warning: assignment makes pointer from integer without a cast vma.c: In function ‘print_content’: vma.c:75: error: ‘GList’ undeclared (first use in this function) vma.c:75: error: ‘l’ undeclared (first use in this function) vma.c:85: error: too many arguments to function ‘vma_reader_get_device_info’ vma.c: In function ‘extract_content’: vma.c:180: error: ‘GList’ undeclared (first use in this function) vma.c:180: error: ‘l’ undeclared (first use in this function) vma.c:184: warning: initialization makes pointer from integer without a cast vma.c:185: error: ‘GError’ undeclared (first use in this function) vma.c:185: error: ‘err’ undeclared (first use in this function) vma.c:186: error: ‘gchar’ undeclared (first use in this function) vma.c:186: error: expected expression before ‘)’ token vma.c:191: error: ‘GHashTable’ undeclared (first use in this function) vma.c:191: error: ‘devmap’ undeclared (first use in this function) vma.c:191: error: ‘g_str_hash’ undeclared (first use in this function) vma.c:191: error: ‘g_str_equal’ undeclared (first use in this function) vma.c:231: error: expected expression before ‘RestoreMap’ vma.c:232: warning: assignment makes pointer from integer without a cast vma.c:233: warning: assignment makes pointer from integer without a cast vma.c:243:
Re: [pve-devel] backup RFC preview
Just sent an updated version - does that work better? -Original Message- From: Alexandre DERUMIER [mailto:aderum...@odiso.com] Sent: Montag, 19. November 2012 12:24 To: Dietmar Maurer Cc: pve-devel@pve.proxmox.com Subject: Re: [pve-devel] backup RFC preview Does it help when you specify the correct target-list (else it tries to build all targets) ./configure --target-list x86_64-softmmu ... Doesn't help, but I have found the problem, I have a part of the patch which doesn't apply ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] backup RFC preview
Just sent an updated version - does that work better? no :/ Last qemu git: I got Hunk Failed on Makefile root@kvmtest1:~/qemu2/qemu# patch -p1 patch1.patch patching file docs/backup-rfc.txt root@kvmtest1:~/qemu2/qemu# patch -p1 patch2.patch patching file Makefile.objs Hunk #1 succeeded at 48 (offset 4 lines). patching file backup.c patching file block.c patching file block.h patching file block_int.h root@kvmtest1:~/qemu2/qemu# patch -p1 patch3.patch patching file Makefile Hunk #2 FAILED at 186. 1 out of 2 hunks FAILED -- saving rejects to file Makefile.rej patching file docs/specs/vma_spec.txt patching file vma-reader.c patching file vma-writer.c patching file vma.c patching file vma.h root@kvmtest1:~/qemu2/qemu# patch -p1 patch4.patch patching file Makefile Hunk #1 FAILED at 186. 1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej patching file Makefile.objs Hunk #1 succeeded at 48 (offset 4 lines). patching file blockdev.c patching file hmp-commands.hx patching file hmp.c patching file hmp.h patching file monitor.c patching file qapi-schema.json patching file qmp-commands.hx root@kvmtest1:~/qemu2/qemu# patch -p1 patch5.patch patching file include/qemu/ratelimit.h patching file tests/Makefile patching file tests/backup-test.c After manually add to Makefile +vma$(EXESUF): vma.o vma-reader.o $(tools-obj-y) $(block-obj-y) I get same error: #./configure --target-list=x86_64-softmmu --prefix=/usr --datadir=/usr/share --docdir=/usr/share/doc/pve-qemu-kvm --sysconfdir=/etc --disable-xen # make CCasync.o CCnbd.o CCblock.o CCblockjob.o CCaes.o CCqemu-config.o CCthread-pool.o CCqemu-progress.o CCuri.o CCnotify.o CCvma-writer.o CCbackup.o CCqemu-coroutine.o CCqemu-coroutine-lock.o CCqemu-coroutine-io.o CCqemu-coroutine-sleep.o CCcoroutine-ucontext.o CCevent_notifier-posix.o CCaio-posix.o CCblock/raw.o CCblock/cow.o CCblock/qcow.o CCblock/vdi.o CCblock/vmdk.o CCblock/cloop.o CCblock/dmg.o CCblock/bochs.o CCblock/vpc.o CCblock/vvfat.o CCblock/qcow2.o CCblock/qcow2-refcount.o CCblock/qcow2-cluster.o CCblock/qcow2-snapshot.o CCblock/qcow2-cache.o CCblock/qed.o CCblock/qed-gencb.o CCblock/qed-l2-cache.o CCblock/qed-table.o CCblock/qed-cluster.o CCblock/qed-check.o CCblock/parallels.o CCblock/blkdebug.o CCblock/blkverify.o CCblock/raw-posix.o CCblock/linux-aio.o CCblock/nbd.o CCblock/sheepdog.o CCblock/iscsi.o CCblock/curl.o CCblock/rbd.o LINK qemu-nbd GEN qemu-img-cmds.h CCqemu-img.o LINK qemu-img CCqemu-io.o CCcmd.o LINK qemu-io CCfsdev/virtfs-proxy-helper.o CCfsdev/virtio-9p-marshal.o LINK fsdev/virtfs-proxy-helper CCvma.o CCvma-reader.o LINK vma osdep.o: In function `qemu_close': /root/qemu2/qemu/osdep.c:212: undefined reference to `monitor_fdset_dup_fd_find' /root/qemu2/qemu/osdep.c:218: undefined reference to `monitor_fdset_dup_fd_remove' osdep.o: In function `qemu_open': /root/qemu2/qemu/osdep.c:166: undefined reference to `monitor_fdset_get_fd' /root/qemu2/qemu/osdep.c:176: undefined reference to `monitor_fdset_dup_fd_add' qemu-sockets.o: In function `socket_connect': /root/qemu2/qemu/qemu-sockets.c:906: undefined reference to `monitor_get_fd' qemu-sockets.o: In function `socket_listen': /root/qemu2/qemu/qemu-sockets.c:937: undefined reference to `monitor_get_fd' collect2: ld returned 1 exit status make: *** [vma] Error 1 note : patch3 add: +vma$(EXESUF): vma.o vma-writer.o vma-reader.o $(tools-obj-y) $(block-obj-y) and patch 4: -vma$(EXESUF): vma.o vma-writer.o vma-reader.o $(tools-obj-y) $(block-obj-y) +vma$(EXESUF): vma.o vma-reader.o $(tools-obj-y) $(block-obj-y) - Mail original - De: Dietmar Maurer diet...@proxmox.com À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com Envoyé: Lundi 19 Novembre 2012 12:30:23 Objet: RE: [pve-devel] backup RFC preview Just sent an updated version - does that work better? -Original Message- From: Alexandre DERUMIER [mailto:aderum...@odiso.com] Sent: Montag, 19. November 2012 12:24 To: Dietmar Maurer Cc: pve-devel@pve.proxmox.com Subject: Re: [pve-devel] backup RFC preview Does it help when you specify the correct target-list (else it tries to build all targets) ./configure --target-list x86_64-softmmu ... Doesn't help, but I have found the problem, I have a part of the patch which doesn't apply ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] backup RFC preview
My patches are against commit 6801038bc52d61f81ac8a25fbe392f1bad982887 Try to use that commit. Maybe I should expose my internal qemu-git tree? -Original Message- From: Alexandre DERUMIER [mailto:aderum...@odiso.com] Sent: Montag, 19. November 2012 13:33 To: Dietmar Maurer Cc: pve-devel@pve.proxmox.com Subject: Re: [pve-devel] backup RFC preview Just sent an updated version - does that work better? no :/ Last qemu git: I got Hunk Failed on Makefile root@kvmtest1:~/qemu2/qemu# patch -p1 patch1.patch patching file docs/backup-rfc.txt root@kvmtest1:~/qemu2/qemu# patch -p1 patch2.patch patching file Makefile.objs Hunk #1 succeeded at 48 (offset 4 lines). patching file backup.c patching file block.c patching file block.h patching file block_int.h root@kvmtest1:~/qemu2/qemu# patch -p1 patch3.patch patching file Makefile Hunk #2 FAILED at 186. 1 out of 2 hunks FAILED -- saving rejects to file Makefile.rej patching file docs/specs/vma_spec.txt patching file vma-reader.c patching file vma- writer.c patching file vma.c patching file vma.h root@kvmtest1:~/qemu2/qemu# patch -p1 patch4.patch patching file Makefile Hunk #1 FAILED at 186. 1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej patching file Makefile.objs Hunk #1 succeeded at 48 (offset 4 lines). patching file blockdev.c patching file hmp-commands.hx patching file hmp.c patching file hmp.h patching file monitor.c patching file qapi-schema.json patching file qmp-commands.hx root@kvmtest1:~/qemu2/qemu# patch -p1 patch5.patch patching file include/qemu/ratelimit.h patching file tests/Makefile patching file tests/backup-test.c After manually add to Makefile +vma$(EXESUF): vma.o vma-reader.o $(tools-obj-y) $(block-obj-y) I get same error: #./configure --target-list=x86_64-softmmu --prefix=/usr --datadir=/usr/share --docdir=/usr/share/doc/pve-qemu-kvm --sysconfdir=/etc --disable-xen # make CCasync.o CCnbd.o CCblock.o CCblockjob.o CCaes.o CCqemu-config.o CCthread-pool.o CCqemu-progress.o CCuri.o CCnotify.o CCvma-writer.o CCbackup.o CCqemu-coroutine.o CCqemu-coroutine-lock.o CCqemu-coroutine-io.o CCqemu-coroutine-sleep.o CCcoroutine-ucontext.o CCevent_notifier-posix.o CCaio-posix.o CCblock/raw.o CCblock/cow.o CCblock/qcow.o CCblock/vdi.o CCblock/vmdk.o CCblock/cloop.o CCblock/dmg.o CCblock/bochs.o CCblock/vpc.o CCblock/vvfat.o CCblock/qcow2.o CCblock/qcow2-refcount.o CCblock/qcow2-cluster.o CCblock/qcow2-snapshot.o CCblock/qcow2-cache.o CCblock/qed.o CCblock/qed-gencb.o CCblock/qed-l2-cache.o CCblock/qed-table.o CCblock/qed-cluster.o CCblock/qed-check.o CCblock/parallels.o CCblock/blkdebug.o CCblock/blkverify.o CCblock/raw-posix.o CCblock/linux-aio.o CCblock/nbd.o CCblock/sheepdog.o CCblock/iscsi.o CCblock/curl.o CCblock/rbd.o LINK qemu-nbd GEN qemu-img-cmds.h CCqemu-img.o LINK qemu-img CCqemu-io.o CCcmd.o LINK qemu-io CCfsdev/virtfs-proxy-helper.o CCfsdev/virtio-9p-marshal.o LINK fsdev/virtfs-proxy-helper CCvma.o CCvma-reader.o LINK vma osdep.o: In function `qemu_close': /root/qemu2/qemu/osdep.c:212: undefined reference to `monitor_fdset_dup_fd_find' /root/qemu2/qemu/osdep.c:218: undefined reference to `monitor_fdset_dup_fd_remove' osdep.o: In function `qemu_open': /root/qemu2/qemu/osdep.c:166: undefined reference to `monitor_fdset_get_fd' /root/qemu2/qemu/osdep.c:176: undefined reference to `monitor_fdset_dup_fd_add' qemu-sockets.o: In function `socket_connect': /root/qemu2/qemu/qemu-sockets.c:906: undefined reference to `monitor_get_fd' qemu-sockets.o: In function `socket_listen': /root/qemu2/qemu/qemu-sockets.c:937: undefined reference to `monitor_get_fd' collect2: ld returned 1 exit status make: *** [vma] Error 1 note : patch3 add: +vma$(EXESUF): vma.o vma-writer.o vma-reader.o $(tools-obj-y) +$(block-obj-y) and patch 4: -vma$(EXESUF): vma.o vma-writer.o vma-reader.o $(tools-obj-y) $(block-obj- y) +vma$(EXESUF): vma.o vma-reader.o $(tools-obj-y) $(block-obj-y) - Mail original - De: Dietmar Maurer diet...@proxmox.com À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com Envoyé: Lundi 19 Novembre 2012 12:30:23 Objet: RE: [pve-devel] backup RFC preview Just sent an updated version - does that work better? -Original Message- From: Alexandre DERUMIER [mailto:aderum...@odiso.com] Sent: Montag, 19. November 2012 12:24 To: Dietmar Maurer Cc: pve-devel@pve.proxmox.com Subject: Re: [pve-devel] backup RFC preview Does it help when you specify the correct
Re: [pve-devel] backup RFC preview
osdep.o: In function `qemu_close': /root/qemu2/qemu/osdep.c:212: undefined reference to `monitor_fdset_dup_fd_find' /root/qemu2/qemu/osdep.c:218: undefined reference to `monitor_fdset_dup_fd_remove' AFAIK my patches does not touch those files - maybe current qemu build is broken? ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] backup RFC preview
yes, maybe qemu build is broken :/ #git checkout 6801038bc52d61f81ac8a25fbe392f1bad982887 and now, seem to build fine :) - Mail original - De: Dietmar Maurer diet...@proxmox.com À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com Envoyé: Lundi 19 Novembre 2012 13:41:03 Objet: RE: [pve-devel] backup RFC preview osdep.o: In function `qemu_close': /root/qemu2/qemu/osdep.c:212: undefined reference to `monitor_fdset_dup_fd_find' /root/qemu2/qemu/osdep.c:218: undefined reference to `monitor_fdset_dup_fd_remove' AFAIK my patches does not touch those files - maybe current qemu build is broken? ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] backup RFC preview
Maybe I should expose my internal qemu-git tree? Maybe can we add a new qemu 1.3 git in proxmox git ? So we could help to port current pve patches to qemu 1.3 . - Mail original - De: Dietmar Maurer diet...@proxmox.com À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com Envoyé: Lundi 19 Novembre 2012 13:37:54 Objet: RE: [pve-devel] backup RFC preview My patches are against commit 6801038bc52d61f81ac8a25fbe392f1bad982887 Try to use that commit. Maybe I should expose my internal qemu-git tree? -Original Message- From: Alexandre DERUMIER [mailto:aderum...@odiso.com] Sent: Montag, 19. November 2012 13:33 To: Dietmar Maurer Cc: pve-devel@pve.proxmox.com Subject: Re: [pve-devel] backup RFC preview Just sent an updated version - does that work better? no :/ Last qemu git: I got Hunk Failed on Makefile root@kvmtest1:~/qemu2/qemu# patch -p1 patch1.patch patching file docs/backup-rfc.txt root@kvmtest1:~/qemu2/qemu# patch -p1 patch2.patch patching file Makefile.objs Hunk #1 succeeded at 48 (offset 4 lines). patching file backup.c patching file block.c patching file block.h patching file block_int.h root@kvmtest1:~/qemu2/qemu# patch -p1 patch3.patch patching file Makefile Hunk #2 FAILED at 186. 1 out of 2 hunks FAILED -- saving rejects to file Makefile.rej patching file docs/specs/vma_spec.txt patching file vma-reader.c patching file vma- writer.c patching file vma.c patching file vma.h root@kvmtest1:~/qemu2/qemu# patch -p1 patch4.patch patching file Makefile Hunk #1 FAILED at 186. 1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej patching file Makefile.objs Hunk #1 succeeded at 48 (offset 4 lines). patching file blockdev.c patching file hmp-commands.hx patching file hmp.c patching file hmp.h patching file monitor.c patching file qapi-schema.json patching file qmp-commands.hx root@kvmtest1:~/qemu2/qemu# patch -p1 patch5.patch patching file include/qemu/ratelimit.h patching file tests/Makefile patching file tests/backup-test.c After manually add to Makefile +vma$(EXESUF): vma.o vma-reader.o $(tools-obj-y) $(block-obj-y) I get same error: #./configure --target-list=x86_64-softmmu --prefix=/usr --datadir=/usr/share --docdir=/usr/share/doc/pve-qemu-kvm --sysconfdir=/etc --disable-xen # make CC async.o CC nbd.o CC block.o CC blockjob.o CC aes.o CC qemu-config.o CC thread-pool.o CC qemu-progress.o CC uri.o CC notify.o CC vma-writer.o CC backup.o CC qemu-coroutine.o CC qemu-coroutine-lock.o CC qemu-coroutine-io.o CC qemu-coroutine-sleep.o CC coroutine-ucontext.o CC event_notifier-posix.o CC aio-posix.o CC block/raw.o CC block/cow.o CC block/qcow.o CC block/vdi.o CC block/vmdk.o CC block/cloop.o CC block/dmg.o CC block/bochs.o CC block/vpc.o CC block/vvfat.o CC block/qcow2.o CC block/qcow2-refcount.o CC block/qcow2-cluster.o CC block/qcow2-snapshot.o CC block/qcow2-cache.o CC block/qed.o CC block/qed-gencb.o CC block/qed-l2-cache.o CC block/qed-table.o CC block/qed-cluster.o CC block/qed-check.o CC block/parallels.o CC block/blkdebug.o CC block/blkverify.o CC block/raw-posix.o CC block/linux-aio.o CC block/nbd.o CC block/sheepdog.o CC block/iscsi.o CC block/curl.o CC block/rbd.o LINK qemu-nbd GEN qemu-img-cmds.h CC qemu-img.o LINK qemu-img CC qemu-io.o CC cmd.o LINK qemu-io CC fsdev/virtfs-proxy-helper.o CC fsdev/virtio-9p-marshal.o LINK fsdev/virtfs-proxy-helper CC vma.o CC vma-reader.o LINK vma osdep.o: In function `qemu_close': /root/qemu2/qemu/osdep.c:212: undefined reference to `monitor_fdset_dup_fd_find' /root/qemu2/qemu/osdep.c:218: undefined reference to `monitor_fdset_dup_fd_remove' osdep.o: In function `qemu_open': /root/qemu2/qemu/osdep.c:166: undefined reference to `monitor_fdset_get_fd' /root/qemu2/qemu/osdep.c:176: undefined reference to `monitor_fdset_dup_fd_add' qemu-sockets.o: In function `socket_connect': /root/qemu2/qemu/qemu-sockets.c:906: undefined reference to `monitor_get_fd' qemu-sockets.o: In function `socket_listen': /root/qemu2/qemu/qemu-sockets.c:937: undefined reference to `monitor_get_fd' collect2: ld returned 1 exit status make: *** [vma] Error 1 note : patch3 add: +vma$(EXESUF): vma.o vma-writer.o vma-reader.o $(tools-obj-y) +$(block-obj-y) and patch 4: -vma$(EXESUF): vma.o vma-writer.o vma-reader.o $(tools-obj-y) $(block-obj- y) +vma$(EXESUF): vma.o vma-reader.o $(tools-obj-y) $(block-obj-y) - Mail original - De: Dietmar Maurer diet...@proxmox.com À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com Envoyé: Lundi 19 Novembre 2012 12:30:23 Objet: RE: [pve-devel] backup RFC preview Just sent an updated version - does that work better? -Original Message- From
Re: [pve-devel] backup RFC preview
I can't get network working in qemu (virtio,e1000)... and I can't get vnc working. (I have make change in pve-auth.patch to get it apply correctly). Any idea ? - Mail original - De: Alexandre DERUMIER aderum...@odiso.com À: Stefan Priebe - Profihost AG s.pri...@profihost.ag Cc: pve-devel@pve.proxmox.com Envoyé: Lundi 19 Novembre 2012 15:08:48 Objet: Re: [pve-devel] backup RFC preview Mhm with -monitor the qm monitor shell stuff doesn't work I always get the failure that qmp human interface cannot be found. I can get it work in pve gui, with renaming qemu-system-x86_64 to kvm I have also apply patch: pve-auth.patch - Mail original - De: Stefan Priebe - Profihost AG s.pri...@profihost.ag À: Dietmar Maurer diet...@proxmox.com Cc: pve-devel@pve.proxmox.com Envoyé: Dimanche 18 Novembre 2012 07:52:16 Objet: Re: [pve-devel] backup RFC preview Am 18.11.2012 um 07:31 schrieb Dietmar Maurer diet...@proxmox.com: # ./x86_64-softmmu/qemu-system-x86_64 -monitor stdio -enable-kvm - hda image.raw ... you meant -qmp not monitor? no Mhm with -monitor the qm monitor shell stuff doesn't work I always get the failure that qmp human interface cannot be found. Stefan ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] backup RFC preview
# ./x86_64-softmmu/qemu-system-x86_64 -monitor stdio -enable-kvm - hda image.raw ... you meant -qmp not monitor? no Mhm with -monitor the qm monitor shell stuff doesn't work I always get the failure that qmp human interface cannot be found. Sure, this does not work with 'qm'. The idea is to use that for testing only, and it is simple convenient to read monitor commands from 'stdin' (you can also see debugging output there). ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] backup RFC preview
Am 18.11.2012 10:28, schrieb Dietmar Maurer: # ./x86_64-softmmu/qemu-system-x86_64 -monitor stdio -enable-kvm - hda image.raw ... you meant -qmp not monitor? no Mhm with -monitor the qm monitor shell stuff doesn't work I always get the failure that qmp human interface cannot be found. Sure, this does not work with 'qm'. The idea is to use that for testing only, and it is simple convenient to read monitor commands from 'stdin' (you can also see debugging output there). mhm OK i wanted to try your patches on a half prod. system and i need the monitor to workprobably. But i wasn't able to get it running stable with qemu.git. Stefan ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] backup RFC preview
Am 18.11.2012 um 07:31 schrieb Dietmar Maurer diet...@proxmox.com: # ./x86_64-softmmu/qemu-system-x86_64 -monitor stdio -enable-kvm - hda image.raw ... you meant -qmp not monitor? no Mhm with -monitor the qm monitor shell stuff doesn't work I always get the failure that qmp human interface cannot be found. Stefan ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] backup RFC preview
How can i test? Command line qm command? # git clone git://git.qemu-project.org/qemu.git then apply the patches. # cd qemu # ./configure --target-list=x86_64-softmmu # make You can then start qemu with something like that: # ./x86_64-softmmu/qemu-system-x86_64 -monitor stdio -enable-kvm -hda image.raw ... Are you going to use qemu instead qemu-kvm for 1.3 release ? (I have read that kvm will be finally officily merged in qemu for 1.3) - Mail original - De: Dietmar Maurer diet...@proxmox.com À: Stefan Priebe - Profihost AG s.pri...@profihost.ag Cc: pve-devel@pve.proxmox.com Envoyé: Mercredi 14 Novembre 2012 07:18:36 Objet: Re: [pve-devel] backup RFC preview How can i test? Command line qm command? # git clone git://git.qemu-project.org/qemu.git then apply the patches. # cd qemu # ./configure --target-list=x86_64-softmmu # make You can then start qemu with something like that: # ./x86_64-softmmu/qemu-system-x86_64 -monitor stdio -enable-kvm -hda image.raw ... ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] backup RFC preview
Are you going to use qemu instead qemu-kvm for 1.3 release ? (I have read that kvm will be finally officily merged in qemu for 1.3) Only if they announce that qemu-kvm is obsolete. I currently use qemu for the backup tests because it is required to send patches against qemu. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] backup RFC preview
I currently use qemu for the backup tests because it is required to send patches against qemu. Oh, you want to push patches upstream ? Great ! - Mail original - De: Dietmar Maurer diet...@proxmox.com À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com, Stefan Priebe - Profihost AG s.pri...@profihost.ag Envoyé: Mercredi 14 Novembre 2012 16:41:29 Objet: RE: [pve-devel] backup RFC preview Are you going to use qemu instead qemu-kvm for 1.3 release ? (I have read that kvm will be finally officily merged in qemu for 1.3) Only if they announce that qemu-kvm is obsolete. I currently use qemu for the backup tests because it is required to send patches against qemu. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] backup RFC preview
I currently use qemu for the backup tests because it is required to send patches against qemu. Oh, you want to push patches upstream ? Great ! Yes, that is the plan. It would be great if we can get at least the basic framework upstream (PATCH 2/4). Else we should think twice if we can maintain that ourselves. Usually it is a pain to get such things upstream, and that is why I posted it here first to get your opinions. So please tell me: - if anything is unclear - should I add further docs - any ideas for cleanups - anything else which helps to get it upsrteam ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] backup RFC preview
Ok, I'm not sure I have the skill to understand all the code, but I'll begin tests today and tomorrow, and I'll try to make a report next week. - Mail original - De: Dietmar Maurer diet...@proxmox.com À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com, Stefan Priebe - Profihost AG s.pri...@profihost.ag Envoyé: Mercredi 14 Novembre 2012 18:31:30 Objet: RE: [pve-devel] backup RFC preview I currently use qemu for the backup tests because it is required to send patches against qemu. Oh, you want to push patches upstream ? Great ! Yes, that is the plan. It would be great if we can get at least the basic framework upstream (PATCH 2/4). Else we should think twice if we can maintain that ourselves. Usually it is a pain to get such things upstream, and that is why I posted it here first to get your opinions. So please tell me: - if anything is unclear - should I add further docs - any ideas for cleanups - anything else which helps to get it upsrteam ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] backup RFC preview
Thanks Dietmar, I'll try to do a feedback tomorrow ! - Mail original - De: Dietmar Maurer diet...@proxmox.com À: pve-devel@pve.proxmox.com Envoyé: Mardi 13 Novembre 2012 14:04:02 Objet: [pve-devel] backup RFC preview This is a preview of the planed backup feature. The following patches are against latest qemu.git I plan to send the patch to the qemu-devel list next week. Before I do that, I would like to get some feedback about: * functionality * implementation style * possible improvements Feel free to ask questions ;-) - Dietmar ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] backup RFC preview
Am 13.11.2012 14:04, schrieb Dietmar Maurer: This is a preview of the planed backup feature. The following patches are against latest qemu.git I plan to send the patch to the qemu-devel list next week. Before I do that, I would like to get some feedback about: * functionality * implementation style * possible improvements Feel free to ask questions ;-) So this is right now only for qcow / disk based backups? Or a general solution? How can i test? Command line qm command? Greets, Stefan ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] backup RFC preview
So this is right now only for qcow / disk based backups? Or a general solution? I do not know what you mean by 'general' solution? But it does not depend on qcow2, instead it works on any storage type and file format. How can i test? Command line qm command? Please use the qemu monitor command: # backup filename ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
