similar to: cluster of virtual machines using libvirt/kvm + Gluster

Hi, Virt-install is not working when I try to provision a vm today. Err is: -- Starting install... Retrieving file vmlinuz... | 1.9 MB 00:00 Retrieving file initrd.img... | 7.1 MB 00:00 Creating storage file... | 110 GB 00:00 ERROR POST operation failed:

I am trying to create a DomU guest domain to run snv77 over an a snv77 host, following the instructions and example in http://opensolaris.org/os/community/xen/docs/virt-install.html. I booted the xVM partition (selected xVM from the grub menu). virt-install spends 2 or 3 minutes after "Starting install ..." then fails. here''s what I get: bash-3.2# virt-install --name

Here's the procedure: # qemu-img -f qcow2 /vm/win2k3.img 8G # virt-install --connect qemu:///system -n win2k3 -r 512 --vcpus=1 -c /home/temp/win2003sp2ins.iso -f /vm/win2k3.img -s 4 --network=bridge:br0 --mac=00:ff:ff:ff:58:58 --noautoconsole --vnc --os-type=windows --os-variant=win2k3 --hvm --accelerate And I get error as below: Starting install... internal error unable to start guest: qemu:

Hi guys, I hope you can help me on this issue with kvm/libvirt: using this command to install a kvm virtual machine: virt-install --connect qemu:///system \ --name p3k0401 \ --ram 2048 \ --file //dev/VolGroup01/p3k0401logvol \ --accelerate \ -s 10 \ --nographics \ --hvm \ --location='http://10.1.4.80' I get: Starting install... Retrieving file vmlinuz... | 1.8 MB 00:00

Hi All, Im getting the following error when I run virt-install: bash-3.2# virt-install -n winxp-01 --hvm -r 384 --vnc -f /etc/opt/vms/winxp-01.img -s 16 -c /etc/opt/images/windowsXP_SP2.iso Starting install... libvir: Xen Daemon error : POST operation failed: (xend.err ''Error creating domain: vncpasswd is not set up in VMconfig and xend-config.'') Traceback (most recent call

I''m unable to create a centos domU on Opensolaris 2009.6. I had no problem following the instructions to make Solaris a dom0. The same process worked just fine with the GUI virtual machine manager under OpenSUSE 11.1. For a number of reasons I''d prefer to use Opensolaris as my Dom0, but not if it going to be a battle to get everything to work. Is Xen actually a

[This email is either empty or too large to be displayed at this time]

[This email is either empty or too large to be displayed at this time]

Hi, I try to start Solaris10 HVM DomU on SNV_93 dom0 running amd athlon x2 and 8gb ram. When I try to create a domU i get: bash-3.2# virt-install -n sol10 --hvm -r 1024 --vnc -f /dev/zvol/dsk/rpool/sol10 -c /rpool/pub/sol-10-u5-ga-x86-dvd.iso Starting install... virDomainCreateLinux() failed POST operation failed: (xend.err ''Device 0 (vif) could not be connected. Backend device not

Hi,    I''ve been using xVM with no problems since 2009.06 release (centos4/5, rhel4/5, sol10 as guests). This was using the 111a version. Just installed a new server with the 111b version and .... virt-install --nographics -p -r 8192 -n CentOS_48_64_92 -f /dev/zvol/dsk/zm0/vm/CentOS_48_64_92 -l ftp://192.168.101.120/pub/CentOS-48 -w bridge=aggr0 --os-type=linux --os-variant=rhel4

Hi, I'm trying to install a qemu-kvm virtual machine on a Debian GNU/Linux squeeze amd64 host, using virtinst 0.500.3 and libvirt 0.8.3. First I tried this command as a normal user (in groups kvm and libvirt): $ virt-install --connect qemu:///system --name test1 \ > --ram $((128 * 1024 * 1024)) --vcpus=1 --description 'Test VM 1' \ >

i'm having difficulty running KVM virtual machines off of a glusterFS volume mounted using the glusterFS client. i am running centOS 6, 64-bit. i am using virt-install to create my images but encountering the following error: qemu: could not open disk image /mnt/myreplicatestvolume/testvm.img: Invalid argument (see below for a more lengthy version of the error) i have found an example of

Nah, RHEL 5.1+ supports 32-bit domU (PAE and non PAE) on 64-bit dom0. Actually RHEL Xen is 3.1 with the brain damaged 3.0 userland utilities. -Ross ----- Original Message ----- From: centos-bounces at centos.org <centos-bounces at centos.org> To: CentOS mailing list <centos at centos.org> Sent: Fri Feb 29 04:46:42 2008 Subject: Re: [CentOS] error creating Centos 5.1 x32 dum_U

Nah, RHEL 5.1+ supports 32-bit domU (PAE and non PAE) on 64-bit dom0. Actually RHEL Xen is 3.1 with the brain damaged 3.0 userland utilities. -Ross ----- Original Message ----- From: centos-bounces at centos.org <centos-bounces at centos.org> To: CentOS mailing list <centos at centos.org> Sent: Fri Feb 29 04:46:42 2008 Subject: Re: [CentOS] error creating Centos 5.1 x32 dum_U

Hi, I just installed a pv-ops Dom0 2.6.32.27 Kernel on a 64 bit non VT machine. Following instructions here http://wiki.xensource.com/xenwiki/Xen4.0 for 64 bit Ubuntu 10.04 apt-get install bcc bin86 gawk bridge-utils iproute libcurl3 libcurl4-openssl-dev bzip2 module-init-tools transfig tgif texinfo texlive-latex-base texlive-latex-recommended texlive-fonts-extra texlive-fonts-recommended

Hi there, I've been happily installing VMs in CentOS 5.2's Xen implementation using virt-manager. However, my latest attempt to use the install wizard in virt-manager failed when I got to the networking screen. The 'forward' button was unresponsive, and I was unable to proceed. I checked the virt-manager logs, and saw this appearing immediately after I tried to proceed:

Hi, I have been trying to get Xen 3.1 running on Fedora 7 since yesterday and no luck. At the beginning I thought it was a problem with teh installation of Fedora 7 so I reinstalled it. Still, I have the same problem. I have never had this problem with Xen (FC5,FC6). The xend.log (below) includes a line "VmError: Device 0 (vif) could not be connected. Hotplug scripts not working."

Hi all, I used "net-define" to create a network to use to attach VMs to an Open vSwitch bridge. The net-define worked fine, I can see the network in "net-list" (I set it to started and to autostart) but when I try to attach a new VM's NIC to this network (via virt-manager), I'm getting the following traceback: Unable to complete install: 'Unable to add bridge

Hi, After full new install of Fedora 19 or 20, I am getting this when I want to create a new VMs. Impossible de terminer l'installation : « Unable to create vcpu cgroup for fedora20(vcpu: 0): Aucun fichier ou dossier de ce type » Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in cb_wrapper callback(asyncjob, *args,

Anyone knows if this is something that will be looked at before b134 is released? Bug 13743 - virsh and xm is unable to start domain first time after boot http://defect.opensolaris.org/bz/show_bug.cgi?id=13743 Regards Henrik http://sparcv9.blogspot.com