similar to: proper config for qemu's host_cdrom

Displaying 20 results from an estimated 100 matches similar to: "proper config for qemu's host_cdrom"

2020 Nov 02
0
Re: proper config for qemu's host_cdrom
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
2017 Apr 19
2
virsh error: driver is not whitelisted
Hi, I'm using virsh to instance a VM in my environment, but I'm running on some issues. I created the following domain file: <domain type='kvm'> <name>demovm</name> <uuid>4a9b3f53-fa2a-47f3-a757-dd87720d9d1d</uuid> <memory unit='KiB'>4194304</memory> <currentMemory
2020 Oct 15
2
Re: scsi passthrough differs between guests
Greetings Peter, > Sent: Thursday, October 15, 2020 at 2:01 PM > 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 > > [...] > > > -drive
2020 Oct 15
2
Re: scsi passthrough differs between guests
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
2012 Jun 04
1
guestfish1.7.17 does not support qemu-kvm1.0.93?
Hi,all,i build qemu-kvm1.0.93 from source code on centos6.2 , # qemu-system-x86_64 --version QEMU emulator version 1.0.93 (qemu-kvm-devel), Copyright (c) 2003-2008 Fabrice Bellard and the guestfish's version: # guestfish --version guestfish 1.7.17 but when i use the guestfish command to upload a file to a vm,it does not work , # guestfish --rw -i -d centosvm upload /test/ifcfg-eth0_centos
2022 Sep 01
2
Backup KVM Guest VM in OVA or VMDK format
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
2014 Feb 13
0
Problem with cdrom device on guest
I have a kvm guest running MS-WinV7 on a CentOS-6.5 host. The WinV7 guest was installed from a CD. It installed correctly and was updated and added to an MS Active Domain without difficulty. I was able to do work on it through the virt-manager console and I was able to shut the system down from the console without problem. I cannot get it to restart however. virsh start
2008 Aug 29
1
[RFC] [PATCH] SCSI passthrough for virtio-blk
Hi all, I got bored and implemented SCSI passthrough for the virtio-blk driver. Principle is quite simple, just put the missing fields (cdb, sense and status header) on the virtio queue and then call the SG_IO ioctl on the host. So when using '-drive file=/dev/sgXX,if=virtio,format=host_device' you can happily call any sg_XX command on the resulting vdX device. Quite neat, methinks. And
2008 Aug 29
1
[RFC] [PATCH] SCSI passthrough for virtio-blk
Hi all, I got bored and implemented SCSI passthrough for the virtio-blk driver. Principle is quite simple, just put the missing fields (cdb, sense and status header) on the virtio queue and then call the SG_IO ioctl on the host. So when using '-drive file=/dev/sgXX,if=virtio,format=host_device' you can happily call any sg_XX command on the resulting vdX device. Quite neat, methinks. And
2020 Oct 15
0
Re: scsi passthrough differs between guests
On Thu, Oct 15, 2020 at 12:36:08 +0200, daggs wrote: > 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
2020 Oct 15
0
Re: scsi passthrough differs between guests
On Thu, Oct 15, 2020 at 13:14:56 +0200, daggs wrote: > Greetings Peter, > > > Sent: Thursday, October 15, 2020 at 2:01 PM > > 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
2017 Apr 19
0
virsh error: driver is not whitelisted
On 04/19/2017 10:00 AM, Marco Aurelio L. Gomes wrote: > Hi, > > I'm using virsh to instance a VM in my environment, but I'm running on > some issues. > I got the following error: > > error: Failed to create domain from domain.xml > error: internal error: qemu unexpectedly closed the monitor: > 2017-04-17T17:00:37.012369Z qemu-kvm: -drive >
2013 Oct 22
0
Re: kvm/libvirt can't use vmdk files? qemu: 'vmdk' invalid format
Dear All, While trying to run kvm VM using vmdk disk on 6.4 , I got into the following error, error: Failed to create domain from vmdkvm.xml error: internal error process exited while connecting to monitor: qemu-kvm: -drive file=/mnt/vmdkTOKVM/vmdkTOKVM.vmdk,if=none,id=drive-ide0-0-0,format=vmdk,cache=none: 'vmdk' invalid format upon further digging I came across this thread (
2020 Oct 22
2
Why "discard":"unmap" is the default option for disks
Hello, I find "discard":"unmap" is defaultly enabled in qemu cmdline(libvirt v6.6, qemu v5.1): XML: <disk type="file" device="disk"> <driver name="qemu" type="qcow2"/> <source file="/var/lib/libvirt/images/new.qcow2" index="2"/> <backingStore/> <target
2020 Oct 14
2
scsi passthrough differs between guests
Greetings, I have two machines running the same distro, both running qemu 5.1.0, one runs libvirt 6.7.0, the other 6.8.0. I've decided to test the viability of passing through my sata cdrom into a vm, so I went to the libvirt docs, read a bit and added the following to a debian10 uefi vm running on libvirt 6.8.0: <controller type='scsi' index='0'
2011 Apr 21
7
[PATCHv11 0/6] libvirt/qemu - persistent modification of devices
Here is v11. Fixed comments/bugs and updated against the latest libvirt.git. Changes v10->v11: - fixed comments on each patches - fixed cgroup handling in patch 3. - fixed MODIFY_CURRENT handling in patch 4. most of diff comes from refactoring qemu/qemu_driver.c -- conf/domain_conf.c | 40 ++ conf/domain_conf.h | 5 libvirt_private.syms | 3 qemu/qemu_driver.c | 727
2020 Oct 22
0
Re: Why "discard":"unmap" is the default option for disks
On Thu, Oct 22, 2020 at 10:57:05 +0800, Han Han wrote: > Hello, > I find "discard":"unmap" is defaultly enabled in qemu cmdline(libvirt > v6.6, qemu v5.1): > XML: > <disk type="file" device="disk"> > <driver name="qemu" type="qcow2"/> > <source
2018 Feb 11
0
Method for connecting to CDROM/DVD
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
2016 Dec 22
0
dvd not whitelisted ???
Hi All, Scientific Linux 7.2 I am drawing a blank on Google here. I am, trying to boot a qemu-kvm virtual machine off of /dev/sr0 (my DVD). But I get 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:
2018 Jul 26
0
Does libvirt (will) support qemu's userspace vhost scsi and blk
Does libvirt (will) support qemu's userspace vhost scsi and blk?