I did the original work using AFL to fuzz qemu-img and find
problematic images. From that work Dan & I suggested some fairly low
limits (10 seconds IIRC). See:
https://bugs.launchpad.net/qemu/+bug/1462944
https://bugs.launchpad.net/qemu/+bug/1462949
A lot more problematic images were found (at
On Thu, Jul 19, 2018 at 10:24 PM Richard W.M. Jones
wrote:
> On Thu, Jul 19, 2018 at 09:50:00PM +0300, Nir Soffer wrote:
> > On Mon, Jul 16, 2018 at 11:56 AM Daniel P. Berrangé >
> > wrote:
> > ...
> >
> > > Recommendation is to run 'qemu-img info' to extract the metadata and
> sanity
> > >
This is the code in libguestfs if you prefer something in C:
https://github.com/libguestfs/libguestfs/blob/3a87c4bb441430c9cef9223e67d10bf51a4e865c/lib/info.c#L150-L160
https://github.com/libguestfs/libguestfs/blob/3a87c4bb441430c9cef9223e67d10bf51a4e865c/lib/command.c#L585-L600
Rich.
--
On Mon, Jul 16, 2018 at 11:56 AM Daniel P. Berrangé
wrote:
...
> Recommendation is to run 'qemu-img info' to extract the metadata and sanity
> check results eg no backing file list, not unreasonable size, etc. When
> running 'qemu-img info' apply process limits of 30 secs CPU time, and 1 GB
>
On Thu, Jul 19, 2018 at 04:25:28PM +0300, Nir Soffer wrote:
> On Mon, Jul 16, 2018 at 11:56 AM Daniel P. Berrangé
> wrote:
>
> > On Wed, Jul 11, 2018 at 02:17:18PM +0300, Adam Litke wrote:
> > > Adding some kubevirt developers to the thread. Thanks guys for the
> > > information! I think this
On Mon, Jul 16, 2018 at 11:56 AM Daniel P. Berrangé
wrote:
> On Wed, Jul 11, 2018 at 02:17:18PM +0300, Adam Litke wrote:
> > Adding some kubevirt developers to the thread. Thanks guys for the
> > information! I think this could work perfectly for on the fly conversion
> > of qcow2 images to
hi,
I try to experiment LinuxTerminalServerProject on qemu virtualization
I installed ltsp on a ubuntu-1804 (virtualized) and run:
qemu-system-x86_64 -enable-kvm -m 1500 -hda /.../ubuser-18.img -k en-us -net
nic,vlan=0 -net tap,vlan=0,ifname=tap0 -k en-us -boot c -usbdevice mouse
(I view
Is there any possibility of doing this? I realize that suspending is not
possible with PCI devices attached, but would it be possible to instead
automate the process of hot removing all the PCI devices first, then
suspending, then hot adding them back again when resuming the machine? That'll
