search for: loadvm

..., this is not expected to >> work. > > Hi David, thanks for getting back to us on this. Hi Florian, (sombeody please correct me if I'm wrong) > > I see your point, except the issue Kashyap and I are describing does > not occur with live migration, it occurs with savevm/loadvm (virsh > managedsave/virsh start in libvirt terms, nova suspend/resume in > OpenStack lingo). And it's not immediately self-evident that the > limitations for the former also apply to the latter. Even for the live > migration limitation, I've been unsuccessful at finding documen...

...s on that. :) Indeed. nesting is nice to enable as it works in 99% of all cases. It just doesn't work when trying to migrate a nested hypervisor. (on x86) That's what most people don't realize, as it works "just fine" for 99% of all use cases. [...] >> >> savevm/loadvm is not expected to work correctly on an L1 if it is >> running L2 guests. It should work on L2 however. > > Again, I'm somewhat struggling to understand this vs. live migration — > but it's entirely possible that I'm sorely lacking in my knowledge of > kernel and CPU...

...screwed up after migration, resulting in L1 crashes. > > In addition, certain VMX features might be missing on the target, which > also still has to be handled via the CPU model in the future. Thanks a bunch for the added detail. Now I got a primer today from Kashyap on IRC on how savevm/loadvm is very similar to migration, but I'm still struggling to wrap my head around it. What you say makes perfect sense to me in that _migration_ might blow up in subtle ways, but can you try to explain to me why the same considerations would apply with savevm/loadvm? > L0, should hopefully not...

..., Feb 8, 2018 at 2:47 PM, David Hildenbrand <david@redhat.com> wrote: >> Again, I'm somewhat struggling to understand this vs. live migration — >> but it's entirely possible that I'm sorely lacking in my knowledge of >> kernel and CPU internals. > > (savevm/loadvm is also called "migration to file") > > When we migrate to a file, it really is the same migration stream. You > "dump" the VM state into a file, instead of sending it over to another > (running) target. > > Once you load your VM state from that file, it is a c...

Hi, Is anyone clear about the format of qemu file for savevm or loadvm? bruce

On 07.02.2018 16:31, Kashyap Chamarthy wrote: > [Cc: KVM upstream list.] > > On Tue, Feb 06, 2018 at 04:11:46PM +0100, Florian Haas wrote: >> Hi everyone, >> >> I hope this is the correct list to discuss this issue; please feel >> free to redirect me otherwise. >> >> I have a nested virtualization setup that looks as follows: >> >> - Host:

...reset the VMs without having to reboot them (booting is > rather slow). > > I practice I'll probably have ~16 instances at the same time. > Constantly being reset to the same state. > I tried with QEMU, and it's seems totally doable with savevm, copy > file, then doing loadvm twice in parallel. > (I'll be using a separate network for each VM, so I can be sure which > one I'm talking to). Well, as long as they're completely isolated from each other, you may have a better chance of success. However there will still be the issue of the IP address of t...

...t for nested VMX yet. So as > soon as your guest is using VMX itself ("nVMX"), this is not expected to > work. Hi David, thanks for getting back to us on this. I see your point, except the issue Kashyap and I are describing does not occur with live migration, it occurs with savevm/loadvm (virsh managedsave/virsh start in libvirt terms, nova suspend/resume in OpenStack lingo). And it's not immediately self-evident that the limitations for the former also apply to the latter. Even for the live migration limitation, I've been unsuccessful at finding documentation that warns us...

...9;', ''-usbdevice'', ''tablet'', ''-net'', ''nic,vlan=1,macaddr=00:50:56:00:00:36,model=rtl8139'', ''-net'', ''tap,vlan=1,bridge=xenbr'', ''-M'', ''xenfv'', ''-loadvm'', ''/var/lib/xen/qemu-save.186''] [2008-05-07 22:40:35 3314] INFO (image:293) device model pid: 27287 [2008-05-07 22:40:35 3314] DEBUG (XendDomainInfo:1008) Storing domain details: {''console/port'': ''3'', ''name'': ''...

...(booting is >>> rather slow). >>> >>> I practice I'll probably have ~16 instances at the same time. Constantly >>> being reset to the same state. >>> I tried with QEMU, and it's seems totally doable with savevm, copy file, >>> then doing loadvm twice in parallel. >>> (I'll be using a separate network for each VM, so I can be sure which one >>> I'm talking to). >>> >> >> Well, as long as they're completely isolated from each other, you may have >> a better chance of success. However...

On Mon, Apr 18, 2016 at 10:05:02PM +0300, Michael Ravits wrote: >Hi Jonas, > >I asked a similar question here last week. You could find it by searching >for this topic in the mailing list archives: "Clone VM with saved state". >That being said I'd be very glad if you could update here when you find a >complete solution. > >- Michael > What I *think* Jones

...e[1024]; void *ioport_opaque[MAX_IOPORTS]; @@ -121,6 +123,7 @@ int bios_size; static DisplayState display_state; int nographic; +int vncviewer; const char* keyboard_layout = NULL; int64_t ticks_per_sec; int boot_device = ''c''; @@ -4801,6 +4804,7 @@ #endif "-loadvm file start right away with a saved state (loadvm in monitor)\n" "-vnc display start a VNC server on display\n" + "-vncviewer start a vncviewer process for this domain\n" "-timeoffset time offset (in seconds) from local time\n"...

..., 'dc', '-localtime', '-serial', 'pty', '-acpi', '-usbdevice', 'tablet', '- net', 'nic,vlan=1,macaddr=00:16:3e:64:bd:33,model=rtl8139', '-net', 'tap,vlan=1,bridge=xenbr0', '-M', 'xenfv', '-loadvm', '/var/lib/xen/qemu-save.6', '-vncviewer'] That path is not a part of any configuration, but hard-coded at several points under /usr/lib/xen-3.2-1 : lib/python/xen/xend/XendCheckpoint.py:115: if os.path.exists("/ var/lib/xen/qemu-save.%d" % dominfo.getDom...

...t having to reboot them (booting is >> rather slow). >> >> I practice I'll probably have ~16 instances at the same time. Constantly >> being reset to the same state. >> I tried with QEMU, and it's seems totally doable with savevm, copy file, >> then doing loadvm twice in parallel. >> (I'll be using a separate network for each VM, so I can be sure which one >> I'm talking to). >> > > Well, as long as they're completely isolated from each other, you may have > a better chance of success. However there will still be the...

...m the same state. This way I can reset the VMs without having to reboot them (booting is rather slow). I practice I'll probably have ~16 instances at the same time. Constantly being reset to the same state. I tried with QEMU, and it's seems totally doable with savevm, copy file, then doing loadvm twice in parallel. (I'll be using a separate network for each VM, so I can be sure which one I'm talking to). Is this doable with libvirt, or am I better off using QEMU directly? and how? I couldn't do internal snapshots with --live, and snapshot-revert says it can't revert to exte...

...> rather slow). >>>> >>>> I practice I'll probably have ~16 instances at the same time. Constantly >>>> being reset to the same state. >>>> I tried with QEMU, and it's seems totally doable with savevm, copy file, >>>> then doing loadvm twice in parallel. >>>> (I'll be using a separate network for each VM, so I can be sure which >>>> one >>>> I'm talking to). >>>> >>>> >>> Well, as long as they're completely isolated from each other, you may >>&...

...create domain using xen hypercalls, bypassing xend warning: should not be used when xend is in use -xen-attach attach to existing xen domain xend will use this when starting QEMU -no-reboot exit instead of rebooting -no-shutdown stop before shutdown -loadvm [tag|id] start right away with a saved state (loadvm in monitor) -daemonize daemonize QEMU after initializing -option-rom rom load a file, rom, into the option ROM space -clock force the use of the given methods for timer alarm. To see what timers are a...

Hi guys, I am new to QEMU-KVM, libvmi and libvirt stuff. Libvmi uses libvirt. I am trying to to run process-list example of libvmi and getting error as below. It seems that this error may be due to libvirt as it is not able to find domain. I seek your kind help on below error: spanhal1@seclab2:~/KVMModule/libvmi-0.10.1$ sudo ./examples/process-list ubuntu libvir: QEMU error : Domain not found:

...', ''-vcpus'', ''1'', ''-boot'', ''c'', ''-acpi'', ''-domain-name'', ''WinXP'', ''-vncunused'', ''-vnclisten'', ''0.0.0.0'', ''-loadvm'', ''/tmp/xen.qemu-dm.5''] [2007-10-19 18:02:58 10530] INFO (__init__:1094) device model pid: 12885 [2007-10-19 18:02:58 10530] DEBUG (__init__:1094) Storing domain details: {''console/port'': ''3'', ''name'': ''WinXP...

Hello all, Here is a new iteration of the patch series that implements a transport for guest and host communications. The code has been updated to reuse the virtio-console device instead of creating a new virtio-serial device. I've tested for compatibility (old qemu & new kernel, new qemu & old kernel, new qemu & new kernel) and it all works fine. There are a few items on my