similar to: create a domain failed using virt-install

oh, there is much much much code,it's too too too hard for me. So,,,,,can i ask more question:use virt-manager create a domain,but with a result of "unsupported configuration:the ioh3420 controller is not supported in this qemu".since it's arm64 platform,and ioh3420 is a intel device.right?Why produce a intel device in arm64 platform? So, can i delete the ioh3420 only by

hi boys： the libvirt code in ftp://libvirt.org does get the function of python-libvirt? Or the python-libvirt is another code ? -- Have a good day

Greetings Andrea, > Sent: Monday, January 06, 2020 at 11:37 AM > From: "Andrea Bolognani" <abologna@redhat.com> > To: daggs <daggs@gmx.com>, libvirt-users@redhat.com > Subject: Re: [libvirt-users] aarch64 vm doesn't boots > > On Thu, 2019-12-26 at 09:00 +0100, daggs wrote: > > Greetings, > > > > I'm trying to bring up a alpine rpi

On Mon, 2020-01-06 at 20:31 +0100, daggs wrote: > > > I'm using ubuntu 16.04 with libvirt 1.3.1, if this is a version issue, I can upgrade to latest version. > > > what I'm I missing? > > > > Your version of libvirt (as well as QEMU and virt-manager, I assume) > > is fairly old, and aarch64 support specifically has seen quite a few > >

Greetings Laine, > Sent: Monday, April 30, 2018 at 8:31 PM > From: "Laine Stump" <laine@redhat.com> > To: libvirt-users@redhat.com > Cc: daggs <daggs@gmx.com> > Subject: Re: [libvirt-users] connecting host and guest vm using a dummy nic > > On 04/27/2018 06:39 PM, daggs wrote: > > Greetings all, > > > > I have a host machine that runs

I would really appreciate some pointers on what I am doing wrong here. I have a need to run multiple virtual guests which have each their own GPU and some USB controllers passed-through. I am able to run one of the guests like this (assuming vfio stuff has happened elsewhere), but I would prefer to use virsh: kvm -M q35 -m 8192 -cpu host,kvm=off \ -smp 4,sockets=1,cores=4,threads=1 \ -bios

Hello All, after update to Centos7.5 all our Latitudes 3570 - some 150- suffer usb problems. Plug and play doesn't work any more, people need to insert usb devices - mouse, keyboard, eidreader - first and then boot in order to use them. dmesg | tail -n15 gives these EM: [ 25.164396] usb 1-8: device descriptor read/64, error -110 [ 25.418387] usb 1-8: new full-speed USB device number 6

Greetings Peter, > Sent: Thursday, October 15, 2020 at 9:52 AM > From: "Peter Krempa" <pkrempa@redhat.com> > To: "daggs" <daggs@gmx.com> > Cc: "libvirt-usersredhat.com" <libvirt-users@redhat.com> > Subject: Re: scsi passthrough differs between guests > > I don't see anything wrong with you configs. There were some changes

On 04/30/2018 03:16 PM, daggs wrote: > Greetings Laine, > >> Sent: Monday, April 30, 2018 at 8:31 PM >> From: "Laine Stump" <laine@redhat.com> >> To: libvirt-users@redhat.com >> Cc: daggs <daggs@gmx.com> >> Subject: Re: [libvirt-users] connecting host and guest vm using a dummy nic >> >> On 04/27/2018 06:39 PM, daggs wrote:

Thanks for your reply what i want to know is that why there are many devices in $domain.xml, actully , i choose nothing in virt-manager? so, Do i need to look at qemuDomainDefineXMLFlags()? hours ago, i thought it's qemuDomainCreateWithFlags. -- Have a good day > -----原始邮件----- > 发件人: Michal Privoznik <mprivozn@redhat.com> > 发送时间: 2018年4月26日 星期四 > 收件人: "李卓瑶"

VirtIO DRM driver crashes when setting specific 16.16 fixed-point property values When running a virtual machine with a VirtIO GPU, it's possible to crash the entire VM by setting the value of a 16.16 fixed-point property to any value below 65536 (1.0 in 16.16 format or 0x00010000). As a specific example, setting the SRC_W property on a plane DRM object to a value of 30000 will cause the VM

VirtIO DRM driver crashes when setting specific 16.16 fixed-point property values When running a virtual machine with a VirtIO GPU, it's possible to crash the entire VM by setting the value of a 16.16 fixed-point property to any value below 65536 (1.0 in 16.16 format or 0x00010000). As a specific example, setting the SRC_W property on a plane DRM object to a value of 30000 will cause the VM

Hi, I config my samba join a ad domain(security = ADS), using samba 4.7.1 in CentOS7.5. Everything gone well, I can login with ad user and local user at the same time. But when the ad domain get down, I can not login with local user. wbinfo -t prompt: NT_STATUS_DOMAIN_CONTROLLER_NOT_FOUND, smbclient login with NT_STATUS_NO_LOGON_SERVER error. I lookup the debug message, and found auth

Hi, I upgraded to a Fedora 29 host using virt-preview repo to libvirt-daemon-5.6.0-1.fc29.x86_64 The host was using plain Fedora 29 without virt-preview before that. After the upgrade, starting some vms that were running fine fail now with this error: Error starting domain: internal error: child reported (status=125): Requested operation is not valid: Setting different DAC user or group on

Moving to libvirt-users where it belongs. On Thu, 2019-04-18 at 06:47 +0000, Tal Attaly wrote: > Hi, > I have bridge type interface defined with slot 3 - > <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> > but after running virsh domxml-to-native qemu-argv I get slot 2- > -netdev tap,fd=21,id=hostnet0 -device

----- Oorspronkelijk bericht ----- Van: "Nataraj" <incoming-centos at rjl.com> Aan: "CentOS mailing list" <centos at centos.org> Verzonden: Maandag 2 juli 2018 23:21:39 Onderwerp: Re: [CentOS] usb problem on Dell Latitude 3570 On 07/02/2018 01:49 AM, johan.vermeulen7 at telenet.be wrote: > Hello All, > > after update to Centos7.5 all our Latitudes 3570 -

Greetings Laine, > Sent: Tuesday, May 01, 2018 at 5:30 PM > From: "Laine Stump" <laine@redhat.com> > To: libvirt-users@redhat.com > Cc: daggs <daggs@gmx.com> > Subject: Re: [libvirt-users] connecting host and guest vm using a dummy nic > > On 04/30/2018 03:16 PM, daggs wrote: > > Greetings Laine, > > > >> Sent: Monday, April 30,

Hello! I want to share some findings with the community about hugh timeouts/delays since upgraded to samba 4.8 end of last year and a patch fixing this in our setup. It would be great if someone from samba dev team could take a look and if acceptable apply the patch to the common code base. It may also affect current stable and release candidates. The patch expects the patch from BUG 13503

hi : i create a domain by virt-manager tool, then there is a xxx.xml generated in /etc/libvirt/qemu/. so, my question is how the xx.xml generated? What the code involves in libvirt ? Thanks! -- Have a good day

Hey all, With libvirt 6.5.0 and qemu 5.1.0 migration of non shared disks in tunneled mode does not work for me: virsh # migrate alpinelinux3.8 qemu+tls://ratchet.lan/system --live --persistent --undefinesource --copy-storage-all --tunneled --p2p error: internal error: qemu unexpectedly closed the monitor: Receiving block device images Error unknown block device 2020-08-15T21:21:48.995016Z