search for: vmstate

...need to do for this is move host_features out > from transports into core virtio device. > > Then we can simply check host features >31 and skip > migrating low guest features is none set. > > Thoughts? Any takers? > After we move host_features, put them into an optional vmstate subsection? I think with the recent patchsets, most of the interesting stuff is already not handled by the transport anymore. There's only VIRTIO_F_NOTIFY_ON_EMPTY and VIRTIO_F_BAD_FEATURE left (set by pci and ccw).

...need to do for this is move host_features out > from transports into core virtio device. > > Then we can simply check host features >31 and skip > migrating low guest features is none set. > > Thoughts? Any takers? > After we move host_features, put them into an optional vmstate subsection? I think with the recent patchsets, most of the interesting stuff is already not handled by the transport anymore. There's only VIRTIO_F_NOTIFY_ON_EMPTY and VIRTIO_F_BAD_FEATURE left (set by pci and ccw).

...tio device. > > > > > > Then we can simply check host features >31 and skip > > > migrating low guest features is none set. > > > > > > Thoughts? Any takers? > > > > > > > After we move host_features, put them into an optional vmstate > > subsection? > > > > I think with the recent patchsets, most of the interesting stuff is > > already not handled by the transport anymore. There's only > > VIRTIO_F_NOTIFY_ON_EMPTY and VIRTIO_F_BAD_FEATURE left (set by pci and > > ccw). notify on empty i...

...tio device. > > > > > > Then we can simply check host features >31 and skip > > > migrating low guest features is none set. > > > > > > Thoughts? Any takers? > > > > > > > After we move host_features, put them into an optional vmstate > > subsection? > > > > I think with the recent patchsets, most of the interesting stuff is > > already not handled by the transport anymore. There's only > > VIRTIO_F_NOTIFY_ON_EMPTY and VIRTIO_F_BAD_FEATURE left (set by pci and > > ccw). notify on empty i...

I'm new to NUT, but didn't find a clear answer to this either in the recent "ordered shutdown" thread or in Google: How to shut down VMWare guest virtual machines earlier than the host machine they run on? (For example, if everything normally shuts down at 5% UPS battery, then the VMs should shut down at 10%.) I also read upssched.txt but I can't tell from the early

...> > from transports into core virtio device. > > > > Then we can simply check host features >31 and skip > > migrating low guest features is none set. > > > > Thoughts? Any takers? > > > > After we move host_features, put them into an optional vmstate > subsection? > > I think with the recent patchsets, most of the interesting stuff is > already not handled by the transport anymore. There's only > VIRTIO_F_NOTIFY_ON_EMPTY and VIRTIO_F_BAD_FEATURE left (set by pci and > ccw). Thinking a bit more, we probably don't need...

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

On Wed, 06 May 2015 14:07:37 +0200 Greg Kurz <gkurz at linux.vnet.ibm.com> wrote: > Unlike with add and clear, there is no valid reason to abort when checking > for a feature. It makes more sense to return false (i.e. the feature bit > isn't set). This is exactly what __virtio_has_feature() does if fbit >= 32. > > This allows to introduce code that is aware about new

On Wed, 06 May 2015 14:07:37 +0200 Greg Kurz <gkurz at linux.vnet.ibm.com> wrote: > Unlike with add and clear, there is no valid reason to abort when checking > for a feature. It makes more sense to return false (i.e. the feature bit > isn't set). This is exactly what __virtio_has_feature() does if fbit >= 32. > > This allows to introduce code that is aware about new

We'd like to propose a scheme to attach "operand bundles" to call and invoke instructions. This is based on the offline discussion mentioned in http://lists.cs.uiuc.edu/pipermail/llvmdev/2015-July/088748.html. # Motivation & Definition Our motivation behind this is to track the state required for deoptimization (described briefly later) through the LLVM pipeline as a

Hi all, this is the long awaited patch series to add xen device model support in qemu; the main author is Anthony Perard. Developing this series we tried to come up with the cleanest possible solution from the qemu point of view, limiting the amount of changes to common code as much as possible. The end result still requires a couple of hooks in piix_pci but overall the impact should be very