You start a qemu like this and another VM already started with the same .iso qemu-system-x86_64 -enable-kvm -m 4096 -cdrom some.iso But you get this error: qemu-system-x86_64: Initialization of device ide-hd failed: Failed to get "write" lock Is another process using the image [some.iso]? It's odd because the -cdrom by default is read-only and qemu should not want or care about getting write lock on........

This has been a tried and true method for Windows because it is finicky with hardware changes without a reinstall (eg BSOD on boot is what happens 9/10 times unless you move to the same hardwar). Surprisingly, if you use a QEMU VM and do a standard install, it has worked in every system I've thrown the drive in afterwards. So the play is this, use a USB SSD, physical SATA drive plugged internally or for convenience, you could use a SATA to USB adapter on another computer to perf........

These types of errors are normally caused by misconfiguration of your /etc/apt/sources.list. In this example on Debian 10, if you didn't complete the install correctly, you will have no repos enabled and only rely on CDROM. "Package wget is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source. E: Package 'wget' ha........

Interestingly enough Windows 2000 works fine on QEMU 64-bit but you have to specify Pentium as your CPU otherwise it doesn't complete the install (it will not pass the detecting/setting up devices phase). -vga cirrus is wise because it is supported by Windows 2000 and allows higher resolutions and 24-bit color. -cpu Pentium emulates an old computer and is necessary for install to complete -device rtl8139 is important as this oldschool Realtek 8139 NIC is supported by W........

It's as simple as below where you just specify the dev device of the CDROM which is usually /dev/sr0. You can boot actual bootable discs like Windows, Linux, etc straight from a physical drive this way. sudo qemu-system-x86_64 -cdrom /dev/sr0 -m 4096 ........

The strange thing is that usually the first install or two will work on any new machine but then it suddenly won't. I had this experience on QEMU 2.13 on a different machine. There is something finicky or buggy about the CUCM installer even when choosing the same virtual hardware specs. qemu-kvm command: /usr/libexec/qemu-kvm -version QEMU PC emulator version 0.12.1 (qemu-kvm-0.12.1.2-2.506.el6_10.1), Copyright (c) 2003-2008 Fabrice Bellard ........

The key thing is that you must use a "machine"id of "pc-1.3" or it will say your hardware is not supported. Additionally you MUST use a virtio disk or you will get a ks_pre.sh error as soon as the install starts (a look at logs will show it can't find a disk). This is funny because even though the OS finds the disk and an fdisk -l shows it, it looks like the script looks for a /dev/vda device (virtio) and nothing else, so if you didn't use Virtio as you........

1.) Create Image using qemu-img qemu-img create -f qcow2 skype.img 40G 2.) Start VM using flags -m = memory in MB -drive file=yourimagefile.img -cdrom /path/to/the.iso qemu-system-x86_64 -m 4096 -drive file=skype.img -cdrom ~/Downloads/SfB-E-9319.0-enUS.ISO Enable Bridged Networking........

dvd+rw-mediainfo /dev/sr0 INQUIRY: [ASUS ][BW-16D1HT ][3.00] GET [CURRENT] CONFIGURATION: Mounted Media: 11h, DVD-R Sequential Media ID: RITEKF1&n........

These errors believe it or not are simply because of not being the root user or running with sudo! However if you didn't know to try as root you'd think there was a problem with your burner or disc Essentially it looks like without root you cannot send the required scsi commands to continue writing. Ithink cdrecord should have built-in tests or safeguards to see if it has the permissions to run the required commands. I guess for more advanced users the idea is simila........

This is useful if you are installing Windows and need virtio but of course Windows needs the virtio driver which is on a second iso. This is the line of code you would add to your kvm startup script and then you get this iso as second cdrom you can browse to for your Windows install of virtio driver's or whatever other use you need it for. -drive file=/kvmtemplates/virtio-win-0.1-94.iso,media=cdrom........

I finally decided to look into some utils that did this, and the first one I found is "mp3burn". It is unbelievable simple and perfect. *2017-11 update and mp3burn is still available in standard repos such as Ubuntu 14/16 so this is a current and working project. Just install the package and it gets all required libraries to convert and then burn's on the fly. And you won't believe how simple it is. I just want to a directory that had the MP3's I wanted t........

This is obviously a bug in the r8169 kernel module and it seems to affect a lot of people. I upgraded to the latest kernel and hope this won't happen anymore, as it is a very serious error. This is especially serious for those who are running servers with this chipset, who can afford for the NIC to randomly go off-line for no apparent reason? [655548.189113] type=1505 audit(1277067560.902:5): operation="profile_load" name="/usr/bin/freshclam&q........

When trying to even cd or ls the mounted OCFS2 partition it crashes. Ithink this is a combination of VMWare Server's problem and the way I mounted and symlinked to it. More than anything this shows the problem and lack of forsight with VMWare, but also that OCFS2 is easily crashed if you do strange things. Output of /var/log/messages for OCFS2 Apr 10 15:57:45 localhost kernel: [84331.691258] Modules linked in: vmnet vmci vmmon ocfs2_stac........