[libvirt-users] Fedora 19/20 new install :Unable to create vcpu cgroup
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, **kwargs) File "/usr/share/virt-manager/virtManager/create.py", line 1787, in do_install guest.start_install(meter=meter) File "/usr/share/virt-manager/virtinst/guest.py", line 403, in start_install noboot) File "/usr/share/virt-manager/virtinst/guest.py", line 467, in _create_guest dom = self.conn.createLinux(start_xml or final_xml, 0) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2897, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: Unable to create vcpu cgroup for fedora20(vcpu: 0): Aucun fichier ou dossier de ce type I saw that there is no cpu mounted, only cpuacct. I saw on other server that cpu is a link to cpu,cpuacct But I can't find how to add this in a config file Thanks for help Patrick
On Thu, Jun 12, 2014 at 01:01:18PM +0300, Patrick Chemla wrote:
Hi,
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 Import the guest into libvirt: $ virt-install --name f20vm1 --ram 2048 --disk \ path=/home/kashyap/f20vm1.qcow2,format=qcow2 --import [1] https://github.com/kashyapc/virt-scripts/blob/master/create-guest-qcow2.bash
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, **kwargs) File "/usr/share/virt-manager/virtManager/create.py", line 1787, in do_install guest.start_install(meter=meter) File "/usr/share/virt-manager/virtinst/guest.py", line 403, in start_install noboot) File "/usr/share/virt-manager/virtinst/guest.py", line 467, in _create_guest dom = self.conn.createLinux(start_xml or final_xml, 0) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2897, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: Unable to create vcpu cgroup for fedora20(vcpu: 0): Aucun fichier ou dossier de ce type
I saw that there is no cpu mounted, only cpuacct.
I saw on other server that cpu is a link to cpu,cpuacct
But I can't find how to add this in a config file
Thanks for help Patrick
_______________________________________________ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
-- /kashyap
Hi I have reinstall Fedora 20 from distrib. I have run yum update and yum upgrade. Running kernel is : 3.14.7-200.fc20.x86_64 Installed Libvirt packages are: libvirt-client-1.1.3.5-2.fc20.x86_64 libvirt-daemon-1.1.3.5-2.fc20.x86_64 libvirt-daemon-config-network-1.1.3.5-2.fc20.x86_64 libvirt-daemon-driver-interface-1.1.3.5-2.fc20.x86_64 libvirt-daemon-driver-network-1.1.3.5-2.fc20.x86_64 libvirt-daemon-driver-nodedev-1.1.3.5-2.fc20.x86_64 libvirt-daemon-driver-nwfilter-1.1.3.5-2.fc20.x86_64 libvirt-daemon-driver-qemu-1.1.3.5-2.fc20.x86_64 libvirt-daemon-driver-secret-1.1.3.5-2.fc20.x86_64 libvirt-daemon-driver-storage-1.1.3.5-2.fc20.x86_64 libvirt-daemon-kvm-1.1.3.5-2.fc20.x86_64 libvirt-glib-0.1.7-2.fc20.x86_64 libvirt-python-1.1.3.5-2.fc20.x86_64 When trying to create a new VM using virt-manager I am getting : Impossible de terminer l'installation : « internal error: process exited while connecting to monitor: Failed to create chardev » Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/create.py", line 1787, in do_install guest.start_install(meter=meter) File "/usr/share/virt-manager/virtinst/guest.py", line 403, in start_install noboot) File "/usr/share/virt-manager/virtinst/guest.py", line 467, in _create_guest dom = self.conn.createLinux(start_xml or final_xml, 0) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2897, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error: process exited while connecting to monitor: Failed to create chardev When tyring to create new VM with virt-install, I am getting: virt-install --name eff1 --disk /home/kvmimages/eff1.img --cdrom /home/kvmimages/Fedora-20-x86_64-DVD.iso --memory 4096B ERROR Error: --memory 4096B: invalid literal for int() with base 10: '4096B' [root@eff1 kvmimages]# virt-install --name eff1 --disk /home/kvmimages/eff1.img --cdrom /home/kvmimages/Fedora-20-x86_64-DVD.iso --memory 4096 WARNING CDROM media does not print to the text console by default, so you likely will not see text install output. You might want to use --location. Début d'installation... ERROR internal error: process exited while connecting to monitor: Failed to create chardev When trying to run with virt-manager a VM created on another F20 server: Erreur lors du démarrage du domaine: internal error: process exited while connecting to monitor: Failed to create chardev Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 127, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/domain.py", line 1355, in startup self._backend.create() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 708, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: internal error: process exited while connecting to monitor: Failed to create chardev What is this chardev error? May someone help. Thanks Patrick Le 12/06/2014 19:06, Kashyap Chamarthy a écrit :
Hi,
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
On Thu, Jun 12, 2014 at 01:01:18PM +0300, Patrick Chemla wrote: 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
Import the guest into libvirt:
$ virt-install --name f20vm1 --ram 2048 --disk \ path=/home/kashyap/f20vm1.qcow2,format=qcow2 --import
[1] https://github.com/kashyapc/virt-scripts/blob/master/create-guest-qcow2.bash
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, **kwargs) File "/usr/share/virt-manager/virtManager/create.py", line 1787, in do_install guest.start_install(meter=meter) File "/usr/share/virt-manager/virtinst/guest.py", line 403, in start_install noboot) File "/usr/share/virt-manager/virtinst/guest.py", line 467, in _create_guest dom = self.conn.createLinux(start_xml or final_xml, 0) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2897, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: Unable to create vcpu cgroup for fedora20(vcpu: 0): Aucun fichier ou dossier de ce type
I saw that there is no cpu mounted, only cpuacct.
I saw on other server that cpu is a link to cpu,cpuacct
But I can't find how to add this in a config file
Thanks for help Patrick
_______________________________________________ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
On Sun, Jun 15, 2014 at 09:01:29AM +0300, Patrick Chemla wrote: [. . .]
When trying to create a new VM using virt-manager I am getting :
Impossible de terminer l'installation : « internal error: process exited while connecting to monitor: Failed to create chardev »
Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/create.py", line 1787, in do_install guest.start_install(meter=meter) File "/usr/share/virt-manager/virtinst/guest.py", line 403, in start_install noboot) File "/usr/share/virt-manager/virtinst/guest.py", line 467, in _create_guest dom = self.conn.createLinux(start_xml or final_xml, 0) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2897, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error: process exited while connecting to monitor: Failed to create chardev
When tyring to create new VM with virt-install, I am getting:
virt-install --name eff1 --disk /home/kvmimages/eff1.img --cdrom /home/kvmimages/Fedora-20-x86_64-DVD.iso --memory 4096B ERROR Error: --memory 4096B: invalid literal for int() with base 10: '4096B'
This is an invalid invocation.
[root@eff1 kvmimages]# virt-install --name eff1 --disk /home/kvmimages/eff1.img --cdrom /home/kvmimages/Fedora-20-x86_64-DVD.iso --memory 4096 WARNING CDROM media does not print to the text console by default, so you likely will not see text install output. You might want to use --location.
Début d'installation... ERROR internal error: process exited while connecting to monitor: Failed to create chardev
I just tested on my Fedora-20 machine, trying to boot a Fedora-19 VM it works for me: $ qemu-img create -f qcow2 -o preallocation=metadata \ /export/vmimages/f19vm 4G $ virt-install --name f19vm --disk /export/vmimages/f19vm \ --cdrom /export/Fedora-Live-Desktop-x86_64-19-1.iso \ --memory 2048 Starting install... Creating domain... . . . But, I should mention that I'm using virt packages from Rawhide: $ rpm -q virt-install libvirt-daemon-kvm qemu-system-x86 virt-install-1.0.1-3.fc21.noarch libvirt-daemon-kvm-1.2.6-1.fc20.x86_64 qemu-system-x86-2.0.0-1.fc21.x86_64
When trying to run with virt-manager a VM created on another F20 server:
Erreur lors du démarrage du domaine: internal error: process exited while connecting to monitor: Failed to create chardev
Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 127, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/domain.py", line 1355, in startup self._backend.create() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 708, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: internal error: process exited while connecting to monitor: Failed to create chardev
What is this chardev error?
Ensure you have correct permissions to allow QEMU to access disk images in your $HOME directory: $ chmod o+rx $HOME I guess that should resolve it. -- /kashyap
Hi, Thanks Kashyap for your answer. I am trying to give more data: virt-install invokation: # virt-install --name eff1 --disk /home/kvmimages/eff1.img --cdrom /home/kvmimages/Fedora-20-x86_64-DVD.iso --memory 4096 WARNING CDROM media does not print to the text console by default, so you likely will not see text install output. You might want to use --location. Début d'installation... ERROR internal error: process exited while connecting to monitor: Failed to create 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 media does not print to the text console by default, so you likely will not see text install output. You might want to use --location. Début d'installation... ERROR internal error: process exited while connecting to monitor: Failed to create chardev L'installation du domaine ne semble pas s'être terminée avec succès. Si c'est bon, vous pouvez démarrer le domaine en lançant : virsh --connect qemu:///system start f20vm sinon, recommencez l'installation. Always the same Failed to create chardev. I do think it's a problem of permission as you said, but on which directory/files? I am connected as root on my remote server, as simple user on my local computer. Both are running F20. When I create/run a F20 VM on my local computer, it's OK. I have verified rpm versions, seem OK. I have rsynced /etc/libvirt dir from local computer to remote server. It works on my local like on yours,but not on my remote. I need the remote to run VMs. Thanks for your help. Patrick Le 15/06/2014 09:51, Kashyap Chamarthy a écrit :
On Sun, Jun 15, 2014 at 09:01:29AM +0300, Patrick Chemla wrote:
[. . .]
When trying to create a new VM using virt-manager I am getting :
Impossible de terminer l'installation : « internal error: process exited while connecting to monitor: Failed to create chardev »
Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/create.py", line 1787, in do_install guest.start_install(meter=meter) File "/usr/share/virt-manager/virtinst/guest.py", line 403, in start_install noboot) File "/usr/share/virt-manager/virtinst/guest.py", line 467, in _create_guest dom = self.conn.createLinux(start_xml or final_xml, 0) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2897, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error: process exited while connecting to monitor: Failed to create chardev
When tyring to create new VM with virt-install, I am getting:
virt-install --name eff1 --disk /home/kvmimages/eff1.img --cdrom /home/kvmimages/Fedora-20-x86_64-DVD.iso --memory 4096B ERROR Error: --memory 4096B: invalid literal for int() with base 10: '4096B' This is an invalid invocation.
[root@eff1 kvmimages]# virt-install --name eff1 --disk /home/kvmimages/eff1.img --cdrom /home/kvmimages/Fedora-20-x86_64-DVD.iso --memory 4096 WARNING CDROM media does not print to the text console by default, so you likely will not see text install output. You might want to use --location.
Début d'installation... ERROR internal error: process exited while connecting to monitor: Failed to create chardev I just tested on my Fedora-20 machine, trying to boot a Fedora-19 VM it works for me:
$ qemu-img create -f qcow2 -o preallocation=metadata \ /export/vmimages/f19vm 4G
$ virt-install --name f19vm --disk /export/vmimages/f19vm \ --cdrom /export/Fedora-Live-Desktop-x86_64-19-1.iso \ --memory 2048
Starting install... Creating domain... . . .
But, I should mention that I'm using virt packages from Rawhide:
$ rpm -q virt-install libvirt-daemon-kvm qemu-system-x86 virt-install-1.0.1-3.fc21.noarch libvirt-daemon-kvm-1.2.6-1.fc20.x86_64 qemu-system-x86-2.0.0-1.fc21.x86_64
When trying to run with virt-manager a VM created on another F20 server:
Erreur lors du démarrage du domaine: internal error: process exited while connecting to monitor: Failed to create chardev
Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 127, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/domain.py", line 1355, in startup self._backend.create() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 708, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: internal error: process exited while connecting to monitor: Failed to create chardev
What is this chardev error? Ensure you have correct permissions to allow QEMU to access disk images in your $HOME directory:
$ chmod o+rx $HOME
I guess that should resolve it.
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 2048 WARNING CDROM media does not print to the text console by default, so you likely will not see text install output. You might want to use --location.
Début d'installation... ERROR internal error: process exited while connecting to monitor: Failed to create chardev
L'installation du domaine ne semble pas s'être terminée avec succès. Si c'est bon, vous pouvez démarrer le domaine en lançant : virsh --connect qemu:///system start f20vm sinon, recommencez l'installation.
Always the same Failed to create chardev.
I do think it's a problem of permission as you said, but on which directory/files?
Wherever your disk image is located (/home/kvmimages) QEMU should be able to access it (executable bit for 'others'). For instance, I have these permissions for my home directory where I store VM images: $ ls -lash / | grep home 4.0K drwxr-xr-x. 7 root root 4.0K Aug 7 2013 home Permissions on the specific directory where I store VM images (/home/kashyap/vmimages): $ ls -lash /home/kashyap/ | grep vmimages 4.0K drwxrwxr-x. 2 kashyap kashyap 4.0K Jun 14 21:50 vmimages
When I create/run a F20 VM on my local computer, it's OK. I have verified rpm versions, seem OK. I have rsynced /etc/libvirt dir from local computer to remote server.
It works on my local like on yours,but not on my remote. I need the remote to run VMs.
If I'm parsing you correctly, you've SSHed into the remote machine and running virt-install. Like I said, if QEMU can access your home directory (as I noted above), where you're storing disk images, you shouldn't have any issues. -- /kashyap
Thanks for your interest. Here are the dir/files permissions for the kvmimages dir: # ls -ld /home /home/kvmimages /home/kvmimages/* drwxr-xr-x. 4 root root 4096 14 juin 23:05 /home drwxrwxrwx 2 root root 4096 15 juin 09:19 /home/kvmimages -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 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 2048 WARNING CDROM media does not print to the text console by default, so you likely will not see text install output. You might want to use --location.
Début d'installation... ERROR internal error: process exited while connecting to monitor: Failed to create chardev
L'installation du domaine ne semble pas s'être terminée avec succès. Si c'est bon, vous pouvez démarrer le domaine en lançant : virsh --connect qemu:///system start f20vm sinon, recommencez l'installation.
Always the same Failed to create chardev.
I do think it's a problem of permission as you said, but on which directory/files? Wherever your disk image is located (/home/kvmimages) QEMU should be able to access it (executable bit for 'others'). For instance, I have these permissions for my home directory where I store VM images:
$ ls -lash / | grep home 4.0K drwxr-xr-x. 7 root root 4.0K Aug 7 2013 home
Permissions on the specific directory where I store VM images (/home/kashyap/vmimages):
$ ls -lash /home/kashyap/ | grep vmimages 4.0K drwxrwxr-x. 2 kashyap kashyap 4.0K Jun 14 21:50 vmimages
When I create/run a F20 VM on my local computer, it's OK. I have verified rpm versions, seem OK. I have rsynced /etc/libvirt dir from local computer to remote server.
It works on my local like on yours,but not on my remote. I need the remote to run VMs. If I'm parsing you correctly, you've SSHed into the remote machine and running virt-install. Like I said, if QEMU can access your home directory (as I noted above), where you're storing disk images, you shouldn't have any issues.
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/Fedora-20-x86_64-DVD.iso --memory 2048 -d [dim., 15 juin 2014 10:45:15 virt-install 9074] DEBUG (cli:195) Requesting libvirt URI default [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (cli:199) Received libvirt URI qemu:///system [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (virt-install:193) Requesting virt method 'Par défaut', hv type 'Par défaut'. [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (virt-install:432) Received virt method 'kvm' [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (virt-install:433) Hypervisor name is 'hvm' [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (cli:476) DISPLAY is not set: defaulting to nographics. [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (pollhelpers:36) Unable to list all volumes: Requested operation is not valid: storage pool 'gnome-boxes' is not active [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (pollhelpers:36) Unable to list all volumes: Requested operation is not valid: storage pool 'Téléchargements' is not active [dim., 15 juin 2014 10:45:16 virt-install 9074] WARNING (virt-install:343) CDROM media does not print to the text console by default, so you likely will not see text install output. You might want to use --location. [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (virt-install:551) Guest.has_install_phase: True Début d'installation... [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (distroinstaller:417) Using scratchdir=/var/lib/libvirt/boot [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (guest:449) Generated install XML: <domain type="kvm"> <name>f20vm</name> <uuid>4ce6b5f5-ed0f-48fa-8d8f-1dc846940f21</uuid> <memory>2097152</memory> <currentMemory>2097152</currentMemory> <vcpu>1</vcpu> <os> <type arch="x86_64">hvm</type> <boot dev="cdrom"/> <boot dev="hd"/> </os> <features> <acpi/> <apic/> <pae/> </features> <cpu mode="custom" match="exact"> <model>SandyBridge</model> </cpu> <clock offset="utc"> <timer name="rtc" tickpolicy="catchup"/> <timer name="pit" tickpolicy="delay"/> <timer name="hpet" present="no"/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>destroy</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-kvm</emulator> <disk type="file" device="disk"> <driver name="qemu" type="qcow2"/> <source file="/home/kvmimages/f20vm"/> <target dev="hda" bus="ide"/> </disk> <disk type="file" device="cdrom"> <driver name="qemu" type="raw"/> <source file="/home/kvmimages/Fedora-20-x86_64-DVD.iso"/> <target dev="hdb" bus="ide"/> <readonly/> </disk> <controller type="usb" index="0" model="ich9-ehci1"/> <controller type="usb" index="0" model="ich9-uhci1"> <master startport="0"/> </controller> <controller type="usb" index="0" model="ich9-uhci2"> <master startport="2"/> </controller> <controller type="usb" index="0" model="ich9-uhci3"> <master startport="4"/> </controller> <interface type="network"> <source network="default"/> <mac address="52:54:00:83:bb:cb"/> </interface> <input type="mouse" bus="ps2"/> <console type="pty"/> </devices> </domain> [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (guest:450) Generated boot XML: <domain type="kvm"> <name>f20vm</name> <uuid>4ce6b5f5-ed0f-48fa-8d8f-1dc846940f21</uuid> <memory>2097152</memory> <currentMemory>2097152</currentMemory> <vcpu>1</vcpu> <os> <type arch="x86_64">hvm</type> <boot dev="hd"/> </os> <features> <acpi/> <apic/> <pae/> </features> <cpu mode="custom" match="exact"> <model>SandyBridge</model> </cpu> <clock offset="utc"> <timer name="rtc" tickpolicy="catchup"/> <timer name="pit" tickpolicy="delay"/> <timer name="hpet" present="no"/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-kvm</emulator> <disk type="file" device="disk"> <driver name="qemu" type="qcow2"/> <source file="/home/kvmimages/f20vm"/> <target dev="hda" bus="ide"/> </disk> <disk type="block" device="cdrom"> <target dev="hdb" bus="ide"/> <readonly/> </disk> <controller type="usb" index="0" model="ich9-ehci1"/> <controller type="usb" index="0" model="ich9-uhci1"> <master startport="0"/> </controller> <controller type="usb" index="0" model="ich9-uhci2"> <master startport="2"/> </controller> <controller type="usb" index="0" model="ich9-uhci3"> <master startport="4"/> </controller> <interface type="network"> <source network="default"/> <mac address="52:54:00:83:bb:cb"/> </interface> <input type="mouse" bus="ps2"/> <console type="pty"/> </devices> </domain> [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (cli:234) File "/usr/share/virt-manager/virt-install", line 876, in <module> sys.exit(main()) File "/usr/share/virt-manager/virt-install", line 870, in main start_install(guest, continue_inst, options) File "/usr/share/virt-manager/virt-install", line 588, in start_install fail(e, do_exit=False) File "/usr/share/virt-manager/virtinst/cli.py", line 234, in fail logging.debug("".join(traceback.format_stack())) [dim., 15 juin 2014 10:45:16 virt-install 9074] ERROR (cli:235) internal error: process exited while connecting to monitor: Failed to create chardev [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (cli:237) Traceback (most recent call last): File "/usr/share/virt-manager/virt-install", line 560, in start_install dom = guest.start_install(meter=meter, noboot=options.noreboot) File "/usr/share/virt-manager/virtinst/guest.py", line 403, in start_install noboot) File "/usr/share/virt-manager/virtinst/guest.py", line 467, in _create_guest dom = self.conn.createLinux(start_xml or final_xml, 0) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2897, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error: process exited while connecting to monitor: Failed to create chardev [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (cli:248) L'installation du domaine ne semble pas s'être terminée avec succès. Si c'est bon, vous pouvez démarrer le domaine en lançant : virsh --connect qemu:///system start f20vm sinon, recommencez l'installation. L'installation du domaine ne semble pas s'être terminée avec succès. Si c'est bon, vous pouvez démarrer le domaine en lançant : virsh --connect qemu:///system start f20vm sinon, recommencez l'installation. Le 15/06/2014 11:41, Patrick Chemla a écrit :
Thanks for your interest.
Here are the dir/files permissions for the kvmimages dir:
# ls -ld /home /home/kvmimages /home/kvmimages/* drwxr-xr-x. 4 root root 4096 14 juin 23:05 /home drwxrwxrwx 2 root root 4096 15 juin 09:19 /home/kvmimages -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 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 2048 WARNING CDROM media does not print to the text console by default, so you likely will not see text install output. You might want to use --location.
Début d'installation... ERROR internal error: process exited while connecting to monitor: Failed to create chardev
L'installation du domaine ne semble pas s'être terminée avec succès. Si c'est bon, vous pouvez démarrer le domaine en lançant : virsh --connect qemu:///system start f20vm sinon, recommencez l'installation.
Always the same Failed to create chardev.
I do think it's a problem of permission as you said, but on which directory/files? Wherever your disk image is located (/home/kvmimages) QEMU should be able to access it (executable bit for 'others'). For instance, I have these permissions for my home directory where I store VM images:
$ ls -lash / | grep home 4.0K drwxr-xr-x. 7 root root 4.0K Aug 7 2013 home
Permissions on the specific directory where I store VM images (/home/kashyap/vmimages):
$ ls -lash /home/kashyap/ | grep vmimages 4.0K drwxrwxr-x. 2 kashyap kashyap 4.0K Jun 14 21:50 vmimages
When I create/run a F20 VM on my local computer, it's OK. I have verified rpm versions, seem OK. I have rsynced /etc/libvirt dir from local computer to remote server.
It works on my local like on yours,but not on my remote. I need the remote to run VMs. If I'm parsing you correctly, you've SSHed into the remote machine and running virt-install. Like I said, if QEMU can access your home directory (as I noted above), where you're storing disk images, you shouldn't have any issues.
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/Fedora-20-x86_64-DVD.iso --memory 2048 -d [dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (cli:195) Requesting libvirt URI default [dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (cli:199) Received libvirt URI qemu:///system [dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (virt-install:193) Requesting virt method 'Par défaut', hv type 'Par défaut'. [dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (virt-install:432) Received virt method 'kvm' [dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (virt-install:433) Hypervisor name is 'hvm' [dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (cli:476) DISPLAY is not set: defaulting to nographics. [dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (pollhelpers:36) Unable to list all volumes: Requested operation is not valid: storage pool 'gnome-boxes' is not active [dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (pollhelpers:36) Unable to list all volumes: Requested operation is not valid: storage pool 'Téléchargements' is not active [dim., 15 juin 2014 10:56:25 virt-install 9795] WARNING (virt-install:343) CDROM media does not print to the text console by default, so you likely will not see text install output. You might want to use --location. [dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (virt-install:551) Guest.has_install_phase: True Début d'installation... [dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (distroinstaller:417) Using scratchdir=/var/lib/libvirt/boot [dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (guest:449) Generated install XML: <domain type="kvm"> <name>f20vm</name> <uuid>2da45a47-cf6c-4564-9608-52b71d4513f0</uuid> <memory>2097152</memory> <currentMemory>2097152</currentMemory> <vcpu>1</vcpu> <os> <type arch="x86_64">hvm</type> <boot dev="cdrom"/> <boot dev="hd"/> </os> <features> <acpi/> <apic/> <pae/> </features> <cpu mode="custom" match="exact"> <model>SandyBridge</model> </cpu> <clock offset="utc"> <timer name="rtc" tickpolicy="catchup"/> <timer name="pit" tickpolicy="delay"/> <timer name="hpet" present="no"/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>destroy</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-kvm</emulator> <disk type="file" device="disk"> <driver name="qemu" type="qcow2"/> <source file="/home/kvmimages/f20vm"/> <target dev="hda" bus="ide"/> </disk> <disk type="file" device="cdrom"> <driver name="qemu" type="raw"/> <source file="/home/kvmimages/Fedora-20-x86_64-DVD.iso"/> <target dev="hdb" bus="ide"/> <readonly/> </disk> <controller type="usb" index="0" model="ich9-ehci1"/> <controller type="usb" index="0" model="ich9-uhci1"> <master startport="0"/> </controller> <controller type="usb" index="0" model="ich9-uhci2"> <master startport="2"/> </controller> <controller type="usb" index="0" model="ich9-uhci3"> <master startport="4"/> </controller> <interface type="network"> <source network="default"/> <mac address="52:54:00:1d:e0:eb"/> </interface> <input type="mouse" bus="ps2"/> <console type="pty"/> </devices> </domain> [dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (guest:450) Generated boot XML: <domain type="kvm"> <name>f20vm</name> <uuid>2da45a47-cf6c-4564-9608-52b71d4513f0</uuid> <memory>2097152</memory> <currentMemory>2097152</currentMemory> <vcpu>1</vcpu> <os> <type arch="x86_64">hvm</type> <boot dev="hd"/> </os> <features> <acpi/> <apic/> <pae/> </features> <cpu mode="custom" match="exact"> <model>SandyBridge</model> </cpu> <clock offset="utc"> <timer name="rtc" tickpolicy="catchup"/> <timer name="pit" tickpolicy="delay"/> <timer name="hpet" present="no"/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-kvm</emulator> <disk type="file" device="disk"> <driver name="qemu" type="qcow2"/> <source file="/home/kvmimages/f20vm"/> <target dev="hda" bus="ide"/> </disk> <disk type="block" device="cdrom"> <target dev="hdb" bus="ide"/> <readonly/> </disk> <controller type="usb" index="0" model="ich9-ehci1"/> <controller type="usb" index="0" model="ich9-uhci1"> <master startport="0"/> </controller> <controller type="usb" index="0" model="ich9-uhci2"> <master startport="2"/> </controller> <controller type="usb" index="0" model="ich9-uhci3"> <master startport="4"/> </controller> <interface type="network"> <source network="default"/> <mac address="52:54:00:1d:e0:eb"/> </interface> <input type="mouse" bus="ps2"/> <console type="pty"/> </devices> </domain> [dim., 15 juin 2014 10:56:26 virt-install 9795] DEBUG (cli:234) File "/usr/share/virt-manager/virt-install", line 876, in <module> sys.exit(main()) File "/usr/share/virt-manager/virt-install", line 870, in main start_install(guest, continue_inst, options) File "/usr/share/virt-manager/virt-install", line 588, in start_install fail(e, do_exit=False) File "/usr/share/virt-manager/virtinst/cli.py", line 234, in fail logging.debug("".join(traceback.format_stack())) [dim., 15 juin 2014 10:56:26 virt-install 9795] ERROR (cli:235) internal error: process exited while connecting to monitor: Failed to create chardev [dim., 15 juin 2014 10:56:26 virt-install 9795] DEBUG (cli:237) Traceback (most recent call last): File "/usr/share/virt-manager/virt-install", line 560, in start_install dom = guest.start_install(meter=meter, noboot=options.noreboot) File "/usr/share/virt-manager/virtinst/guest.py", line 403, in start_install noboot) File "/usr/share/virt-manager/virtinst/guest.py", line 467, in _create_guest dom = self.conn.createLinux(start_xml or final_xml, 0) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2897, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error: process exited while connecting to monitor: Failed to create chardev [dim., 15 juin 2014 10:56:26 virt-install 9795] DEBUG (cli:248) L'installation du domaine ne semble pas s'être terminée avec succès. Si c'est bon, vous pouvez démarrer le domaine en lançant : virsh --connect qemu:///system start f20vm sinon, recommencez l'installation. L'installation du domaine ne semble pas s'être terminée avec succès. Si c'est bon, vous pouvez démarrer le domaine en lançant : virsh --connect qemu:///system start f20vm sinon, recommencez l'installation. Le 15/06/2014 11:46, Patrick Chemla a écrit :
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/Fedora-20-x86_64-DVD.iso --memory 2048 -d [dim., 15 juin 2014 10:45:15 virt-install 9074] DEBUG (cli:195) Requesting libvirt URI default [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (cli:199) Received libvirt URI qemu:///system [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (virt-install:193) Requesting virt method 'Par défaut', hv type 'Par défaut'. [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (virt-install:432) Received virt method 'kvm' [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (virt-install:433) Hypervisor name is 'hvm' [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (cli:476) DISPLAY is not set: defaulting to nographics. [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (pollhelpers:36) Unable to list all volumes: Requested operation is not valid: storage pool 'gnome-boxes' is not active [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (pollhelpers:36) Unable to list all volumes: Requested operation is not valid: storage pool 'Téléchargements' is not active [dim., 15 juin 2014 10:45:16 virt-install 9074] WARNING (virt-install:343) CDROM media does not print to the text console by default, so you likely will not see text install output. You might want to use --location. [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (virt-install:551) Guest.has_install_phase: True
Début d'installation... [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (distroinstaller:417) Using scratchdir=/var/lib/libvirt/boot [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (guest:449) Generated install XML: <domain type="kvm"> <name>f20vm</name> <uuid>4ce6b5f5-ed0f-48fa-8d8f-1dc846940f21</uuid> <memory>2097152</memory> <currentMemory>2097152</currentMemory> <vcpu>1</vcpu> <os> <type arch="x86_64">hvm</type> <boot dev="cdrom"/> <boot dev="hd"/> </os> <features> <acpi/> <apic/> <pae/> </features> <cpu mode="custom" match="exact"> <model>SandyBridge</model> </cpu> <clock offset="utc"> <timer name="rtc" tickpolicy="catchup"/> <timer name="pit" tickpolicy="delay"/> <timer name="hpet" present="no"/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>destroy</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-kvm</emulator> <disk type="file" device="disk"> <driver name="qemu" type="qcow2"/> <source file="/home/kvmimages/f20vm"/> <target dev="hda" bus="ide"/> </disk> <disk type="file" device="cdrom"> <driver name="qemu" type="raw"/> <source file="/home/kvmimages/Fedora-20-x86_64-DVD.iso"/> <target dev="hdb" bus="ide"/> <readonly/> </disk> <controller type="usb" index="0" model="ich9-ehci1"/> <controller type="usb" index="0" model="ich9-uhci1"> <master startport="0"/> </controller> <controller type="usb" index="0" model="ich9-uhci2"> <master startport="2"/> </controller> <controller type="usb" index="0" model="ich9-uhci3"> <master startport="4"/> </controller> <interface type="network"> <source network="default"/> <mac address="52:54:00:83:bb:cb"/> </interface> <input type="mouse" bus="ps2"/> <console type="pty"/> </devices> </domain>
[dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (guest:450) Generated boot XML: <domain type="kvm"> <name>f20vm</name> <uuid>4ce6b5f5-ed0f-48fa-8d8f-1dc846940f21</uuid> <memory>2097152</memory> <currentMemory>2097152</currentMemory> <vcpu>1</vcpu> <os> <type arch="x86_64">hvm</type> <boot dev="hd"/> </os> <features> <acpi/> <apic/> <pae/> </features> <cpu mode="custom" match="exact"> <model>SandyBridge</model> </cpu> <clock offset="utc"> <timer name="rtc" tickpolicy="catchup"/> <timer name="pit" tickpolicy="delay"/> <timer name="hpet" present="no"/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-kvm</emulator> <disk type="file" device="disk"> <driver name="qemu" type="qcow2"/> <source file="/home/kvmimages/f20vm"/> <target dev="hda" bus="ide"/> </disk> <disk type="block" device="cdrom"> <target dev="hdb" bus="ide"/> <readonly/> </disk> <controller type="usb" index="0" model="ich9-ehci1"/> <controller type="usb" index="0" model="ich9-uhci1"> <master startport="0"/> </controller> <controller type="usb" index="0" model="ich9-uhci2"> <master startport="2"/> </controller> <controller type="usb" index="0" model="ich9-uhci3"> <master startport="4"/> </controller> <interface type="network"> <source network="default"/> <mac address="52:54:00:83:bb:cb"/> </interface> <input type="mouse" bus="ps2"/> <console type="pty"/> </devices> </domain>
[dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (cli:234) File "/usr/share/virt-manager/virt-install", line 876, in <module> sys.exit(main()) File "/usr/share/virt-manager/virt-install", line 870, in main start_install(guest, continue_inst, options) File "/usr/share/virt-manager/virt-install", line 588, in start_install fail(e, do_exit=False) File "/usr/share/virt-manager/virtinst/cli.py", line 234, in fail logging.debug("".join(traceback.format_stack()))
[dim., 15 juin 2014 10:45:16 virt-install 9074] ERROR (cli:235) internal error: process exited while connecting to monitor: Failed to create chardev
[dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (cli:237) Traceback (most recent call last): File "/usr/share/virt-manager/virt-install", line 560, in start_install dom = guest.start_install(meter=meter, noboot=options.noreboot) File "/usr/share/virt-manager/virtinst/guest.py", line 403, in start_install noboot) File "/usr/share/virt-manager/virtinst/guest.py", line 467, in _create_guest dom = self.conn.createLinux(start_xml or final_xml, 0) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2897, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error: process exited while connecting to monitor: Failed to create chardev
[dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (cli:248) L'installation du domaine ne semble pas s'être terminée avec succès. Si c'est bon, vous pouvez démarrer le domaine en lançant : virsh --connect qemu:///system start f20vm sinon, recommencez l'installation. L'installation du domaine ne semble pas s'être terminée avec succès. Si c'est bon, vous pouvez démarrer le domaine en lançant : virsh --connect qemu:///system start f20vm sinon, recommencez l'installation.
Le 15/06/2014 11:41, Patrick Chemla a écrit :
Thanks for your interest.
Here are the dir/files permissions for the kvmimages dir:
# ls -ld /home /home/kvmimages /home/kvmimages/* drwxr-xr-x. 4 root root 4096 14 juin 23:05 /home drwxrwxrwx 2 root root 4096 15 juin 09:19 /home/kvmimages -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 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 2048 WARNING CDROM media does not print to the text console by default, so you likely will not see text install output. You might want to use --location.
Début d'installation... ERROR internal error: process exited while connecting to monitor: Failed to create chardev
L'installation du domaine ne semble pas s'être terminée avec succès. Si c'est bon, vous pouvez démarrer le domaine en lançant : virsh --connect qemu:///system start f20vm sinon, recommencez l'installation.
Always the same Failed to create chardev.
I do think it's a problem of permission as you said, but on which directory/files? Wherever your disk image is located (/home/kvmimages) QEMU should be able to access it (executable bit for 'others'). For instance, I have these permissions for my home directory where I store VM images:
$ ls -lash / | grep home 4.0K drwxr-xr-x. 7 root root 4.0K Aug 7 2013 home
Permissions on the specific directory where I store VM images (/home/kashyap/vmimages):
$ ls -lash /home/kashyap/ | grep vmimages 4.0K drwxrwxr-x. 2 kashyap kashyap 4.0K Jun 14 21:50 vmimages
When I create/run a F20 VM on my local computer, it's OK. I have verified rpm versions, seem OK. I have rsynced /etc/libvirt dir from local computer to remote server.
It works on my local like on yours,but not on my remote. I need the remote to run VMs. If I'm parsing you correctly, you've SSHed into the remote machine and running virt-install. Like I said, if QEMU can access your home directory (as I noted above), where you're storing disk images, you shouldn't have any issues.
Hi, I sill need some help. I tried to remove cdrom and USB controllers from qemu xml definition file. It doesn't help. Still same Failed 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 /home/kvmimages/Fedora-20-x86_64-DVD.iso --memory 2048 -d [dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (cli:195) Requesting libvirt URI default [dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (cli:199) Received libvirt URI qemu:///system [dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (virt-install:193) Requesting virt method 'Par défaut', hv type 'Par défaut'. [dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (virt-install:432) Received virt method 'kvm' [dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (virt-install:433) Hypervisor name is 'hvm' [dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (cli:476) DISPLAY is not set: defaulting to nographics. [dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (pollhelpers:36) Unable to list all volumes: Requested operation is not valid: storage pool 'gnome-boxes' is not active [dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (pollhelpers:36) Unable to list all volumes: Requested operation is not valid: storage pool 'Téléchargements' is not active [dim., 15 juin 2014 10:56:25 virt-install 9795] WARNING (virt-install:343) CDROM media does not print to the text console by default, so you likely will not see text install output. You might want to use --location. [dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (virt-install:551) Guest.has_install_phase: True
Début d'installation... [dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (distroinstaller:417) Using scratchdir=/var/lib/libvirt/boot [dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (guest:449) Generated install XML: <domain type="kvm"> <name>f20vm</name> <uuid>2da45a47-cf6c-4564-9608-52b71d4513f0</uuid> <memory>2097152</memory> <currentMemory>2097152</currentMemory> <vcpu>1</vcpu> <os> <type arch="x86_64">hvm</type> <boot dev="cdrom"/> <boot dev="hd"/> </os> <features> <acpi/> <apic/> <pae/> </features> <cpu mode="custom" match="exact"> <model>SandyBridge</model> </cpu> <clock offset="utc"> <timer name="rtc" tickpolicy="catchup"/> <timer name="pit" tickpolicy="delay"/> <timer name="hpet" present="no"/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>destroy</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-kvm</emulator> <disk type="file" device="disk"> <driver name="qemu" type="qcow2"/> <source file="/home/kvmimages/f20vm"/> <target dev="hda" bus="ide"/> </disk> <disk type="file" device="cdrom"> <driver name="qemu" type="raw"/> <source file="/home/kvmimages/Fedora-20-x86_64-DVD.iso"/> <target dev="hdb" bus="ide"/> <readonly/> </disk> <controller type="usb" index="0" model="ich9-ehci1"/> <controller type="usb" index="0" model="ich9-uhci1"> <master startport="0"/> </controller> <controller type="usb" index="0" model="ich9-uhci2"> <master startport="2"/> </controller> <controller type="usb" index="0" model="ich9-uhci3"> <master startport="4"/> </controller> <interface type="network"> <source network="default"/> <mac address="52:54:00:1d:e0:eb"/> </interface> <input type="mouse" bus="ps2"/> <console type="pty"/> </devices> </domain>
[dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (guest:450) Generated boot XML: <domain type="kvm"> <name>f20vm</name> <uuid>2da45a47-cf6c-4564-9608-52b71d4513f0</uuid> <memory>2097152</memory> <currentMemory>2097152</currentMemory> <vcpu>1</vcpu> <os> <type arch="x86_64">hvm</type> <boot dev="hd"/> </os> <features> <acpi/> <apic/> <pae/> </features> <cpu mode="custom" match="exact"> <model>SandyBridge</model> </cpu> <clock offset="utc"> <timer name="rtc" tickpolicy="catchup"/> <timer name="pit" tickpolicy="delay"/> <timer name="hpet" present="no"/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-kvm</emulator> <disk type="file" device="disk"> <driver name="qemu" type="qcow2"/> <source file="/home/kvmimages/f20vm"/> <target dev="hda" bus="ide"/> </disk> <disk type="block" device="cdrom"> <target dev="hdb" bus="ide"/> <readonly/> </disk> <controller type="usb" index="0" model="ich9-ehci1"/> <controller type="usb" index="0" model="ich9-uhci1"> <master startport="0"/> </controller> <controller type="usb" index="0" model="ich9-uhci2"> <master startport="2"/> </controller> <controller type="usb" index="0" model="ich9-uhci3"> <master startport="4"/> </controller> <interface type="network"> <source network="default"/> <mac address="52:54:00:1d:e0:eb"/> </interface> <input type="mouse" bus="ps2"/> <console type="pty"/> </devices> </domain>
[dim., 15 juin 2014 10:56:26 virt-install 9795] DEBUG (cli:234) File "/usr/share/virt-manager/virt-install", line 876, in <module> sys.exit(main()) File "/usr/share/virt-manager/virt-install", line 870, in main start_install(guest, continue_inst, options) File "/usr/share/virt-manager/virt-install", line 588, in start_install fail(e, do_exit=False) File "/usr/share/virt-manager/virtinst/cli.py", line 234, in fail logging.debug("".join(traceback.format_stack()))
[dim., 15 juin 2014 10:56:26 virt-install 9795] ERROR (cli:235) internal error: process exited while connecting to monitor: Failed to create chardev
[dim., 15 juin 2014 10:56:26 virt-install 9795] DEBUG (cli:237) Traceback (most recent call last): File "/usr/share/virt-manager/virt-install", line 560, in start_install dom = guest.start_install(meter=meter, noboot=options.noreboot) File "/usr/share/virt-manager/virtinst/guest.py", line 403, in start_install noboot) File "/usr/share/virt-manager/virtinst/guest.py", line 467, in _create_guest dom = self.conn.createLinux(start_xml or final_xml, 0) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2897, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error: process exited while connecting to monitor: Failed to create chardev
[dim., 15 juin 2014 10:56:26 virt-install 9795] DEBUG (cli:248) L'installation du domaine ne semble pas s'être terminée avec succès. Si c'est bon, vous pouvez démarrer le domaine en lançant : virsh --connect qemu:///system start f20vm sinon, recommencez l'installation. L'installation du domaine ne semble pas s'être terminée avec succès. Si c'est bon, vous pouvez démarrer le domaine en lançant : virsh --connect qemu:///system start f20vm sinon, recommencez l'installation.
Le 15/06/2014 11:46, Patrick Chemla a écrit :
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/Fedora-20-x86_64-DVD.iso --memory 2048 -d [dim., 15 juin 2014 10:45:15 virt-install 9074] DEBUG (cli:195) Requesting libvirt URI default [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (cli:199) Received libvirt URI qemu:///system [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (virt-install:193) Requesting virt method 'Par défaut', hv type 'Par défaut'. [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (virt-install:432) Received virt method 'kvm' [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (virt-install:433) Hypervisor name is 'hvm' [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (cli:476) DISPLAY is not set: defaulting to nographics. [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (pollhelpers:36) Unable to list all volumes: Requested operation is not valid: storage pool 'gnome-boxes' is not active [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (pollhelpers:36) Unable to list all volumes: Requested operation is not valid: storage pool 'Téléchargements' is not active [dim., 15 juin 2014 10:45:16 virt-install 9074] WARNING (virt-install:343) CDROM media does not print to the text console by default, so you likely will not see text install output. You might want to use --location. [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (virt-install:551) Guest.has_install_phase: True
Début d'installation... [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (distroinstaller:417) Using scratchdir=/var/lib/libvirt/boot [dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (guest:449) Generated install XML: <domain type="kvm"> <name>f20vm</name> <uuid>4ce6b5f5-ed0f-48fa-8d8f-1dc846940f21</uuid> <memory>2097152</memory> <currentMemory>2097152</currentMemory> <vcpu>1</vcpu> <os> <type arch="x86_64">hvm</type> <boot dev="cdrom"/> <boot dev="hd"/> </os> <features> <acpi/> <apic/> <pae/> </features> <cpu mode="custom" match="exact"> <model>SandyBridge</model> </cpu> <clock offset="utc"> <timer name="rtc" tickpolicy="catchup"/> <timer name="pit" tickpolicy="delay"/> <timer name="hpet" present="no"/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>destroy</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-kvm</emulator> <disk type="file" device="disk"> <driver name="qemu" type="qcow2"/> <source file="/home/kvmimages/f20vm"/> <target dev="hda" bus="ide"/> </disk> <disk type="file" device="cdrom"> <driver name="qemu" type="raw"/> <source file="/home/kvmimages/Fedora-20-x86_64-DVD.iso"/> <target dev="hdb" bus="ide"/> <readonly/> </disk> <controller type="usb" index="0" model="ich9-ehci1"/> <controller type="usb" index="0" model="ich9-uhci1"> <master startport="0"/> </controller> <controller type="usb" index="0" model="ich9-uhci2"> <master startport="2"/> </controller> <controller type="usb" index="0" model="ich9-uhci3"> <master startport="4"/> </controller> <interface type="network"> <source network="default"/> <mac address="52:54:00:83:bb:cb"/> </interface> <input type="mouse" bus="ps2"/> <console type="pty"/> </devices> </domain>
[dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (guest:450) Generated boot XML: <domain type="kvm"> <name>f20vm</name> <uuid>4ce6b5f5-ed0f-48fa-8d8f-1dc846940f21</uuid> <memory>2097152</memory> <currentMemory>2097152</currentMemory> <vcpu>1</vcpu> <os> <type arch="x86_64">hvm</type> <boot dev="hd"/> </os> <features> <acpi/> <apic/> <pae/> </features> <cpu mode="custom" match="exact"> <model>SandyBridge</model> </cpu> <clock offset="utc"> <timer name="rtc" tickpolicy="catchup"/> <timer name="pit" tickpolicy="delay"/> <timer name="hpet" present="no"/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-kvm</emulator> <disk type="file" device="disk"> <driver name="qemu" type="qcow2"/> <source file="/home/kvmimages/f20vm"/> <target dev="hda" bus="ide"/> </disk> <disk type="block" device="cdrom"> <target dev="hdb" bus="ide"/> <readonly/> </disk> <controller type="usb" index="0" model="ich9-ehci1"/> <controller type="usb" index="0" model="ich9-uhci1"> <master startport="0"/> </controller> <controller type="usb" index="0" model="ich9-uhci2"> <master startport="2"/> </controller> <controller type="usb" index="0" model="ich9-uhci3"> <master startport="4"/> </controller> <interface type="network"> <source network="default"/> <mac address="52:54:00:83:bb:cb"/> </interface> <input type="mouse" bus="ps2"/> <console type="pty"/> </devices> </domain>
[dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (cli:234) File "/usr/share/virt-manager/virt-install", line 876, in <module> sys.exit(main()) File "/usr/share/virt-manager/virt-install", line 870, in main start_install(guest, continue_inst, options) File "/usr/share/virt-manager/virt-install", line 588, in start_install fail(e, do_exit=False) File "/usr/share/virt-manager/virtinst/cli.py", line 234, in fail logging.debug("".join(traceback.format_stack()))
[dim., 15 juin 2014 10:45:16 virt-install 9074] ERROR (cli:235) internal error: process exited while connecting to monitor: Failed to create chardev
[dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (cli:237) Traceback (most recent call last): File "/usr/share/virt-manager/virt-install", line 560, in start_install dom = guest.start_install(meter=meter, noboot=options.noreboot) File "/usr/share/virt-manager/virtinst/guest.py", line 403, in start_install noboot) File "/usr/share/virt-manager/virtinst/guest.py", line 467, in _create_guest dom = self.conn.createLinux(start_xml or final_xml, 0) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2897, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error: process exited while connecting to monitor: Failed to create chardev
[dim., 15 juin 2014 10:45:16 virt-install 9074] DEBUG (cli:248) L'installation du domaine ne semble pas s'être terminée avec succès. Si c'est bon, vous pouvez démarrer le domaine en lançant : virsh --connect qemu:///system start f20vm sinon, recommencez l'installation. L'installation du domaine ne semble pas s'être terminée avec succès. Si c'est bon, vous pouvez démarrer le domaine en lançant : virsh --connect qemu:///system start f20vm sinon, recommencez l'installation.
Le 15/06/2014 11:41, Patrick Chemla a écrit :
Thanks for your interest.
Here are the dir/files permissions for the kvmimages dir:
# ls -ld /home /home/kvmimages /home/kvmimages/* drwxr-xr-x. 4 root root 4096 14 juin 23:05 /home drwxrwxrwx 2 root root 4096 15 juin 09:19 /home/kvmimages -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 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 2048 WARNING CDROM media does not print to the text console by default, so you likely will not see text install output. You might want to use --location.
Début d'installation... ERROR internal error: process exited while connecting to monitor: Failed to create chardev
L'installation du domaine ne semble pas s'être terminée avec succès. Si c'est bon, vous pouvez démarrer le domaine en lançant : virsh --connect qemu:///system start f20vm sinon, recommencez l'installation.
Always the same Failed to create chardev.
I do think it's a problem of permission as you said, but on which directory/files? Wherever your disk image is located (/home/kvmimages) QEMU should be able to access it (executable bit for 'others'). For instance, I have these permissions for my home directory where I store VM images:
$ ls -lash / | grep home 4.0K drwxr-xr-x. 7 root root 4.0K Aug 7 2013 home
Permissions on the specific directory where I store VM images (/home/kashyap/vmimages):
$ ls -lash /home/kashyap/ | grep vmimages 4.0K drwxrwxr-x. 2 kashyap kashyap 4.0K Jun 14 21:50 vmimages
When I create/run a F20 VM on my local computer, it's OK. I have verified rpm versions, seem OK. I have rsynced /etc/libvirt dir from local computer to remote server.
It works on my local like on yours,but not on my remote. I need the remote to run VMs. If I'm parsing you correctly, you've SSHed into the remote machine and running virt-install. Like I said, if QEMU can access your home directory (as I noted above), where you're storing disk images, you shouldn't have any issues.
On Sun, Jun 15, 2014 at 01:33:46PM +0300, Patrick Chemla wrote:
Hi,
I sill need some help.
I tried to remove cdrom and USB controllers from qemu xml definition file.
Still same Failed to create chardev when trying to run a Vms that run on my local Fedora 20 computer.
You didn't answer my question in the previous email that you ensured that you have enough free memory to create a VM on your remote host.
From your previous mail, your permissions look right, and you don't have to own the disk images to QEMU.
Also, please try `virt-builder` tool to create a VM as I noted in my first reply to this thread. -- /kashyap
Hi, I have now 2 servers, each with 128Gb memory and 6c/12t processors and 2Tb RAID1 disks. It should large enough. 1 server is running Fedora 20 kernel 3.14.7-200.fc20.x86_64. I set the second server back to Fedora 19 running kernel 3.14.4-100.fc19.x86_64. I am running virt-manager-1.0.1-3.fc20.noarch from my Fedora 20 desktop kernel 3.14.6-200.fc20.x86_64. I have created a VM Fedora20 onto my desktop, I tested there and it's OK, and I have transfered the disk image to the 2 servers. On Fedora 19 server, I can start this image, but it seems it is not fully started because I can't connect to it through the virt-manager, nor I can't find its IP address to try ssh. I tried to create a new VM and it works just fine. On Fedora 20 I tried to create a new VM based on Fedora20 DVD.iso. I am getting this message when the VM is started: Impossible de terminer l'installation : « internal error: process exited while connecting to monitor: Failed to create chardev » Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/create.py", line 1787, in do_install guest.start_install(meter=meter) File "/usr/share/virt-manager/virtinst/guest.py", line 403, in start_install noboot) File "/usr/share/virt-manager/virtinst/guest.py", line 467, in _create_guest dom = self.conn.createLinux(start_xml or final_xml, 0) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2897, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error: process exited while connecting to monitor: Failed to create chardev So I will format all my servers to Fedora 19. Thanks for help Patrick Le 16/06/2014 07:08, Kashyap Chamarthy a écrit :
Hi,
I sill need some help.
I tried to remove cdrom and USB controllers from qemu xml definition file.
Still same Failed to create chardev when trying to run a Vms that run on my local Fedora 20 computer. You didn't answer my question in the previous email that you ensured
On Sun, Jun 15, 2014 at 01:33:46PM +0300, Patrick Chemla wrote: that you have enough free memory to create a VM on your remote host.
From your previous mail, your permissions look right, and you don't have to own the disk images to QEMU.
Also, please try `virt-builder` tool to create a VM as I noted in my first reply to this thread.
Hi, I have now 2 servers, each with 128Gb memory and 6c/12t processors and 2Tb RAID1 disks. It should large enough. 1 server is running Fedora 20 kernel 3.14.7-200.fc20.x86_64. I set the second server back to Fedora 19 running kernel 3.14.4-100.fc19.x86_64. I am running virt-manager-1.0.1-3.fc20.noarch from my Fedora 20 desktop kernel 3.14.6-200.fc20.x86_64. I have created a VM Fedora20 onto my desktop, I tested there and it's OK, and I have transfered the disk image to the 2 servers. On Fedora 19 server, I can start this image, but it seems it is not fully started because I can't connect to it through the virt-manager, nor I can't find its IP address to try ssh. I tried to create a new VM and it works just fine. On Fedora 20 I tried to create a new VM based on Fedora20 DVD.iso. I am getting this message when the VM is started: Impossible de terminer l'installation : « internal error: process exited while connecting to monitor: Failed to create chardev » Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/create.py", line 1787, in do_install guest.start_install(meter=meter) File "/usr/share/virt-manager/virtinst/guest.py", line 403, in start_install noboot) File "/usr/share/virt-manager/virtinst/guest.py", line 467, in _create_guest dom = self.conn.createLinux(start_xml or final_xml, 0) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2897, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error: process exited while connecting to monitor: Failed to create chardev So I will format all my servers to Fedora 19. Thanks for help Patrick Le 16/06/2014 07:08, Kashyap Chamarthy a écrit :
Hi,
I sill need some help.
I tried to remove cdrom and USB controllers from qemu xml definition file.
Still same Failed to create chardev when trying to run a Vms that run on my local Fedora 20 computer. You didn't answer my question in the previous email that you ensured
On Sun, Jun 15, 2014 at 01:33:46PM +0300, Patrick Chemla wrote: that you have enough free memory to create a VM on your remote host.
From your previous mail, your permissions look right, and you don't have to own the disk images to QEMU.
Also, please try `virt-builder` tool to create a VM as I noted in my first reply to this thread.
participants (2)
-
Kashyap Chamarthy -
Patrick Chemla