12:29 a.m.
Hi,
I'm trying to install a qemu-kvm virtual machine on a Debian GNU/Linux
squeeze amd64 host, using virtinst 0.500.3 and libvirt 0.8.3.
First I tried this command as a normal user (in groups kvm and libvirt):
$ virt-install --connect qemu:///system --name test1 \
--ram $((128 * 1024 * 1024)) --vcpus=1 --description 'Test VM
1' \
--location=http://http.us.debian.org/debian/dists/squeeze/main/installer-amd64/ \
--extra-args='auto url=http://10.0.0.128/baldr1.cfg' \
--os-type=linux --os-variant=debiansqueeze \
--disk path=/mnt/data/vms/test1.img --network bridge=br0 \
--nographics --hvm --virt-type=kvm --serial pty --autostart
This failed, giving me the following output:
Starting install...
Retrieving file MANIFEST... | 3.3 kB 00:00 ...
Retrieving file linux... | 4.6 MB 00:13 ...
Retrieving file initrd.gz... | 13 MB 00:38 ...
ERROR internal error Process exited while reading console log output: char device
redirected to /dev/pts/4
Domain installation does not appear to have been
successful. If it was, you can restart your domain
by running 'virsh start test1'; otherwise, please
restart your installation.
ERROR internal error Process exited while reading console log output: char device
redirected to /dev/pts/4
Traceback (most recent call last):
File "/usr/bin/virt-install", line 1033, in <module>
main()
File "/usr/bin/virt-install", line 915, in main
start_time, guest.start_install)
File "/usr/bin/virt-install", line 957, in do_install
dom = install_func(conscb, progresscb, wait=(not wait))
File "/usr/lib/pymodules/python2.6/virtinst/Guest.py", line 973, in
start_install
return self._do_install(consolecb, meter, removeOld, wait)
File "/usr/lib/pymodules/python2.6/virtinst/Guest.py", line 1038, in
_do_install
"install")
File "/usr/lib/pymodules/python2.6/virtinst/Guest.py", line 1009, in
_create_guest
dom = self.conn.createLinux(start_xml, 0)
File "/usr/lib/python2.6/dist-packages/libvirt.py", line 1277, in
createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed',
conn=self)
libvirtError: internal error Process exited while reading console log output: char
device redirected to /dev/pts/4
I tried the same virt-install command without "--serial pty" and as
root, to no avail.
I then tried setting "console" using --extra-args, i.e.:
$ virt-install --connect qemu:///system --name test1 \
--ram $((128 * 1024 * 1024)) --vcpus=1 --description 'Test VM
1' \
--location=http://http.us.debian.org/debian/dists/squeeze/main/installer-amd64/ \
--extra-args='console=tty0 console=ttyS0,115200n8' \
--os-type=linux --os-variant=debiansqueeze \
--disk path=/mnt/data/vms/test1.img --network bridge=br0 \
--nographics --hvm --virt-type=kvm --serial pty --autostart
Again, I get the same error.
Can anyone tell me why I'm getting this error or give me some hints to
troubleshoot this? So far nothing in the Python or C code of libvirt
stands out at me, and nothing in ~/.virtinst/virt-install.log looks
helpful.
Since there's no specific error message to say why the process exited,
does this perhaps mean that debian-installer is simply shutting down
immediately after booting?
(I'm sending this to the libvirt-users list because it looks like a
libvirt issue. Let me know if I should query a different list.)
Thanks,
--
Patrick "P. J." McDermott
http://www.pehjota.net/
http://www.pehjota.net/contact.html
8:49 a.m.
On 2012年12月20日 14:29, Patrick 'P. J.' McDermott wrote:
Hi,
I'm trying to install a qemu-kvm virtual machine on a Debian GNU/Linux
squeeze amd64 host, using virtinst 0.500.3 and libvirt 0.8.3.
First I tried this command as a normal user (in groups kvm and libvirt):
$ virt-install --connect qemu:///system --name test1 \
> --ram $((128 * 1024 * 1024)) --vcpus=1 --description 'Test VM 1' \
>
--location=http://http.us.debian.org/debian/dists/squeeze/main/installer-amd64/ \
> --extra-args='auto url=http://10.0.0.128/baldr1.cfg' \
> --os-type=linux --os-variant=debiansqueeze \
> --disk path=/mnt/data/vms/test1.img --network bridge=br0 \
> --nographics --hvm --virt-type=kvm --serial pty --autostart
This failed, giving me the following output:
Starting install...
Retrieving file MANIFEST... | 3.3 kB 00:00 ...
Retrieving file linux... | 4.6 MB 00:13 ...
Retrieving file initrd.gz... | 13 MB 00:38 ...
ERROR internal error Process exited while reading console log output: char device
redirected to /dev/pts/4
Domain installation does not appear to have been
successful. If it was, you can restart your domain
by running 'virsh start test1'; otherwise, please
restart your installation.
ERROR internal error Process exited while reading console log output: char device
redirected to /dev/pts/4
Traceback (most recent call last):
File "/usr/bin/virt-install", line 1033, in<module>
main()
File "/usr/bin/virt-install", line 915, in main
start_time, guest.start_install)
File "/usr/bin/virt-install", line 957, in do_install
dom = install_func(conscb, progresscb, wait=(not wait))
File "/usr/lib/pymodules/python2.6/virtinst/Guest.py", line 973, in
start_install
return self._do_install(consolecb, meter, removeOld, wait)
File "/usr/lib/pymodules/python2.6/virtinst/Guest.py", line 1038, in
_do_install
"install")
File "/usr/lib/pymodules/python2.6/virtinst/Guest.py", line 1009, in
_create_guest
dom = self.conn.createLinux(start_xml, 0)
File "/usr/lib/python2.6/dist-packages/libvirt.py", line 1277, in
createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed',
conn=self)
libvirtError: internal error Process exited while reading console log output: char
device redirected to /dev/pts/4
Generally, this means qemu crashed, can you check the guest log
to see if there is any useful info?
/var/log/libvirt/qemu/$guest.log
PS: perhaps we should grab the stderr of qemu process and dump it
to user instead.
I tried the same virt-install command without "--serial pty" and as
root, to no avail.
I then tried setting "console" using --extra-args, i.e.:
$ virt-install --connect qemu:///system --name test1 \
> --ram $((128 * 1024 * 1024)) --vcpus=1 --description 'Test VM 1' \
>
--location=http://http.us.debian.org/debian/dists/squeeze/main/installer-amd64/ \
> --extra-args='console=tty0 console=ttyS0,115200n8' \
> --os-type=linux --os-variant=debiansqueeze \
> --disk path=/mnt/data/vms/test1.img --network bridge=br0 \
> --nographics --hvm --virt-type=kvm --serial pty --autostart
Again, I get the same error.
Can anyone tell me why I'm getting this error or give me some hints to
troubleshoot this? So far nothing in the Python or C code of libvirt
stands out at me, and nothing in ~/.virtinst/virt-install.log looks
helpful.
Since there's no specific error message to say why the process exited,
does this perhaps mean that debian-installer is simply shutting down
immediately after booting?
(I'm sending this to the libvirt-users list because it looks like a
libvirt issue. Let me know if I should query a different list.)
Thanks,
9:28 a.m.
> Can anyone tell me why I'm getting this error or give me some hints to
> troubleshoot this? So far nothing in the Python or C code of libvirt
> stands out at me, and nothing in ~/.virtinst/virt-install.log looks
> helpful.
>
> you could change the log level of libvirt daemon by edit
/etc/libvirt/libvirtd.log, and see more information
3:28 p.m.
On 2012-12-26 10:28, Gao Yongwei wrote:
>> you could change the log level of libvirt daemon by edit
/etc/libvirt/libvirtd.log, and see more information
On 2012-12-26 09:49, Osier Yang wrote:
Generally, this means qemu crashed, can you check the guest log
to see if there is any useful info?
/var/log/libvirt/qemu/$guest.log
PS: perhaps we should grab the stderr of qemu process and dump it
to user instead.
Thanks. I set log_level and log_outputs to log everything and write it
to a file. I ran the virt-install command again and saw this output:
Starting install...
Retrieving file MANIFEST... | 3.3 kB 00:00 ...
Retrieving file linux... | 4.6 MB 00:13 ...
Retrieving file initrd.gz... | 13 MB 00:37 ...
ERROR internal error Process exited while reading console log output: 11:53:20.676:
debug : qemudInitCpuAffinity:2423 : Setting CPU affinity
11:53:20.676: debug : qemuSecurityDACSetProcessLabel:547 : Dropping privileges of VM
to 113:115
char device redirected to /dev/pts/5
Domain installation does not appear to have been
successful. If it was, you can restart your domain
by running 'virsh start test1'; otherwise, please
restart your installation.
ERROR internal error Process exited while reading console log output: 11:53:20.676:
debug : qemudInitCpuAffinity:2423 : Setting CPU affinity
11:53:20.676: debug : qemuSecurityDACSetProcessLabel:547 : Dropping privileges of VM
to 113:115
char device redirected to /dev/pts/5
Traceback (most recent call last):
File "/usr/bin/virt-install", line 1033, in <module>
main()
File "/usr/bin/virt-install", line 915, in main
start_time, guest.start_install)
File "/usr/bin/virt-install", line 957, in do_install
dom = install_func(conscb, progresscb, wait=(not wait))
File "/usr/lib/pymodules/python2.6/virtinst/Guest.py", line 973, in
start_install
return self._do_install(consolecb, meter, removeOld, wait)
File "/usr/lib/pymodules/python2.6/virtinst/Guest.py", line 1038, in
_do_install
"install")
File "/usr/lib/pymodules/python2.6/virtinst/Guest.py", line 1009, in
_create_guest
dom = self.conn.createLinux(start_xml, 0)
File "/usr/lib/python2.6/dist-packages/libvirt.py", line 1277, in
createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed',
conn=self)
libvirtError: internal error Process exited while reading console log output:
11:53:20.676: debug : qemudInitCpuAffinity:2423 : Setting CPU affinity
11:53:20.676: debug : qemuSecurityDACSetProcessLabel:547 : Dropping privileges of VM
to 113:115
char device redirected to /dev/pts/5
The log [1] is a bit more helpful. I see the following warnings and
errors:
11:52:19.564: error : ebiptablesDriverInit:3416 : internal error essential tools to
support ip(6)tables firewalls could not be located
11:52:19.564: error : ebiptablesDriverInit:3425 : internal error firewall tools were
not found or cannot be used
11:52:19.565: warning : qemudStartup:1832 : Unable to create cgroup for driver: No
such device or address
11:52:19.613: warning : lxcStartup:1900 : Unable to create cgroup for driver: No such
device or address
11:52:21.146: error : qemudDomainLookupByName:4403 : Domain not found: no domain with
matching name 'test1'
11:52:21.163: error : storageVolumeLookupByPath:1241 : Storage volume not found: no
storage vol with matching path
11:52:21.221: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit status
'1', qemu probably failed
11:52:21.229: error : storageVolumeLookupByPath:1241 : Storage volume not found: no
storage vol with matching path
11:52:21.286: error : storageVolumeLookupByPath:1241 : Storage volume not found: no
storage vol with matching path
11:52:21.290: error : qemudDomainLookupByUUID:4378 : Domain not found: no domain with
matching uuid '53c30756-0a2c-3cd1-a07d-9084da91e9b5'
11:53:20.570: error : qemudDomainLookupByName:4403 : Domain not found: no domain with
matching name 'test1'
11:53:20.629: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit status
'1', qemu probably failed
11:53:20.673: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit status
'1', qemu probably failed
11:53:20.776: error : qemudReadLogOutput:2118 : internal error Process exited while
reading console log output: 11:53:20.676: debug : qemudInitCpuAffinity:2423 : Setting CPU
affinity
Of particular interest in the log seems to be:
11:53:20.636: debug : virExecWithHook:709 : LC_ALL=C /usr/bin/kvm -device
pci-assign,?
11:53:20.673: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit status
'1', qemu probably failed
I ran QEMU with that "-device" option:
$ LC_ALL=C /usr/bin/kvm -device pci-assign,?
property "pci-assign.?" not found
can't set property "?" to "on" for "pci-assign"
So it looks like libvirtd (0.8.3) is trying to get a list of all
properties of the pci-assign driver, but QEMU 0.12.x doesn't support
this. But I'm not sure if that's related to why QEMU crashes later on.
[1]: http://odin1.pehjota.net/~pj/servers/libvirtd.log
--
Patrick "P. J." McDermott
http://www.pehjota.net/
http://www.pehjota.net/contact.html
11:14 p.m.
On 2012年12月28日 05:28, Patrick 'P. J.' McDermott wrote:
On 2012-12-26 10:28, Gao Yongwei wrote:
>>> you could change the log level of libvirt daemon by edit
> /etc/libvirt/libvirtd.log, and see more information
On 2012-12-26 09:49, Osier Yang wrote:
> Generally, this means qemu crashed, can you check the guest log
> to see if there is any useful info?
>
> /var/log/libvirt/qemu/$guest.log
>
> PS: perhaps we should grab the stderr of qemu process and dump it
> to user instead.
Thanks. I set log_level and log_outputs to log everything and write it
to a file. I ran the virt-install command again and saw this output:
Starting install...
Retrieving file MANIFEST... | 3.3 kB 00:00 ...
Retrieving file linux... | 4.6 MB 00:13 ...
Retrieving file initrd.gz... | 13 MB 00:37 ...
ERROR internal error Process exited while reading console log output:
11:53:20.676: debug : qemudInitCpuAffinity:2423 : Setting CPU affinity
11:53:20.676: debug : qemuSecurityDACSetProcessLabel:547 : Dropping privileges of VM
to 113:115
char device redirected to /dev/pts/5
Domain installation does not appear to have been
successful. If it was, you can restart your domain
by running 'virsh start test1'; otherwise, please
restart your installation.
ERROR internal error Process exited while reading console log output:
11:53:20.676: debug : qemudInitCpuAffinity:2423 : Setting CPU affinity
11:53:20.676: debug : qemuSecurityDACSetProcessLabel:547 : Dropping privileges of VM
to 113:115
char device redirected to /dev/pts/5
Traceback (most recent call last):
File "/usr/bin/virt-install", line 1033, in<module>
main()
File "/usr/bin/virt-install", line 915, in main
start_time, guest.start_install)
File "/usr/bin/virt-install", line 957, in do_install
dom = install_func(conscb, progresscb, wait=(not wait))
File "/usr/lib/pymodules/python2.6/virtinst/Guest.py", line 973, in
start_install
return self._do_install(consolecb, meter, removeOld, wait)
File "/usr/lib/pymodules/python2.6/virtinst/Guest.py", line 1038, in
_do_install
"install")
File "/usr/lib/pymodules/python2.6/virtinst/Guest.py", line 1009, in
_create_guest
dom = self.conn.createLinux(start_xml, 0)
File "/usr/lib/python2.6/dist-packages/libvirt.py", line 1277, in
createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed',
conn=self)
libvirtError: internal error Process exited while reading console log output:
11:53:20.676: debug : qemudInitCpuAffinity:2423 : Setting CPU affinity
11:53:20.676: debug : qemuSecurityDACSetProcessLabel:547 : Dropping privileges of VM
to 113:115
char device redirected to /dev/pts/5
The log [1] is a bit more helpful. I see the following warnings and
errors:
11:52:19.564: error : ebiptablesDriverInit:3416 : internal error essential tools to
support ip(6)tables firewalls could not be located
11:52:19.564: error : ebiptablesDriverInit:3425 : internal error firewall tools were
not found or cannot be used
11:52:19.565: warning : qemudStartup:1832 : Unable to create cgroup for driver: No
such device or address
11:52:19.613: warning : lxcStartup:1900 : Unable to create cgroup for driver: No
such device or address
11:52:21.146: error : qemudDomainLookupByName:4403 : Domain not found: no domain
with matching name 'test1'
11:52:21.163: error : storageVolumeLookupByPath:1241 : Storage volume not found: no
storage vol with matching path
11:52:21.221: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit status
'1', qemu probably failed
11:52:21.229: error : storageVolumeLookupByPath:1241 : Storage volume not found: no
storage vol with matching path
11:52:21.286: error : storageVolumeLookupByPath:1241 : Storage volume not found: no
storage vol with matching path
11:52:21.290: error : qemudDomainLookupByUUID:4378 : Domain not found: no domain
with matching uuid '53c30756-0a2c-3cd1-a07d-9084da91e9b5'
11:53:20.570: error : qemudDomainLookupByName:4403 : Domain not found: no domain
with matching name 'test1'
11:53:20.629: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit status
'1', qemu probably failed
11:53:20.673: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit status
'1', qemu probably failed
11:53:20.776: error : qemudReadLogOutput:2118 : internal error Process exited while
reading console log output: 11:53:20.676: debug : qemudInitCpuAffinity:2423 : Setting CPU
affinity
Of particular interest in the log seems to be:
11:53:20.636: debug : virExecWithHook:709 : LC_ALL=C /usr/bin/kvm -device
pci-assign,?
11:53:20.673: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit status
'1', qemu probably failed
I ran QEMU with that "-device" option:
$ LC_ALL=C /usr/bin/kvm -device pci-assign,?
property "pci-assign.?" not found
can't set property "?" to "on" for "pci-assign"
qemudParsePCIDeviceStrs should be involked when detecting the
qemu capability, and it should be the cause of the qemu crash.
However, unfortunately, I can't even find the function from
git log.
So it looks like libvirtd (0.8.3) is trying to get a list of all
It's too old. :-), can you try to upgrade your libvirt?
properties of the pci-assign driver, but QEMU 0.12.x doesn't
support
this. But I'm not sure if that's related to why QEMU crashes later on.
[1]: http://odin1.pehjota.net/~pj/servers/libvirtd.log
11:15 p.m.
On 2012年12月28日 13:14, Osier Yang wrote:
On 2012年12月28日 05:28, Patrick 'P. J.' McDermott wrote:
> On 2012-12-26 10:28, Gao Yongwei wrote:
>>>> you could change the log level of libvirt daemon by edit
>> /etc/libvirt/libvirtd.log, and see more information
>
> On 2012-12-26 09:49, Osier Yang wrote:
>> Generally, this means qemu crashed, can you check the guest log
>> to see if there is any useful info?
>>
>> /var/log/libvirt/qemu/$guest.log
>>
>> PS: perhaps we should grab the stderr of qemu process and dump it
>> to user instead.
>
> Thanks. I set log_level and log_outputs to log everything and write it
> to a file. I ran the virt-install command again and saw this output:
>
> Starting install...
> Retrieving file MANIFEST... | 3.3 kB 00:00 ...
> Retrieving file linux... | 4.6 MB 00:13 ...
> Retrieving file initrd.gz... | 13 MB 00:37 ...
> ERROR internal error Process exited while reading console log output:
> 11:53:20.676: debug : qemudInitCpuAffinity:2423 : Setting CPU affinity
> 11:53:20.676: debug : qemuSecurityDACSetProcessLabel:547 : Dropping
> privileges of VM to 113:115
> char device redirected to /dev/pts/5
>
> Domain installation does not appear to have been
> successful. If it was, you can restart your domain
> by running 'virsh start test1'; otherwise, please
> restart your installation.
> ERROR internal error Process exited while reading console log output:
> 11:53:20.676: debug : qemudInitCpuAffinity:2423 : Setting CPU affinity
> 11:53:20.676: debug : qemuSecurityDACSetProcessLabel:547 : Dropping
> privileges of VM to 113:115
> char device redirected to /dev/pts/5
> Traceback (most recent call last):
> File "/usr/bin/virt-install", line 1033, in<module>
> main()
> File "/usr/bin/virt-install", line 915, in main
> start_time, guest.start_install)
> File "/usr/bin/virt-install", line 957, in do_install
> dom = install_func(conscb, progresscb, wait=(not wait))
> File "/usr/lib/pymodules/python2.6/virtinst/Guest.py", line 973, in
> start_install
> return self._do_install(consolecb, meter, removeOld, wait)
> File "/usr/lib/pymodules/python2.6/virtinst/Guest.py", line 1038, in
> _do_install
> "install")
> File "/usr/lib/pymodules/python2.6/virtinst/Guest.py", line 1009, in
> _create_guest
> dom = self.conn.createLinux(start_xml, 0)
> File "/usr/lib/python2.6/dist-packages/libvirt.py", line 1277, in
> createLinux
> if ret is None:raise libvirtError('virDomainCreateLinux() failed',
> conn=self)
> libvirtError: internal error Process exited while reading console log
> output: 11:53:20.676: debug : qemudInitCpuAffinity:2423 : Setting CPU
> affinity
> 11:53:20.676: debug : qemuSecurityDACSetProcessLabel:547 : Dropping
> privileges of VM to 113:115
> char device redirected to /dev/pts/5
>
> The log [1] is a bit more helpful. I see the following warnings and
> errors:
>
> 11:52:19.564: error : ebiptablesDriverInit:3416 : internal error
> essential tools to support ip(6)tables firewalls could not be located
> 11:52:19.564: error : ebiptablesDriverInit:3425 : internal error
> firewall tools were not found or cannot be used
> 11:52:19.565: warning : qemudStartup:1832 : Unable to create cgroup
> for driver: No such device or address
> 11:52:19.613: warning : lxcStartup:1900 : Unable to create cgroup for
> driver: No such device or address
> 11:52:21.146: error : qemudDomainLookupByName:4403 : Domain not found:
> no domain with matching name 'test1'
> 11:52:21.163: error : storageVolumeLookupByPath:1241 : Storage volume
> not found: no storage vol with matching path
> 11:52:21.221: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit
> status '1', qemu probably failed
> 11:52:21.229: error : storageVolumeLookupByPath:1241 : Storage volume
> not found: no storage vol with matching path
> 11:52:21.286: error : storageVolumeLookupByPath:1241 : Storage volume
> not found: no storage vol with matching path
> 11:52:21.290: error : qemudDomainLookupByUUID:4378 : Domain not found:
> no domain with matching uuid '53c30756-0a2c-3cd1-a07d-9084da91e9b5'
> 11:53:20.570: error : qemudDomainLookupByName:4403 : Domain not found:
> no domain with matching name 'test1'
> 11:53:20.629: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit
> status '1', qemu probably failed
> 11:53:20.673: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit
> status '1', qemu probably failed
> 11:53:20.776: error : qemudReadLogOutput:2118 : internal error Process
> exited while reading console log output: 11:53:20.676: debug :
> qemudInitCpuAffinity:2423 : Setting CPU affinity
>
> Of particular interest in the log seems to be:
>
> 11:53:20.636: debug : virExecWithHook:709 : LC_ALL=C /usr/bin/kvm
> -device pci-assign,?
> 11:53:20.673: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit
> status '1', qemu probably failed
>
> I ran QEMU with that "-device" option:
>
> $ LC_ALL=C /usr/bin/kvm -device pci-assign,?
> property "pci-assign.?" not found
> can't set property "?" to "on" for "pci-assign"
qemudParsePCIDeviceStrs should be involked when detecting the
qemu capability, and it should be the cause of the qemu crash.
s/should/should not/,
However, unfortunately, I can't even find the function from
git log.
>
> So it looks like libvirtd (0.8.3) is trying to get a list of all
It's too old. :-), can you try to upgrade your libvirt?
> properties of the pci-assign driver, but QEMU 0.12.x doesn't support
> this. But I'm not sure if that's related to why QEMU crashes later on.
>
> [1]: http://odin1.pehjota.net/~pj/servers/libvirtd.log
>
_______________________________________________
libvirt-users mailing list
libvirt-users(a)redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
11:10 a.m.
New subject: [libvirt-users] [Solved] Error installing VM: "Process exited while reading console log output"
On 2012-12-28 00:14, Osier Yang wrote:
On 2012年12月28日 05:28, Patrick 'P. J.' McDermott wrote:
[...]
> Of particular interest in the log seems to be:
>
> 11:53:20.636: debug : virExecWithHook:709 : LC_ALL=C /usr/bin/kvm -device
pci-assign,?
> 11:53:20.673: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit status
'1', qemu probably failed
>
> I ran QEMU with that "-device" option:
>
> $ LC_ALL=C /usr/bin/kvm -device pci-assign,?
> property "pci-assign.?" not found
> can't set property "?" to "on" for
"pci-assign"
qemudParsePCIDeviceStrs should be involked when detecting the
qemu capability, and it should [not] be the cause of the qemu crash.
Yeah, that's what I thought.
However, unfortunately, I can't even find the function from
git log.
It's defined statically at src/qemu/qemu_conf.c:1384 in libvirt 0.8.3
[1].
> So it looks like libvirtd (0.8.3) is trying to get a list of all
It's too old. :-), can you try to upgrade your libvirt?
Yeah, I'm trying to set up virtual machines in an old host system, which
I plan to reinstall – likely with a newer OS version – after I move all
of its services to the VMs. :)
I installed backported packages of libvirt 0.9.12 and qemu-kvm 1.1.2.
Running virt-install again failed, but this time QEMU gave a rather
helpful error message:
Starting install...
Retrieving file MANIFEST... | 3.3 kB 00:00 ...
Retrieving file linux... | 4.6 MB 00:13 ...
Retrieving file initrd.gz... | 13 MB 00:45 ...
ERROR internal error Process exited while reading console log output: 2012-12-29
03:41:07.802+0000: 1532: info : libvirt version: 0.9.12
char device redirected to /dev/pts/5
Failed to allocate 140737488355328 B: Cannot allocate memory
Domain installation does not appear to have been
successful. If it was, you can restart your domain
by running 'virsh start test1'; otherwise, please
restart your installation.
ERROR internal error Process exited while reading console log output: 2012-12-29
03:41:07.802+0000: 1532: info : libvirt version: 0.9.12
char device redirected to /dev/pts/5
Failed to allocate 140737488355328 B: Cannot allocate memory
Traceback (most recent call last):
File "/usr/bin/virt-install", line 1033, in <module>
main()
File "/usr/bin/virt-install", line 915, in main
start_time, guest.start_install)
File "/usr/bin/virt-install", line 957, in do_install
dom = install_func(conscb, progresscb, wait=(not wait))
File "/usr/lib/pymodules/python2.6/virtinst/Guest.py", line 973, in
start_install
return self._do_install(consolecb, meter, removeOld, wait)
File "/usr/lib/pymodules/python2.6/virtinst/Guest.py", line 1038, in
_do_install
"install")
File "/usr/lib/pymodules/python2.6/virtinst/Guest.py", line 1009, in
_create_guest
dom = self.conn.createLinux(start_xml, 0)
File "/usr/lib/python2.6/dist-packages/libvirt.py", line 1277, in
createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed',
conn=self)
libvirtError: internal error Process exited while reading console log output:
2012-12-29 03:41:07.802+0000: 1532: info : libvirt version: 0.9.12
char device redirected to /dev/pts/5
Failed to allocate 140737488355328 B: Cannot allocate memory
(This error message is from qemu_memalign() at oslib-posix.c:95 in
qemu-kvm 1.1.2 [2].)
Apparently I misunderstood the units of the --ram option value… On my
system which has 2 GiB of RAM, running virt-install with a --ram option
value of "128" (128 MiB) instead of "$((128 * 1024 * 1024))" (128
TiB!)
worked much better. :)
So this is just a case of user error, hidden by a lack of output in an
old version of QEMU.
> properties of the pci-assign driver, but QEMU 0.12.x doesn't
support
> this. But I'm not sure if that's related to why QEMU crashes later on.
>
> [1]: http://odin1.pehjota.net/~pj/servers/libvirtd.log
[1]:
http://libvirt.org/git/?p=libvirt.git;a=blob;f=src/qemu/qemu_conf.c;h=539...
[2]:
http://anonscm.debian.org/gitweb/?p=collab-maint/qemu-kvm.git;a=blob;f=os...
Thanks for the help, and sorry for the noise over such a mistake,
--
Patrick "P. J." McDermott
http://www.pehjota.net/
http://www.pehjota.net/contact.html
4:29 p.m.
On 2012-12-26 09:49, Osier Yang wrote:
Generally, this means qemu crashed, can you check the guest log
to see if there is any useful info?
/var/log/libvirt/qemu/$guest.log
PS: perhaps we should grab the stderr of qemu process and dump it
to user instead.
There's nothing there about the issue at hand, but the full QEMU command
is there. So I tried executing it (with "fd=41," removed from the
"-net tap,…" option):
# /usr/bin/kvm -S -M pc-0.12 -enable-kvm \
-m 134217728 -smp 1,sockets=1,cores=1,threads=1 \
-name test1 -uuid 393fb861-6fbf-67e7-9b98-16511b17ea0c \
-nographic -nodefaults \
-chardev socket,id=monitor,path=/var/lib/libvirt/qemu/test1.monitor,server,nowait \
-mon chardev=monitor,mode=readline \
-rtc base=utc -no-reboot -boot c \
-kernel current/images/netboot/debian-installer/amd64/linux \
-initrd current/images/netboot/debian-installer/amd64/initrd.gz \
-append 'method=http://http.us.debian.org/debian/dists/squeeze/main/installer-amd64/
auto url=http://10.0.0.128/baldr1.cfg' \
-drive file=/mnt/data/vms/test1.img,if=none,id=drive-virtio-disk0,boot=on,format=raw \
-device virtio-blk-pci,bus=pci.0,addr=0x3,drive=drive-virtio-disk0,id=virtio-disk0 \
-device virtio-net-pci,vlan=0,id=net0,mac=52:54:00:4b:97:f4,bus=pci.0,addr=0x2 \
-net tap,vlan=0,name=hostnet0 \
-chardev pty,id=serial0 -device isa-serial,chardev=serial0 \
-usb -device usb-tablet,id=input0 \
-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4
char device
redirected to /dev/pts/5
# echo ${?}
134
So it looks live I've reproduced the issue outside of libvirtd. But I
don't know what an exit status of 134 from QEMU means. Any ideas?
Thanks,
--
Patrick "P. J." McDermott
http://www.pehjota.net/
http://www.pehjota.net/contact.html
4173
days inactive
4182
days old
8 comments
3 participants
participants (3)
-
Gao Yongwei -
Osier Yang -
Patrick 'P. J.' McDermott