Bug 19960 - Невозможно запустить виртуальную машину
Summary: Невозможно запустить виртуальную машину
Status: CLOSED WONTFIX
Alias: None
Product: Sisyphus
Classification: Development
Component: mkve (show other bugs)
Version: unstable
Hardware: all Linux
: P3 normal
Assignee: placeholder@altlinux.org
QA Contact: qa-sisyphus
URL:
Keywords:
Depends on:
Blocks: 19564
  Show dependency tree
 
Reported: 2009-05-07 12:58 MSD by Andriy Stepanov (stanv)
Modified: 2009-06-08 18:00 MSD (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andriy Stepanov (stanv) 2009-05-07 12:58:29 MSD 
[root@stanv ~]# mkve start --name fst
libvir: error : Unknown failure
/usr/bin/mkve: Unknown failure

или же:

# mkve start --name fst
libvir: QEMU error : internal error unable to start guest:
/usr/bin/mkve: internal error unable to start guest:

Раз так раз так.

# rpm -q mkve
mkve-0.10-alt1
Comment 1 Andriy Stepanov (stanv) 2009-05-07 13:02:23 MSD 
Или вот так:

# mkve start --name fst
libvir: QEMU error : internal error Unable to open monitor path /dev/pts/12
/usr/bin/mkve: internal error Unable to open monitor path /dev/pts/12

# mkve start --name fst
libvir: QEMU error : Failure while reading monitor startup output: Input/output error
/usr/bin/mkve: Failure while reading monitor startup output: Input/output error
Comment 2 Andriy Stepanov (stanv) 2009-05-07 13:28:37 MSD 
Может будет интересен лог, когда виртуальная машина создавалась из bundle:

/usr/bin/mkve: Machine: run hypervisor-specific stuff after creating a template
/usr/bin/mkve: Machine: create and define an XML description of domain
/usr/bin/mkve: Machine: create with following xml:
<domain type="kvm">
  <name>fst</name>
  <memory>524288</memory>
  <vcpu>1</vcpu>
  <os>
    <type arch="x86_64" machine="pc">hvm</type>
    <boot dev="hd"/>
  </os>
  <devices>
    <emulator>/usr/bin/kvm</emulator>
    <graphics type="vnc" port="-1"/>
    <disk device="disk" type="file">
      <source file="/var/lib/mkve/machines/fst/files.tar"/>
      <target dev="sda"/>
    </disk>
    <interface type="bridge">
      <source bridge="lan"/>
    </interface>
  </devices>
</domain>

/usr/bin/mkve: Machine: run hypervisor-specific stuff after defining an XML
Comment 3 Andriy Stepanov (stanv) 2009-05-07 13:36:13 MSD 
Когда говоришь: # mkve start --name fst

В /var/log/messages появляеться такое:
May  6 17:36:17 stanv kernel: device vnet0 entered promiscuous mode
May  6 17:36:17 stanv kernel: lan: port 4(vnet0) entering learning state
May  6 17:36:17 stanv /etc/net: ERROR: /etc/net/scripts/ifup-removable: ignored unknown interface 'vnet0' (lookup ALLOW_UNKNOWN option or create a usable configuration)
May  6 17:36:17 stanv /etc/net: ERROR: /etc/net/scripts/ifup-removable: USE_HOTPLUG is disabled for vnet0
May  6 17:36:17 stanv /etc/net: ERROR: /etc/net/scripts/ifup-removable: No TYPE is specified for iface 'vnet0' and can't guess automatically. Please fix.
May  6 17:36:17 stanv kernel: lan: port 4(vnet0) entering disabled state
May  6 17:36:17 stanv kernel: device vnet0 left promiscuous mode
May  6 17:36:17 stanv kernel: lan: port 4(vnet0) entering disabled state
May  6 17:36:17 stanv libvirtd: 17:36:17.448: error : internal error Unable to open monitor path /dev/pts/12
May  6 17:36:17 stanv /etc/net: ERROR: /etc/net/scripts/ifdown-removable: ignored unknown interface 'vnet0' (lookup ALLOW_UNKNOWN option or create a usable configuration)
May  6 17:36:17 stanv /etc/net: ERROR: /etc/net/scripts/ifdown-removable: No TYPE is specified for iface 'vnet0' and can't guess automatically. Please fix.
May  6 17:36:17 stanv /etc/net: ERROR: /etc/net/scripts/ifdown-removable: USE_HOTPLUG is disabled for vnet0
Comment 4 aspsk 2009-05-15 14:56:23 MSD 
(В ответ на комментарий №3)
> Когда говоришь: # mkve start --name fst
> 
> В /var/log/messages появляеться такое:
> May  6 17:36:17 stanv kernel: device vnet0 entered promiscuous mode
> May  6 17:36:17 stanv kernel: lan: port 4(vnet0) entering learning state
> May  6 17:36:17 stanv /etc/net: ERROR: /etc/net/scripts/ifup-removable: ignored
> unknown interface 'vnet0' (lookup ALLOW_UNKNOWN option or create a usable
> configuration)
> May  6 17:36:17 stanv /etc/net: ERROR: /etc/net/scripts/ifup-removable:
> USE_HOTPLUG is disabled for vnet0
> May  6 17:36:17 stanv /etc/net: ERROR: /etc/net/scripts/ifup-removable: No TYPE
> is specified for iface 'vnet0' and can't guess automatically. Please fix.
> May  6 17:36:17 stanv kernel: lan: port 4(vnet0) entering disabled state
> May  6 17:36:17 stanv kernel: device vnet0 left promiscuous mode
> May  6 17:36:17 stanv kernel: lan: port 4(vnet0) entering disabled state
> May  6 17:36:17 stanv libvirtd: 17:36:17.448: error : internal error Unable to
> open monitor path /dev/pts/12
> May  6 17:36:17 stanv /etc/net: ERROR: /etc/net/scripts/ifdown-removable:
> ignored unknown interface 'vnet0' (lookup ALLOW_UNKNOWN option or create a
> usable configuration)
> May  6 17:36:17 stanv /etc/net: ERROR: /etc/net/scripts/ifdown-removable: No
> TYPE is specified for iface 'vnet0' and can't guess automatically. Please fix.
> May  6 17:36:17 stanv /etc/net: ERROR: /etc/net/scripts/ifdown-removable:
> USE_HOTPLUG is disabled for vnet0

rpm -qa | grep libvirt
Comment 5 aspsk 2009-05-27 13:19:54 MSD 
Так что, какие симптомы, если обновиться до Сизифа?
Comment 6 aspsk 2009-06-08 18:00:09 MSD 
.