search for: startuppolicy

...own still works as expected. I get the same error when attaching a device in virt-manager, as I do when running the following command: sudo virsh attach-device wenger /dev/stdin --persistent <<END <hostdev mode='subsystem' type='usb' managed='yes'> <source startupPolicy='optional'> <vendor id='0x046d' /> <product id='0xc215' /> </source> </hostdev> END This returns error: Failed to attach device from /dev/stdin error: failed to load cgroup BPF prog: Operation not permitted virt-manager returns basical...

...which >> will wait for the VM start event and then execute what's necessary. >> > > I see, is there another way to do what I need (on startup usb hotplug) or maybe optional hotplug (e.g. don't fail the device isn't present)? I've never used it, but does the "startupPolicy" attribute do what you need? Search for that string at: https://libvirt.org/formatdomain.html#elementsHostDevSubsys

Hi, I'm trying to use USB pass through with devices that are not present at the VM startup. However, when starting the machine, libvirt complains that the USB device doesn't exist. I was following the guide at [1], but this doesn't seem to work on Debian Wheezy. Any hints how to achieve that? Thanks, Felicitus [1]

Greetings Peter, > Sent: Friday, January 04, 2019 at 4:47 PM > From: "Peter Krempa" <pkrempa@redhat.com> > To: daggs <daggs@gmx.com> > Cc: libvirt-users@redhat.com > Subject: Re: [libvirt-users] script called from qemu hook freezes. > > On Thu, Jan 03, 2019 at 18:07:58 +0100, daggs wrote: > > Greetings, > > > > I'm executing an

...in virt-manager, as I do > > > when running the following command: > > > > > > sudo virsh attach-device wenger /dev/stdin --persistent <<END > > > <hostdev mode='subsystem' type='usb' managed='yes'> > > > <source startupPolicy='optional'> > > > <vendor id='0x046d' /> > > > <product id='0xc215' /> > > > </source> > > > </hostdev> > > > END > > > > > > This returns > > > error: Failed to att...

Hi, We have a VM with several USB devices attached. Everything works well, but sometimes, after a reboot of the host, some usb device get a different bus/device number and that prevent the reboot of the VM : ------- error: Failed to start domain xxx error: internal error: Did not find USB device 04b9:0300 bus:1 device:5 ------- I guess this is because we have multiple usb devices with the same

...${DOMAIN} --live for USB vendor=0x${ID_VENDOR_ID} product=0x${ID_MODEL_ID} bus=${BUSNUM} device=${DEVNUM}:" >&2 virsh "${COMMAND}" "${DOMAIN}" /dev/stdin --live <<END <hostdev mode='subsystem' type='usb' managed='yes'> <source startupPolicy='optional'> <vendor id='0x${ID_VENDOR_ID}' /> <product id='0x${ID_MODEL_ID}' /> <address bus='${BUSNUM}' device='${DEVNUM}' /> </source> </hostdev> END ===

...> > > > when running the following command: > > > > > > > > sudo virsh attach-device wenger /dev/stdin --persistent <<END > > > > <hostdev mode='subsystem' type='usb' managed='yes'> > > > > <source startupPolicy='optional'> > > > > <vendor id='0x046d' /> > > > > <product id='0xc215' /> > > > > </source> > > > > </hostdev> > > > > END > > > > > > > > This returns...