[Qemu-discuss] "-netdev user" vlan syntax
Hi! Can anyone tell me how to do this right? qemu-system-x86_64 -netdev hubport,id=hub1port0,hubid=1 -device virtio-net,id=nic1,netdev=hub1port0 -netdev hubport,id=hub1port1,hubid=1 -netdev user,id=user.0,netdev=hub1port1 qemu-system-x86_64: -netdev user,id=user.0,netdev=hub1port1: Invalid parameter 'netdev' I'm trying to recreate a network like this, but using "-netdev" instead of "-net". qemu-system-x86_64 -net nic,model=virtio,id=nic1,vlan=1 -net user,vlan=1 Thank you very much! Moritz -- Moritz Duge d...@pre-sense.de PRESENSE Technologies GmbHSachsenstr. 5, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 Wir sind auf der it-sa: 18.-20.10.2016 http://www.it-sa.de smime.p7s Description: S/MIME Cryptographic Signature
[Qemu-discuss] Using vhost scsi
Hello Everyone I am trying the compare the performance of virtio-blk, vhost-scsi, and native host on a SATA3 SSD. i figured out how to use virtio-blk but i can't find any reference on how to use vhost scsi i figured i probably need to use "-device virtio-scsi" but other than that i couldn't find option that i should set. simply replacing vitrtio-blk with virtio-scsi doesn't work Any hint or advise is really appreciated :) Thanks Yehuda
Re: [Qemu-discuss] [problem] QEMU-GA & Windows 10
Hi Dominique,
Thank you for your help. I have added the requested XML and created the
missing directory, verifying the permissions and ownership exist for
libvirt-qemu:kvm as all the other directories do. This should allow
libvirt to have write permissions, no?
Here is the error I'm receiving when trying to start the VM (it looks
like a permission issue):
--
Error starting domain: internal error: process exited while connecting
to monitor: qemu-system-x86_64: -chardev
socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/Windows10.org.qemu.quest_agent.0,server,nowait:
Failed to bind socket: Permission denied
qemu-system-x86_64: -chardev
socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/Windows10.org.qemu.quest_agent.0,server,nowait:
chardev: opening backend "socket" failed
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 96, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 117, in
tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/domain.py", line 1162, in
startup
self._backend.create()
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 866, in
create
if ret == -1: raise libvirtError ('virDomainCreate() failed',
dom=self)
libvirtError: internal error: process exited while connecting to
monitor: qemu-system-x86_64: -chardev
socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/Windows10.org.qemu.quest_agent.0,server,nowait:
Failed to bind socket: Permission denied
qemu-system-x86_64: -chardev
socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/Windows10.org.qemu.quest_agent.0,server,nowait:
chardev: opening backend "socket" failed
---
Here is the ownership and file permissions for every directory off
of /var/lib/libvirt. I had to create the channel/target/ directory and
sub
--
root@Linux-Precision-T1500:/# tree -dugp /var/lib/libvirt
/var/lib/libvirt
├── [drwx--x--x root root] boot
├── [drwxr-xr-x root root] dnsmasq
├── [drwx--x--x root root] images
├── [drwxr-xr-x root root] network
├── [drwxr-x--- libvirt- kvm ] qemu
│ ├── [drwxr-xr-x libvirt- kvm ] channel
│ │ └── [drwxr-xr-x libvirt- kvm ] target
│ ├── [drwxr-xr-x root root] dump
│ ├── [drwxr-xr-x libvirt- kvm ] save
│ └── [drwxr-xr-x libvirt- kvm ] snapshot
└── [drwx-- root root] sanlock
... did I miss something?
Thank you in advance.
Kind regards,
-Frank
-Original Message-
From: Dominique Ramaekers
To: Frank Sfalanga Jr.
Cc: qemu-discuss@nongnu.org
Subject: RE: [problem] QEMU-GA & Windows 10
Date: Sun, 24 Jul 2016 13:32:39 +
> -Oorspronkelijk bericht-
> Van: Frank Sfalanga Jr. [mailto:fr...@csiglobalvcard.com]
> Verzonden: maandag 18 juli 2016 20:16
> Aan: Dominique Ramaekers
> CC: qemu-discuss@nongnu.org
> Onderwerp: Re: [problem] QEMU-GA & Windows 10
>
> Hi Dominique,
>
> Just returned from my trip. Thank you for your patience. As requested, here
> is a copy of the XML for this VM on the host:
>
>
> Windows10
> b69f4f7e-84db-faf5-0f93-9b14babdba78
#Add in the xml before the closing tag :
After saving, look into the xml again. If all is right, libvirt added some
extra lines. One of the lines
has a path (ex.
path='/var/lib/libvirt/qemu/channel/target/domain-X/org.qemu.guest_agent.0').
Check if the path (until the folder domain-X) exists and libvirt can write
to it. If not, create it
yourselves and apply the correct rights.
Also look at the 'address' part. The combination type+controller+bus+port
should be unique in
your xml. If not, change the port to a free port of that bus.
>
>
...
> Thank you in advance for any direction you can provide.
>
> Kind regards,
>
> -Frank
Make shure you have shutdown the guest.
Start the guest again.
If all is right, the guest agent should start on startup.
Note: it's not necessary QEMU GUEST AGENT VSS PROVIDER is started.
The guest agent will start the VSS Provider if needed.
It can't hurt neither, it will stop automatically when it wants to...
Hope this helps...
> -Original Message-
> From: Dominique Ramaekers
> To: Frank Sfalanga Jr. , qemu-
> disc...@nongnu.org
> Subject: RE: [problem] QEMU-GA & Windows 10
> Date: Thu, 14 Jul 2016 09:30:33 +
>
>
> > -Oorspronkelijk bericht-
> > Van: Qemu-discuss [mailto:qemu-discuss-
> > bounces+dominique.ramaekers=cometal...@nongnu.org] Namens Frank
> > Sfalanga Jr.
> > Verzonden: dinsdag 12 juli 2016 19:31
> > Aan: qemu-discuss@nongnu.org
> > Onderwerp: [Qemu-discuss] [problem] QEMU-GA & Windows 10
> >
> > Hello,
> >
> > Ubuntu 14.04LTS
> > KVM/Qemu
>
Re: [Qemu-discuss] [problem] QEMU-GA & Windows 10
Also, here is the latest XML (after making the suggested changes) Windows10 b69f4f7e-84db-faf5-0f93-9b14babdba78 12617728 12617728 4 hvm Haswell Intel destroy restart restart /usr/bin/kvm-spice
Re: [Qemu-discuss] [problem] QEMU-GA & Windows 10
Now the channel is there and the VM is booting but the QEMU-GA still will not start. It is failing with the same (original) error: -- Windows could not start the QEMU Guest Agent service on local computer. Error 1053: the service did not respond to the start or control request in a timely fashion. --- Following Dominique's directions, I was able to get past the "Failed to bind socket: Permission denied errors" below using information I found here: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1407434 "WORKAROUND for those who want to go on with MV creation while this bug is valid : 0. do not quit virt-manager vm creation 1. locate apparmor profile for your VM with ls-ltr /etc/apparmor.d/libvirt/libvirt-* (the long string with numbers is your vm UUID - look inside to find your vm name) 2. set this apparmor profil in complain mode # aa-complain /etc/apparmor.d/libvirt/libvirt-73aa79f1-0023-4e37-8001-5be78e884348 (for example) 3. go on with vm creation - it will succeed" Now the Windows 10 VM is booting up and working fine. Also, the channel appears to be created too: root@Linux-Precision-T1500:/var/lib/libvirt/qemu/channel/target# ls -l total 0 srwxr-xr-x 1 libvirt-qemu kvm 0 Jul 25 17:16 Windows10.org.qemu.quest_agent.0 -- As I said above, I'm still not able to get the QEMU-GA to start, although the VSS starts fine. -Frank
[Qemu-discuss] [problem]-starting a VM causes RT (latency) problem for application running on another VM
Hello All, Here is a problem I saw when I ran virsh start to a VM. I have 2VMs on a server when one of them is running a RT application and the other is in shut down state. Then I executed "virsh start" to the second VM and saw 2-3 seconds later a big latency problem in my RT application running on the first VM. I want to emphasize that the VMs use dedicated isolated cores of the server and I have the relevant configuration on the server and the vcpu pinning section of virsh xml. Can anyone tell me why I experience such behavior and how it can be resolved? I will highly appreciate your help. Thank you, Yan
Re: [Qemu-discuss] [problem]-starting a VM causes RT (latency) problem for application running on another VM
On 2016年07月25日 23:03, Yan Fridland wrote: Hello All, Here is a problem I saw when I ran virsh start to a VM. I have 2VMs on a server when one of them is running a RT application and the other is in shut down state. Then I executed "virsh start" to the second VM and saw 2-3 seconds later a big latency problem in my RT application running on the first VM. I want to emphasize that the VMs use dedicated isolated cores of the server and I have the relevant configuration on the server and the vcpu pinning section of virsh xml. Can anyone tell me why I experience such behavior and how it can be resolved? I will highly appreciate your help. Thank you, Yan I am not very sure, but I suggest you to add emulatorpin in xml file, then see results. actually, all qemu associated process can use all processors via cgroup configure created by libvirt,|| https://libvirt.org/formatdomain.html#elementsCPUTuning
[Qemu-discuss] How to use the in-qemu API for virtio serial device
IA==
