Re: [libvirt-users] Fedora 19/20 new install :Unable to create vcpu cgroup

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. >> >