Hello
I am back withe the commands results:
-#cat /etc/issue
\S
Kernel \r on an \m (\l)
-# uname -a Linux localhost.localdomain 5.5.10-200.fc31.x86_64 #1 SMP Wed
Mar 18 14:21:38 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
-#agrant --version
Vagrant 2.2.6
-#virsh --version
5.6.0
-#virt-host-validate
QEMU : Vérification for hardware virtualization
: PASS
QEMU : Vérification if device /dev/kvm exists
: PASS
QEMU : Vérification if device /dev/kvm is accessible
: PASS
QEMU : Vérification if device /dev/vhost-net exists
: PASS
QEMU : Vérification if device /dev/net/tun exists
: PASS
QEMU : Vérification for cgroup 'cpu' controller support
: WARN (Enable 'cpu' in kernel Kconfig file or mount/enable cgroup
controller in your system)
QEMU : Vérification for cgroup 'cpuacct' controller support
: PASS
QEMU : Vérification for cgroup 'cpuset' controller support
: WARN (Enable 'cpuset' in kernel Kconfig file or mount/enable
cgroup controller in your system)
QEMU : Vérification for cgroup 'memory' controller support
: PASS
QEMU : Vérification for cgroup 'devices' controller support
: WARN (Enable 'devices' in kernel Kconfig file or mount/enable
cgroup controller in your system)
QEMU : Vérification for cgroup 'blkio' controller support
: WARN (Enable 'blkio' in kernel Kconfig file or mount/enable
cgroup controller in your system)
QEMU : Vérification for device assignment IOMMU support
: WARN (No ACPI DMAR table found, IOMMU either disabled in BIOS or
not supported by this hardware platform)
LXC : Vérification pour Linux >= 2.6.26
: PASS
LXC : Vérification for namespace ipc
: PASS
LXC : Vérification for namespace mnt
: PASS
LXC : Vérification for namespace pid
: PASS
LXC : Vérification for namespace uts
: PASS
LXC : Vérification for namespace net
: PASS
LXC : Vérification for namespace user
: PASS
LXC : Vérification for cgroup 'cpu' controller support
: FAIL (Enable 'cpu' in kernel Kconfig file or mount/enable cgroup
controller in your system)
LXC : Vérification for cgroup 'cpuacct' controller support
: PASS
LXC : Vérification for cgroup 'cpuset' controller support
: FAIL (Enable 'cpuset' in kernel Kconfig file or mount/enable
cgroup controller in your system)
LXC : Vérification for cgroup 'memory' controller support
: PASS
LXC : Vérification for cgroup 'devices' controller support
: FAIL (Enable 'devices' in kernel Kconfig file or mount/enable
cgroup controller in your system)
LXC : Vérification for cgroup 'freezer' controller support
: FAIL (Enable 'freezer' in kernel Kconfig file or mount/enable
cgroup controller in your system)
LXC : Vérification for cgroup 'blkio' controller support
: FAIL (Enable 'blkio' in kernel Kconfig file or mount/enable
cgroup controller in your system)
LXC : Vérification if device /sys/fs/fuse/connections exists
: PASS
I hope that will help
thank you very much for your help
KInds Regards
On Friday, March 27, 2020 at 10:57:48 PM UTC+1, dragon788 wrote:
>
> Can you run each of these commands and paste all the output into your
> reply:
>
> cat /etc/issue
> uname -a
> vagrant --version
> virsh --version
> virt-host-validate
>
> I found a bug mentioning an issue with the tap0 device on Debian and I
> want to see if maybe it is related.
>
>
>
> On Friday, March 27, 2020 at 4:28:31 PM UTC-5, Abdeslam Tahari wrote:
>>
>> Hello
>>
>> Thank you very much for your help
>>
>>
>>
>> i checked the groups and permissions , everything is ok, but just dont
>> know what is going wrong
>>
>>
>> here is few lignes from *livirtd.log*
>>
>> 2020-03-27 21:18:02.943+0000: 2215119: debug :
>> udevProcessDeviceListEntry:1403 : Failed to create node device for udev
>> device '/sys/devices/virtual/vtconsole/vtcon1'
>> 2020-03-27 21:18:02.943+0000: 2215119: debug : udevGetDeviceProperty:145 :
>> Found property key 'DRIVER' value '<null>' for device with sysname
>> 'blkcg_punt_bio'
>> 2020-03-27 21:18:02.943+0000: 2215119: debug : udevGetDeviceProperty:145 :
>> Found property key 'SUBSYSTEM' value 'workqueue' for device with sysname
>> 'blkcg_punt_bio'
>> 2020-03-27 21:18:02.943+0000: 2215119: debug : udevGetDeviceType:1189 :
>> Could not determine device type for device with sysfs name 'blkcg_punt_bio'
>> 2020-03-27 21:18:02.943+0000: 2215119: debug : udevAddOneDevice:1380 :
>> Discarding device -1 0x7f7ed01c80e0
>> /sys/devices/virtual/workqueue/blkcg_punt_bio
>> 2020-03-27 21:18:02.943+0000: 2215119: debug :
>> udevProcessDeviceListEntry:1403 : Failed to create node device for udev
>> device '/sys/devices/virtual/workqueue/blkcg_punt_bio'
>> 2020-03-27 21:18:02.943+0000: 2215119: debug : udevGetDeviceProperty:145 :
>> Found property key 'DRIVER' value '<null>' for device with sysname
>> 'writeback'
>> 2020-03-27 21:18:02.943+0000: 2215119: debug : udevGetDeviceProperty:145 :
>> Found property key 'SUBSYSTEM' value 'workqueue' for device with sysname
>> 'writeback'
>> 2020-03-27 21:18:02.943+0000: 2215119: debug : udevGetDeviceType:1189 :
>> Could not determine device type for device with sysfs name 'writeback'
>> 2020-03-27 21:18:02.943+0000: 2215119: debug : udevAddOneDevice:1380 :
>> Discarding device -1 0x7f7ed01c80e0 /sys/devices/virtual/workqueue/writeback
>> 2020-03-27 21:18:02.943+0000: 2215119: debug :
>> udevProcessDeviceListEntry:1403 : Failed to create node device for udev
>> device '/sys/devices/virtual/workqueue/writeback'
>> 2020-03-27 21:18:02.943+0000: 2215119: debug : udevGetDeviceProperty:145 :
>> Found property key 'DRIVER' value '<null>' for device with sysname 'dm-0'
>> 2020-03-27 21:18:02.943+0000: 2215119: debug : udevGetDeviceProperty:145 :
>> Found property key 'ID_BUS' value '<null>' for device with sysname 'dm-0'
>> 2020-03-27 21:18:02.943+0000: 2215119: debug : udevGetDeviceProperty:145 :
>> Found property key 'ID_SERIAL' value '<null>' for device with sysname 'dm-0'
>> 2020-03-27 21:18:02.943+0000: 2215119: debug : udevGetDeviceSysfsAttr:211 :
>> Found sysfs attribute 'device/vendor' value '<null>' for device with sysname
>> 'dm-0'
>> 2020-03-27 21:18:02.943+0000: 2215119: debug : udevGetDeviceSysfsAttr:211 :
>> Found sysfs attribute 'device/model' value '<null>' for device with sysname
>> 'dm-0'
>> 2020-03-27 21:18:02.943+0000: 2215119: debug : udevGetDeviceProperty:145 :
>> Found property key 'ID_TYPE' value '<null>' for device with sysname 'dm-0'
>> 2020-03-27 21:18:02.943+0000: 2215119: debug : udevGetDeviceProperty:145 :
>> Found property key 'ID_DRIVE_FLOPPY' value '<null>' for device with sysname
>> 'dm-0'
>> 2020-03-27 21:18:02.943+0000: 2215119: debug : udevGetDeviceProperty:145 :
>> Found property key 'ID_CDROM' value '<null>' for device with sysname 'dm-0'
>> 2020-03-27 21:18:02.943+0000: 2215119: debug : udevGetDeviceProperty:145 :
>> Found property key 'ID_DRIVE_FLASH_SD' value '<null>' for device with
>> sysname 'dm-0'
>> 2020-03-27 21:18:02.943+0000: 2215119: debug : udevKludgeStorageType:890 :
>> Could not find definitive storage type for device with sysfs path
>> '/sys/devices/virtual/block/dm-0', trying to guess it
>> 2020-03-27 21:18:02.943+0000: 2215119: debug : udevKludgeStorageType:903 :
>> Could not determine storage type for device with sysfs path
>> '/sys/devices/virtual/block/dm-0'
>> 2020-03-27 21:18:02.943+0000: 2215119: debug : udevProcessStorage:1002 :
>> Storage ret=-1
>> 2020-03-27 21:18:02.943+0000: 2215119: debug : udevAddOneDevice:1380 :
>> Discarding device -1 0x7f7ed01c80e0 /sys/devices/virtual/block/dm-0
>> 2020-03-27 21:18:02.943+0000: 2215119: debug :
>> udevProcessDeviceListEntry:1403 : Failed to create node device for udev
>> device '/sys/devices/virtual/block/dm-0'
>> 2020-03-27 21:18:02.943+0000: 2215119: debug : udevGetDeviceProperty:145 :
>> Found property key 'DRIVER' value '<null>' for device with sysname 'dm-1'
>> 2020-03-27 21:18:02.944+0000: 2215119: debug : udevGetDeviceProperty:145 :
>> Found property key 'ID_BUS' value '<null>' for device with sysname 'dm-1'
>> 2020-03-27 21:18:02.944+0000: 2215119: debug : udevGetDeviceProperty:145 :
>> Found property key 'ID_SERIAL' value '<null>' for device with sysname 'dm-1'
>> 2020-03-27 21:18:02.944+0000: 2215119: debug : udevGetDeviceSysfsAttr:211 :
>> Found sysfs attribute 'device/vendor' value '<null>' for device with sysname
>> 'dm-1'
>> 2020-03-27 21:18:02.944+0000: 2215119: debug : udevGetDeviceSysfsAttr:211 :
>> Found sysfs attribute 'device/model' value '<null>' for device with sysname
>> 'dm-1'
>> 2020-03-27 21:18:02.944+0000: 2215119: debug : udevGetDeviceProperty:145 :
>> Found property key 'ID_TYPE' value '<null>' for device with sysname 'dm-1'
>> 2020-03-27 21:18:02.944+0000: 2215119: debug : udevGetDeviceProperty:145 :
>> Found property key 'ID_DRIVE_FLOPPY' value '<null>' for device with sysname
>> 'dm-1'
>> 2020-03-27 21:18:02.944+0000: 2215119: debug : udevGetDeviceProperty:145 :
>> Found property key 'ID_CDROM' value '<null>' for device with sysname 'dm-1'
>> 2020-03-27 21:18:02.944+0000: 2215119: debug : udevGetDeviceProperty:145 :
>> Found property key 'ID_DRIVE_FLASH_SD' value '<null>' for device with
>> sysname 'dm-1'
>> 2020-03-27 21:18:02.944+0000: 2215119: debug : udevKludgeStorageType:890 :
>> Could not find definitive storage type for device with sysfs path
>> '/sys/devices/virtual/block/dm-1', trying to guess it
>> 2020-03-27 21:18:02.944+0000: 2215119: debug : udevKludgeStorageType:903 :
>> Could not determine storage type for device with sysfs path
>> '/sys/devices/virtual/block/dm-1'
>> 2020-03-27 21:18:02.944+0000: 2215119: debug : udevProcessStorage:1002 :
>> Storage ret=-1
>> 2020-03-27 21:18:02.944+0000: 2215119: debug : udevAddOneDevice:1380 :
>> Discarding device -1 0x7f7ed01c80e0 /sys/devices/virtual/block/dm-1
>> 2020-03-27 21:18:02.944+0000: 2215119: debug :
>> udevProcessDeviceListEntry:1403 : Failed to create node device for udev
>> device '/sys/devices/virtual/block/dm-1'
>> 2020-03-27 21:18:02.944+0000: 2215119: debug : udevGetDeviceProperty:145 :
>> Found property key 'DRIVER' value '<null>' for device with sysname 'dm-2'
>> 2020-03-27 21:18:02.944+0000: 2215119: debug : udevGetDeviceProperty:145 :
>> Found property key 'ID_BUS' value '<null>' for device with sysname 'dm-2'
>> 2020-03-27 21:18:02.944+0000: 2215119: debug : udevGetDeviceProperty:145 :
>> Found property key 'ID_SERIAL' value '<null>' for device with sysname 'dm-2'
>> 2020-03-27 21:18:02.944+0000: 2215119: debug : udevGetDeviceSysfsAttr:211 :
>> Found sysfs attribute 'device/vendor' value '<null>' for device with sysname
>> 'dm-2'
>> 2020-03-27 21:18:02.944+0000: 2215119: debug : udevGetDeviceSysfsAttr:211 :
>> Found sysfs attribute 'device/model' value '<null>' for device with sysname
>> 'dm-2'
>> 2020-03-27 21:18:02.944+0000: 2215119: debug : udevGetDeviceProperty:145 :
>> Found property key 'ID_TYPE' value '<null>' for device with sysname 'dm-2'
>> 2020-03-27 21:18:02.944+0000: 2215119: debug : udevGetDeviceProperty:145 :
>> Found property key 'ID_DRIVE_FLOPPY' value '<null>' for device with sysname
>> 'dm-2'
>> 2020-03-27 21:18:02.944+0000: 2215119: debug : udevGetDeviceProperty:145 :
>> Found property key 'ID_CDROM' value '<null>' for device with sysname 'dm-2'
>> 2020-03-27 21:18:02.944+0000: 2215119: debug : udevGetDeviceProperty:145 :
>> Found property key 'ID_DRIVE_FLASH_SD' value '<null>' for device with
>> sysname 'dm-2'
>> 2020-03-27 21:18:02.944+0000: 2215119: debug : udevKludgeStorageType:890 :
>> Could not find definitive storage type for device with sysfs path
>> '/sys/devices/virtual/block/dm-2', trying to guess it
>> 2020-03-27 21:18:02.944+0000: 2215119: debug : udevKludgeStorageType:903 :
>> Could not determine storage type for device with sysfs path
>> '/sys/devices/virtual/block/dm-2'
>> 2020-03-27 21:18:02.944+0000: 2215119: debug : udevProcessStorage:1002 :
>> Storage ret=-1
>> 2020-03-27 21:18:02.944+0000: 2215119: debug : udevAddOneDevice:1380 :
>> Discarding device -1 0x7f7ed01c80e0 /sys/devices/virtual/block/dm-2
>> 2020-03-27 21:18:02.944+0000: 2215119: debug :
>> udevProcessDeviceListEntry:1403 : Failed to create node device for udev
>> device '/sys/devices/virtual/block/dm-2'
>> 2020-03-27 21:18:02.946+0000: 2215119: debug : virThreadJobClear:121 :
>> Thread 2215119 finished job nodeStateInitializeEnumerate with ret=0
>> 2020-03-27 21:18:10.665+0000: 2215024: debug : virNetlinkEventCallback:871 :
>> dispatching to max 0 clients, called from event watch 7
>> 2020-03-27 21:18:10.665+0000: 2215024: debug : virNetlinkEventCallback:885 :
>> event not handled.
>> 2020-03-27 21:18:10.668+0000: 2215024: debug : virNetlinkEventCallback:871 :
>> dispatching to max 0 clients, called from event watch 7
>> 2020-03-27 21:18:10.668+0000: 2215024: debug : virNetlinkEventCallback:885 :
>> event not handled.
>> 2020-03-27 21:18:10.668+0000: 2215024: debug : virNetlinkEventCallback:871 :
>> dispatching to max 0 clients, called from event watch 7
>> 2020-03-27 21:18:10.668+0000: 2215024: debug : virNetlinkEventCallback:885 :
>> event not handled.
>> 2020-03-27 21:18:10.680+0000: 2215024: debug : virNetlinkEventCallback:871 :
>> dispatching to max 0 clients, called from event watch 7
>> 2020-03-27 21:18:10.680+0000: 2215024: debug : virNetlinkEventCallback:885 :
>> event not handled.
>> 2020-03-27 21:18:10.680+0000: 2215024: debug : virNetlinkEventCallback:871 :
>> dispatching to max 0 clients, called from event watch 7
>> 2020-03-27 21:18:10.680+0000: 2215024: debug : virNetlinkEventCallback:885 :
>> event not handled.
>> 2020-03-27 21:18:10.680+0000: 2215024: debug : virNetlinkEventCallback:871 :
>> dispatching to max 0 clients, called from event watch 7
>> 2020-03-27 21:18:10.680+0000: 2215024: debug : virNetlinkEventCallback:885 :
>> event not handled.
>> 2020-03-27 21:18:10.731+0000: 2215118: debug : udevHandleOneDevice:1518 :
>> udev action: 'add'
>> 2020-03-27 21:18:10.731+0000: 2215118: debug : udevGetDeviceProperty:145 :
>> Found property key 'DRIVER' value '<null>' for device with sysname 'tap0'
>> 2020-03-27 21:18:10.731+0000: 2215118: debug : udevGetDeviceProperty:145 :
>> Found property key 'SUBSYSTEM' value 'net' for device with sysname 'tap0'
>> 2020-03-27 21:18:10.731+0000: 2215118: debug : udevGetDeviceProperty:145 :
>> Found property key 'INTERFACE' value 'tap0' for device with sysname 'tap0'
>> 2020-03-27 21:18:10.731+0000: 2215118: debug : udevGetDeviceSysfsAttr:211 :
>> Found sysfs attribute 'address' value '<null>' for device with sysname 'tap0'
>> 2020-03-27 21:18:10.731+0000: 2215118: debug : udevGetDeviceSysfsAttr:211 :
>> Found sysfs attribute 'addr_len' value '<null>' for device with sysname
>> 'tap0'
>> 2020-03-27 21:18:10.731+0000: 2215118: error : virFileReadAll:1431 : Failed
>> to open file '/sys/class/net/tap0/operstate': Aucun fichier ou dossier de ce
>> type
>> 2020-03-27 21:18:10.731+0000: 2215118: error : virNetDevGetLinkInfo:2458 :
>> unable to read: /sys/class/net/tap0/operstate: Aucun fichier ou dossier de
>> ce type
>> 2020-03-27 21:18:10.732+0000: 2215118: debug : udevAddOneDevice:1380 :
>> Discarding device -1 0x7f7ecc003190 /sys/devices/virtual/net/tap0
>>
>>
>> *and the log for journalctl -u libvirtd aswell*
>>
>>
>> *s 27 22:18:01 localhost.localdomain systemd[1]: libvirtd.service: Found
>> left-over process 662694 (dnsmasq) in control group whil>*
>> *mars 27 22:18:01 localhost.localdomain systemd[1]: This usually
>> indicates unclean termination of a previous run, or service impleme>*
>> *mars 27 22:18:01 localhost.localdomain systemd[1]: libvirtd.service:
>> Found left-over process 662693 (dnsmasq) in control group whil>*
>> *mars 27 22:18:01 localhost.localdomain systemd[1]: This usually
>> indicates unclean termination of a previous run, or service impleme>*
>> *mars 27 22:18:01 localhost.localdomain systemd[1]: libvirtd.service:
>> Found left-over process 330980 (dnsmasq) in control group whil>*
>> *mars 27 22:18:01 localhost.localdomain systemd[1]: This usually
>> indicates unclean termination of a previous run, or service impleme>*
>> *mars 27 22:18:01 localhost.localdomain systemd[1]: libvirtd.service:
>> Found left-over process 330979 (dnsmasq) in control group whil>*
>> *mars 27 22:13:38 localhost.localdomain systemd[1]: libvirtd.service:
>> Succeeded.*
>> *mars 27 22:11:39 localhost.localdomain libvirtd[2186894]: 2020-03-27
>> 21:11:39.003+0000: 2187000: debug : virFileClose:114 : Closed >*
>> *mars 27 22:11:39 localhost.localdomain libvirtd[2186894]: 2020-03-27
>> 21:11:39.003+0000: 2187000: debug : virFileClose:114 : Closed >*
>> *mars 27 22:11:39 localhost.localdomain libvirtd[2186894]: 2020-03-27
>> 21:11:39.003+0000: 2187000: debug : virFileClose:114 : Closed >*
>> *mars 27 22:11:39 localhost.localdomain libvirtd[2186894]: 2020-03-27
>> 21:11:39.003+0000: 2187000: debug : virFileClose:114 : Closed >*
>> *mars 27 22:11:39 localhost.localdomain libvirtd[2186894]: 2020-03-27
>> 21:11:39.003+0000: 2187000: debug : virFileClose:114 : Closed >*
>> *mars 27 22:11:39 localhost.localdomain libvirtd[2186894]: 2020-03-27
>> 21:11:39.003+0000: 2187000: debug : virFileClose:114 : Closed >*
>> *mars 27 22:11:39 localhost.localdomain libvirtd[2186894]: 2020-03-27
>> 21:11:39.003+0000: 2187000: debug : virFileClose:114 : Closed >*
>> *mars 27 22:11:39 localhost.localdomain libvirtd[2186894]: 2020-03-27
>> 21:11:39.003+0000: 2187000: debug : virFileClose:114 : Closed >*
>> *mars 27 22:11:39 localhost.localdomain libvirtd[2186894]: 2020-03-27
>> 21:11:39.003+0000: 2187000: debug : virFileClose:114 : Closed >*
>> *mars 27 22:11:39 localhost.localdomain libvirtd[2186894]: 2020-03-27
>> 21:11:39.003+0000: 2187000: debug : virFileClose:114 : Closed >*
>> *mars 27 22:11:39 localhost.localdomain libvirtd[2186894]: 2020-03-27
>> 21:11:39.003+0000: 2187000: debug : virFileClose:114 : Closed >*
>> *mars 27 22:11:39 localhost.localdomain libvirtd[2186894]: 2020-03-27
>> 21:11:39.003+0000: 2187000: debug : virFileClose:114 : Closed >*
>> *mars 27 22:11:39 localhost.localdomain libvirtd[2186894]: 2020-03-27
>> 21:11:39.003+0000: 2187000: debug : virFileClose:114 : Closed >*
>> *mars 27 22:11:39 localhost.localdomain libvirtd[2186894]: 2020-03-27
>> 21:11:39.003+0000: 2187000: debug : virFileClose:114 : Closed >*
>> *mars 27 22:11:39 localhost.localdomain libvirtd[2186894]: 2020-03-27
>> 21:11:39.003+0000: 2187000: debug : virFileClose:114 : Closed >*
>> *mars 27 22:11:39 localhost.localdomain libvirtd[2186894]: 2020-03-27
>> 21:11:39.003+0000: 2187000: debug : virFileClose:114 : Closed >*
>> *mars 27 22:11:39 localhost.localdomain libvirtd[2186894]: 2020-03-27
>> 21:11:39.003+0000: 2187000: debug : virFileClose:114 : Closed >*
>> *mars 27 22:11:39 localhost.localdomain libvirtd[2186894]: 2020-03-27
>> 21:11:39.003+0000: 2187000: debug : virFileClose:114 : Closed >*
>> *mars 27 22:11:39 localhost.localdomain libvirtd[2186894]: 2020-03-27
>> 21:11:39.003+0000: 2187000: debug : virFileClose:114 : Closed >*
>> *mars 27 22:11:39 localhost.localdomain libvirtd[2186894]: 2020-03-27
>> 21:11:39.003+0000: 2187000: debug : virFileClose:114 : Closed >*
>> *mars 27 22:11:39 localhost.localdomain libvirtd[2186894]: 2020-03-27
>> 21:11:39.003+0000: 2187000: debug : virFileClose:114 : Closed >*
>> *mars 27 22:11:39 localhost.localdomain libvirtd[2186894]: 2020-03-27
>> 21:11:39.003+00*
>>
>>
>>
>>
>>
>>
>>
>> Le vendredi 27 mars 2020 19:37:08 UTC+1, dragon788 a écrit :
>>>
>>> You may need to try using a different network type. There are several to
>>> choose from and I discovered that sometimes due to host restrictions you
>>> can't use certain types that want to do a "tap". This could also mean that
>>> you aren't a member of the `libvirt` and/or `kvm` groups on the host which
>>> might have permission to create this type of interface.
>>>
>>> On Thursday, March 26, 2020 at 12:45:16 PM UTC-5, Abdeslam Tahari wrote:
>>>>
>>>> Hello Everybody
>>>>
>>>>
>>>> I have a probleme with a vm(guest machine) it hangs up at boot process
>>>> and here is the error message
>>>>
>>>> *Call to virDomainCreateWithFlags failed: error creating macvtap
>>>> interface macvtap0@eth0*
>>>>
>>>>
>>>>
>>>> i don't know how to resolve it i tried but couldn't resolve it
>>>>
>>>>
>>>>
>>>>
>>>> Any help would be very appreciated.
>>>>
>>>>
>>>>
>>>> T
>>>>
>>>
>> Le jeudi 26 mars 2020 18:45:16 UTC+1, Abdeslam Tahari a écrit :
>>>
>>> Hello Everybody
>>>
>>>
>>> I have a probleme with a vm(guest machine) it hangs up at boot process
>>> and here is the error message
>>>
>>> *Call to virDomainCreateWithFlags failed: error creating macvtap
>>> interface macvtap0@eth0*
>>>
>>>
>>>
>>> i don't know how to resolve it i tried but couldn't resolve it
>>>
>>>
>>>
>>>
>>> Any help would be very appreciated.
>>>
>>>
>>>
>>> Thank you
>>>
>>>
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/ef66e820-78c9-492b-85e0-df404cbedefa%40googlegroups.com.
