Dear Mateusz,
Thanks for replying. Is the below command correct?
[root@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
Hello Mateusz,
I have given now 17G for win7 OS.
On adding target=hda * hdb, it throws the below error.
[root@front images]# virt-install --connect qemu:///system --name win7
--ram 1024 --vcpus 2 --disk
Dear OpenNebula community,
The EU CloudCatalyst http://cloudcatalyst.eu/ initiative invites you to
participate in a survey about cloud computing trends. You can influence
over the CloudCatalyst project by collaborating on the identification of
existing challenges for Cloud expansion as well as on
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
Hi,
I'm trying to setup vdc admin acl's. He should have rights to create
vm's from his image's and templates. I setup group (first-group) and
admin (first-group-admin) for this group, next i set acls:
Applies to Affected resources Resource ID / Owned
by Allowed
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
Hello,
We would like to create a few templates with persistent images so they
can be shared with a group of users, so then users can provision new
VM's, each having its own VM with persistent image. The persistent image
is bacause we want that VM's be users personal VM's (aka desktops).
But if
