[one-users] Odp.: Re: VM Failed with Windows OS
Carlos Martín Sánchez
cmartin at opennebula.org
Thu Aug 14 01:11:25 PDT 2014
Hi Lorenzo,
I've seen you have provided valuable help with Windows guests in OpenNebula
a few times in the list.
I'd like to welcome you to make a pull request to our windows
contextualization docs [1], if you feel the installation section can be
improved with more detail.
Thanks!
[1]
http://docs.opennebula.org/4.8/user/virtual_machine_setup/windows_context.html
--
Carlos Martín, MSc
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org | cmartin at opennebula.org | @OpenNebula
<http://twitter.com/opennebula> <cmartin at opennebula.org>
On Fri, Jul 18, 2014 at 3:17 PM, Lorenzo Faleschini <
lorenzo.faleschini at nordestsystems.com> wrote:
> Il 18/07/2014 14:47, Sudeep Narayan Banerjee ha scritto:
>
> Hello All,
>
> I followed your advice & now I installed the RedHat Virtio drivers and
> it detected the HDD from virt-install command.
>
> Finally it created & instantiated the image, template & VM.
>
> For past 20mins the VM is in Prolog mode.
>
> Whereas, virt-viewer -c qemu:///system Win7 is still running &
> viewable.
>
>
>
> do you mean you manually ran the kvm machine (outside ONE) then when still
> running tried to instantiate it from the onetemplate on the same server
> using the same image?
>
> if so shutdown that vm first then instantiate it.
>
> BUT
> I usually prefer doing everything in ONE rather than creating otherwise
> and then importing.
> my suggestion is to start from scratch:
>
> - create an empty datablock image (raw or qcow2) we'll call WINDRIVEC
> - change type to from DATABLOCK to OS for WINDRIVEC
> - mark it as persistent for convenience while you install reboot and
> eventually change the template to your needs
> - create a template for the windows machine defining 2 cdrom images
> (virtiodrivers and win7installdvd) and a virtio (DEV_PREFIX=vd) entry for
> WINDRIVEC
> - boot the template
> - attach console and when prompted where to install Windows you will have
> to choose "load driver" here a screenshot to help you
> http://minus.com/l7EqEC9VvJOWG
> - then you will just install it as a common vm
>
> hope this will help you to solve your WINightmare
> just my 2cents
>
>
>
>
> What could be the reason?
>
>
> [oneadmin at front ~]$ onevm list
> ID USER GROUP NAME STAT UCPU UMEM
> HOST TIME
> 51 oneadmin oneadmin myvm14 prol 0 0K nc1 0d
> 00h17
>
> [oneadmin at front ~]$ tail -f /var/log/one/51.log
> Fri Jul 18 17:51:33 2014 [DiM][I]: New VM state is ACTIVE.
> Fri Jul 18 17:51:33 2014 [LCM][I]: New VM state is PROLOG.
>
>
> *I APOLOGIZE THAT IT IS TAKING 15 EMAIL CHAINS TO UNDERSTAND & SOLVE FOR
> ME*. :-(
>
> Regards,
> Sudeep
>
>
> On Wed, Jul 16, 2014 at 7:56 PM, Lorenzo Faleschini <
> lorenzo.faleschini at nordestsystems.com> wrote:
>
>> Hi Sudeep ,
>>
>> I deal with windows machines in ONE day by day (unfortunately).
>>
>> what I can see here (a part from the raw-qcow issue) is that it seems you
>> never installed virtio-drivers (and devices) and you're trying to boot
>> using virtio bus.
>>
>> if you haven't installed in the OS (windows) the "Red Hat Virtio SCSI
>> controller" (see VirtIO drivers) you will have no luck in using virtio
>> bus.. don't use bus=virtio, use standard emulated IDE ( in the template a
>> plain IMAGE=[ID="whatever"] ) and you eventually be able to boot it.
>>
>> then if you want to convert it (the window machine) to use virtio bus,
>> you can do the following:
>>
>> 1- attach a second image as virtio device (like this:
>> IMAGE=[ID="xx",DEV_PREVIX="vd"] being "xx" any non persistent image in
>> your datastore eg: a cdrom image),
>>
>> 2- boot it (keeping your main image in IDE emulation without virtio,
>> like IMAGE=[ID="yy"] where "yy" is your vbox converted image of Win's C:
>> drive
>>
>> 3- install the newly found "unknown device" with the divers of Red Hat
>> Virtio SCSI controller from the binaries relative to your win edition in
>> the iso here:
>> http://www.linux-kvm.org/page/WindowsGuestDrivers/Download_Drivers as
>> suggested by Valentin (he's a smart guy, follow his suggestions ;) in this
>> way you will tell windows that it's now on "virtio-steroids" that is: it
>> will eventually boot from a virtio device 'cause now the controller drivers
>> are enabled at boot.
>>
>> 4- then you can shutdown vm, modify template removing the "xx" cdrom
>> image you put to install the virtio controller and edit the main image (c:
>> drive) with a string like this:
>> DISK=[AIO="native",CACHE="none",DEV_PREFIX="vd",IMAGE_ID="yy"]
>> if you find awkard slowliness try to enable default cache for virtio
>> and see if you get it any better (windows really sucks anyway.. be at peace
>> with it)
>> DISK=[AIO="native",CACHE="default",DEV_PREFIX="vd",IMAGE_ID="yy"]
>> i usually get best results with these 2 configs for images of the "best
>> OS out there"
>>
>> 5- instatiate it again... boom virtio storage will boot.
>>
>>
>> hope it helps.
>>
>> cheers
>>
>> Lorenzo Faleschini
>> IT Manager @ Nord Est Systems srl
>> ----------------------------------------
>> m: +39 335 6055225 | skype: falegalizeit
>>
>> Il 16/07/2014 13:13, Sudeep Narayan Banerjee ha scritto:
>>
>> Dear Mateusz & All,
>>
>> I tried a lot but looks like I am not able to figure out.
>>
>> Again the VM says "No bootable device" gpxe searching for bootdisk from
>> HDD/Floppy/DVD-CD" etc.
>>
>> But it is running fine from frontend mode "virt-viewer -c qemu:///system
>> myvm3"
>>
>> I tried to virtually mount the iso in the CD drive but that too did not
>> help.
>>
>> I have also tried the interactive setup: virt-install --prompt -->
>> that too does not work when I instantiate in OpenNebula VM.
>>
>> I have also tried to write the template in Advanced Tab in OpenNebula
>> following [1] but I am failing.
>>
>> [1] *http://wiki.ieeta.pt/wiki/index.php/OpenNebula#SetupComplete.cmd
>> <http://wiki.ieeta.pt/wiki/index.php/OpenNebula#SetupComplete.cmd>*
>>
>>
>> Regards,
>> Sudeep
>>
>>
>> On Wed, Jul 16, 2014 at 2:43 PM, Sudeep Narayan Banerjee <
>> snbanerjee at iitgn.ac.in> wrote:
>>
>>> Hello Mateusz,
>>>
>>> I have given now 17G for win7 OS.
>>>
>>> On adding target=hda * hdb, it throws the below error.
>>>
>>> [root at front images]# virt-install --connect qemu:///system --name win7
>>> --ram 1024 --vcpus 2 --disk
>>> path=/var/lib/libvirt/images/win7.qcow2,size=17,format=qcow2,bus=virtio,cache=none,target=hda
>>> --cdrom /home/Windows-7-x86.iso,target=hdb --vnc --os-type=windows
>>> --os-variant=win7 -noautoconsole --accelerate --noapic --keymap=en-us
>>>
>>> ERROR Unknown options ['target']
>>>
>>> Regards,
>>> Sudeep
>>>
>>>
>>>
>>> On Wed, Jul 16, 2014 at 1:57 PM, Mateusz Skała <
>>> mateusz.skala at budikom.net> wrote:
>>>
>>>>
>>>>
>>>> W dniu 2014-07-16 08:00, Sudeep Narayan Banerjee napisał(a):
>>>>
>>>> Dear Mateusz,
>>>>>
>>>>> Thanks for replying. Is the below command correct?
>>>>>
>>>>> [root at front ~]# virt-install --connect qemu:///system --name win7
>>>>> --ram 1024 --vcpus 2 --disk
>>>>>
>>>>> path=/var/lib/libvirt/images/win7.qcow2,size=7,format=qcow2,bus=virtio,cache=none
>>>>> --cdrom /home/Windows-7-x86.iso --vnc --os-type=windows
>>>>> --os-variant=win7 -noautoconsole --accelerate --noapic --keymap=en-us
>>>>>
>>>>>
>>>> try to add target=hda, for example:
>>>>
>>>> virt-install --connect qemu:///system --name win7 --ram 1024 --vcpus 2
>>>> --disk
>>>> path=/var/lib/libvirt/images/win7.qcow2,size=7,format=qcow2,bus=virtio,cache=none,target=hda
>>>> --cdrom /home/Windows-7-x86.iso,target=hdb --vnc --os-type=windows
>>>> --os-variant=win7 -noautoconsole --accelerate --noapic --keymap=en-us
>>>>
>>>> If You are using virtio then drivers for this bus will be needed, so
>>>> You need add floppy drive with drivers.
>>>>
>>>>
>>>>
>>>> The win7.qcow2 image is prepared under /var/lib/libvirt/images folder
>>>>>
>>>>> [root at front images ~]# qemu-img create -f qcow2 -o
>>>>> preallocation=metadata /var/lib/libvirt/images/win7.qcow2 7G
>>>>>
>>>>>
>>>>
>>>> Only 7G for win7 os device?
>>>>
>>>>
>>>> Or how do I tweak it?
>>>>>
>>>>> Regards,
>>>>> Sudeep
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> Thanks & Regards,
>>> Sudeep Narayan Banerjee
>>>
>>
>>
>>
>> --
>> Thanks & Regards,
>> Sudeep Narayan Banerjee
>>
>>
>> _______________________________________________
>> Users mailing listUsers at lists.opennebula.orghttp://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opennebula.org
>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>
>>
>
>
> --
> Thanks & Regards,
> Sudeep Narayan Banerjee
>
>
> Lorenzo Faleschini
> IT Manager @ Nord Est Systems srl
> ----------------------------------------
> m: +39 335 6055225 | skype: falegalizeit
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20140814/40996a29/attachment-0001.htm>
More information about the Users
mailing list