search for: f20vm

...s -rw-rw-rwx 1 root root 12884901888 14 juin 23:07 /home/kvmimages/eff1.img -rw-rw-rwx 1 root root 12884901888 14 juin 23:11 /home/kvmimages/eff2.img -rw----r-x 1 root root 12887130112 11 juin 15:51 /home/kvmimages/effi.qcow2 -rw-r--r-- 1 root root 4295884800 15 juin 09:19 /home/kvmimages/f20vm -rw-r--r-x 1 qemu qemu 4603248640 12 déc. 2013 /home/kvmimages/Fedora-20-x86_64-DVD.iso As you can see, all are executabled by others. Should I chown to qemu? or something else? Patrick Le 15/06/2014 11:32, Kashyap Chamarthy a écrit : > On Sun, Jun 15, 2014 at 10:27:12AM +0300, Patrick C...

Sorry for posting bad debug info. Here are the right one with the chardev error only: # virt-install --name f20vm --disk /home/kvmimages/f20vm --cdrom /home/kvmimages/Fedora-20-x86_64-DVD.iso --memory 2048 -d [dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (cli:187) Launched with command line: /usr/share/virt-manager/virt-install --name f20vm --disk /home/kvmimages/f20vm --cdrom /home/kvmimages/Fedor...

...ed to create chardev when trying to run a Vms that run on my local Fedora 20 computer. Any idea? Thanks Patrick Le 15/06/2014 11:57, Patrick Chemla a écrit : > > Sorry for posting bad debug info. > > Here are the right one with the chardev error only: > > # virt-install --name f20vm --disk /home/kvmimages/f20vm --cdrom > /home/kvmimages/Fedora-20-x86_64-DVD.iso --memory 2048 -d > [dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (cli:187) > Launched with command line: /usr/share/virt-manager/virt-install > --name f20vm --disk /home/kvmimages/f20vm --cdrom &...

Hi, It it can help, I run virt-install with -d option # virt-install --name f20vm --disk /home/kvmimages/f20vm --cdrom /home/kvmimages/Fedora-20-x86_64-DVD.iso --memory 2048 -d [dim., 15 juin 2014 10:45:15 virt-install 9074] DEBUG (cli:187) Launched with command line: /usr/share/virt-manager/virt-install --name f20vm --disk /home/kvmimages/f20vm --cdrom /home/kvmimages/Fedor...

...eate chardev Rpm: infos # rpm -q virt-install libvirt-daemon-kvm qemu-system-x86 virt-install-1.0.1-3.fc20.noarch libvirt-daemon-kvm-1.1.3.5-2.fc20.x86_64 qemu-system-x86-1.6.2-6.fc20.x86_64 I adapted your commands to my conf: # qemu-img create -f qcow2 -o preallocation=metadata /home/kvmimages/f20vm 4G Formatting '/home/kvmimages/f20vm', fmt=qcow2 size=4294967296 encryption=off cluster_size=65536 preallocation='metadata' lazy_refcounts=off # virt-install --name f20vm --disk /home/kvmimages/f20vm --cdrom /home/kvmimages/Fedora-20-x86_64-DVD.iso --memory 2048 WARNING CDROM me...

On Sun, Jun 15, 2014 at 10:27:12AM +0300, Patrick Chemla wrote: [. . .] > I adapted your commands to my conf: > > # qemu-img create -f qcow2 -o preallocation=metadata /home/kvmimages/f20vm > 4G > Formatting '/home/kvmimages/f20vm', fmt=qcow2 size=4294967296 encryption=off > cluster_size=65536 preallocation='metadata' lazy_refcounts=off > # virt-install --name f20vm --disk /home/kvmimages/f20vm --cdrom > /home/kvmimages/Fedora-20-x86_64-DVD.iso --memory...

Morning, I have a KVM guest running Win 2012 with MS SQL 2012. In order to provide a quick method of restoring the service should the live server die, we've decided to clone it to a preserved state. Ideally, this clone should also be kept up to date and cloning should be done on a regular basis. Is there any reason not to do unattended cloning? As in, when I leave on a Friday afternoon,

...; After full new install of Fedora 19 or 20, I am getting this when I want to >> create a new VMs. > FWIW, I'm able to create new unattended Fedora 20 VMs just fine with a > script like that[1] which uses virt-install. To invoke the script: > > $ ./create-guest-qcow2.bash f20vm1 f20 x86_64 > > > Or you can try trivially install guests with a tool like virt-builder. > To install a Fedora 20 guest and update to latest available packages: > > $ virt-builder fedora-20 -o f20vm1.qcow2 --update --selinux-relabel \ > --format qcow2 --size 30G &gt...