Xen Error

Questions about virtualization software
Forum rules
Before you post please read how to get help
bonzi
Level 1
Level 1
Posts: 18
Joined: Wed Mar 19, 2014 1:49 am

Xen Error

Postby bonzi » Wed Mar 26, 2014 2:28 am

Hi,

I'm trying to setup Xen and I'm having some problems with passthrough of my graphics card. I'm hoping there are some people here who might have had similar problems and or know what to do next. I am trying to run windows 7 enterprise in DomU. I have posted already here: http://forums.linuxmint.com/viewtopic.php?f=42&t=112013&start=380#p837253 My hardware:

MB: DX58SO
CPU: Core i7 920
Dom0: AMD R7 250
DomU: Diamond AMD 6450 http://www.amazon.com/Diamond-Multimedi ... B00519BEG4
Dom0: 4 GB RAM
DomU: 4 GB RAM

The problem is that when I do xm create /etc/xen/win7.cfg I get 'Error: (22, 'Invalid argument')' Does anybody know what this means and how I can fix it? It is related to the graphics passthrough since I can remove graphics passthrough from my win7.conf and then I can start the vm, in this case, my USB ports are still being passed through, so that at least is working. Here is some other information which might help to figure out what is wrong:

Code: Select all

uname -a
Linux jonathan-desktop 3.2.0-60-generic #91-Ubuntu SMP Wed Feb 19 03:54:44 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux


/var/log/xen/qemu-dm-win7.log

Code: Select all

domid: 1
-c config qemu network with xen bridge for
tap1.0 xenbr0
Using file /dev/mapper/guest-win7 in read-write mode
Using file /media/install/Win7.iso in read-only mode
Watching /local/domain/0/device-model/1/logdirty/cmd
Watching /local/domain/0/device-model/1/command
Watching /local/domain/1/cpu
char device redirected to /dev/pts/1
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = 0d5f4132-37e5-59a4-0510-1a14ccc4cb99
Time offset set 0
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
xs_read(/local/domain/0/device-model/1/xen_extended_power_mgmt): read error
xs_read(): vncpasswd get error. /vm/0d5f4132-37e5-59a4-0510-1a14ccc4cb99/vncpas$
medium change watch on `hdc' (index: 1): /media/install/Win7.iso
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Log-dirty: no command yet.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
vcpu-set: watch node error.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
xs_read(/local/domain/1/log-throttling): read error
qemu: ignoring not-understood drive `/local/domain/1/log-throttling'
medium change watch on `/local/domain/1/log-throttling' - unknown device, ignor$
dm-command: hot insert pass-through pci dev
register_real_device: Assigning real physical device 03:00.0 ...
register_real_device: Enable MSI translation via per device option
register_real_device: Enable power management
pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such$
pt_register_regions: IO region registered (size=0x10000000 base_addr=0xe000000c)
pt_register_regions: IO region registered (size=0x00020000 base_addr=0xc0200004)
pt_register_regions: IO region registered (size=0x00000100 base_addr=0x00004001)
pt_register_regions: Expansion ROM registered (size=0x00020000 base_addr=0xc024$
pt_msgctrl_reg_init: MSI enabled already, disable first
register_real_device: Error: Mapping irq failed, rc = -1
pt_msi_setup: msi mapped with pirq 37
pci_intx: intx=1
register_real_device: Real physical device 03:00.0 registered successfuly!
IRQ type = MSI-INTx


/etc/default/grub

Code: Select all

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
# GRUB_HIDDEN_TIMEOUT=0
# GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
GRUB_CMDLINE_XEN="iommu=1 dom0_mem=4096M"

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"


/etc/xen/win7.cfg

Code: Select all

kernel = '/usr/lib/xen-default/boot/hvmloader'
builder='hvm'
memory = 4096
name = 'win7'
vcpus=4
acpi=1
apic=1
on_xend_stop='shutdown'
vif = [ 'mac=00:16:3e:68:e1:01,bridge=xenbr0' ]
disk = [ 'phy:/dev/mapper/guest-win7,hda,w' , 'file:/media/install/Win7.iso,hdc$
device_model = '/usr/lib/xen-default/bin/qemu-dm'
boot='dc'
sdl=0
vnc=1
vncpasswd=''
stdvga=0
serial='pty'
tsc_mode=0
viridian=1
usb=0
usbdevice='tablet'
gfx_passthru=0
pci=[ '03:00.0', '03:00.1', '00:1a.2' ]
localtime=1
pci_power_mgmt=1


inxi -F

Code: Select all

System:    Host: jonathan-desktop Kernel: 3.2.0-60-generic x86_64 (64 bit) Desktop: Gnome Distro: Linux Mint 13 Maya
Machine:   Mobo: Intel model: DX58SO version: AAE29331-701
           Bios: Intel version: SOX5810J.86A.5600.2013.0729.2250 date: 07/29/2013
CPU:       Quad core Intel Core i7 CPU 920 (-HT-MCP-) cache: 8192 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3)
           Clock Speeds: 1: 2702.586 MHz 2: 2702.586 MHz 3: 2702.586 MHz 4: 2702.586 MHz 5: 2702.586 MHz 6: 2702.586 MHz 7: 2702.586 MHz 8: 2702.586 MHz
Graphics:  Card-1: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8600 Series]
           Card-2: Advanced Micro Devices [AMD/ATI] Caicos [Radeon HD 6450/7450/8450]
           X.Org: 1.11.3 drivers: ati,fglrx (unloaded: vesa,fbdev,radeon) Resolution: 1920x1080@60.0hz
           GLX Renderer: AMD Radeon R7 200 Series GLX Version: 4.3.12682 - CPC 13.251
Audio:     Card-1: Advanced Micro Devices [AMD/ATI] Caicos HDMI Audio [Radeon HD 6400 Series] driver: pciback
           Card-2: C-Media CMI8738/CMI8768 PCI Audio driver: snd_cmipci
           Card-3: Advanced Micro Devices [AMD/ATI] Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] driver: snd_hda_intel
           Card-4: Logitech driver: USB Audio
           Sound: Advanced Linux Sound Architecture ver: 1.0.24
Network:   Card: Intel 82574L Gigabit Network Connection driver: e1000e
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 68:05:ca:12:09:c4
Drives:    HDD Total Size: 8201.7GB (13.3% used) 1: /dev/sda WDC_WD20EARS 2000.4GB
           2: /dev/sdb INTEL_SSDSA2CW12 120.0GB 3: /dev/sdc INTEL_SSDSA2M080 80.0GB
           4: /dev/sdd WDC_WD20EARS 2000.4GB 5: /dev/sde WDC_WD20EARS 2000.4GB
           6: /dev/sdf Hitachi_HDS72101 1000.2GB 7: /dev/sdg Hitachi_HDS72101 1000.2GB
Partition: ID: / size: 103G used: 15G (16%) fs: ext4 ID: swap-1 size: 8.58GB used: 0.00GB (0%) fs: swap
Sensors:   Error: You do not have the sensors app installed.
Info:      Processes: 226 Uptime: 17 min Memory: 915.3/2831.2MB Client: Shell inxi: 1.7.33


xm dmesg

Code: Select all

(XEN) Xen version 4.1.2 (Ubuntu 4.1.2-2ubuntu2) (stefan.bader@canonical.com) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu2) ) Thu Mar  8 14:31:11 UTC 2012
(XEN) Bootloader: GRUB 1.99-21ubuntu3.14
(XEN) Command line: placeholder iommu=1 dom0_mem=4096M xen-pciback.hide=(03.00.0)(03.00.1)
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN)  Found 7 MBR signatures
(XEN)  Found 6 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000008f000 (usable)
(XEN)  000000000008f000 - 0000000000090000 (reserved)
(XEN)  0000000000090000 - 000000000009a800 (usable)
(XEN)  000000000009a800 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000bf49d000 (usable)
(XEN)  00000000bf49d000 - 00000000bf4bf000 (reserved)
(XEN)  00000000bf4bf000 - 00000000bf622000 (usable)
(XEN)  00000000bf622000 - 00000000bf7bf000 (ACPI NVS)
(XEN)  00000000bf7bf000 - 00000000bf7db000 (usable)
(XEN)  00000000bf7db000 - 00000000bf7ff000 (ACPI data)
(XEN)  00000000bf7ff000 - 00000000bf800000 (usable)
(XEN)  00000000bf800000 - 00000000c0000000 (reserved)
(XEN)  00000000f8000000 - 00000000fd000000 (reserved)
(XEN)  00000000ffe00000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 0000000240000000 (usable)
(XEN) ACPI: RSDP 000FE020, 0024 (r2 INTEL )
(XEN) ACPI: XSDT BF7FE120, 0074 (r1 INTEL  DX58SO       15E0       1000013)
(XEN) ACPI: FACP BF7FD000, 00F4 (r3 INTEL  DX58SO       15E0 MSFT  100000D)
(XEN) ACPI Warning (tbfadt-0444): Optional field "Pm2ControlBlock" has zero address or length: 0000000000000450/0 [20070126]
(XEN) ACPI: DSDT BF7F8000, 4622 (r2 INTEL  DX58SO       15E0 MSFT  100000D)
(XEN) ACPI: FACS BF725000, 0040
(XEN) ACPI: APIC BF7F7000, 0138 (r2 INTEL  DX58SO       15E0 MSFT  100000D)
(XEN) ACPI: WDDT BF7F6000, 0040 (r1 INTEL  DX58SO       15E0 MSFT  100000D)
(XEN) ACPI: MCFG BF7F5000, 003C (r1 INTEL  DX58SO       15E0 MSFT  100000D)
(XEN) ACPI: ASF! BF7F4000, 00AC (r32 INTEL  DX58SO       15E0 MSFT  100000D)
(XEN) ACPI: HPET BF7F3000, 0038 (r1 INTEL  DX58SO       15E0 MSFT  100000D)
(XEN) ACPI: SSDT BF7DE000, 12A04 (r1 INTEL  SSDT  PM     15E0 MSFT  100000D)
(XEN) ACPI: DMAR BF7DB000, 0168 (r1 INTEL  DX58SO       15E0 MSFT  100000D)
(XEN) ACPI: WDTT BF7F1000, 020C (r2 INTEL  DX58SO       15E0 MSFT  100000D)
(XEN) ACPI: ASPT BF7F2000, 0034 (r4 INTEL  PerfTune     15E0 MSFT  100000D)
(XEN) System RAM: 8181MB (8378072kB)
(XEN) Domain heap initialised
(XEN) Processor #0 7:10 APIC version 21
(XEN) Processor #2 7:10 APIC version 21
(XEN) Processor #4 7:10 APIC version 21
(XEN) Processor #6 7:10 APIC version 21
(XEN) Processor #1 7:10 APIC version 21
(XEN) Processor #3 7:10 APIC version 21
(XEN) Processor #5 7:10 APIC version 21
(XEN) Processor #7 7:10 APIC version 21
(XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) Table is not found!
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2702.586 MHz processor.
(XEN) Initing memory sharing.
(XEN) Intel VT-d Snoop Control enabled.
(XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
(XEN) Intel VT-d Queued Invalidation enabled.
(XEN) Intel VT-d Interrupt Remapping enabled.
(XEN) Intel VT-d Shared EPT tables not enabled.
(XEN) I/O virtualisation enabled
(XEN)  - Dom0 mode: Relaxed
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) Platform timer is 14.318MHz HPET
(XEN) Allocated console ring of 16 KiB.
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Extended Page Tables (EPT)
(XEN)  - Virtual-Processor Identifiers (VPID)
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN) EPT supports 2MB super page.
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging detected.
(XEN) Brought up 8 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x2060000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   0000000230000000->0000000234000000 (1022083 pages to be allocated)
(XEN)  Init. ramdisk: 000000023d883000->0000000240000000
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff81000000->ffffffff82060000
(XEN)  Init. ramdisk: ffffffff82060000->ffffffff847dd000
(XEN)  Phys-Mach map: ffffffff847dd000->ffffffff84fdd000
(XEN)  Start info:    ffffffff84fdd000->ffffffff84fdd4b4
(XEN)  Page tables:   ffffffff84fde000->ffffffff8500b000
(XEN)  Boot stack:    ffffffff8500b000->ffffffff8500c000
(XEN)  TOTAL:         ffffffff80000000->ffffffff85400000
(XEN)  ENTRY ADDRESS: ffffffff81cfc200
(XEN) Dom0 has maximum 8 VCPUs
(XEN) Scrubbing Free RAM: ........................................done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type \047CTRL-a\047 three times to switch input to Xen)
(XEN) Freed 220kB init memory.
(XEN) physdev.c:155: dom0: wrong map_pirq type 3


/var/log/xen/xend.log

Code: Select all

[2014-03-24 21:32:41 1760] DEBUG (XendDomainInfo:103) XendDomainInfo.create(['vm', ['name', 'win7'], ['memory', 4096], ['on_xend_start', 'ignore'], ['on_xend_stop', 'shutdown'], ['vcpus', 4], ['localtime', 1], ['oos', 1], ['image', ['hvm', ['kernel', '/usr/lib/xen-default/boot/hvmloader'], ['videoram', 4], ['serial', 'pty'], ['acpi', 1], ['apic', 1], ['boot', 'dc'], ['cpuid', []], ['cpuid_check', []], ['display', ':0'], ['fda', ''], ['fdb', ''], ['gfx_passthru', 0], ['guest_os_type', 'default'], ['hap', 1], ['hpet', 0], ['isa', 0], ['keymap', ''], ['localtime', 1], ['nographic', 0], ['oos', 1], ['pae', 1], ['pci', [['0x0000', '0x03', '0x00', '0x0', '0x100', [], '03:00.0'], ['0x0000', '0x03', '0x00', '0x1', '0x100', [], '03:00.1'], ['0x0000', '0x00', '0x1a', '0x2', '0x100', [], '00:1a.2']]], ['pci_msitranslate', 1], ['pci_power_mgmt', 1], ['rtc_timeoffset', 0], ['sdl', 0], ['soundhw', ''], ['stdvga', 0], ['timer_mode', 1], ['usb', 0], ['usbdevice', 'tablet'], ['vcpus', 4], ['vnc', 1], ['vncunused', 1], ['viridian', 1], ['vpt_align', 1], ['xauthority', '/home/jonathan/.Xauthority'], ['xen_platform_pci', 1], ['memory_sharing', 0], ['device_model', '/usr/lib/xen-default/bin/qemu-dm'], ['vncpasswd', 'XXXXXXXX'], ['tsc_mode', 0], ['nomigrate', 0]]], ['s3_integrity', 1], ['device', ['vbd', ['uname', 'phy:/dev/mapper/guest-win7'], ['dev', 'hda'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'file:/media/install/Win7.iso'], ['dev', 'hdc:cdrom'], ['mode', 'r']]], ['device', ['pci', ['dev', ['slot', '0x00'], ['domain', '0x0000'], ['key', '03:00.0'], ['bus', '0x03'], ['vdevfn', '0x100'], ['func', '0x0']], ['dev', ['slot', '0x00'], ['domain', '0x0000'], ['key', '03:00.1'], ['bus', '0x03'], ['vdevfn', '0x100'], ['func', '0x1']], ['dev', ['slot', '0x1a'], ['domain', '0x0000'], ['key', '00:1a.2'], ['bus', '0x00'], ['vdevfn', '0x100'], ['func', '0x2']]]], ['device', ['vif', ['bridge', 'xenbr0'], ['mac', '00:16:3e:68:e1:01']]]])
[2014-03-24 21:32:41 1760] DEBUG (XendDomainInfo:2498) XendDomainInfo.constructDomain
[2014-03-24 21:32:41 1760] DEBUG (balloon:187) Balloon: 5127156 KiB free; need 16384; done.
[2014-03-24 21:32:41 1760] DEBUG (XendDomain:476) Adding Domain: 1
[2014-03-24 21:32:41 1760] DEBUG (XendDomainInfo:2836) XendDomainInfo.initDomain: 1 256
[2014-03-24 21:32:41 1760] DEBUG (image:339) No VNC passwd configured for vfb access
[2014-03-24 21:32:41 1760] DEBUG (image:891) args: boot, val: dc
[2014-03-24 21:32:41 1760] DEBUG (image:891) args: fda, val: None
[2014-03-24 21:32:41 1760] DEBUG (image:891) args: fdb, val: None
[2014-03-24 21:32:41 1760] DEBUG (image:891) args: soundhw, val: None
[2014-03-24 21:32:41 1760] DEBUG (image:891) args: localtime, val: 1
[2014-03-24 21:32:41 1760] DEBUG (image:891) args: serial, val: ['pty']
[2014-03-24 21:32:41 1760] DEBUG (image:891) args: std-vga, val: 0
[2014-03-24 21:32:41 1760] DEBUG (image:891) args: isa, val: 0
[2014-03-24 21:32:41 1760] DEBUG (image:891) args: acpi, val: 1
[2014-03-24 21:32:41 1760] DEBUG (image:891) args: usb, val: 0
[2014-03-24 21:32:41 1760] DEBUG (image:891) args: usbdevice, val: tablet
[2014-03-24 21:32:41 1760] DEBUG (image:891) args: gfx_passthru, val: 0
[2014-03-24 21:32:41 1760] INFO (image:822) Need to create platform device.[domid:1]
[2014-03-24 21:32:41 1760] DEBUG (XendDomainInfo:2863) _initDomain:shadow_memory=0x0, memory_static_max=0x100000000, memory_static_min=0x0.
[2014-03-24 21:32:41 1760] INFO (image:182) buildDomain os=hvm dom=1 vcpus=4
[2014-03-24 21:32:41 1760] DEBUG (image:949) domid          = 1
[2014-03-24 21:32:41 1760] DEBUG (image:950) image          = /usr/lib/xen-default/boot/hvmloader
[2014-03-24 21:32:41 1760] DEBUG (image:951) store_evtchn   = 5
[2014-03-24 21:32:41 1760] DEBUG (image:952) memsize        = 4096
[2014-03-24 21:32:41 1760] DEBUG (image:953) target         = 4096
[2014-03-24 21:32:41 1760] DEBUG (image:954) vcpus          = 4
[2014-03-24 21:32:41 1760] DEBUG (image:955) vcpu_avail     = 15
[2014-03-24 21:32:41 1760] DEBUG (image:956) acpi           = 1
[2014-03-24 21:32:41 1760] DEBUG (image:957) apic           = 1
[2014-03-24 21:32:41 1760] INFO (XendDomainInfo:2357) createDevice: vfb : {'vncunused': 1, 'other_config': {'vncunused': 1, 'vnc': '1'}, 'vnc': '1', 'uuid': '5275279a-8a65-00f6-b8d9-b214cc326516'}
[2014-03-24 21:32:41 1760] DEBUG (DevController:95) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/vfb/1/0'} to /local/domain/1/device/vfb/0.
[2014-03-24 21:32:41 1760] DEBUG (DevController:97) DevController: writing {'vncunused': '1', 'domain': 'win7', 'frontend': '/local/domain/1/device/vfb/0', 'uuid': '5275279a-8a65-00f6-b8d9-b214cc326516', 'frontend-id': '1', 'state': '1', 'online': '1', 'vnc': '1'} to /local/domain/0/backend/vfb/1/0.
[2014-03-24 21:32:41 1760] INFO (XendDomainInfo:2357) createDevice: vbd : {'uuid': 'b5c08b1c-9453-c227-5d03-93c5913a1a04', 'bootable': 1, 'driver': 'paravirtualised', 'dev': 'hda', 'uname': 'phy:/dev/mapper/guest-win7', 'mode': 'w'}
[2014-03-24 21:32:41 1760] DEBUG (DevController:95) DevController: writing {'backend-id': '0', 'virtual-device': '768', 'device-type': 'disk', 'state': '1', 'backend': '/local/domain/0/backend/vbd/1/768'} to /local/domain/1/device/vbd/768.
[2014-03-24 21:32:41 1760] DEBUG (DevController:97) DevController: writing {'domain': 'win7', 'frontend': '/local/domain/1/device/vbd/768', 'uuid': 'b5c08b1c-9453-c227-5d03-93c5913a1a04', 'bootable': '1', 'dev': 'hda', 'state': '1', 'params': '/dev/mapper/guest-win7', 'mode': 'w', 'online': '1', 'frontend-id': '1', 'type': 'phy'} to /local/domain/0/backend/vbd/1/768.
[2014-03-24 21:32:41 1760] INFO (XendDomainInfo:2357) createDevice: vbd : {'uuid': 'd3daee78-9c63-d837-5da3-8ddb00628a82', 'bootable': 0, 'driver': 'paravirtualised', 'dev': 'hdc:cdrom', 'uname': 'file:/media/install/Win7.iso', 'mode': 'r'}
[2014-03-24 21:32:41 1760] DEBUG (DevController:95) DevController: writing {'backend-id': '0', 'virtual-device': '5632', 'device-type': 'cdrom', 'state': '1', 'backend': '/local/domain/0/backend/vbd/1/5632'} to /local/domain/1/device/vbd/5632.
[2014-03-24 21:32:41 1760] DEBUG (DevController:97) DevController: writing {'domain': 'win7', 'frontend': '/local/domain/1/device/vbd/5632', 'uuid': 'd3daee78-9c63-d837-5da3-8ddb00628a82', 'bootable': '0', 'dev': 'hdc', 'state': '1', 'params': '/media/install/Win7.iso', 'mode': 'r', 'online': '1', 'frontend-id': '1', 'type': 'file'} to /local/domain/0/backend/vbd/1/5632.
[2014-03-24 21:32:41 1760] INFO (XendDomainInfo:2357) createDevice: vif : {'bridge': 'xenbr0', 'mac': '00:16:3e:68:e1:01', 'uuid': '08632ff1-5c6b-a34f-aeb1-0189214d0858'}
[2014-03-24 21:32:41 1760] DEBUG (DevController:95) DevController: writing {'backend-id': '0', 'mac': '00:16:3e:68:e1:01', 'handle': '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/1/0'} to /local/domain/1/device/vif/0.
[2014-03-24 21:32:41 1760] DEBUG (DevController:97) DevController: writing {'bridge': 'xenbr0', 'domain': 'win7', 'handle': '0', 'uuid': '08632ff1-5c6b-a34f-aeb1-0189214d0858', 'script': '/etc/xen/scripts/vif-bridge', 'mac': '00:16:3e:68:e1:01', 'frontend-id': '1', 'state': '1', 'online': '1', 'frontend': '/local/domain/1/device/vif/0'} to /local/domain/0/backend/vif/1/0.
[2014-03-24 21:32:41 1760] INFO (XendDomainInfo:2357) createDevice: pci : {'devs': [{'slot': '0x00', 'domain': '0x0000', 'key': '03:00.0', 'bus': '0x03', 'vdevfn': '0x100', 'func': '0x0', 'uuid': 'bc34d0ee-b4fb-fa7e-9f9a-b87db2aceb95'}, {'slot': '0x00', 'domain': '0x0000', 'key': '03:00.1', 'bus': '0x03', 'vdevfn': '0x100', 'func': '0x1', 'uuid': 'd0f451b8-c4b1-7d07-49ea-6c743c4a249b'}, {'slot': '0x1a', 'domain': '0x0000', 'key': '00:1a.2', 'bus': '0x00', 'vdevfn': '0x100', 'func': '0x2', 'uuid': '0cbd1e10-6ece-8af3-d90f-8fd08a25fcd9'}], 'uuid': 'ad2f7425-a604-b4d1-b0a6-cd819f9ceae3'}
[2014-03-24 21:32:45 1760] INFO (image:418) spawning device models: /usr/lib/xen-default/bin/qemu-dm ['/usr/lib/xen-default/bin/qemu-dm', '-d', '1', '-domain-name', 'win7', '-videoram', '4', '-vnc', '127.0.0.1:0', '-vncunused', '-vcpus', '4', '-vcpu_avail', '0xf', '-boot', 'dc', '-localtime', '-serial', 'pty', '-acpi', '-usbdevice', 'tablet', '-net', 'nic,vlan=1,macaddr=00:16:3e:68:e1:01,model=rtl8139', '-net', 'tap,vlan=1,ifname=tap1.0,bridge=xenbr0', '-M', 'xenfv']
[2014-03-24 21:32:45 1760] INFO (image:467) device model pid: 3837
[2014-03-24 21:32:45 1760] INFO (image:590) waiting for sentinel_fifo
[2014-03-24 21:32:45 1760] DEBUG (XendDomainInfo:893) XendDomainInfo.pci_device_configure: ['pci', ['dev', ['slot', '0x00'], ['domain', '0x0000'], ['key', '03:00.0'], ['bus', '0x03'], ['vdevfn', '0x100'], ['func', '0x0'], ['uuid', 'bc34d0ee-b4fb-fa7e-9f9a-b87db2aceb95']], ['state', 'Initialising'], ['sub_state', 'Booting']]
[2014-03-24 21:32:45 1760] DEBUG (XendDomainInfo:779) XendDomainInfo.hvm_pci_device_insert: {'devs': [{'slot': '0x00', 'domain': '0x0000', 'key': '03:00.0', 'bus': '0x03', 'vdevfn': '0x100', 'func': '0x0', 'uuid': 'bc34d0ee-b4fb-fa7e-9f9a-b87db2aceb95'}], 'states': ['Initialising']}
[2014-03-24 21:32:45 1760] DEBUG (XendDomainInfo:790) XendDomainInfo.hvm_pci_device_insert_dev: {'slot': '0x00', 'domain': '0x0000', 'key': '03:00.0', 'bus': '0x03', 'vdevfn': '0x100', 'func': '0x0', 'uuid': 'bc34d0ee-b4fb-fa7e-9f9a-b87db2aceb95'}
[2014-03-24 21:32:45 1760] DEBUG (XendDomainInfo:811) XendDomainInfo.hvm_pci_device_insert_dev: 0000:03:00.0@100,msitranslate=1,power_mgmt=1
[2014-03-24 21:32:45 1760] DEBUG (XendDomainInfo:815) pci: assign device 0000:03:00.0@100,msitranslate=1,power_mgmt=1
[2014-03-24 21:32:45 1760] DEBUG (image:508) signalDeviceModel: orig_state is None, retrying
[2014-03-24 21:32:46 1760] INFO (image:538) signalDeviceModel:restore dm state to running
[2014-03-24 21:32:46 1760] INFO (pciquirk:92) NO quirks found for PCI device [1002:6779:1092:6450]
[2014-03-24 21:32:46 1760] DEBUG (pciquirk:135) Permissive mode NOT enabled for PCI device [1002:6779:1092:6450]
[2014-03-24 21:32:46 1760] DEBUG (pciif:320) pci: enabling ioport 0x4000/0x100
[2014-03-24 21:32:46 1760] DEBUG (pciif:334) pci: enabling iomem 0xe0000000/0x10000000 pfn 0xe0000/0x10000
[2014-03-24 21:32:46 1760] DEBUG (pciif:334) pci: enabling iomem 0xc0200000/0x20000 pfn 0xc0200/0x20
[2014-03-24 21:32:46 1760] DEBUG (pciif:334) pci: enabling iomem 0xc0240000/0x20000 pfn 0xc0240/0x20
[2014-03-24 21:32:46 1760] DEBUG (pciif:351) pci: enabling irq 336
[2014-03-24 21:32:46 1760] ERROR (XendDomainInfo:2927) XendDomainInfo.initDomain: exception occurred
Traceback (most recent call last):
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 2914, in _initDomain
    self._createDevices()
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 2395, in _createDevices
    self.pci_device_configure_boot()
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 627, in pci_device_configure_boot
    self.pci_device_configure(dev_sxp, first_dev = first)
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 970, in pci_device_configure
    devid = self._createDevice('pci', existing_pci_conf)
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 2326, in _createDevice
    return self.getDeviceController(deviceClass).createDevice(devConfig)
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/server/DevController.py", line 67, in createDevice
    self.setupDevice(config)
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/server/pciif.py", line 453, in setupDevice
    self.setupOneDevice(d)
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/server/pciif.py", line 353, in setupOneDevice
    allow_access = True)
Error: (22, 'Invalid argument')
[2014-03-24 21:32:46 1760] ERROR (XendDomainInfo:488) VM start failed
Traceback (most recent call last):
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 474, in start
    XendTask.log_progress(31, 60, self._initDomain)
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendTask.py", line 209, in log_progress
    retval = func(*args, **kwds)
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 2930, in _initDomain
    raise VmError(str(exn))
VmError: (22, 'Invalid argument')
[2014-03-24 21:32:46 1760] DEBUG (XendDomainInfo:3071) XendDomainInfo.destroy: domid=1
[2014-03-24 21:32:46 1760] DEBUG (XendDomainInfo:2401) Destroying device model
[2014-03-24 21:32:47 1760] INFO (image:615) win7 device model terminated
[2014-03-24 21:32:47 1760] DEBUG (XendDomainInfo:2408) Releasing devices
[2014-03-24 21:32:47 1760] DEBUG (XendDomainInfo:2414) Removing vif/0
[2014-03-24 21:32:47 1760] DEBUG (XendDomainInfo:1276) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2014-03-24 21:32:47 1760] DEBUG (XendDomainInfo:2414) Removing vbd/768
[2014-03-24 21:32:47 1760] DEBUG (XendDomainInfo:1276) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
[2014-03-24 21:32:47 1760] DEBUG (XendDomainInfo:2414) Removing vbd/5632
[2014-03-24 21:32:47 1760] DEBUG (XendDomainInfo:1276) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/5632
[2014-03-24 21:32:47 1760] DEBUG (XendDomainInfo:2414) Removing vfb/0
[2014-03-24 21:32:47 1760] DEBUG (XendDomainInfo:1276) XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
[2014-03-24 21:32:47 1760] DEBUG (XendDomainInfo:2406) No device model
[2014-03-24 21:32:47 1760] DEBUG (XendDomainInfo:2408) Releasing devices
[2014-03-24 21:32:47 1760] DEBUG (XendDomainInfo:2414) Removing vif/0
[2014-03-24 21:32:47 1760] DEBUG (XendDomainInfo:1276) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2014-03-24 21:32:47 1760] DEBUG (XendDomainInfo:2414) Removing vbd/768
[2014-03-24 21:32:47 1760] DEBUG (XendDomainInfo:1276) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
[2014-03-24 21:32:47 1760] DEBUG (XendDomainInfo:2414) Removing vbd/5632
[2014-03-24 21:32:47 1760] DEBUG (XendDomainInfo:1276) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/5632
[2014-03-24 21:32:47 1760] ERROR (XendDomainInfo:108) Domain construction failed
Traceback (most recent call last):
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 106, in create
    vm.start()
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 474, in start
    XendTask.log_progress(31, 60, self._initDomain)
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendTask.py", line 209, in log_progress
    retval = func(*args, **kwds)
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 2930, in _initDomain
    raise VmError(str(exn))
VmError: (22, 'Invalid argument')


Thanks!

powerhouse
Level 5
Level 5
Posts: 979
Joined: Thu May 03, 2012 3:54 am
Location: Israel
Contact:

Re: Xen Error

Postby powerhouse » Thu Mar 27, 2014 5:48 am

EDIT: Deleted my previous post !

I installed my AMD 6450 card and tried the suggestions I had posted - with no success. I'm still looking for a solution to this nasty error 22 business. I've installed LM 16 and Xen 4.3, though.

The following thread perhaps provides a solution: http://lists.xen.org/archives/html/xen-users/2013-07/msg00077.html - read the follow-ups too. I need to try it.

My next step is to try a newer Xen release 4.3.2 and see how that fares.
Asus Sabertooth X79, i7 3930K CPU, 8x4GB Kingston DDR3 RAM, Noctua NH-D14 CPU cooler, Gigabyte GTX 970 + PNY Quadro 2000 GPU, Asus Xonar Essence STX, Sandisk Extreme 120GB + Samsung EVO 850 250GB SSD + 5 HDD, Corsair 500R case, SeaSonic 660W Gold X PS

powerhouse
Level 5
Level 5
Posts: 979
Joined: Thu May 03, 2012 3:54 am
Location: Israel
Contact:

Re: Xen Error

Postby powerhouse » Thu Mar 27, 2014 3:33 pm

I downloaded Xen 4.3.2 but wasn't able to compile it - probably some missing link. Unfortunately due to lack of time I couldn't carry on.

Here the results so far:
Hardware: AMD 7770 GPU for dom0, AMD Sapphire 6450 for domU, Asus Sabertooth X79 m/b, Intel 3930K CPU, 32 GB RAM.
OS: Linux Mint 16 Mate 64 bit for dom0, Xen 4.3, Windows 7 Pro 64 bit for domU (not installed).
Graphics driver for dom0: fglrx
Toolstack: xm

I tried different /etc/xen/win7.cfg settings, but the "error 22: invalid argument" kept showing up. I also changed the XEN command line in /etc/default/grub to read iommu=no-intremap instead of iommu=1, followed by update-grub and a reboot, all to no effect - see http://www.novell.com/support/kb/doc.php?id=7012337.

In addition, in /etc/xen/win7.cfg I changed pci = [ '02:00.0' , '02:00.1' ] to pci = [ '02:00.0' ] or pci = [ '02:00.*' ], again no luck.

A while ago I got the same results when trying to pass through my AMD 7770, but eventually succeeded with Linux Mint 13 and an old Xen 4.1.2 release (using "Force Version" in Synaptic to downgrade). Following your (bonzi's) report I didn't try LM 13.

Unfortunately I'm a little short of time now, but hope to continue my trials on Sunday. Please let me/us know if you have any news.

This is really a very annoying problem.
Asus Sabertooth X79, i7 3930K CPU, 8x4GB Kingston DDR3 RAM, Noctua NH-D14 CPU cooler, Gigabyte GTX 970 + PNY Quadro 2000 GPU, Asus Xonar Essence STX, Sandisk Extreme 120GB + Samsung EVO 850 250GB SSD + 5 HDD, Corsair 500R case, SeaSonic 660W Gold X PS

bonzi
Level 1
Level 1
Posts: 18
Joined: Wed Mar 19, 2014 1:49 am

Re: Xen Error

Postby bonzi » Thu Mar 27, 2014 11:40 pm

Thanks powerhouse! That helps, its good to know that I'm not the only one with this problem. I'm sort of tempted to just buy a NVIDIA card and be done with it...kind of a waste of money though. I'm pretty short on time also, I'm planning on having another go at it over the weekend also.

I found that thread on Xen users also, I was planning on trying that also as a last resort. Thanks!

powerhouse
Level 5
Level 5
Posts: 979
Joined: Thu May 03, 2012 3:54 am
Location: Israel
Contact:

Re: Xen Error

Postby powerhouse » Fri Mar 28, 2014 11:48 pm

bonzi wrote:Thanks powerhouse! That helps, its good to know that I'm not the only one with this problem. I'm sort of tempted to just buy a NVIDIA card and be done with it...kind of a waste of money though. I'm pretty short on time also, I'm planning on having another go at it over the weekend also.

I found that thread on Xen users also, I was planning on trying that also as a last resort. Thanks!


As explained before, I ran into the same problem before with a AMD 7770 card. However, that card worked with LM13 and an older Xen 4.1.2.

I had a long mail exchange on the Xen user mailing list with the guy who first reported that error 22 bug. He is of the opinion that Nvidia cards are way better for VGA passthrough. However, you should note that only the "Multi-OS" type Nvidia cards are suitable for VGA passthrough, out of the box! The Multi-OS cards include only a few select professional cards, the cheapest of which is the Quadro 2000 (which I own). For gaming, these cards are totally overpriced and often underpowered.

A solution is to get a suitable non-Multi-OS Nvidia card and modify it to work as its Quadro or Tesla counterpart. Doing so requires soldering skills, and certainly voids the warranty on that card. You can easily brick the card by accident, which is what happened to the guy who started this thread: http://www.eevblog.com/forum/chat/hacking-nvidia-cards-into-their-professional-counterparts/.

I hope to be able to give the AMD 6450 another try tomorrow.
Asus Sabertooth X79, i7 3930K CPU, 8x4GB Kingston DDR3 RAM, Noctua NH-D14 CPU cooler, Gigabyte GTX 970 + PNY Quadro 2000 GPU, Asus Xonar Essence STX, Sandisk Extreme 120GB + Samsung EVO 850 250GB SSD + 5 HDD, Corsair 500R case, SeaSonic 660W Gold X PS

bonzi
Level 1
Level 1
Posts: 18
Joined: Wed Mar 19, 2014 1:49 am

Re: Xen Error

Postby bonzi » Sun Mar 30, 2014 2:07 pm

Hi, so I applied the patch and tried to build the new xen. I'm not sure if I did it correctly or not though and if the new xen has installed. I still get error 22. Here is the build log.

sudo make -j9 world

http://pastebin.com/13qvpkJx

As you can see it errors out.

sudo make -j9 install

http://pastebin.com/ZuKVs8RL

This looks ok, but I don't know if it has installed to the right place.

powerhouse
Level 5
Level 5
Posts: 979
Joined: Thu May 03, 2012 3:54 am
Location: Israel
Contact:

Re: Xen Error

Postby powerhouse » Sun Mar 30, 2014 2:56 pm

bonzi wrote:Hi, so I applied the patch and tried to build the new xen. I'm not sure if I did it correctly or not though and if the new xen has installed. I still get error 22. Here is the build log.

sudo make -j9 world

http://pastebin.com/13qvpkJx

As you can see it errors out.

sudo make -j9 install

http://pastebin.com/ZuKVs8RL

This looks ok, but I don't know if it has installed to the right place.


I unfortunately couldn't test today. I did download Ubuntu 14.04 beta2 to see if the newer kernel and Xen 4.4 makes any difference. But I haven't managed to test it yet, and I won't be able to do so before Thursday.

I do hope there is a better way than patching, but the way things look it might be the only way. The error 22 issue has been fixed long ago, AFAIK, and I can't explain why it still appears.

For the moment I don't have any answers. I really need to give it a try myself. Somehow I can't explain why 4.1.2 works perfect with my AMD 7770, but you say it doesn't work with the AMD 6450 (I haven't tried it yet, but I probably will give it a try).

So here is my plan for testing the AMD 6450 (if I only find the time):
1. Try Ubuntu 14.04 beta2 with Xen 4.4 and xl toolstack
2. If the above doesn't work, I'll try LM 13 with Xen 4.1.2 and xm (I have to see it with my own eyes)
3. Last resort is LM 16 with xl and xm (I tested xm already, but I want to know where it hangs and what's causing it).
Asus Sabertooth X79, i7 3930K CPU, 8x4GB Kingston DDR3 RAM, Noctua NH-D14 CPU cooler, Gigabyte GTX 970 + PNY Quadro 2000 GPU, Asus Xonar Essence STX, Sandisk Extreme 120GB + Samsung EVO 850 250GB SSD + 5 HDD, Corsair 500R case, SeaSonic 660W Gold X PS

powerhouse
Level 5
Level 5
Posts: 979
Joined: Thu May 03, 2012 3:54 am
Location: Israel
Contact:

Re: Xen Error

Postby powerhouse » Sun Mar 30, 2014 11:49 pm

Here some thread on error 22 and the AMD 6450: http://www.gossamer-threads.com/lists/xen/users/277870.

Gordon was the one who reported the error 22 bug that was introduced last year with a security update. I haven't read the entire thread but there seem to be some useful clues.
Asus Sabertooth X79, i7 3930K CPU, 8x4GB Kingston DDR3 RAM, Noctua NH-D14 CPU cooler, Gigabyte GTX 970 + PNY Quadro 2000 GPU, Asus Xonar Essence STX, Sandisk Extreme 120GB + Samsung EVO 850 250GB SSD + 5 HDD, Corsair 500R case, SeaSonic 660W Gold X PS

bonzi
Level 1
Level 1
Posts: 18
Joined: Wed Mar 19, 2014 1:49 am

Re: Xen Error

Postby bonzi » Sun Mar 30, 2014 11:51 pm

Here some thread on error 22 and the AMD 6450: http://www.gossamer-threads.com/lists/xen/users/277870.

Gordon was the one who reported the error 22 bug that was introduced last year with a security update. I haven't read the entire thread but there seem to be some useful clues.


Thanks, I'll have a look through tonight and post back my findings.

EDIT: According to Gordan, Xen 4.1.7 has issues with error 22. He switched back to 4.1.6 and the error went away. Looks like 4.1.5 is the latest offered in LM13. I already tried this though.

EDIT2: I also tried to pass through the R7 250 instead of the 6450 and I still get the same error.

bonzi
Level 1
Level 1
Posts: 18
Joined: Wed Mar 19, 2014 1:49 am

Re: Xen Error

Postby bonzi » Mon Mar 31, 2014 2:58 am

So I switched the xl toolstack. It still doesn't work, but I get different error messages at least:

sudo xl create /etc/xen/win7.conf

Code: Select all

sudo xl create /etc/xen/win7.cfg
Parsing config file /etc/xen/win7.cfg
xc: info: VIRTUAL MEMORY ARRANGEMENT:
  Loader:        0000000000100000->000000000017c510
  TOTAL:         0000000000000000->00000000ff800000
  ENTRY ADDRESS: 00000000001015a0
xc: info: PHYSICAL MEMORY ALLOCATION:
  4KB PAGES: 0x0000000000000200
  2MB PAGES: 0x00000000000005fb
  1GB PAGES: 0x0000000000000001
libxl: error: libxl_dom.c:718:libxl_userdata_store cannot write /var/lib/xen/userdata-n.1.5cecc435-8255-4883-9dbb-c4d462a70ba8.xl for /var/lib/xen/userdata-d.1.5cecc435-8255-4883-9dbb-c4d462a70ba8.xl: No such file or directory
cannot save config file: No such file or directory
libxl: error: libxl_device.c:470:libxl__wait_for_device_model Device Model not ready
libxl: error: libxl_pci.c:892:do_pci_remove Device Model didn't respond in time
libxl: error: libxl_device.c:470:libxl__wait_for_device_model Device Model not ready
libxl: error: libxl_pci.c:892:do_pci_remove Device Model didn't respond in time
libxl: error: libxl_device.c:470:libxl__wait_for_device_model Device Model not ready
libxl: error: libxl_pci.c:892:do_pci_remove Device Model didn't respond in time
libxl: error: libxl_dom.c:645:libxl__userdata_destroyall glob failed for /var/lib/xen/userdata-?.1.5cecc435-8255-4883-9dbb-c4d462a70ba8.*: No such file or directory

powerhouse
Level 5
Level 5
Posts: 979
Joined: Thu May 03, 2012 3:54 am
Location: Israel
Contact:

Re: Xen Error

Postby powerhouse » Mon Mar 31, 2014 3:35 pm

For xl to work you need to change the device model in the win.cfg file. Look through the recent posts in the how-to, there should be instructions. If not check the xen wiki pages. You need to select legacy.
Asus Sabertooth X79, i7 3930K CPU, 8x4GB Kingston DDR3 RAM, Noctua NH-D14 CPU cooler, Gigabyte GTX 970 + PNY Quadro 2000 GPU, Asus Xonar Essence STX, Sandisk Extreme 120GB + Samsung EVO 850 250GB SSD + 5 HDD, Corsair 500R case, SeaSonic 660W Gold X PS

bonzi
Level 1
Level 1
Posts: 18
Joined: Wed Mar 19, 2014 1:49 am

Re: Xen Error

Postby bonzi » Tue Apr 01, 2014 2:49 am

powerhouse wrote:For xl to work you need to change the device model in the win.cfg file. Look through the recent posts in the how-to, there should be instructions. If not check the xen wiki pages. You need to select legacy.


I see, I changed it as per your recommendation. I see get the error that the device is not ready:

Code: Select all

Parsing config file /etc/xen/win7.cfg
xc: info: VIRTUAL MEMORY ARRANGEMENT:
  Loader:        0000000000100000->000000000017c510
  TOTAL:         0000000000000000->00000000ff800000
  ENTRY ADDRESS: 00000000001015a0
xc: info: PHYSICAL MEMORY ALLOCATION:
  4KB PAGES: 0x0000000000000200
  2MB PAGES: 0x00000000000005fb
  1GB PAGES: 0x0000000000000001
libxl: error: libxl_device.c:470:libxl__wait_for_device_model Device Model not ready
xl: fatal error: libxl_create.c:535, rc=-1: libxl__confirm_device_model_startup
libxl: error: libxl_dom.c:645:libxl__userdata_destroyall glob failed for /var/lib/xen/userdata-?.1.1c858bde-e2cc-48a8-92ae-2b23a4534fc8.*: No such file or directory


I picked up a quadro 2000 off of ebay for $75, so I'll see in a week or so if that is any better.

powerhouse
Level 5
Level 5
Posts: 979
Joined: Thu May 03, 2012 3:54 am
Location: Israel
Contact:

Re: Xen Error

Postby powerhouse » Tue Apr 01, 2014 11:55 pm

$75 for a Quadro 2000 is a good price (I wish I paid that little). With the Quadro 2000 you best install LM 16 with Xen 4.3 (regular repo package) and run xl. This is what I use with the Quadro 2000 and it works like a charm.

I'm a little perplexed about the "libxl__wait_for_device_model Device Model not ready" message. Can you post the following log: /var/log/xen/qemu-dm-win7.log (your domU log), as well as your current win7.cfg file?
Asus Sabertooth X79, i7 3930K CPU, 8x4GB Kingston DDR3 RAM, Noctua NH-D14 CPU cooler, Gigabyte GTX 970 + PNY Quadro 2000 GPU, Asus Xonar Essence STX, Sandisk Extreme 120GB + Samsung EVO 850 250GB SSD + 5 HDD, Corsair 500R case, SeaSonic 660W Gold X PS

bonzi
Level 1
Level 1
Posts: 18
Joined: Wed Mar 19, 2014 1:49 am

Re: Xen Error

Postby bonzi » Thu Apr 03, 2014 11:08 am

Hi,

Sorry for the slow response, work has had me very busy in the past few days. You are right, something seems to be wrong still with the way I setup xl

/var/log/xen/qemu-dm-win7.log

Code: Select all

libxl: cannot execute /usr/lib/xen-4.1/bin/qemu-xen-traditional: No such file or directory


/etc/xen/win7.cfg

Code: Select all

kernel = '/usr/lib/xen-default/boot/hvmloader'
builder='hvm'
memory = 4096
name = 'win7'
vcpus=4
acpi=1
apic=1
on_xend_stop='shutdown'
vif = [ 'mac=00:16:3e:68:e1:01,bridge=xenbr0' ]
disk = [ 'phy:/dev/mapper/guest-win7,hda,w' , 'file:/media/install/Win7.iso,hdc:cdrom,r' ]
device_model = 'qemu-xen-traditional'
boot='dc'
sdl=0
vnc=1
vncpasswd=''
stdvga=1
serial='pty'
tsc_mode=0
viridian=1
usb=0
usbdevice='tablet'
gfx_passthru=0
pci=[ '03:00.0', '03:00.1', '00:1a.2' ]
localtime=1
pci_power_mgmt=1

powerhouse
Level 5
Level 5
Posts: 979
Joined: Thu May 03, 2012 3:54 am
Location: Israel
Contact:

Re: Xen Error

Postby powerhouse » Thu Apr 03, 2014 11:31 am

bonzi wrote:Hi,

Sorry for the slow response, work has had me very busy in the past few days. You are right, something seems to be wrong still with the way I setup xl

/var/log/xen/qemu-dm-win7.log

Code: Select all

libxl: cannot execute /usr/lib/xen-4.1/bin/qemu-xen-traditional: No such file or directory


/etc/xen/win7.cfg

Code: Select all

kernel = '/usr/lib/xen-default/boot/hvmloader'
builder='hvm'
memory = 4096
name = 'win7'
vcpus=4
acpi=1
apic=1
on_xend_stop='shutdown'
vif = [ 'mac=00:16:3e:68:e1:01,bridge=xenbr0' ]
disk = [ 'phy:/dev/mapper/guest-win7,hda,w' , 'file:/media/install/Win7.iso,hdc:cdrom,r' ]
device_model = 'qemu-xen-traditional'
boot='dc'
sdl=0
vnc=1
vncpasswd=''
stdvga=1
serial='pty'
tsc_mode=0
viridian=1
usb=0
usbdevice='tablet'
gfx_passthru=0
pci=[ '03:00.0', '03:00.1', '00:1a.2' ]
localtime=1
pci_power_mgmt=1

Go to /usr/lib and check that xen-4.1 exists (as a folder or link). If yes, go to /usr/lib/xen-4.1/bin/ and see if qemu-xen-traditional is there.

By the way, are you trying xl with LM13 and Xen 4.1.2?

Note: I'm in the middle of installing LM13 and Xen 4.1.2 to test VGA passthrough with the AMD 6450 using xm toolstack.

EDIT 8.4.2014: Instead of "device_model = ..." the correct win7.cfg entry for xl is:

Code: Select all

device_model_version = 'qemu-xen-traditional'
Last edited by powerhouse on Tue Apr 08, 2014 9:05 am, edited 1 time in total.
Asus Sabertooth X79, i7 3930K CPU, 8x4GB Kingston DDR3 RAM, Noctua NH-D14 CPU cooler, Gigabyte GTX 970 + PNY Quadro 2000 GPU, Asus Xonar Essence STX, Sandisk Extreme 120GB + Samsung EVO 850 250GB SSD + 5 HDD, Corsair 500R case, SeaSonic 660W Gold X PS

bonzi
Level 1
Level 1
Posts: 18
Joined: Wed Mar 19, 2014 1:49 am

Re: Xen Error

Postby bonzi » Thu Apr 03, 2014 11:48 am

ls -l

Code: Select all

ls /usr/lib/xen-4.1/bin/
gtracestat  xc_save      xen-detect    xenpm                xentrace_setmask
gtraceview  xenbaked     xen-hptool    xen-python-path      xentrace_setsize
lsevtchn    xen-bugtool  xen-hvmcrash  xenstore-control     xenwatchdogd
pygrub      xencons      xen-hvmctx    xenstored            xl
qemu-dm     xenconsole   xenlockprof   xen-tmem-list-parse  xm
readnotes   xenconsoled  xenmon        xentop               xsview
tap-ctl     xenctx       xenpaging     xentrace
xc_restore  xend         xenperf       xentrace_format


qemu-xen-traditional is not there. I am using LM13 and Xen-4.1.2.

powerhouse
Level 5
Level 5
Posts: 979
Joined: Thu May 03, 2012 3:54 am
Location: Israel
Contact:

Re: Xen Error

Postby powerhouse » Thu Apr 03, 2014 12:54 pm

bonzi wrote:ls -l

Code: Select all

ls /usr/lib/xen-4.1/bin/
gtracestat  xc_save      xen-detect    xenpm                xentrace_setmask
gtraceview  xenbaked     xen-hptool    xen-python-path      xentrace_setsize
lsevtchn    xen-bugtool  xen-hvmcrash  xenstore-control     xenwatchdogd
pygrub      xencons      xen-hvmctx    xenstored            xl
qemu-dm     xenconsole   xenlockprof   xen-tmem-list-parse  xm
readnotes   xenconsoled  xenmon        xentop               xsview
tap-ctl     xenctx       xenpaging     xentrace
xc_restore  xend         xenperf       xentrace_format


qemu-xen-traditional is not there. I am using LM13 and Xen-4.1.2.


Use qemu-dm.
Asus Sabertooth X79, i7 3930K CPU, 8x4GB Kingston DDR3 RAM, Noctua NH-D14 CPU cooler, Gigabyte GTX 970 + PNY Quadro 2000 GPU, Asus Xonar Essence STX, Sandisk Extreme 120GB + Samsung EVO 850 250GB SSD + 5 HDD, Corsair 500R case, SeaSonic 660W Gold X PS

powerhouse
Level 5
Level 5
Posts: 979
Joined: Thu May 03, 2012 3:54 am
Location: Israel
Contact:

Re: Xen Error

Postby powerhouse » Thu Apr 03, 2014 5:06 pm

So, I finally got xm create ... started without the error 22. It turned out that Ubuntu / Linux Mint had been busy updating the kernel and other packages for LM13 / Ubuntu 12.04 which in turn broke sort of everything Xen-related. Even Xorg wouldn't start when running Xen.

Here is the configuration that seems to work (still installing Windows - cross my fingers):
Kernel: 3.2.0-23-generic
Xen: 4.1.2-2ubuntu2

I downgraded both Xen and the related packages (5 packages altogether) as well as the kernel.

So far the Windows installation and xm "survived" 2 reboots of the guest.
Asus Sabertooth X79, i7 3930K CPU, 8x4GB Kingston DDR3 RAM, Noctua NH-D14 CPU cooler, Gigabyte GTX 970 + PNY Quadro 2000 GPU, Asus Xonar Essence STX, Sandisk Extreme 120GB + Samsung EVO 850 250GB SSD + 5 HDD, Corsair 500R case, SeaSonic 660W Gold X PS

bonzi
Level 1
Level 1
Posts: 18
Joined: Wed Mar 19, 2014 1:49 am

Re: Xen Error

Postby bonzi » Thu Apr 03, 2014 9:47 pm

Thanks, I tried the same config but I still get error 22 passing through my R7 250. I'll reboot and try again with the 6450.

EDIT: Nope, it doesn't work with the 6450 either :( I guess I'm stuck waiting for the quadro 2000.

powerhouse
Level 5
Level 5
Posts: 979
Joined: Thu May 03, 2012 3:54 am
Location: Israel
Contact:

Re: Xen Error

Postby powerhouse » Thu Apr 03, 2014 11:54 pm

bonzi wrote:Thanks, I tried the same config but I still get error 22 passing through my R7 250. I'll reboot and try again with the 6450.

EDIT: Nope, it doesn't work with the 6450 either :( I guess I'm stuck waiting for the quadro 2000.


Following up on my previous post:
Kernel: 3.2.0-23-generic
Xen: 4.1.2-2ubuntu2

I managed to install the AMD driver under Windows by downloading the driver file and doing a custom installation without CCC (Catalyst Control Center). The card and driver show in the Device Manager.

Now the embarrassing part: I rebooted and everything seemed fine until the point where the AMD 6450 should kick in (see the Windows logo in the VNC window). To make it short, I forgot to connect the screen to the AMD 6450 card :oops: :oops: :oops: :oops: :oops: :oops: .

My guess is that it just worked (though I never saw the output from the AMD 6450), since Windows didn't crash and all points to not having connected the cable. Unfortunately I only discovered my mistake when I flipped the graphics cards back to my regular setup (the Quadro 2000) and I just didn't have more time to test.

I hope to give it a try today evening.

Here a list of the hurdles I had to overcome (I believe they are almost all kernel related):
1. Installed and updated LM13 (over 600 packages to update).
2. Installed Xen without specifying the version described in my how-to.
3. Downgraded Xen using Synaptic -> Packages -> Force version... - all five Xen-related packages showing 4.1.5 as release number must be downgraded to the original version offered in Synaptic.
4. Copied the pci passthrough parameters into /etc/initram-tools/modules and updated the initramfs as per my how-to.
5. Configured networking, but had to create a /etc/resolv.conf file listing the DNS name servers.
6. Rebooted into Xen, but Xen wouldn't load X - did a CLI login followed by sudo service mdm stop.
7. Followed this guide https://help.ubuntu.com/community/BinaryDriverHowto/AMD for command line installation of fglrx. Finally ran

Code: Select all

amdconfig --adapter=0 --initial

to create a xorg.conf file. The --adapter=0 was taken from a previous amdconfig --adapter=list (or was it check?) - just run amdconfig to get the command line arguments.
8. After installing the fglrx driver, ran service mdm start and the GUI came up.
9. The rest is described in the LM13 / LM14 how-to.

Important: I was using the "xm" toolstack!

Hopefully I can confirm this evening that these steps really work.

EDIT: It worked !!! See my next post.
Last edited by powerhouse on Fri Apr 04, 2014 4:27 pm, edited 1 time in total.
Asus Sabertooth X79, i7 3930K CPU, 8x4GB Kingston DDR3 RAM, Noctua NH-D14 CPU cooler, Gigabyte GTX 970 + PNY Quadro 2000 GPU, Asus Xonar Essence STX, Sandisk Extreme 120GB + Samsung EVO 850 250GB SSD + 5 HDD, Corsair 500R case, SeaSonic 660W Gold X PS


Return to “Virtualization”

Who is online

Users browsing this forum: No registered users and 0 guests