[libvirt] Bug reported... with respect to console problems
A few days ago I reported a bug with respect to console problems after the <bootloader /> bug was 'solved'. Now the status of it did not change, nor did anyone comment. Any updates? Stefan
On Wed, Sep 03, 2008 at 07:43:39AM +0200, Stefan de Konink wrote:
A few days ago I reported a bug with respect to console problems after the <bootloader /> bug was 'solved'. Now the status of it did not change, nor did anyone comment.
Don't report new bugs in old bugzilla tickets. One bug report per ticket. I posted a patch which related to Xen text console handling on monday afternoon which may or may not be related - I can't tell with your rather limited bug description of 'console problems' Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
On Wed, 3 Sep 2008, Daniel P. Berrange wrote:
On Wed, Sep 03, 2008 at 07:43:39AM +0200, Stefan de Konink wrote:
A few days ago I reported a bug with respect to console problems after the <bootloader /> bug was 'solved'. Now the status of it did not change, nor did anyone comment.
Don't report new bugs in old bugzilla tickets. One bug report per ticket.
...and I opened a new one. https://bugzilla.redhat.com/show_bug.cgi?id=460812
I posted a patch which related to Xen text console handling on monday afternoon which may or may not be related - I can't tell with your rather limited bug description of 'console problems'
I'll try to find it. Stefan
Hi All, A newbie question: Does the libvirtd need to be running all the time if I want to use any functions of libvirt (as simple as start/stop/pause my virtual machines (qemu/zen)). Or is it only try if I use the remote functions or virsh. Thanks, -Yushu
Hi, Yao You should differenciate Qemu and Xen(zen). For QEMU, libvirtd need to run always. For Xen, it does not requrired to run for local machine. and required to run for remote machine. Thanks Atsushi SAKAI Yushu Yao <yushuyaoyao@gmail.com> wrote:
Hi All,
A newbie question: Does the libvirtd need to be running all the time if I want to use any functions of libvirt (as simple as start/stop/pause my virtual machines (qemu/zen)). Or is it only try if I use the remote functions or virsh.
Thanks, -Yushu
-- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Atsushi SAKAI schreef:
You should differenciate Qemu and Xen(zen).
For QEMU, libvirtd need to run always. For Xen, it does not requrired to run for local machine. and required to run for remote machine.
Some people still have their hopes that libvirtd will do the same for Xen in the near future :) Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEUEARECAAYFAki/NP8ACgkQYH1+F2Rqwn32awCXdiNGVwZWj3dEA526BZDOM2Zh qwCeOGf7fQmG9pzG7tKKuuL7ZzMT18c= =+umj -----END PGP SIGNATURE-----
Thanks Atsushi and Stefan, It seems that libvirtd has to run with root, is this true? But why does libvirtd need to run for QEMU? If it's for start/stop/pause vm, is Qemu's command line tool not enough? Thanks! -Yushu On 9/3/08 6:08 PM, "Stefan de Konink" <skinkie@xs4all.nl> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Atsushi SAKAI schreef:
You should differenciate Qemu and Xen(zen).
For QEMU, libvirtd need to run always. For Xen, it does not requrired to run for local machine. and required to run for remote machine.
Some people still have their hopes that libvirtd will do the same for Xen in the near future :)
Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEUEARECAAYFAki/NP8ACgkQYH1+F2Rqwn32awCXdiNGVwZWj3dEA526BZDOM2Zh qwCeOGf7fQmG9pzG7tKKuuL7ZzMT18c= =+umj -----END PGP SIGNATURE-----
Yushu Yao <yushuyaoyao@gmail.com> wrote:
Thanks Atsushi and Stefan,
It seems that libvirtd has to run with root, is this true? Yes
But why does libvirtd need to run for QEMU? If it's for start/stop/pause vm, is Qemu's command line tool not enough?
Please see follows https://www.redhat.com/archives/libvir-list/2008-September/msg00005.html
Thanks!
-Yushu
On 9/3/08 6:08 PM, "Stefan de Konink" <skinkie@xs4all.nl> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Atsushi SAKAI schreef:
You should differenciate Qemu and Xen(zen).
For QEMU, libvirtd need to run always. For Xen, it does not requrired to run for local machine. and required to run for remote machine.
Some people still have their hopes that libvirtd will do the same for Xen in the near future :)
Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEUEARECAAYFAki/NP8ACgkQYH1+F2Rqwn32awCXdiNGVwZWj3dEA526BZDOM2Zh qwCeOGf7fQmG9pzG7tKKuuL7ZzMT18c= =+umj -----END PGP SIGNATURE-----
On Wed, 3 Sep 2008, Yushu Yao wrote:
It seems that libvirtd has to run with root, is this true?
To make itself useful it should be root yes.
But why does libvirtd need to run for QEMU? If it's for start/stop/pause vm, is Qemu's command line tool not enough?
I presume it works by keeping reference to the domain, and is not able to manipulate the domain if it does not own it... but this is a guess :) Stefan
On Wed, Sep 03, 2008 at 07:55:20PM -0700, Yushu Yao wrote:
Thanks Atsushi and Stefan,
It seems that libvirtd has to run with root, is this true?
Yes, because it has todo lots of privileged jobs, such as starting QEMU with permissiong to use /dev/kvm, accessing disks and logical volumes in /dev, creating TAP devices, creating bridge devices, and much more. That said, if you were to chmod/chown all the devices in question, you could run libvirtd unprivileged - it requires alot of setup ahead of time though.
But why does libvirtd need to run for QEMU? If it's for start/stop/pause vm, is Qemu's command line tool not enough?
Libvirt does much more than just starting/stopping QEMU. It interacts with its monitor console to control many aspects of it at runtime. It also tracks state of running VMs to detect shutdown & cleanup, and also manages storage, and networking state. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
On Wed, Sep 03, 2008 at 10:45:41AM -0700, Yushu Yao wrote:
A newbie question: Does the libvirtd need to be running all the time if I want to use any functions of libvirt (as simple as start/stop/pause my virtual machines (qemu/zen)). Or is it only try if I use the remote functions or virsh.
The answer is yes & no. Libvirtd does *not* need to be running if you want to control the local Xen hypervisor. In this case libvirt makes direct hypervisor calls and/or uses a connection to xend to do its work. It *is* needed for: - remote access - non-root access - if you use the network or storage features - managing QEMU and KVM instances If libvirtd isn't running you will get a warning, but that can just be ignored. Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top
participants (5)
-
Atsushi SAKAI -
Daniel P. Berrange -
Richard W.M. Jones -
Stefan de Konink -
Yushu Yao