Error Restoring Domain Unable To Open Disk Path /dev/sr0
Common F23 Bugs Common F24 Bugs Communicate with Fedora The Documents Bug Reports Fedora Update System (Bodhi) Fedora Build System (Koji) Official Spins FedoraForum.org > Fedora 23/24 > Using Fedora virtual machine manager start with error:unable to open disk path /dev/sr0: No medium FedoraForum Search User Name Remember Me? Password Forgot Password? Join Us! Register All Albums FAQ Today's Posts Search Using Fedora General support for current versions. Ask questions about Fedora that do not belong in any other forum. Google™ Search FedoraForum Search Red Hat Bugzilla Search Search Forums Show Threads Show Posts Tag Search Advanced Search Go to Page... Thread Tools Search this Thread Display Modes #1 23rd May 2011, 05:17 PM xtcsin Offline Registered User Join Date: Aug 2008 Posts: 17 virtual machine manager start with error:unable to open disk path /dev/sr0: No medium virtual machine manager start with error as follows: Error starting domain:unable to open disk path /dev/sr0: No medium found details: Error starting domain: unable to open disk path /dev/sr0: No medium found Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 45, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/engine.py", line 959, in asyncfunc vm.startup() File "/usr/share/virt-manager/virtManager/domain.py", line 1128, in startup self._backend.create() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 330, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: unable to open disk path /dev/sr0: No medium found xtcsin View Public Profile Find all posts by xtcsin #2 1st June 2011, 11:57 PM mpustel Offline Registered User Join Date: Jun 2011 Posts: 1 Re: virtual machine manager start with error:unable to open disk path /dev/sr0: No me You have the cdrom connected so the vm expects a disk to be mounted. Here is how you fix. 1. click on the icon for vm hardware details 2. under CDROM click disconnect button (toggle to connect) 3. go back to vm and start That should fix your problem. Remember to connect when you need to mount a cd disk. Have fun. mpustel View Public Profile Find all posts by mpustel #3 23rd September 2011, 06:55 AM marcosaluzzo Offline Registered User Join Date: Jul 2008 Location: Torino Age: 39 Posts: 43 Re: virtual machine manager start with error:unable to open disk path /
[x] Format For Printing -XML -Clone This Bug -Last Comment First Last Prev Next This bug is not in your last search results. Bug709585 - qemu-kvm can not start with /dev/sr0 if no media in physical cdrom Summary: qemu-kvm can not start with /dev/sr0 if no media in physical cdrom Status: CLOSED DEFERRED Aliases: None Product: Red Hat Enterprise Linux 5 Classification: Red http://forums.fedoraforum.org/showthread.php?t=263396 Hat Component: kvm (Show other bugs) Sub Component: --- Version: 5.7 Hardware: Unspecified Unspecified Priority medium Severity medium TargetMilestone: rc TargetRelease: --- Assigned To: Markus Armbruster QA Contact: Virtualization Bugs Docs Contact: URL: Whiteboard: Keywords: Depends On: Blocks: Rhel5KvmTier2 Show dependency tree /graph Reported: 2011-06-01 01:52 EDT by Mike Cao Modified: 2014-06-28 https://bugzilla.redhat.com/show_bug.cgi?id=709585 07:28 EDT (History) CC List: 10 users (show) bcao bughunt byrnejb gcosta juzhang michen mkenneth nerijus rhod virt-maint See Also: Fixed In Version: Doc Type: Bug Fix Doc Text: Story Points: --- Clone Of: Environment: Last Closed: 2011-08-10 16:15:48 EDT Type: --- Regression: --- Mount Type: --- Documentation: --- CRM: Verified Versions: Category: --- oVirt Team: --- RHEL 7.3 requirements from Atomic Host: Cloudforms Team: --- Attachments (Terms of Use) Add an attachment (proposed patch, testcase, etc.) Groups: None (edit) Description Mike Cao 2011-06-01 01:52:55 EDT Description of problem: ,do not insert media in physical cdrom ,try to start guest with -cdrom /dev/sr0 ,qemu-kvm could not start Version-Release number of selected component (if applicable): # uname -r 2.6.18-264.el5 # rpm -q kvm kvm-83-235.el5 How reproducible: 100% Steps to Reproduce: 1.Do not insert any media in physical cdrom 2.start guest with -drive file=/dev/sr0,if=ide,media=cdrom eg:/usr/libexec/qemu-kvm -M rhel5.6.0 -m 2048 -smp 4,sockets=4,cores=1,threads=1 -name RHEL6u1 -uuid 7c9a4b2c-8d58-6771-7748-0ce92bfd83f7 -monitor stdio -no-kvm-pit-reinjection -boot dc -drive file=/dev/stress/rhel6u1,if=vir
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn http://serverfault.com/questions/373372/how-to-connect-a-cdrom-device-to-a-kvm-qemu-domain-using-command-line-tools more about Stack Overflow the company Business Learn more about hiring developers or posting https://wiki.archlinux.org/index.php/libvirt ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise error restoring to the top How to connect a cdrom device to a kvm/qemu domain (using command-line tools)? up vote 20 down vote favorite 7 I have set up a virtual machine running Windows XP on my Ubuntu laptop. Using the virt-manager GUI application, I can insert a CD in my drive and go to Details→IDE CDROM 1 and click on the Connect button. Then the CD becomes available in my virtual error restoring domain machine. How can I do the same through the command line? Obviously, I'd like to be able to disconnect from the command line too. Note: I can start the VM from the command line using virsh start testbed (testbed being the name of the domain/VM). kvm-virtualization optical-media virsh share|improve this question edited Mar 28 '12 at 18:58 asked Mar 26 '12 at 10:14 ΤΖΩΤΖΙΟΥ 6831717 add a comment| 4 Answers 4 active oldest votes up vote 21 down vote accepted If you defined no CDROM when you created your virtual machine, you can attach the device even to a running domain (virtual machine) by running the following command: virsh attach-disk testbed /dev/sr0 hdc --type cdrom If you already defined a CDROM, but it pointed to an ISO image, in my experience, you can still run the same command. The hdcpart needs to match the block device you have in the testbed virtual machine. When you want to point to an ISO image again, you replace /dev/sr0 to the filename on the host, something like virsh attach-disk testbed ~/virtio-win-0.1-22.iso hdc --type cdrom The documentation suggests using virsh update-device, but it is more labour to create an XML definition something like: and other virtualization functionality, such as storage and network interface management. These software pieces include a long term stable C API, a daemon (libvirtd), and a command line utility (virsh). A primary goal of libvirt is to provide a single way to manage multiple different virtualization providers/hypervisors, such as the KVM/QEMU, Xen, LXC, OpenVZ or VirtualBox hypervisors (among others). Some of the major libvirt features are: VM management: Various domain lifecycle operations such as start, stop, pause, save, restore, and migrate. Hotplug operations for many device types including disk and network interfaces, memory, and cpus. Remote machine support: All libvirt functionality is accessible on any machine running the libvirt daemon, including remote machines. A variety of network transports are supported for connecting remotely, with the simplest being SSH, which requires no extra explicit configuration. Storage management: Any host running the libvirt daemon can be used to manage various types of storage: create file images of various formats (qcow2, vmdk, raw, ...), mount NFS shares, enumerate existing LVM volume groups, create new LVM volume groups and logical volumes, partition raw disk devices, mount iSCSI shares, and much more. Network interface management: Any host running the libvirt daemon can be used to manage physical and logical network interfaces. Enumerate existing interfaces, as well as configure (and create) interfaces, bridges, vlans, and bond devices. Virtual NAT and Route based networking: Any host running the libvirt daemon can manage and create virtual networks. Libvirt virtual networks use firewall rules to act as a router, providing VMs transparent access to the host machines network. Contents 1 Installation 1.1 Server 1.2 Client 2 Configuration 2.1 Set up authentication 2.1.1 Using polkit 2.1.2 Authenticate