Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1443066 - Unable to encode message payload when creating a guest with 16384 virtio-scsi disks
Summary: Unable to encode message payload when creating a guest with 16384 virtio-scsi...
Keywords:
Status: NEW
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: TRACKER-bugs-affecting-libguestfs
TreeView+ depends on / blocked
 
Reported: 2017-04-18 12:10 UTC by Richard W.M. Jones
Modified: 2018-07-18 15:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)
log from libvirt client (4.77 MB, text/plain)
2017-04-18 12:12 UTC, Richard W.M. Jones 		no flags Details
log from libvirtd (1.17 MB, text/plain)
2017-04-18 12:13 UTC, Richard W.M. Jones 		no flags Details
View All

Description Richard W.M. Jones 2017-04-18 12:10:05 UTC 
Description of problem:

When creating a guest with 16384 virtio-scsi disks, libvirt
fails with:

  Unable to encode message payload

Version-Release number of selected component (if applicable):

libvirt-daemon-3.2.0-1.fc27.x86_64

How reproducible:

100%

Steps to Reproduce:
1. Create a guest with 16384 virtio-scsi disks.  See the attached
   file for libvirt XML and so on.
Comment 1 Richard W.M. Jones 2017-04-18 12:12:32 UTC 
Created attachment 1272310 [details]
log from libvirt client
Comment 2 Richard W.M. Jones 2017-04-18 12:13:36 UTC 
Created attachment 1272312 [details]
log from libvirtd
Note You need to log in before you can comment on or make changes to this bug.