similar to: Guests ignoring config changes

On Mon, January 16, 2012 17:01, Dennis Jacobfeuerborn wrote: > On 01/16/2012 10:16 PM, James B. Byrne wrote: > > ... >> The xmldump for this guest instance contains this: > ... > > Please post the xmldumps of the original guest and cloned > guest right after > cloning and without any modifications. > > Regards, > Dennis Prototype dumpxml virsh # dumpxml

Hi, I'm using libvirt and qemu on Debian Wheezy. I'm having a strange behavior. Guests can't connect to each other when they're on the same host. On the host I'm using bonding (in active / backup mode) and vlan. It looks like this : eth0 \ / macvtap0 bond0 --- vlan222 eth1 / \ macvtap1 So I've got two guests, let's say A and B. When

Greetings - I shutdown one of my Centos 6.2 VMs for some offline maintenance and am now unable to get it to restart. I am also unable to create and start a new VM. The host system is Centos 6.2, fully up to date. I have been searching Google for two days and have not been successful in getting a VM to start. I have restarted libvirtd, but did not want to shutdown my other two running VMs and

I have a very strange issue that has plagued our KVM-based hypervisor infrastructure. Environment: - All EL7-based libvirt releases since EL7.0 - Fully patched EL7-based KVM guest on a fully patched EL7-based KVM host. - Secondary disk attached via 'virsh attach-device guest /vm/guest-with-secondary-disk-01/disk2.xml --persistent' (note --persistent flag here) Problem Description: -

Just the output of one of the viridian enabled windows hvm machines: Florian virsh dumpxml titan <domain type=''xen'' id=''40''> <name>titan</name> <uuid>cedb6201-82d6-3c96-4da3-e0bfad6a7501</uuid> <memory>2097152</memory> <currentMemory>2097152</currentMemory> <vcpu>2</vcpu> <os>

Just the output of one of the viridian enabled windows hvm machines: Florian virsh dumpxml titan <domain type=''xen'' id=''40''> <name>titan</name> <uuid>cedb6201-82d6-3c96-4da3-e0bfad6a7501</uuid> <memory>2097152</memory> <currentMemory>2097152</currentMemory> <vcpu>2</vcpu> <os>

Hello, everybody here I have a question about graphical buffers for rhel7. Thanks so much in advance who can give me some suggestions about that. When I try to do regression for bug859317(https://bugzilla.redhat.com/show_bug.cgi?id=859317) on RHEL7， I found that guest could be connected success with virt-viewer when set/update the graphics passwd to empty. But according to comment 2 in this bug,

----- On Mar 2, 2016, at 3:15 PM, Dominique Ramaekers dominique.ramaekers@cometal.be wrote: >>Van: libvirt-users-bounces@redhat.com [mailto:libvirt-users-bounces@redhat.com] >>Namens Lentes, Bernd >>Verzonden: woensdag 2 maart 2016 15:04 >>Aan: libvirt-ML >>Onderwerp: [libvirt-users] VM's in a HA-configuration - synchronising vm config >>files >>

Hi developer, i got a problem and need your help!(my english not very good) My KVM host in IDC, and there are some restrict in there lead to me connect to KVM host by port 22 or 16509 impossible. In generally If i want login my KVM host i must login in to a "stepping stones" first, then login to that KVM host.( Now assume that the KVM host ip is 1.1.1.1 and the "stepping

Hi, All There is following issue in latest libvirt-4.5.0-10.el7_6.12 package, which could prevent live VM migrations with web sockets enabled, when libvirtd were restarted prior to migration. Environment: # uname -a Linux inv-cp1-hv3-centos7 3.10.0-957.12.2.el7.x86_64 #1 SMP Tue May 14 21:24:32 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/redhat-release CentOS Linux release 7.6.1810

On 3/23/2015 12:49 PM, Michal Privoznik wrote: > On 23.03.2015 16:02, Fiorenza Meini wrote: >> Hi there, >> I'm running KVM under Openstack . >> >> When I give virsh list command, I see some VM in NON persistent state. >> What does it mean? How can I move it to a persisten state ? > You can do that by running: > > virsh dumpxml $dom > dom.xml

Greetings All, following a suggestion I got here on how to properly boot uefi-q35 guest, I found an weird config in the xml. this is what I see when I run virsh edit streamer-vm-q35: <os firmware='efi'> <type arch='x86_64' machine='pc-q35-5.0'>hvm</type> <boot dev='hd'/> </os> when I run virsh dumpxml streamer-vm-q35, I get this:

Hi again! More TPM + XEN stuff. have look at the following: ================= "xl list -l centos7.0" ============== [ { "domid": 31, "config": { "c_info": { "type": "hvm", "name": "centos7.0", "uuid":

Hi I have configured KVM with Fedora Core 13 by enabling the KVM virtualization option while installing OS. I have successfully created the guest OS by using the virt-install API /usr/sbin/virt-install --name centos5 --ram 512 --disk path=/var/lib/libvirt/images/ centos.img,size=5 --network network:default --accelerate --vnc -c /tmp/CentOS-5.3-i386-bin-DVD.iso I am able to login to the guest OS

On 10/20/20 11:39 AM, daggs wrote: > Greetings All, > > following a suggestion I got here on how to properly boot uefi-q35 guest, I found an weird config in the xml. > this is what I see when I run virsh edit streamer-vm-q35: > <os firmware='efi'> > <type arch='x86_64' machine='pc-q35-5.0'>hvm</type> > <boot

Hi I tried to use virsh blkstat to get information of a block, but it returns an error message as shown below This function works fine in KVM, but fail in XEN. I tried XEN 3.4.3 ,4.0.0 and 4.0.1 with libvirt 0.7.1 from fedora yum server and 0.8.1 from libvirt . All of them are fail to get the block status. The following is the config file and error message of virsh domblkstat. Any one

Hi I have configured KVM with Fedora Core 13 by enabling the KVM virtualization option while installing OS. I have successfully created the guest OS by using the virt-install API /usr/sbin/virt-install --name centos5 --ram 512 --disk path=/var/lib/libvirt/images/ centos.img,size=5 --network network:default --accelerate --vnc -c /tmp/CentOS-5.3-i386-bin-DVD.iso Os installed successfully and after

Hi, i have a weird problem. I have a vm (KVM) which seems to run fine. I believe the respective config file for this vm is /etc/libvirt/qemu/MausDB.xml. This is it: ========================================================= <domain type='kvm'> <name>MausDB</name> <uuid>d4c7956c-b57f-967a-0454-99835a3a740b</uuid> <memory

I am needing to explicitly assign VNC ports to my virtual guests so that I can connect to them externally via a VNC client, and not virt-viewer. Since I will have multiple KVM Hosts with access to the same shared storage (to facilitate migrations) I need to ensure I have unique VNC ports assigned to each guest so that I don't overlap somehow. I had planned to use a range of ports starting at

Hi, Thanks for infos. My concern is the following : In order to establish datas exchanges between hosts and guest , I'll add a channel device to a running Guest ( as I learned from you that it's possible to do that without stopping the Guest). When the guest migrates to another host , this one must be able to retrieve the channel device parameters to be able to dialog with the