Bug 200126
Summary: | x86_64 guest creation fails | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jeremy Katz <katzj> |
Component: | kernel | Assignee: | Xen Maintainance List <xen-maint> |
Status: | CLOSED DUPLICATE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | jbaron, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-07-26 19:28:49 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 200124 |
Description
Jeremy Katz
2006-07-25 16:32:20 UTC
i'm also hitting this on 2.6.17-1.2439.fc6xen, when i do: /usr/sbin/xenguest-install.py What is the name of your virtual machine? foo How much RAM should be allocated (in megabytes)? 256 What would you like to use as the disk (path)? /tmp/xen-image What is the install location? nfs:qafiler.boston.redhat.com:/vol/vol1/redhat/fc5-x86_64 Starting install... Communication error with proxy: got 8250 bytes packet libvir: Xen Daemon error : GET operation failed: No such domain foo Traceback (most recent call last): File "/usr/sbin/xenguest-install.py", line 475, in ? main() File "/usr/sbin/xenguest-install.py", line 466, in main start_paravirt_install(name, ram, disk, mac, uuid, bridge, src, options.extra) File "/usr/sbin/xenguest-install.py", line 343, in start_paravirt_install dom = conn.createLinux(cfgxml, 0) File "/usr/lib64/python2.4/site-packages/libvirt.py", line 233, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed') libvirt.libvirtError: virDomainCreateLinux() failed The output of 'xm dmesg' is: (XEN) domain_crash_sync called from entry.S (XEN) Domain 11 (vcpu#0) crashed on cpu#3: (XEN) ----[ Xen-3.0-unstable Not tainted ]---- (XEN) CPU: 3 (XEN) RIP: e033:[<ffffffff80100000>] (XEN) RFLAGS: 0000000000010202 CONTEXT: guest (XEN) rax: 0000000000000000 rbx: 0000000000000000 rcx: 0000000000000000 (XEN) rdx: 0000000000000000 rsi: ffffffff807d1000 rdi: 0000000000000000 (XEN) rbp: 0000000000000000 rsp: ffffffff807de000 r8: 0000000000000000 (XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000 (XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000 (XEN) r15: 0000000000000000 cr0: 000000008005003b cr3: 0000000035d8b000 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 (XEN) Guest stack trace from rsp=ffffffff807de000: (XEN) Fault while accessing guest memory. |