8:41 a.m.
Hello
During the installation of a virtual machine, I have a problem with some
ISOs because they can not boot the machine.
Occur the following error:
Booting from DVD / CD ....
Boot failed: Could not read from CDROM (code 0003)
--
“Encarada do ponto de vista da juventude, a vida parece um futuro
indefinidamente longo, ao passo que, na velhice, ela parece um passado
deveras curto. Assim, a vida no seu início se apresenta do mesmo modo
que as coisas quando as olhamos através de um binóculo usado ao contrário;
mas, ao
seu final, ela se parece com as coisas tal qual são vistas quando o
binóculo
é usado de modo normal. Um homem precisa ter envelhecido e vivido
bastante para perceber como a vida é curta”.
(Poema de Arthur Schopenhauer)
9:44 a.m.
On Mon, Apr 22, 2013 at 10:41:29AM -0300, victor nunes wrote:
I have a similar problem with a newly installed All-in-one setup
running oVirt 3.2.1. When starting a VM with an CD-ROM image
attached, I can see the following message in engine.log:
2013-04-29 16:38:33,744 INFO [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo]
(DefaultQuartzScheduler_Worker-9) Received a cdrom Device without an address when
processing VM 658ca53d-12cf-4b03-973d-a0d2cdf5315f devices, skipping device:
{shared=false, bootOrder=1, iface=ide, index=2,
specParams={path=FreeBSD-9.1-RELEASE-amd64-disc1.iso}, device=cdrom,
path=/rhev/data-center/93cacf4c-6891-4c44-8b46-f1acf6913605/d61b3c06-b320-4b47-9981-5d64c0ce3736/images/11111111-1111-1111-1111-111111111111/FreeBSD-9.1-RELEASE-amd64-disc1.iso,
type=disk, readonly=true, deviceId=089a2b81-89a8-4868-acb0-a991b2f6b9a7}
As a result of this message I can see with `virsh -r` that the
CD-ROM is starting up with default configuration and NO IMAGE
attached:
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source startupPolicy='optional'/>
<target dev='hdc' bus='ide'/>
<readonly/>
<serial></serial>
<boot order='1'/>
<alias name='ide0-1-0'/>
<address type='drive' controller='0' bus='1'
target='0' unit='0'/>
</disk>
This is a Fedora 18 ovirt host with all updates installed and the
following oVirt packages installed:
ovirt-engine-3.2.1-1.fc18.noarch
ovirt-engine-backend-3.2.1-1.fc18.noarch
ovirt-engine-cli-3.2.0.11-1.fc18.noarch
ovirt-engine-dbscripts-3.2.1-1.fc18.noarch
ovirt-engine-genericapi-3.2.1-1.fc18.noarch
ovirt-engine-restapi-3.2.1-1.fc18.noarch
ovirt-engine-sdk-3.2.0.10-1.fc18.noarch
ovirt-engine-setup-3.2.1-1.fc18.noarch
ovirt-engine-setup-plugin-allinone-3.2.1-1.fc18.noarch
ovirt-engine-tools-3.2.1-1.fc18.noarch
ovirt-engine-userportal-3.2.1-1.fc18.noarch
ovirt-engine-webadmin-portal-3.2.1-1.fc18.noarch
ovirt-host-deploy-1.0.1-1.fc18.noarch
ovirt-host-deploy-java-1.0.1-1.fc18.noarch
ovirt-host-deploy-offline-1.0.1-1.fc18.noarch
ovirt-image-uploader-3.2.2-1.fc18.noarch
ovirt-iso-uploader-3.2.2-1.fc18.noarch
ovirt-log-collector-3.2.2-1.fc18.noarch
ovirt-release-fedora-5-3.1.noarch
Thanks
- Frank
10:50 a.m.
On Mon, Apr 29, 2013 at 04:44:22PM +0200, Frank Wall wrote:
This is strange. I tried a reboot of the oVirt host, but it did
not solve this issue. Afterwards I set the host to maintenance
mode and - after a few minutes - activated it again.
Now it's again possible to boot VMs with an CD-ROM image.
Thanks
- Frank
4427
days inactive
4434
days old
3 comments
3 participants
participants (3)
-
Frank Wall -
Roy Golan -
victor nunes