search for: host_cdrom

Greetings, I was wondering what is the proper way to configure a scsi cdrom pass-through so in when the qemu line is generated, host_Cdrom will be used instead of host_device. looking at https://gitlab.com/libvirt/libvirt/-/blob/master/src/qemu/qemu_block.c#L1090, I see that hostcdrom must be true. in order for that to be true, the following must be (see https://gitlab.com/libvirt/libvirt/-/blob/master/src/qemu/qemu_domain.c#L7167):...

On Wed, Oct 28, 2020 at 15:06:51 +0100, daggs wrote: > Greetings, > > I was wondering what is the proper way to configure a scsi cdrom pass-through so in when the qemu line is generated, host_Cdrom will be used instead of host_device. > > looking at https://gitlab.com/libvirt/libvirt/-/blob/master/src/qemu/qemu_block.c#L1090, I see that hostcdrom must be true. > in order for that to be true, the following must be (see https://gitlab.com/libvirt/libvirt/-/blob/master/src/qemu/qemu_do...

...s so far: > > format=raw doesn't work with /dev/sr0. Omitting format=raw works. > format=host_device works. > > Apparently, virt-manager specifically asks for "raw". > > Things are different in RHEL-6: format=raw works, > format=host_device doesn't, format=host_cdrom does > (doesn't exist in RHEL-5). Now, in my configuration files there is no 'format' attribute found in any tag. I find 'type=raw' inside of many <device/> tags but it seems strange to me that a RedHat bug report would use such imprecise language so as to confuse the...

...--prefix=/usr/local/qemu-kvm \ --sysconfdir=/etc \ --audio-drv-list=alsa \ --audio-card-list=ac97,es1370 \ --disable-strip \ --disable-xen \ --enable-virtfs \ --block-drv-whitelist=qcow2,raw,file,host_device,host_cdrom,qed \ --disable-debug-tcg \ --disable-sparse \ --enable-werror \ --disable-sdl \ --disable-curses \ --disable-curl \ --enable-vnc \ --enable-vnc-tls \ --enable-vnc-sasl \ --disabl...

...And the strange thing about this error is that when I check the available drives, there is vvfat in the list: /usr/libexec/qemu-kvm -drive format=? Supported formats: ftps http null-aio null-co file quorum blkverify vvfat blkreplay qed raw qcow2 bochs dmg vmdk parallels vhdx vpc https sheepdog host_cdrom ssh host_device nbd gluster qcow iscsi rbd tftp ftp vdi blkdebug luks cloop Here some information about the environment: cat /etc/redhat-release CentOS Linux release 7.3.1611 (Core) virsh --version 2.0.0 /usr/libexec/qemu-kvm --version QEMU emulator version 2.6.0 (qemu-kvm-ev-2.6.0-28.el7_3.6....

...es since the vm creation. I don't know if the syntax is changed every version or not. > > Anyways the problem is almost certainly that the hostdev code doesn't > detect that it's a cdrom. We have such a hack in the disk code which > turns a 'host_device' into a 'host_cdrom'. I'll try fixing it but I > don't have a machine with a cdrom handy, so it would be nice if you > could test it afterwards. > > Thanks for the report. > > my system is gentoo, hence, every pkg is compiled, if you provide a patch, I can test it easily. Thanks for the...

Hi everyone, I have a question on connecting to hardware devices. With virt- manager I am attempting to use a hardware cdrom/dvd drive from an Ubuntu 16.04 VM however, i keep getting "'host_cdrom' is not whitelisted" errors when starting the VM. After some searching I checked my processor and realized it does not support VT-d. Is this 1) a requirement for sharing the device with the VM, and 2) the only way of sharing the device?

...39;ve mentioned, because the "new" syntax which uses -blockdev was present both in 6.7.0 and 6.8.0. Anyways the problem is almost certainly that the hostdev code doesn't detect that it's a cdrom. We have such a hack in the disk code which turns a 'host_device' into a 'host_cdrom'. I'll try fixing it but I don't have a machine with a cdrom handy, so it would be nice if you could test it afterwards. Thanks for the report.

...keep their configuration. Restarting it will use the new syntax and thus break. > > Anyways the problem is almost certainly that the hostdev code doesn't > > detect that it's a cdrom. We have such a hack in the disk code which > > turns a 'host_device' into a 'host_cdrom'. I'll try fixing it but I > > don't have a machine with a cdrom handy, so it would be nice if you > > could test it afterwards. > > > > Thanks for the report. > > > > > > my system is gentoo, hence, every pkg is compiled, if you provide a patc...

...the following error Error starting domain: internal error: qemu unexpectedly closed the monitor: 2016-12-22T00:00:30.330333Z qemu-kvm: -drive file=/dev/sr0,format=raw,if=none,media=cdrom, id=drive-sata0-0-0,readonly=on: could not open disk image /dev/sr0: Driver 'host_cdrom' is not whitelisted "Not whitelisted" ???? What am I doing wrong? Many thanks, -T -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Computers are like air conditioners. They malfunction when you open windows ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

...t this error is that when I check the > available drives, there is vvfat in the list: > > /usr/libexec/qemu-kvm -drive format=? > Supported formats: ftps http null-aio null-co file quorum blkverify > vvfat blkreplay qed raw qcow2 bochs dmg vmdk parallels vhdx vpc https > sheepdog host_cdrom ssh host_device nbd gluster qcow iscsi rbd tftp ftp > vdi blkdebug luks cloop > > Here some information about the environment: > > cat /etc/redhat-release > CentOS Linux release 7.3.1611 (Core) > > virsh --version > 2.0.0 > > /usr/libexec/qemu-kvm --version >...

...in vain Even if I try running with command line instead of XML I get error though it says it is supported [root@vmdkTOKVM]# /usr/libexec/qemu-kvm -drive file=/mnt/vmdkTOKVM/vmdkTOKVM.vmdk,format=? Supported formats: raw cow qcow vdi vmdk cloop dmg bochs vpc vvfat qcow2 qed parallels nbd blkdebug host_cdrom host_floppy host_device file [root@vmdkTOKVM]# /usr/libexec/qemu-kvm -drive file=/mnt/vmdkTOKVM/vmdkTOKVM.vmdk,format=vmdk qemu-kvm: -drive file=/mnt/XOcom-prx-kvm/XOcom-prx-kvm.vmdk,format=vmdk: 'vmdk' invalid format The packages being used are: qemu-img-0.12.1.2-2.355.0.1.el6_4.9.x86_...

Greetings Peter, > Sent: Thursday, October 15, 2020 at 9:52 AM > From: "Peter Krempa" <pkrempa@redhat.com> > To: "daggs" <daggs@gmx.com> > Cc: "libvirt-usersredhat.com" <libvirt-users@redhat.com> > Subject: Re: scsi passthrough differs between guests > > I don't see anything wrong with you configs. There were some changes

Hi, Is there a way to backup KVM Guest VM running CentOS Linux release 7.9.2009 (Core) OS in kvmguestosimage.ova or kvmguestosimage.vmdk format as I am trying to restore it in AWS by referring to https://aws.amazon.com/ec2/vm-import/ article as per the below supported file format. [1] Open Virtualization Archive (OVA) [2] Virtual Machine Disk (VMDK) [3] Virtual Hard Disk (VHD/VHDX) [4] raw Also