similar to: getting oriented/networking

Displaying 20 results from an estimated 6000 matches similar to: "getting oriented/networking"

2015 Mar 20
1
Re: getting oriented/networking [some success]
I seem to have run into https://bugzilla.redhat.com/show_bug.cgi?id=855640, because when I tried the fix/work-around at the end (comment 11), ethtool -K eth0 gro off, my download speed by speedtest went from undetectable to ~150Mb/s. However, it was not able to connect for the upload test, and so something may still be off. Non-virtual machines can do the upload test, so it's not just a
2015 Mar 20
0
Re: getting oriented/networking
Dear Boyland, In collaboration with some of this mailing list users, I had put some effort in optimising the guest settings in function of a windows guest. The libvirt-gui doesn't include these options. You'll have to edit the XML in virsh. This was my conclusion on 15-03-2015 but I added the hugepages tip in this list today. As for networking, I only use or bridged or the default virtual
2017 Apr 26
3
Tunnelled migrate Windows7 VMs halted
[moderator note: I'm forwarding a stripped down version of the original mail which was rejected in the moderator queue. I stripped the 3.3 megabyte .tar.bz2 of the log file attachment, which is inappropriate for a technical list. Either trim the log to the relevant portion, or host the log externally and have your list email merely give a URL of the externally-hosted file] >
2015 Mar 13
6
Re: Processor usage of qemu process.
On Fri, Mar 13, 2015 at 12:35 PM, Daniel P. Berrange <berrange@redhat.com> wrote: > On Fri, Mar 13, 2015 at 10:32:14AM +0100, Dominique Ramaekers wrote: >> Dear Daniel, my XML's: >> >> Note: It seems I was to quick, the Windows 8.1 isn't fixed... >> >> Windows Server 2015 R2 >> >> <domain type='kvm' id='146'> >>
2020 May 13
2
macvtap direct
Hi Couple of questions around macvtap direct usage: 1) is the document here current? https://libvirt.org/formatnetwork.html#examplesDirect I have been able to get host to guest network traffic without any special configuration or switch since Fedora 28 when I first started using it. Using <forward mode=vepa> requires switch port mirroring, but just using <forward mode=bridge>
2020 May 19
1
Re: macvtap direct
On Thu, May 14, 2020 at 1:32 PM Laine Stump <laine@redhat.com> wrote: > On 5/13/20 12:52 AM, Subhendu Ghosh wrote: > > Hi > > > > Couple of questions around macvtap direct usage: > > > > 1) is the document here current? > > https://libvirt.org/formatnetwork.html#examplesDirect > > Yes. None of that has changed in any major way in many years. >
2015 Mar 13
2
Re: Processor usage of qemu process.
Small update: traceFlag T8038 => no improvement... -----Oorspronkelijk bericht----- Van: Dominique Ramaekers Verzonden: vrijdag 13 maart 2015 16:35 Aan: 'Daniel P. Berrange'; Andrey Korolyov CC: libvirt-users@redhat.com Onderwerp: RE: [libvirt-users] Processor usage of qemu process. Results ---------- First I want to show my appreciation to Daniel and Andrey. So thanks... I've
2014 Sep 28
2
Re: what is the xml fomat about memory-backend-file
On 2014/9/25 2:05, Eric Blake wrote: > On 09/24/2014 02:05 AM, Linhaifeng wrote: >> Hi, >> >> I want to use virsh to create a VM with the qemu parameter '-object memory-backend-file,id=mem,size=2048M,mem-path=/mnt/huge,share=on -numa node,memdev=mem'. > > Looking at tests/qemuxml2argvdata/qemuxml2argv-hugepages-pages.args, I > see several instances of
2015 Mar 13
2
Re: Processor usage of qemu process.
Dear Daniel, my XML's: Note: It seems I was to quick, the Windows 8.1 isn't fixed... Windows Server 2015 R2 <domain type='kvm' id='146'> <name>CmsrvAPP2</name> <uuid>02c5daef-662a-85ba-7291-485118badc64</uuid> <memory unit='KiB'>3149824</memory> <currentMemory unit='KiB'>3149824</currentMemory>
2014 Sep 24
2
what is the xml fomat about memory-backend-file
Hi, I want to use virsh to create a VM with the qemu parameter '-object memory-backend-file,id=mem,size=2048M,mem-path=/mnt/huge,share=on -numa node,memdev=mem'. How to write the XML file?
2015 Feb 04
2
Re: HugePages - can't start guest that requires them
*facepalm* Now that I'm re-reading the documentation it's obvious that <page/> and @nodeset are for the guest, "This tells the hypervisor that the guest should have its memory allocated using hugepages instead of the normal native page size." Pretty clear there. Thank you SO much for the guidance, I'll return to my tweaking. I'll report back here with my results.
2015 Jan 30
4
HugePages - can't start guest that requires them
Hello All, I'm trying to enable hugepages, I've turned off THP (Transparent Huge Pages), and enabled hugepages in memoryBacking, and set my 2MB hugepages count via sysctl. I'm getting "libvirtd[5788]: Failed to autostart VM 'atlas': internal error: Unable to find any usable hugetlbfs mount for 16777216 KiB" where atlas is one of my guests and 16777216 KiB is the
2015 Feb 04
2
Re: HugePages - can't start guest that requires them
As I mentioned, I got the instances to launch... but they're only taking HugePages from "Node 0", when I believe my setup should pull from both nodes. [atlas] http://sprunge.us/FSEf [prometheus] http://sprunge.us/PJcR 2015-02-03 16:51:48 root@eanna i ~ # virsh start atlas Domain atlas started 2015-02-03 16:51:58 root@eanna i ~ # virsh start prometheus Domain prometheus started
2014 Oct 08
2
is memoryBacking support 'share' and 'mem-path' parameter
Hi, I want to use this qemu command '-object memory-backend-file,id=mem,size=2048M,mem-path=/mnt/huge,share=on' with libvirt but i can't find the 'mem-path' and 'share' in the documentation. because the vhost-user backend based on 'share=on' parameter and libvirt support vhostuser i guess there maybe another way to support this parameter? this is my xml:
2015 Mar 12
3
Processor usage of qemu process.
I have been using libvirt for a while now with some linux guest installed. And everything has been working great. I've got a nice new (used) HP virtual host with 12 x dual core and 48Gb mem. My Windows servers are getting old, so I found it was time to take the next step and also virtualise my Windows systems. Now I've got two Windows guests on my new host: - A Windows 8.1 which runs a
2014 Oct 09
1
Re: is memoryBacking support 'share' and 'mem-path' parameter
On 2014/10/8 16:57, Martin Kletzander wrote: > On Wed, Oct 08, 2014 at 10:03:47AM +0800, Linhaifeng wrote: >> Hi, >> >> I want to use this qemu command '-object memory-backend-file,id=mem,size=2048M,mem-path=/mnt/huge,share=on' with libvirt but i can't find the 'mem-path' and 'share' in the documentation. >> because the vhost-user backend
2016 Feb 29
1
Network speed between two guests on same host.
Hi, I've got two hosts. Most of my guests are Windows systems. I'm using LANBench to test network performance. 1) From an physical PC to a guest (it doesn't matter on which host), I get almost 1Gb/s. They are connected through a 1Gb/s swich => very good! 2) From a guest on one host to a guest on the other host => plusminus 1Gb/s => Okay! 3) Between two guests on the same
2015 Feb 10
2
Re: HugePages - can't start guest that requires them
On 09.02.2015 18:19, G. Richard Bellamy wrote: > First I'll quickly summarize my understanding of how to configure numa... > > In "//memoryBacking/hugepages/page[@nodeset]" I am telling libvirt to > use hugepages for the guest, and to get those hugepages from a > particular host NUMA node. No, @nodeset refers to guest NUMA nodes. > > In
2015 Jan 31
2
Re: HugePages - can't start guest that requires them
Yeah, Dominique, your wiki was one of the many docs I read through before/during/after starting down this primrose path... thanks for writing it. I'm an Arch user, and I couldn't find anything to indicate qemu, as its compiled for Arch, will look in /etc/default/qemu-kvm. And now that I've got the right page size, the instances are starting... The reason I want to use the page element
2019 Apr 03
1
SEV machines and memory pinning
Hello, I am working on implementing SEV support in OpenStack. There are some questions that came up in the discussion of the spec [0] [0] https://review.openstack.org/#/c/641994/ As far as i understand, the memory for SEV machines need to be pinned so that it doesn't migrate to swap and page migration. ROMS, UEFI pflash and video RAM should be pinned too. Initially we planned to use