search for: kashyapc

Migration without --p2p works just fine, ie. the below works: $ virsh migrate --verbose --copy-storage-all \ --live cvm1 qemu+ssh://kashyapc@devstack3/system Migration: [100 %] Result: - On the source host, the guest is shut off - On the destination host, the guest is live migratied successfully Migration with "--p2p" fails, a simple test below: First, I should note, I didn't modify any settings...

...> -enable-fips \ > -nodefaults \ > -display none \ > -M vexpress-a15 \ > -cpu host \ > -machine accel=kvm:tcg \ > -m 500 \ > -no-reboot \ > -rtc driftfix=slew \ > -global kvm-pit.lost_tick_policy=discard \ > -kernel /home/kashyapc/src/libguestfs/tmp/.guestfs-1000/appliance.d/kernel \ > -dtb /home/kashyapc/src/libguestfs/tmp/.guestfs-1000/appliance.d/dtb \ > -initrd /home/kashyapc/src/libguestfs/tmp/.guestfs-1000/appliance.d/initrd \ > -device virtio-scsi-device,id=scsi \ > -drive file=/home/kashya...

...\ > > -display none \ > > -M vexpress-a15 \ > > -cpu host \ > > -machine accel=kvm:tcg \ > > -m 500 \ > > -no-reboot \ > > -rtc driftfix=slew \ > > -global kvm-pit.lost_tick_policy=discard \ > > -kernel /home/kashyapc/src/libguestfs/tmp/.guestfs-1000/appliance.d/kernel \ > > -dtb /home/kashyapc/src/libguestfs/tmp/.guestfs-1000/appliance.d/dtb \ > > -initrd /home/kashyapc/src/libguestfs/tmp/.guestfs-1000/appliance.d/initrd \ > > -device virtio-scsi-device,id=scsi \ > > -dri...

...> > > > cp pc-bios/optionrom/linuxboot_dma.bin pc-bios/optionrom/ > > I mean: > > cp pc-bios/optionrom/linuxboot_dma.bin pc-bios/ Yep, that did it. Thanks! I see about 1.35 seconds time improvement, with `supermin` from Git + QEMU & the add patch[1]. https://kashyapc.fedorapeople.org/virt/stdouts/faster-supermin-custom-qemu-appliance-boot-analysis.txt This is with `supermin` from F23, and QEMU from Git (without adding the 'optionrom' patch): https://kashyapc.fedorapeople.org/virt/stdouts/supermin-f23-without-add-optionrom-patch-boot-analysis.txt...

Hi, I'm experimenting with the migration function of virsh. I'm doing the migrate with following commands: virsh migrate --life --persistent --copy-storage-all --verbose --abort-on-error domain qemu+ssh://root@destination/system virsh migrate-setmaxdowntime domain 20000 However sometimes at the end of the migration, the guest isn't started on the destination host. So I'm left

...+0200, Kashyap Chamarthy wrote: > On Fri, Apr 03, 2015 at 10:08:21AM +0200, Kashyap Chamarthy wrote: > > Migration without --p2p works just fine, ie. the below works: > > > > > > $ virsh migrate --verbose --copy-storage-all \ > > --live cvm1 qemu+ssh://kashyapc@devstack3/system > > Migration: [100 %] > > > > [. . .] > > > > > (2) Perform peer to peer live migration (as root): > > > > $ virsh migrate --verbose --p2p --copy-storage-all \ > > --live cvm1 qemu+ssh://kashyapc@devstack3/sys...

On Fri, Apr 03, 2015 at 10:08:21AM +0200, Kashyap Chamarthy wrote: > Migration without --p2p works just fine, ie. the below works: > > > $ virsh migrate --verbose --copy-storage-all \ > --live cvm1 qemu+ssh://kashyapc@devstack3/system > Migration: [100 %] > [. . .] > > (2) Perform peer to peer live migration (as root): > > $ virsh migrate --verbose --p2p --copy-storage-all \ > --live cvm1 qemu+ssh://kashyapc@devstack3/system > > error: operation failed: Fail...

...y your guest on destination host doesn't start, but I've previously successfully tested wih qemu+tcp URI and these three variants, without shared storage: (1) Native migration, client to two libvirtd servers $ virsh migrate --verbose --copy-storage-all \ --live cvm1 qemu+tcp://kashyapc@desthost/system (2) Native migration, peer2peer between two libvirtd servers: $ virsh migrate --verbose --copy-storage-all \ --p2p --live cvm1 qemu+tcp://kashyapc@desthost/system (3) Tunnelled migration, peer2peer between two libvirtd servers: $ virsh migrate --verbose --copy...

Hello, I am working on my PhD thesis and it would be really helpfull if someone could advise me, whether can Virsh create snapshots of VMs using copy-on-write. Thanks for reply. Juraj

Hi All I was reading through this: http://kashyapc.com/2011/12/02/little-more-disk-io-perf-improvement-with-fallocateing-a-qcow2-disk/ I was basically searching for pointers on improving disk I/O. I wanted to know the purpose of preallocation=full & preallocation=metadata , What is the difference between them ? and which one would yield a b...

...etting landed into same error. Is there any troubleshooting or solution to this issue. Stuck on this issue for last 2 days. Quick help much appreciated. Thanks, Keyur Bhalerao Reference used - http://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit - http://kashyapc.com/2012/09/14/externaland-live-snapshots-with-libvirt/

I ran into an odd problem today. I wanted to share it here in the hopes of maybe saving someone else some lost time. When you run libvirtd as an unprivileged user (e.g., if you target qemu:///session from a non-root account), then libvirt will open a unix domain socket in one of two places: - If XDG_RUNTIME_DIR is defined, then inside $XDG_RUNTIME_DIR/libvirt/libvirt-sock - If

Hi, I am following the below link to install a Fedora19 guest on Fedora19 Host. http://kashyapc.com/2011/08/18/unattended-guest-install-with-a-local-kickstart/ Version : libvirtd (libvirt) 1.0.5.1, QEMU emulator version 1.4.2, Copyright (c) 2003-2008 Fabrice Bellard I have the iso which I loop mounted and created a http repo using python module "python -m SimpleHTTPServer". Th...

On Mon, Mar 21, 2016 at 02:14:19PM +0100, Kashyap Chamarthy wrote: > I gave this series a spin, along a custom QEMU, and `supermin` from Git, > for my `libguestfs-test-tool` itself fails with: > > "Could not open option rom 'linuxboot_dma.bin': No such file or > directory" The qemu build is broken in some way. To fix it you have to do: cp

Firstly I'd like to learn where a snapshot is stored once it has been made. I understand that the principle is that when changes occur in the VM, the difference is written to the snapshot, thus recording the differences between the date/time of the snapshot and the current value of the VM. Is that a correct assessment of the process? If that is indeed so, can I take regular snapshots and

...sed > during the operation. > > The new qemu feature is called drive-backup > (http://wiki.qemu.org/Features/IncrementalBackup). Unless things > changed recently, it is not exposed through libvirt, so the only way > to use it is by sending qemu monitor commands > ( > http://kashyapc.com/2013/03/31/multiple-ways-to-access-qemu-monitor-protocol-qmp/ > ). > > This is all pretty bleeding edge. I still think you'd be better off > just ignoring snapshots that fail and moving on to the next one. > > Rich. I might be missing something then as the guest is actu...

Hello, I have created an ovs bridge on which i have attached a port. I would like to connect my vm to that port,so i have created an xml defining the network. The xml is: <network> <name>ovs-snort</name> <forward mode='bridge'/> <bridge name='snort'/> <virtualport type='openvswitch'/> </network> but when i do virsh

...py/gentoo-template/gentoo-template.qcow2 the >> snapshot is gone. >> >> Someone has an idea what i'm missing? I suppose i'm just missunderstandig the snapshot >> mechanism. > > Here's how I used blockcopy (few months ago, slightly outdated) -- > http://kashyapc.fedorapeople.org/virt/lc-2012/live-backup-with-blockcopy.txt > > >> >> thanks an best regards >> t. >> >> _______________________________________________ >> libvirt-users mailing list >> libvirt-users@redhat.com >> https://www.redhat.com/mai...

On Sat, Sep 03, 2016 at 02:39:11PM +0800, gunnar.wagner@netcologne.de wrote: > hi all & @Kayshap > > does [this handout on > snapshots](https://kashyapc.fedorapeople.org/virt/lc-2012/snapshots-handout.html) > by Kashyap Chamarthy (I believe from 2012) still apply to current > versions of libvirt-bin & qemu? Yes, as the URL indicates, it's from 2012. And, most of the content there is valid. However, some things have changed, with re...

...istent, point-in-time snapshots (which it > > > sounds like you do), qemu has recently been adding this capability. > > > See the 'drive-backup' monitor command. I've not tried using that > > A small QMP test for 'drive-backup': > > https://kashyapc.fedorapeople.org/virt/test-qmp-drive-backup.txt That's interesting, but even more interesting would be to see drive-backup writing to NBD. >From what I gather, drive-backup would take a nbd:... target, meaning that it is the *client* (not the server). What's interesting is what you...