6:25 a.m.
---1212189890-1011463599-1408447541=:44715
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Hello.=0AI currently have oVirt 3.4.x set up.=0AA colleague mentioned that =
he was having an issue where booting a VM with an attached iso and installi=
ng via cd/dvd does not allow the contents of the 'drive' to eject after the=
install.=A0 Sure enough, I have tested this myself and observed the same b=
ehaviour.=0A=0AInstalling an EL/fedora iso image with a kickstart that has =
a 'reboot --eject' line in will eject the 'drive' after the installing
when=
doing the exact same thing on VMware ESXi (and 'real' hardware).=0A=0AA su=
ggestion was made that VMware emulates a laptop style optical drive that on=
ce the disk ejects the system cannot close the drive bay upon reboot - this=
is a manual operation.=0ADoes oVirt emulate a destop style drive where eve=
n if the disk is ejected, when a reboot occurs the drive will close?=0A=0AT=
he long an short of this that even though the 'reboot --eject' option is in=
the kickstart, the iso image seems be be reattached when the VM reboots an=
d the installs process starts again.=A0 An infinite loop effectively.=0A=0A=
I'm told this isn't an issue with an KVM/Qemu VM under virt-manager.=0A=0AA=
ny suggestions as to how to solve this?=0AI should point out that I cannot =
simply extract files and boot via PXE as this process is supposed to be tes=
ting an install process via generated media.=0A=0AThanks.=0A
---1212189890-1011463599-1408447541=:44715
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
<html><body><div style=3D"color:#000; background-color:#fff;
font-family:He=
lveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif;fo=
nt-size:12pt"><div>Hello.</div><div><span>I currently have
oVirt 3.4.x set =
up.</span></div><div style=3D"color: rgb(0, 0, 0); font-size: 16px;
font-fa=
mily: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,Sans-Serif=
; background-color: transparent; font-style: normal;"><span>A colleague
men=
tioned that he was having an issue where booting a VM with an attached iso =
and installing via cd/dvd does not allow the contents of the 'drive' to eje=
ct after the install. Sure enough, I have tested this myself and obse=
rved the same behaviour.<br></span></div><div style=3D"color:
rgb(0, 0, 0);=
font-size: 16px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial=
,Lucida Grande,Sans-Serif; background-color: transparent; font-style: norma=
l;"><span>Installing an EL/fedora iso image with a kickstart that has a
'reboot --eject' line in will eject the 'drive' after the installing when
=
doing the exact same thing on VMware ESXi (and 'real'
hardware).<br></span>=
</div><div style=3D"color: rgb(0, 0, 0); font-size: 16px; font-family:
Helv=
eticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,Sans-Serif; backgrou=
nd-color: transparent; font-style: normal;"><span>A suggestion was made
tha=
t VMware emulates a laptop style optical drive that once the disk ejects th=
e system cannot close the drive bay upon reboot - this is a manual operatio=
n.</span></div><div style=3D"color: rgb(0, 0, 0); font-size: 16px;
font-fam=
ily: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,Sans-Serif;=
background-color: transparent; font-style: normal;"><span>Does oVirt
emula=
te a destop style drive where even if the disk is ejected, when a reboot oc=
curs the drive will close?</span></div><div style=3D"color: rgb(0, 0,
0); f=
ont-size: 16px; font-family: HelveticaNeue,Helvetica
Neue,Helvetica,Arial,Lucida Grande,Sans-Serif; background-color: transpare=
nt; font-style: normal;"><span><br></span></div><div
style=3D"color: rgb(0,=
0, 0); font-size: 16px; font-family: HelveticaNeue,Helvetica Neue,Helvetic=
a,Arial,Lucida Grande,Sans-Serif; background-color: transparent; font-style=
: normal;"><span>The long an short of this that even though the 'reboot
--e=
ject' option is in the kickstart, the iso image seems be be reattached when=
the VM reboots and the installs process starts again. An infinite lo=
op effectively.</span></div><div style=3D"color: rgb(0, 0, 0);
font-size: 1=
6px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grand=
e,Sans-Serif; background-color: transparent; font-style:
normal;"><br><span=
</span></div><div style=3D"color: rgb(0, 0, 0);
font-size: 16px; font-fami=
ly: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida
Grande,Sans-Serif; =
background-color: transparent; font-style: normal;"><span>I'm told this
isn't an issue with an KVM/Qemu VM under
virt-manager.</span></div><div st=
yle=3D"color: rgb(0, 0, 0); font-size: 16px; font-family: HelveticaNeue,Hel=
vetica Neue,Helvetica,Arial,Lucida Grande,Sans-Serif; background-color: tra=
nsparent; font-style:
normal;"><br><span></span></div><div
style=3D"color: =
rgb(0, 0, 0); font-size: 16px; font-family: HelveticaNeue,Helvetica Neue,He=
lvetica,Arial,Lucida Grande,Sans-Serif; background-color: transparent; font=
-style: normal;"><span>Any suggestions as to how to solve
this?</span></div=
<div style=3D"color: rgb(0, 0, 0); font-size: 16px;
font-family: Helvetica=
Neue,Helvetica Neue,Helvetica,Arial,Lucida
Grande,Sans-Serif; background-co=
lor: transparent; font-style: normal;"><span>I should point out that I
cann=
ot simply extract files and boot via PXE as this process is supposed to be =
testing an install process via generated media.</span></div><div
style=3D"c=
olor: rgb(0, 0, 0); font-size: 16px; font-family: HelveticaNeue,Helvetica
Neue,Helvetica,Arial,Lucida Grande,Sans-Serif; background-color: transpare=
nt; font-style: normal;"><br><span></span></div><div
style=3D"color: rgb(0,=
0, 0); font-size: 16px; font-family: HelveticaNeue,Helvetica Neue,Helvetic=
a,Arial,Lucida Grande,Sans-Serif; background-color: transparent; font-style=
: normal;"><span>Thanks.</span></div><div
style=3D"color: rgb(0, 0, 0); fon=
t-size: 16px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Luc=
ida Grande,Sans-Serif; background-color: transparent; font-style: normal;">=
<span><br></span></div></div></body></html>
---1212189890-1011463599-1408447541=:44715--
4:21 a.m.
----- Original Message -----
From: "Paul Jansen" <vlaero(a)yahoo.com.au>
To: "users" <users(a)ovirt.org>
Sent: Tuesday, August 19, 2014 2:25:41 PM
Subject: [ovirt-users] vm install via iso - optical drive eject behaviour?
Hello.
I currently have oVirt 3.4.x set up.
A colleague mentioned that he was having an issue where booting a VM with an
attached iso and installing via cd/dvd does not allow the contents of the
'drive' to eject after the install. Sure enough, I have tested this myself
and observed the same behaviour.
Installing an EL/fedora iso image with a kickstart that has a 'reboot
--eject' line in will eject the 'drive' after the installing when doing the
exact same thing on VMware ESXi (and 'real' hardware).
A suggestion was made that VMware emulates a laptop style optical drive that
once the disk ejects the system cannot close the drive bay upon reboot -
this is a manual operation.
Does oVirt emulate a destop style drive where even if the disk is ejected,
when a reboot occurs the drive will close?
The long an short of this that even though the 'reboot --eject' option is in
the kickstart, the iso image seems be be reattached when the VM reboots and
the installs process starts again. An infinite loop effectively.
I'm told this isn't an issue with an KVM/Qemu VM under virt-manager.
Any suggestions as to how to solve this?
I should point out that I cannot simply extract files and boot via PXE as
this process is supposed to be testing an install process via generated
media.
Thanks.
there is an open RFE for detecting the reboot and eject the cd in run once.
until that, what i do is: (assuming the HD doesn't have anything bootable on it)
edit the vm,
select in 'boot options':
first device- hard disk,
second device-CD and select the CD file you want to use.
start the vm regularly (not run once)
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
4:53 a.m.
This is a multi-part message in MIME format.
--------------040401080501030704070407
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
On 08/20/2014 11:21 AM, Omer Frenkel wrote:
----- Original Message -----
> From: "Paul Jansen" <vlaero(a)yahoo.com.au>
> To: "users" <users(a)ovirt.org>
> Sent: Tuesday, August 19, 2014 2:25:41 PM
> Subject: [ovirt-users] vm install via iso - optical drive eject behaviour?
>
> Hello.
> I currently have oVirt 3.4.x set up.
> A colleague mentioned that he was having an issue where booting a VM with an
> attached iso and installing via cd/dvd does not allow the contents of the
> 'drive' to eject after the install. Sure enough, I have tested this myself
> and observed the same behaviour.
> Installing an EL/fedora iso image with a kickstart that has a 'reboot
> --eject' line in will eject the 'drive' after the installing when doing
the
> exact same thing on VMware ESXi (and 'real' hardware).
> A suggestion was made that VMware emulates a laptop style optical drive that
> once the disk ejects the system cannot close the drive bay upon reboot -
> this is a manual operation.
> Does oVirt emulate a destop style drive where even if the disk is ejected,
> when a reboot occurs the drive will close?
>
> The long an short of this that even though the 'reboot --eject' option is in
> the kickstart, the iso image seems be be reattached when the VM reboots and
> the installs process starts again. An infinite loop effectively.
>
> I'm told this isn't an issue with an KVM/Qemu VM under virt-manager.
>
> Any suggestions as to how to solve this?
> I should point out that I cannot simply extract files and boot via PXE as
> this process is supposed to be testing an install process via generated
> media.
>
> Thanks.
there is an open RFE for detecting the reboot and eject the cd in run once.
until that, what i do is: (assuming the HD doesn't have anything bootable on it)
edit the vm,
select in 'boot options':
first device- hard disk,
second device-CD and select the CD file you want to use.
start the vm regularly (not run once)
Does this work for you?
In 3.5rc1, I have the following issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1131018
Description of problem:
Installing a VM with the Second Boot device CDROM. After installation, I choose reboot
in the VM and the installer of the CDROM appears again even though I have the HDD as first
boot device.
When I power down the VM, don't change anything, and power it up again. It does
start from the local HDD
Kind regards,
Jorick Astrego
Netbulae
--------------040401080501030704070407
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 08/20/2014 11:21 AM, Omer Frenkel
wrote:<br>
</div>
<blockquote
cite="mid:1033150319.34823323.1408526469937.JavaMail.zimbra@redhat.com"
type="cite">
<pre wrap="">
----- Original Message -----
</pre>
<blockquote type="cite">
<pre wrap="">From: "Paul Jansen" <a
class="moz-txt-link-rfc2396E"
href="mailto:vlaero@yahoo.com.au"><vlaero@yahoo.com.au></a>
To: "users" <a class="moz-txt-link-rfc2396E"
href="mailto:users@ovirt.org"><users@ovirt.org></a>
Sent: Tuesday, August 19, 2014 2:25:41 PM
Subject: [ovirt-users] vm install via iso - optical drive eject behaviour?
Hello.
I currently have oVirt 3.4.x set up.
A colleague mentioned that he was having an issue where booting a VM with an
attached iso and installing via cd/dvd does not allow the contents of the
'drive' to eject after the install. Sure enough, I have tested this myself
and observed the same behaviour.
Installing an EL/fedora iso image with a kickstart that has a 'reboot
--eject' line in will eject the 'drive' after the installing when doing the
exact same thing on VMware ESXi (and 'real' hardware).
A suggestion was made that VMware emulates a laptop style optical drive that
once the disk ejects the system cannot close the drive bay upon reboot -
this is a manual operation.
Does oVirt emulate a destop style drive where even if the disk is ejected,
when a reboot occurs the drive will close?
The long an short of this that even though the 'reboot --eject' option is in
the kickstart, the iso image seems be be reattached when the VM reboots and
the installs process starts again. An infinite loop effectively.
I'm told this isn't an issue with an KVM/Qemu VM under virt-manager.
Any suggestions as to how to solve this?
I should point out that I cannot simply extract files and boot via PXE as
this process is supposed to be testing an install process via generated
media.
Thanks.
</pre>
</blockquote>
<pre wrap="">
there is an open RFE for detecting the reboot and eject the cd in run once.
until that, what i do is: (assuming the HD doesn't have anything bootable on it)
edit the vm,
select in 'boot options':
first device- hard disk,
second device-CD and select the CD file you want to use.
start the vm regularly (not run once)
</pre>
</blockquote>
Does this work for you? <br>
<br>
In 3.5rc1, I have the following issue:<br>
<br>
<a class="moz-txt-link-freetext"
href="https://bugzilla.redhat.com/show_bug.cgi?id=1131018">h...
<br>
<blockquote>
<pre class="bz_comment_text
bz_wrap_comment_text" id="comment_text_0">Description
of problem:
Installing a VM with the Second Boot device CDROM. After installation, I choose reboot in
the VM and the installer of the CDROM appears again even though I have the HDD as first
boot device.
When I power down the VM, don't change anything, and power it up again. It does start
from the local HDD</pre>
</blockquote>
Kind regards,<br>
<br>
Jorick Astrego<br>
Netbulae<br>
<br>
</body>
</html>
--------------040401080501030704070407--
6:16 a.m.
New subject: vm install via iso - optical drive eject behaviour?
----- Original Message -----
From: "Jorick Astrego" <j.astrego(a)netbulae.eu>
To: users(a)ovirt.org
Sent: Wednesday, August 20, 2014 12:53:56 PM
Subject: Re: [ovirt-users] vm install via iso - optical drive eject behaviour?
On 08/20/2014 11:21 AM, Omer Frenkel wrote:
----- Original Message -----
From: "Paul Jansen" <vlaero(a)yahoo.com.au> To: "users"
<users(a)ovirt.org> Sent:
Tuesday, August 19, 2014 2:25:41 PM
Subject: [ovirt-users] vm install via iso - optical drive eject behaviour?
Hello.
I currently have oVirt 3.4.x set up.
A colleague mentioned that he was having an issue where booting a VM with an
attached iso and installing via cd/dvd does not allow the contents of the
'drive' to eject after the install. Sure enough, I have tested this myself
and observed the same behaviour.
Installing an EL/fedora iso image with a kickstart that has a 'reboot
--eject' line in will eject the 'drive' after the installing when doing the
exact same thing on VMware ESXi (and 'real' hardware).
A suggestion was made that VMware emulates a laptop style optical drive that
once the disk ejects the system cannot close the drive bay upon reboot -
this is a manual operation.
Does oVirt emulate a destop style drive where even if the disk is ejected,
when a reboot occurs the drive will close?
The long an short of this that even though the 'reboot --eject' option is in
the kickstart, the iso image seems be be reattached when the VM reboots and
the installs process starts again. An infinite loop effectively.
I'm told this isn't an issue with an KVM/Qemu VM under virt-manager.
Any suggestions as to how to solve this?
I should point out that I cannot simply extract files and boot via PXE as
this process is supposed to be testing an install process via generated
media.
Thanks.
there is an open RFE for detecting the reboot and eject the cd in run once.
until that, what i do is: (assuming the HD doesn't have anything bootable on
it)
edit the vm,
select in 'boot options':
first device- hard disk,
second device-CD and select the CD file you want to use.
start the vm regularly (not run once)
Does this work for you?
interesting, i just installed one vm and it worked for me yesterday,
and i tried again now couple of times (to be sure) and i see the same issue.
trying to investigate now what is the difference
In 3.5rc1, I have the following issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1131018
Description of problem:
Installing a VM with the Second Boot device CDROM. After installation, I
choose reboot in the VM and the installer of the CDROM appears again even
though I have the HDD as first boot device.
When I power down the VM, don't change anything, and power it up again. It
does start from the local HDD
Kind regards,
Jorick Astrego
Netbulae
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
9:20 a.m.
New subject: vm install via iso - optical drive eject behaviour?
----- Original Message -----
From: "Omer Frenkel" <ofrenkel(a)redhat.com>
To: "Jorick Astrego" <j.astrego(a)netbulae.eu>
Cc: users(a)ovirt.org
Sent: Wednesday, August 20, 2014 2:16:25 PM
Subject: Re: [ovirt-users] vm install via iso - optical drive eject behaviour?
----- Original Message -----
> From: "Jorick Astrego" <j.astrego(a)netbulae.eu>
> To: users(a)ovirt.org
> Sent: Wednesday, August 20, 2014 12:53:56 PM
> Subject: Re: [ovirt-users] vm install via iso - optical drive eject
> behaviour?
>
>
> On 08/20/2014 11:21 AM, Omer Frenkel wrote:
>
>
>
> ----- Original Message -----
>
>
>
> From: "Paul Jansen" <vlaero(a)yahoo.com.au> To: "users"
<users(a)ovirt.org>
> Sent:
> Tuesday, August 19, 2014 2:25:41 PM
> Subject: [ovirt-users] vm install via iso - optical drive eject behaviour?
>
> Hello.
> I currently have oVirt 3.4.x set up.
> A colleague mentioned that he was having an issue where booting a VM with
> an
> attached iso and installing via cd/dvd does not allow the contents of the
> 'drive' to eject after the install. Sure enough, I have tested this myself
> and observed the same behaviour.
> Installing an EL/fedora iso image with a kickstart that has a 'reboot
> --eject' line in will eject the 'drive' after the installing when doing
the
> exact same thing on VMware ESXi (and 'real' hardware).
> A suggestion was made that VMware emulates a laptop style optical drive
> that
> once the disk ejects the system cannot close the drive bay upon reboot -
> this is a manual operation.
> Does oVirt emulate a destop style drive where even if the disk is ejected,
> when a reboot occurs the drive will close?
>
> The long an short of this that even though the 'reboot --eject' option is
> in
> the kickstart, the iso image seems be be reattached when the VM reboots and
> the installs process starts again. An infinite loop effectively.
>
> I'm told this isn't an issue with an KVM/Qemu VM under virt-manager.
>
> Any suggestions as to how to solve this?
> I should point out that I cannot simply extract files and boot via PXE as
> this process is supposed to be testing an install process via generated
> media.
>
> Thanks.
> there is an open RFE for detecting the reboot and eject the cd in run once.
>
> until that, what i do is: (assuming the HD doesn't have anything bootable
> on
> it)
> edit the vm,
> select in 'boot options':
> first device- hard disk,
> second device-CD and select the CD file you want to use.
>
> start the vm regularly (not run once)
> Does this work for you?
>
interesting, i just installed one vm and it worked for me yesterday,
and i tried again now couple of times (to be sure) and i see the same issue.
trying to investigate now what is the difference
ok found the issue, there is a bug in add disk that cause the boot order to be wrong
(order is calculated before the disk is added).
looks like this affects vms created from blank (or other diskless) template and the disk
is added afterwards
while this is fixed, a workaround is to first create the vm and the disk,
and only after that, edit the vm and choose the wanted boot options, this will cause the
boot order to be re-calculated, taking into account also the disk.
if your vm already created, you can edit the boot order to something and then return it to
what you like.
> In 3.5rc1, I have the following issue:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1131018
>
>
>
>
> Description of problem:
> Installing a VM with the Second Boot device CDROM. After installation, I
> choose reboot in the VM and the installer of the CDROM appears again even
> though I have the HDD as first boot device.
>
> When I power down the VM, don't change anything, and power it up again. It
> does start from the local HDD
> Kind regards,
>
> Jorick Astrego
> Netbulae
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
10:03 a.m.
New subject: vm install via iso - optical drive eject behaviour?
Also this bug regarding boot order with cloud init
might be relevant:
https://bugzilla.redhat.com/show_bug.cgi?id=1064927
Am 20.08.2014 16:20, schrieb Omer Frenkel:
----- Original Message -----
> From: "Omer Frenkel" <ofrenkel(a)redhat.com>
> To: "Jorick Astrego" <j.astrego(a)netbulae.eu>
> Cc: users(a)ovirt.org
> Sent: Wednesday, August 20, 2014 2:16:25 PM
> Subject: Re: [ovirt-users] vm install via iso - optical drive eject behaviour?
>
>
>
> ----- Original Message -----
>> From: "Jorick Astrego" <j.astrego(a)netbulae.eu>
>> To: users(a)ovirt.org
>> Sent: Wednesday, August 20, 2014 12:53:56 PM
>> Subject: Re: [ovirt-users] vm install via iso - optical drive eject
>> behaviour?
>>
>>
>> On 08/20/2014 11:21 AM, Omer Frenkel wrote:
>>
>>
>>
>> ----- Original Message -----
>>
>>
>>
>> From: "Paul Jansen" <vlaero(a)yahoo.com.au> To: "users"
<users(a)ovirt.org>
>> Sent:
>> Tuesday, August 19, 2014 2:25:41 PM
>> Subject: [ovirt-users] vm install via iso - optical drive eject behaviour?
>>
>> Hello.
>> I currently have oVirt 3.4.x set up.
>> A colleague mentioned that he was having an issue where booting a VM with
>> an
>> attached iso and installing via cd/dvd does not allow the contents of the
>> 'drive' to eject after the install. Sure enough, I have tested this
myself
>> and observed the same behaviour.
>> Installing an EL/fedora iso image with a kickstart that has a 'reboot
>> --eject' line in will eject the 'drive' after the installing when
doing the
>> exact same thing on VMware ESXi (and 'real' hardware).
>> A suggestion was made that VMware emulates a laptop style optical drive
>> that
>> once the disk ejects the system cannot close the drive bay upon reboot -
>> this is a manual operation.
>> Does oVirt emulate a destop style drive where even if the disk is ejected,
>> when a reboot occurs the drive will close?
>>
>> The long an short of this that even though the 'reboot --eject' option
is
>> in
>> the kickstart, the iso image seems be be reattached when the VM reboots and
>> the installs process starts again. An infinite loop effectively.
>>
>> I'm told this isn't an issue with an KVM/Qemu VM under virt-manager.
>>
>> Any suggestions as to how to solve this?
>> I should point out that I cannot simply extract files and boot via PXE as
>> this process is supposed to be testing an install process via generated
>> media.
>>
>> Thanks.
>> there is an open RFE for detecting the reboot and eject the cd in run once.
>>
>> until that, what i do is: (assuming the HD doesn't have anything bootable
>> on
>> it)
>> edit the vm,
>> select in 'boot options':
>> first device- hard disk,
>> second device-CD and select the CD file you want to use.
>>
>> start the vm regularly (not run once)
>> Does this work for you?
>>
>
> interesting, i just installed one vm and it worked for me yesterday,
> and i tried again now couple of times (to be sure) and i see the same issue.
>
> trying to investigate now what is the difference
>
ok found the issue, there is a bug in add disk that cause the boot order to be wrong
(order is calculated before the disk is added).
looks like this affects vms created from blank (or other diskless) template and the disk
is added afterwards
while this is fixed, a workaround is to first create the vm and the disk,
and only after that, edit the vm and choose the wanted boot options, this will cause the
boot order to be re-calculated, taking into account also the disk.
if your vm already created, you can edit the boot order to something and then return it
to what you like.
>> In 3.5rc1, I have the following issue:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1131018
>>
>>
>>
>>
>> Description of problem:
>> Installing a VM with the Second Boot device CDROM. After installation, I
>> choose reboot in the VM and the installer of the CDROM appears again even
>> though I have the HDD as first boot device.
>>
>> When I power down the VM, don't change anything, and power it up again. It
>> does start from the local HDD
>> Kind regards,
>>
>> Jorick Astrego
>> Netbulae
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--
Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +49-5772-293-100
F: +49-5772-293-333
https://www.mittwald.de
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
3822
days inactive
3823
days old
5 comments
4 participants
participants (4)
-
Jorick Astrego -
Omer Frenkel -
Paul Jansen -
Sven Kieske