11:46 a.m.
On 04/12/2013 12:23 AM, Martin Kletzander wrote:
On 04/11/2013 04:04 PM, Alexey Kardashevskiy wrote:
> oops. Misunderstood. Sorry. "qemu:///session" shows the list. What is
> the difference (shortly if possible)? Two different daemons?
>
In system mode, the daemon runs as root. It is the preferable option,
default when connecting as root, supports more features than session mode.
In session mode, the daemon runs under the user who connects, some
features might not work.
There are many differences which I wouldn't be able to explain here, but
I will direct you to http://libvirt.org/drvqemu.html where more on that
can be found.
Thanks, this is exactly I was looking for.
> There are 2 scsi drives - one is HDD, the other one is DVD.
>
> HDD is:
> -device
>
scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
>
> -drive
>
file=/home/aik/virtimg/Fedora-18-ppc64-DVD.iso,if=none,id=drive-scsi0-0-0-1,readonly=on,format=raw
>
>
>
> DVD is:
> -device scsi-cd,bus=scsi0.0,ch
>
> The second one is cut, "ch" is not a valid parameterer name. Furthermore
> when I add a machine with "virsh -c qemu:///system create lalala.xml"
> (and I have boith scsi devices in that xml), both parameters are passed
> to QEMU as is and it all works.
>
Not that's interesting! What's the info in the logs now when you can
access them? (my previous explanation was aimed at system mode)
I am not sure I understood the question precisely. The only log I can see
is the one created on "virsh -c qemu:///session create
libvirtguest-aik.xml" (or with "system" instead of "session"), I
pasted
"ls" from /var/log/libvirtd/ below.
When "virsh ... create ...", the number of SCSI drives in my xml is exactly
the same and the command line is passed completely to QEMU so it does not
fail as if I run "virt-install".
[root@vpl2 ~]# ls -aR /var/log/libvirt/
/var/log/libvirt/:
. .. lxc qemu uml
/var/log/libvirt/lxc:
. ..
/var/log/libvirt/qemu:
. .. AikLibvirtTest.log
/var/log/libvirt/uml:
. ..
[root@vpl2 ~]#
This is a piece from the log after successful run of "virsh create":
2013-04-12 03:35:25.178+0000: starting up
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
/usr/local/bin/qemu-system-ppc64 -name AikLibvirtTest -S -M pseries
-enable-kvm -m 2048 -smp 2,sockets=2,cores=1,threads=1 -uuid
b130a388-5ae2-a6f9-e583-db491330ee85 -nographic -no-user-config -nodefaults
-chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/AikLibvirtTest.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown
-device pci-ohci,id=usb,bus=pci,addr=0x1.0x2 -device
spapr-vscsi,id=scsi0,reg=0x2000 -drive
file=/var/lib/libvirt/images/fc18guest,if=none,id=drive-scsi0-0-0-0,format=raw
-device
scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
-drive
file=/home/aik/virtimg/Fedora-18-ppc64-DVD.iso,if=none,id=drive-scsi0-0-0-2,readonly=on,format=raw
-device
scsi-cd,bus=scsi0.0,channel=0,scsi-id=0,lun=2,drive=drive-scsi0-0-0-2,id=scsi0-0-0-2,bootindex=1
-chardev pty,id=charserial0 -device
spapr-vty,chardev=charserial0,reg=0x30000000 -device
virtio-balloon-pci,id=balloon0,bus=pci,addr=0x3
This is the broken command line after "virt-install" (for the reference):
/usr/local/bin/qemu-system-ppc64 -name fc18guest5 -S -M pseries -enable-kvm
-m 1024 -smp 1,sockets=1,cores=1,threads=1 -uuid
71f8b17f-ca48-80fe-db58-4d933c66fe2d -no-user-config -nodefaults -chardev
socket,id=charmonitor,path=/home/aik/.config/libvirt/qemu/lib/fc18guest5.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-reboot
-no-shutdown -device pci-ohci,id=usb,bus=pci,addr=0x1.0x2 -device
spapr-vscsi,id=scsi0,reg=0x2000 -drive
file=/home/aik/virtimg/fc18guest,if=none,id=drive-scsi0-0-0-0,format=raw
-device
scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
-drive
file=/home/aik/virtimg/Fedora-18-ppc64-DVD.iso,if=none,id=drive-scsi0-0-0-1,readonly=on,format=raw
-device scsi-cd,bus=scsi0.0,ch
--
Alexey