Re: [Query] Facing issue in build libvirt6.0 on ubuntu 1804
[Please keep the list CCed] On 4/30/20 12:02 PM, Ramesh B wrote:
Hi Michal,
Thanks for quick response.
Ubuntu: 18.04.3 LTS QEMU emulator version 4.2.0 libvirtd (libvirt) 4.0.0
I have lunched the guest os using QEMU. I would like to use the virsh commands to get the status / control of guest OS. when i run any virsh commands not getting any response from QEMU. When i tried to explore, found the solution saying use of QEMU monitor will help. added the below command while lunch, -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-freebsd11.0/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control
but result in below mentioed error: Failed to bind socket to /var/lib/libvirt/qemu/domain-freebsd11.0/monitor.sock
Then thought of building libvirt 6.0 version, will help to solve the problem.
Ah, so you wanted to use 'virsh qemu-attach' to attach libvirt to a running qemu. Yeah, it needs a monitor. However, the functionality was not maintained and probably not functional anyway so we've removed in the 5.5.0 release.
Please guide me to solve this problem.
Regards, Babu B
But what's interesting is that you are unable to build. Which package is providing the rst2* binaries? Are their up to date? Michal
Hi Michal, Please find the details below, rst2html5 1.10.6 (Docutils 0.16 [release], Python 3.6.9, on linux) is there any other way to access/control the guest os running on top QEMU ? Thanks, Ramesh On Thu, Apr 30, 2020 at 3:47 PM Michal Privoznik <mprivozn@redhat.com> wrote:
[Please keep the list CCed]
On 4/30/20 12:02 PM, Ramesh B wrote:
Hi Michal,
Thanks for quick response.
Ubuntu: 18.04.3 LTS QEMU emulator version 4.2.0 libvirtd (libvirt) 4.0.0
I have lunched the guest os using QEMU. I would like to use the virsh commands to get the status / control of guest OS. when i run any virsh commands not getting any response from QEMU. When i tried to explore, found the solution saying use of QEMU monitor will help. added the below command while lunch, -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-freebsd11.0/monitor.sock,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control
but result in below mentioed error: Failed to bind socket to /var/lib/libvirt/qemu/domain-freebsd11.0/monitor.sock
Then thought of building libvirt 6.0 version, will help to solve the problem.
Ah, so you wanted to use 'virsh qemu-attach' to attach libvirt to a running qemu. Yeah, it needs a monitor. However, the functionality was not maintained and probably not functional anyway so we've removed in the 5.5.0 release.
Please guide me to solve this problem.
Regards, Babu B
But what's interesting is that you are unable to build. Which package is providing the rst2* binaries? Are their up to date?
Michal
On 4/30/20 12:53 PM, Ramesh B wrote:
Hi Michal,
Please find the details below, rst2html5 1.10.6 (Docutils 0.16 [release], Python 3.6.9, on linux)
Weird. I have slightly older version and it works for me. Maybe configure is picking something else, some weird binary/python script?
is there any other way to access/control the guest os running on top QEMU ?
Ideally, you would construct the domain XML to match the command line and then use 'virsh define' to store the XML in libvirt. From that point on, libvirt will know about the domain and you can use all libvirt APIs to control it. Unless your cmd line is super complicated then usually virt-install --import in combination with --print-xml allows you to converge into the current config. Michal
Hi Michel, Thanks for quick update. Weird. I have slightly older version and it works for me. Maybe configure is picking something else, some weird binary/python script? * =>* I have python 3.6 version, is it required latest version e.g Python 3.8 ? Ideally, you would construct the domain XML to match the command line and then use 'virsh define' to store the XML in libvirt. From that point on, libvirt will know about the domain and you can use all libvirt APIs to control it. * =>* could you please share sample xml & commands for reference to try above procedure. Few Qemu parameters are as follows, -m 2048 -smp 2 -M q35 -enable-kvm --cpu host Regards, Babu B On Thu, Apr 30, 2020 at 4:33 PM Michal Privoznik <mprivozn@redhat.com> wrote:
On 4/30/20 12:53 PM, Ramesh B wrote:
Hi Michal,
Please find the details below, rst2html5 1.10.6 (Docutils 0.16 [release], Python 3.6.9, on linux)
Weird. I have slightly older version and it works for me. Maybe configure is picking something else, some weird binary/python script?
is there any other way to access/control the guest os running on top
QEMU ?
Ideally, you would construct the domain XML to match the command line and then use 'virsh define' to store the XML in libvirt. From that point on, libvirt will know about the domain and you can use all libvirt APIs to control it. Unless your cmd line is super complicated then usually virt-install --import in combination with --print-xml allows you to converge into the current config.
Michal
On 4/30/20 2:26 PM, Ramesh B wrote:
Hi Michel,
Thanks for quick update.
Weird. I have slightly older version and it works for me. Maybe configure is picking something else, some weird binary/python script?
*=>* I have python 3.6 version, is it required latest version e.g Python 3.8 ?
No. I meant that perhaps configure was picking the script from say /usr/local/bin, e.g. some local, self installed version which is broken.
Ideally, you would construct the domain XML to match the command line and then use 'virsh define' to store the XML in libvirt. From that point on, libvirt will know about the domain and you can use all libvirt APIs to control it.
*=>* could you please share sample xml & commands for reference to try above procedure. Few Qemu parameters are as follows, -m 2048 -smp 2 -M q35 -enable-kvm --cpu host
<domain type='kvm> <name>fedora</name> <memory unit='GiB'>2</memory> <vcpu>2</vcpu> <os> <type arch='x86_64' machine='q35'>hvm</type> </os> <cpu mode='host-passthrough' check='none'> <topology sockets='1' dies='1' cores='2' threads='2'/> </cpu> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> </devices> </domain> Michal
Thanks, I'll check it out. On Thu, Apr 30, 2020, 6:02 PM Michal Privoznik <mprivozn@redhat.com> wrote:
On 4/30/20 2:26 PM, Ramesh B wrote:
Hi Michel,
Thanks for quick update.
Weird. I have slightly older version and it works for me. Maybe configure is picking something else, some weird binary/python script?
*=>* I have python 3.6 version, is it required latest version e.g Python 3.8 ?
No. I meant that perhaps configure was picking the script from say /usr/local/bin, e.g. some local, self installed version which is broken.
Ideally, you would construct the domain XML to match the command line and then use 'virsh define' to store the XML in libvirt. From that point on, libvirt will know about the domain and you can use all libvirt APIs to control it.
*=>* could you please share sample xml & commands for reference to try above procedure. Few Qemu parameters are as follows, -m 2048 -smp 2 -M q35 -enable-kvm --cpu host
<domain type='kvm> <name>fedora</name> <memory unit='GiB'>2</memory> <vcpu>2</vcpu> <os> <type arch='x86_64' machine='q35'>hvm</type> </os> <cpu mode='host-passthrough' check='none'> <topology sockets='1' dies='1' cores='2' threads='2'/> </cpu> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> </devices> </domain>
Michal
participants (2)
-
Michal Privoznik -
Ramesh B