similar to: Reg: content of disk is not reflecting in host.

On Wed, Aug 07, 2019 at 09:57:02PM +0530, bharath paulraj wrote: > Hi Team, > > I am doing a small testing and I don't know if my expectation is correct or > not. Pardon me if I am ignorant. > I created a VM and the VM is running. In the hypervisor I have created > ".img" file and attached this .img file to the VM. > My expectation is that, if VM is writing

Hello Han, Thanks for the response. The XML option with qemu:commandline works if the device is added during the VM creation. But I would like to hot-plug the device to the running VM. I can add the device using the command line <virsh qemu-monitor-command --hmp VM-Name device_add edu,id=edu0> But I would like to add the device using the XML file, like <virsh attach-device VM-Name

Hi Team, I am exploring "edu" device in QEMU to add my own custom device. I am able to add the device using the command line. Would it be possible to add the device using XML file through libvirt? -- Regards, Bharath

Hi Team, I am using QEMU/KVM for launching VMs and libvirt to govern those VMs. I would like to synchronise the connection tracking entries specific to the VM during the VM LIVE migrations. It is required when the firewall is implemented at the host level like libvirt's "network filters". If stateful firewall is enabled, then unless these connection tracking entries are

On Wed, Oct 23, 2019 at 4:27 PM bharath paulraj <bharathpaul@gmail.com> wrote: > Hello Han, > > Thanks for the response. The XML option with qemu:commandline works if the > device is added during the VM creation. But I would like to hot-plug the > device to the running VM. I can add the device using the command line > <virsh qemu-monitor-command --hmp VM-Name

Hi, When i use "virsh attach-device rhel disk.xml" when the guest is booting,then i can't find the disk in the guest after booting.But i can find it by "virsh domblklist rhel",and when i want to detach it from the guest and use "virsh detach-disk rhel vdb", i still can find the disk by "virsh domblklist rhel" The disk.xml is like: <disk

On Wed, Mar 01, 2017 at 04:02:53PM +0100, Viktor Mihajlovski wrote: > On 01.03.2017 04:30, Zbigniew J?drzejewski-Szmek wrote: > > On Tue, Feb 28, 2017 at 09:47:42AM +0100, Viktor Mihajlovski wrote: > >>>>>> One could argue about back-level compatibility, but virtio by-path > >>>>>> naming has changed multiple times. We have seen

On Wed, Mar 01, 2017 at 04:02:53PM +0100, Viktor Mihajlovski wrote: > On 01.03.2017 04:30, Zbigniew J?drzejewski-Szmek wrote: > > On Tue, Feb 28, 2017 at 09:47:42AM +0100, Viktor Mihajlovski wrote: > >>>>>> One could argue about back-level compatibility, but virtio by-path > >>>>>> naming has changed multiple times. We have seen

On Tue, Oct 22, 2019 at 5:41 PM bharath paulraj <bharathpaul@gmail.com> wrote: > Hi Team, > > I am exploring "edu" device in QEMU to add my own custom device. I am able > to add the device using the command line. Would it be possible to add the > device using XML file through libvirt? > Hello, edu device is not implemented to libvirt xml. However you can use it

On Wed, Mar 01, 2017 at 07:28:46PM +0100, Viktor Mihajlovski wrote: > On 01.03.2017 16:58, Daniel P. Berrange wrote: > > given a basic Fedora 25 guest, with a virtio-mmio disk added as per the > > guide above... > > > > looking at device '/devices/platform/a003e00.virtio_mmio/virtio3/block/vda': > > KERNEL=="vda" > >

On Wed, Mar 01, 2017 at 07:28:46PM +0100, Viktor Mihajlovski wrote: > On 01.03.2017 16:58, Daniel P. Berrange wrote: > > given a basic Fedora 25 guest, with a virtio-mmio disk added as per the > > guide above... > > > > looking at device '/devices/platform/a003e00.virtio_mmio/virtio3/block/vda': > > KERNEL=="vda" > >

Hi All. I have a dell system with a H700 raid. Within the hardware RAID config I've created a "virtual disk" which I have assigned to one of my guests. On the host the device is "/dev/sdb", on the guest it's "/dev/vdb". This works fine. Within the guest, we have created lvm PV on /dev/vdb (using the whole disk - no partitions) and created a volume

Good day to all. i have problems with cdrom hot adding code. currently i using virDomainAttachDevice with type=file, device=cdrom, dev=hdc, this code works for machine with one ide hdd and one ide cdrom, but this not work for machine with only one ide hdd, and i looking for solution to hot add cdrom to machine independent of existing devices or i need way to determinate which target device

HI!, I am using virt-manager GUI. There I can add a `Console Device` through Add Hardware. I can add a virtio pty WITHOUT restarting the VM. also I get a pty allocated to host machine say `/dev/pty/M` My expectation is this `host:/dev/pty/M` is connected with a `guest:/dev/ttyN`. so If I open minicom or screen and write to `host:/dev/pty/M` it will be propagated to 'guest:/dev/ttyN'. Is

Thanks for the reply Daniel, However I think you slightly misunderstood the scenario... On 14 November 2017 at 10:32, Daniel P. Berrange <berrange@redhat.com> wrote: > IOW, if your application has a certain expectation of performance that can only > be satisfied by having the KVM guest backed by huge pages, then you should > really change to explicitly reserve huge pages for the

On Thu, Dec 05, 2013 at 01:28:07PM +0200, Alexandr Gluzskiy wrote: > Alexandr писал 2013-12-02 09:36: > >Good day to all. i have problems with cdrom hot adding code. currently > >i using virDomainAttachDevice with type=file, device=cdrom, dev=hdc, > >this code works for machine with one ide hdd and one ide cdrom, but > >this not work for machine with only one ide hdd,

On Mon, Mar 02, 2020 at 12:26:00PM +0100, Tomáš Golembiovský wrote: > Instead of running firstboot script during early boot schedule a task > delayed for 1-2 minute. IIUC, you picked 119 seconds, so effectively 2 minutes. IOW, s/1-2/2/ > During the first boot, after virt-v2v conversion, Windows installs the > drivers injected by virit-v2v. When this installation is finished

Hi, What is the difference between chroot & pivot_root. They don't seem obvious based on the man pages apart from the below mentioned caveats. 1) Inherited Open file descriptors, have to be explicitly closed. 2) Does not change CWD of the process, which can be overcome by doing a chdir before & after chroot call. Any information on this would be useful. Thanks,

Daniel P. Berrangé <berrange@redhat.com> writes: > On Thu, Jul 02, 2020 at 01:21:15PM +0200, Milan Zamazal wrote: >> Hi, >> > >> I've met two situations with NVDIMM support in libvirt where I'm not >> sure all the parties (libvirt & I) do the things correctly. >> >> The first problem is with memory alignment and size changes. In

On Tue, Mar 03, 2020 at 02:27:46PM +0100, Tomáš Golembiovský wrote: > On Mon, Mar 02, 2020 at 11:35:29AM +0000, Daniel P. Berrangé wrote: > > On Mon, Mar 02, 2020 at 12:26:00PM +0100, Tomáš Golembiovský wrote: > > > Instead of running firstboot script during early boot schedule a task > > > delayed for 1-2 minute. > > > > IIUC, you picked 119 seconds, so