Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Trying to install Windows 7 into KVM and Windows attempts to read CD and install, but when it gets to "Starting Setup" in Windows, it crashes BSOD,
Error Message: " DRIVER_IRQL_NOT_LESS_OR_EQUAL STOP" can't go any further.
The error message is explained below line.
I ran a Memory Test with Memtest86 and NO BAD Memory was indicated.
This same computer has Two Sata Drives Installed.
Sda - 500gb. Wndows 7 is installed on this drive and had no errors while installing.
Sdb - 1 tb. Has Fedora 12 installed and This is the drive I'm trying to install Windows 7 in KVM .
So it would appear if it is a DRIVER problem, KVM would be part of the problem.
----------------------------------------------------------------------------------------------------------------------------------
Copied off of a Google Search
There are many reasons why your system may crash due to a DRIVER_IRQL_NOT_LESS_OR_EQUAL STOP or BSOD (Blue Screen of Death
) error, so this guide will provide some common tips that may solve the problem, along with some troubleshooting advice.
This error message means that the system attempted to access pageable memory using a kernel interrupt request level (IRQL)
that was too high. This is one of the most common errors and has many possible causes, but the most common scenarios are:
* Faulty drivers
* Hardware issue
* Anti-virus software problem
* Overclocking too far
If you notice any filenames mentioned on the blue screen, googling for the filename may indicate if it is attached to
any driver or software package. This can pinpoint the driver which you need to update. SCSI, Network and graphics drivers
are often the offenders if this is a driver problem - so you can try updating all your drivers manually if it is difficult
to track down the problem.
It is possible to analyse a "dump file" which contains more detailed information about the crash. These dump file are
located in C:\Windows\MiniDump and can be opened using diagnostic packages or posted to the forums for analysis by an
expert. This extra information will often provide a good clue to the BSOD crash.
If you aren't able to boot in to Windows 7 to fix the problem, you may be able to boot using safe mode (press F8 during
startup, or follow this guide) and access Windows again. If this still doesn't work, try selecting the "Last known good
configuration" option. If this also fails, using system restore to roll back your system a few days may be a valid option.
You can use your Windows 7 installation DVD to boot to the recovery options menu, then select "System Restore".
Hardware issues are more difficult to diagnose, but if you have resorted to a clean install of Windows 7 and the problem
still occurs, then it is a possibility. Memory is a frequent culprit, so you can use a tool like MemTest (or the Windows 7
memory diagnostics) to check your RAM for problems. Replacing components is often the only foolproof way to check for
faults.
It appears in "messages" that it's trying to install on /dev/sdc which is /dev/sr0, it can't make hdc/sr0 write enable.
The drive it should be writing image to is Fedora install /dev/hdb or sdb .
The BSOD is a *.png file and I can't attach it on this site.
May 7 13:55:27 localhost ntpd_initres[1753]: host name not found: 2.fedora.pool.ntp.org
May 7 13:55:37 localhost kernel: br0: port 2(vnet0) entering forwarding state
May 7 13:57:37 localhost dhclient[1249]: DHCPREQUEST on br0 to 172.16.0.1 port 67
May 7 13:57:37 localhost dhclient[1249]: DHCPACK from 172.16.0.1
May 7 13:57:37 localhost dhclient[1249]: bound to 172.16.1.34 -- renewal in 1777 seconds.
May 7 13:58:40 localhost avahi-daemon[1439]: Withdrawing address record for fe80::c8bb:29ff:fef9:2607 on vnet0.
May 7 13:58:40 localhost kernel: br0: port 2(vnet0) entering disabled state
May 7 13:58:40 localhost kernel: device vnet0 left promiscuous mode
May 7 13:58:40 localhost kernel: br0: port 2(vnet0) entering disabled state
May 7 13:58:41 localhost ntpd[1660]: Deleting interface #9 vnet0, fe80::c8bb:29ff:fef9:2607#123, interface stats: received=0, sent=0, dropped=0, active_time=196 secs
May 7 14:00:41 localhost libvirtd: 14:00:41.981: error : qemudDomainLookupByName:3080 : Domain not found: no domain with matching name 'Windows7'
May 7 14:01:01 localhost libvirtd: 14:01:01.254: error : qemudDomainLookupByName:3080 : Domain not found: no domain with matching name 'Windows7'
May 7 14:01:38 localhost libvirtd: 14:01:38.751: error : qemudDomainLookupByName:3080 : Domain not found: no domain with matching name 'Windows7'
May 7 14:01:38 localhost libvirtd: 14:01:38.756: error : qemudDomainLookupByName:3080 : Domain not found: no domain with matching name 'Windows7'
May 7 14:01:38 localhost libvirtd: 14:01:38.790: error : storageVolumeLookupByName:1105 : Storage volume not found: no storage vol with matching name 'Windows7-1.img'
May 7 14:01:38 localhost libvirtd: 14:01:38.795: error : storageVolumeLookupByPath:1191 : invalid storage volume pointer in no storage vol with matching path
May 7 14:01:38 localhost libvirtd: 14:01:38.796: error : storageVolumeLookupByPath:1191 : invalid storage volume pointer in no storage vol with matching path
May 7 14:01:38 localhost libvirtd: 14:01:38.797: error : storageVolumeLookupByName:1105 : Storage volume not found: no storage vol with matching name 'Windows7-1.img'
May 7 14:02:06 localhost libvirtd: 14:02:06.737: error : qemudDomainLookupByName:3080 : Domain not found: no domain with matching name 'Windows7'
May 7 14:02:06 localhost libvirtd: 14:02:06.752: error : qemudDomainLookupByName:3080 : Domain not found: no domain with matching name 'Windows7'
May 7 14:02:06 localhost libvirtd: 14:02:06.782: error : storageVolumeLookupByName:1105 : Storage volume not found: no storage vol with matching name 'Windows7-1.img'
May 7 14:02:06 localhost libvirtd: 14:02:06.793: error : storageVolumeLookupByPath:1191 : invalid storage volume pointer in no storage vol with matching path
May 7 14:02:06 localhost libvirtd: 14:02:06.793: error : storageVolumeLookupByPath:1191 : invalid storage volume pointer in no storage vol with matching path
May 7 14:02:06 localhost libvirtd: 14:02:06.794: error : storageVolumeLookupByName:1105 : Storage volume not found: no storage vol with matching name 'Windows7-1.img'
May 7 14:02:06 localhost libvirtd: 14:02:06.905: error : qemudDomainLookupByUUID:3055 : Domain not found: no domain with matching uuid '46ad4c04-c192-957b-a91a-c89c0faa3a9a'
May 7 14:02:06 localhost libvirtd: 14:02:06.910: error : qemudDomainLookupByName:3080 : Domain not found: no domain with matching name 'Windows7'
May 7 14:02:06 localhost libvirtd: 14:02:06.912: error : storageVolumeLookupByName:1105 : Storage volume not found: no storage vol with matching name 'Windows7-1.img'
May 7 14:02:07 localhost libvirtd: 14:02:07.288: error : storagePoolRefresh:820 : internal error pool 'default' has asynchronous jobs running.
May 7 14:02:07 localhost kernel: device vnet0 entered promiscuous mode
May 7 14:02:07 localhost kernel: br0: port 2(vnet0) entering learning state
May 7 14:02:08 localhost avahi-daemon[1439]: Registering new address record for fe80::5448:d3ff:fe40:7b39 on vnet0.*.
May 7 14:02:10 localhost ntpd[1660]: Listening on interface #10 vnet0, fe80::5448:d3ff:fe40:7b39#123 Enabled
May 7 14:02:12 localhost ntpd_initres[1753]: host name not found: 0.fedora.pool.ntp.org
May 7 14:02:12 localhost ntpd_initres[1753]: host name not found: 1.fedora.pool.ntp.org
May 7 14:02:12 localhost ntpd_initres[1753]: host name not found: 2.fedora.pool.ntp.org
May 7 14:02:22 localhost kernel: br0: port 2(vnet0) entering forwarding state
May 7 14:06:03 localhost avahi-daemon[1439]: Withdrawing address record for fe80::5448:d3ff:fe40:7b39 on vnet0.
May 7 14:06:03 localhost kernel: br0: port 2(vnet0) entering disabled state
May 7 14:06:03 localhost kernel: device vnet0 left promiscuous mode
May 7 14:06:03 localhost kernel: br0: port 2(vnet0) entering disabled state
May 7 14:06:05 localhost ntpd[1660]: Deleting interface #10 vnet0, fe80::5448:d3ff:fe40:7b39#123, interface stats: received=0, sent=0, dropped=0, active_time=235 secs
May 7 14:07:44 localhost kernel: usb 2-6: new high speed USB device using ehci_hcd and address 3
May 7 14:07:44 localhost kernel: usb 2-6: New USB device found, idVendor=058f, idProduct=6387
May 7 14:07:44 localhost kernel: usb 2-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 7 14:07:44 localhost kernel: usb 2-6: SerialNumber: VAWD64GZ
May 7 14:07:44 localhost kernel: usb 2-6: configuration #1 chosen from 1 choice
May 7 14:07:45 localhost kernel: Initializing USB Mass Storage driver...
May 7 14:07:45 localhost kernel: scsi6 : SCSI emulation for USB Mass Storage devices
May 7 14:07:45 localhost kernel: usbcore: registered new interface driver usb-storage
May 7 14:07:45 localhost kernel: USB Mass Storage support registered.
May 7 14:07:50 localhost kernel: scsi 6:0:0:0: Direct-Access Flash Drive AU_UB20 8.07 PQ: 0 ANSI: 2
May 7 14:07:50 localhost kernel: sd 6:0:0:0: Attached scsi generic sg3 type 0
May 7 14:07:50 localhost kernel: sd 6:0:0:0: [sdc] 8192000 512-byte logical blocks: (4.19 GB/3.90 GiB)
May 7 14:07:50 localhost kernel: sd 6:0:0:0: [sdc] Write Protect is off
May 7 14:07:50 localhost kernel: sd 6:0:0:0: [sdc] Assuming drive cache: write through
May 7 14:07:50 localhost kernel: sd 6:0:0:0: [sdc] Assuming drive cache: write through
May 7 14:07:50 localhost kernel: sdc: sdc1
May 7 14:07:50 localhost kernel: sd 6:0:0:0: [sdc] Assuming drive cache: write through
May 7 14:07:50 localhost kernel: sd 6:0:0:0: [sdc] Attached SCSI removable disk
May 7 14:08:06 localhost hald: mounted /dev/sdc1 on behalf of uid 500
I just discovered a problem. In Virtual-Manager it is showing /var/lib/libvirt/images/ is on hda that is wrong , the /var/lib/libvirt/images is on hdb.
A full install of Windows 7 is on hda1 ntfs
Fedora / is on hdb1 ext4
Why would the KVM be selecting hda as target disk when it should be hdb ?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.