similar to: virt-install not spawning VM

Hi and hello, I have a problem confusing me. I hope someone can help me with it. I followed a "best practise" - I think - using dedicated zfs filesystems for my virtual machines. Commands (for completion): [i]zfs create rpool/vms[/i] [i]zfs create rpool/vms/vm1[/i] [i] zfs create -V 10G rpool/vms/vm1/vm1-dsk[/i] This command creates the file system [i]/rpool/vms/vm1/vm1-dsk[/i] and the

Hi, When I tested xm new command without uuid parameter repeatedly, I saw many same managed domain as follows. # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 941 2 r----- 51.9 # xm new /xen/vm1.conf Using config file "/xen/vm1.conf". # xm new /xen/vm1.conf Using config file

On Fri, Jun 30, 2017 at 10:41:25 -0400, doug.hughes@keystonenap.com wrote: > sorry about top post, tablet mail client... > > brilliant! that did it! Any idea what happened to cause it to partially fail and get into this state? virsh blockcommit --pivot is actually 3 operations in sequence: 1) initiate the commit job 2) wait till it finishes 3) initiate the pivot job (this is

Hello, I want to do a snapshot which the VM has volumes. But I want to skip the volume check when I do the snapshot. (Which means I want to do a snapshot without detaching the volume) So I try to write a snapshot XML refer by http://libvirt.org/formatsnapshot.html as following: vda is my VM basic disk (qcow2) vdb is a volume (raw) ================ t1.xml =============== <domainsnapshot>

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 i am envisioning a scenario that a fellow sysadmin is employing using xen, where the host is configured with LVM. basically, one volume group spans the physical disk. then, various logical volumes are created for the host and (Linux) guest OSes. this makes it easy to resize logical volumes should it be needed. is a setup like this possible with

Hello everybody! I love xen , But ... I use Xen in HVM mode on my server (no graphical) and every thing works well: I export Dom0 display and have my popup windows VM on my Personnal Computer (PC)... >From my PC, to launch a VM i do (after an ssh -X server) : #xm create VM1.conf there is a pop-up windows with my VM in it (always my PC ....), it''s OK !! and #xm list show my VM1 is

We used to stop the handling of tx when the number of pending DMAs exceeds VHOST_MAX_PEND. This is used to reduce the memory occupation of both host and guest. But it was too aggressive in some cases, since any delay or blocking of a single packet may delay or block the guest transmission. Consider the following setup: +-----+ +-----+ | VM1 | | VM2 | +--+--+

We used to stop the handling of tx when the number of pending DMAs exceeds VHOST_MAX_PEND. This is used to reduce the memory occupation of both host and guest. But it was too aggressive in some cases, since any delay or blocking of a single packet may delay or block the guest transmission. Consider the following setup: +-----+ +-----+ | VM1 | | VM2 | +--+--+

[It may be necessary to remove virtio-dev at lists.oasis-open.org from CC if you are a non-TC member.] Hi, Some modern networking applications bypass the kernel network stack so that rx/tx rings and DMA buffers can be directly mapped. This is typical in DPDK applications where virtio-net currently is one of several NIC choices. Existing virtio-net implementations are not optimized for VM-to-VM

[It may be necessary to remove virtio-dev at lists.oasis-open.org from CC if you are a non-TC member.] Hi, Some modern networking applications bypass the kernel network stack so that rx/tx rings and DMA buffers can be directly mapped. This is typical in DPDK applications where virtio-net currently is one of several NIC choices. Existing virtio-net implementations are not optimized for VM-to-VM

On Wed, Aug 6, 2014 at 12:27 PM, Eric Blake <eblake@redhat.com> wrote: > On 08/06/2014 10:06 AM, Yuanzhen Gu wrote: > > yes, I got your point, thanks very much Eric. > > not entirely, because you still top-posted. > > got it entirely this time, not top-posted. > > > > If I want to take a distributed snapshot, which need pause all the VMs > and >

Hi , I have two virtual machines VM1 and VM2. Then I have added eth0 of my VM to 'default' network. Use case :- I want to monitor all traffic on virbr0('default' network). Steps followed :- 1. Add VM1 eth0 to virbr0 2. Add VM2 eth1 to virbr0 3. brctl setageing ovsbr0 0 ..(To put bridge in promiscuous) Now I am running tcpdump on eth1 of VM2 and trying to ping

On 02/25/2014 09:57 PM, Michael S. Tsirkin wrote: > On Tue, Feb 25, 2014 at 02:53:58PM +0800, Jason Wang wrote: >> We used to stop the handling of tx when the number of pending DMAs >> exceeds VHOST_MAX_PEND. This is used to reduce the memory occupation >> of both host and guest. But it was too aggressive in some cases, since >> any delay or blocking of a single packet

On 02/25/2014 09:57 PM, Michael S. Tsirkin wrote: > On Tue, Feb 25, 2014 at 02:53:58PM +0800, Jason Wang wrote: >> We used to stop the handling of tx when the number of pending DMAs >> exceeds VHOST_MAX_PEND. This is used to reduce the memory occupation >> of both host and guest. But it was too aggressive in some cases, since >> any delay or blocking of a single packet

On 03/10/2014 04:03 PM, Michael S. Tsirkin wrote: > On Fri, Mar 07, 2014 at 01:28:27PM +0800, Jason Wang wrote: >> > We used to stop the handling of tx when the number of pending DMAs >> > exceeds VHOST_MAX_PEND. This is used to reduce the memory occupation >> > of both host and guest. But it was too aggressive in some cases, since >> > any delay or blocking

On 03/10/2014 04:03 PM, Michael S. Tsirkin wrote: > On Fri, Mar 07, 2014 at 01:28:27PM +0800, Jason Wang wrote: >> > We used to stop the handling of tx when the number of pending DMAs >> > exceeds VHOST_MAX_PEND. This is used to reduce the memory occupation >> > of both host and guest. But it was too aggressive in some cases, since >> > any delay or blocking

We used to stop the handling of tx when the number of pending DMAs exceeds VHOST_MAX_PEND. This is used to reduce the memory occupation of both host and guest. But it was too aggressive in some cases, since any delay or blocking of a single packet may delay or block the guest transmission. Consider the following setup: +-----+ +-----+ | VM1 | | VM2 | +--+--+

We used to stop the handling of tx when the number of pending DMAs exceeds VHOST_MAX_PEND. This is used to reduce the memory occupation of both host and guest. But it was too aggressive in some cases, since any delay or blocking of a single packet may delay or block the guest transmission. Consider the following setup: +-----+ +-----+ | VM1 | | VM2 | +--+--+

On 02/26/2014 02:32 PM, Qin Chuanyu wrote: > On 2014/2/26 13:53, Jason Wang wrote: >> On 02/25/2014 09:57 PM, Michael S. Tsirkin wrote: >>> On Tue, Feb 25, 2014 at 02:53:58PM +0800, Jason Wang wrote: >>>> We used to stop the handling of tx when the number of pending DMAs >>>> exceeds VHOST_MAX_PEND. This is used to reduce the memory occupation

On 02/26/2014 02:32 PM, Qin Chuanyu wrote: > On 2014/2/26 13:53, Jason Wang wrote: >> On 02/25/2014 09:57 PM, Michael S. Tsirkin wrote: >>> On Tue, Feb 25, 2014 at 02:53:58PM +0800, Jason Wang wrote: >>>> We used to stop the handling of tx when the number of pending DMAs >>>> exceeds VHOST_MAX_PEND. This is used to reduce the memory occupation