Gentoo Archives: gentoo-user

From: hydra <hydrapolic@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] xen doesn't work
Date: Mon, 13 Jul 2015 18:17:42
Message-Id: CAG6MAzRAZk65vcEG0S8X9F-oHT936FM-8unjyG4oUhEQB_Rw4A@mail.gmail.com
In Reply to: [gentoo-user] xen doesn't work by hw
1 On Mon, Jul 13, 2015 at 3:01 PM, hw <hw@×××××××××××××××××××××.de> wrote:
2
3 >
4 > Hi,
5 >
6 > I'm trying to get a windoze 7 to run as a domU on a fresh install of
7 > gentoo with xen. I need to use the installer ISO to boot from and to
8 > install into a partition on a physical disk.
9 >
10 > Running 'xl -vvv create /etc/xen/ws-01.hvm' gives me the following
11 > messages:
12 >
13 >
14 > Parsing config from /etc/xen/ws-01.hvm
15 > libxl: debug: libxl_create.c:1504:do_domain_create: ao 0x1a97440: create:
16 > how=(nil) callback=(nil) poller=0x1a974a0
17 > libxl: verbose: libxl_create.c:137:libxl__domain_build_info_setdefault:
18 > qemu-xen is unavailable, use qemu-xen-traditional instead: No such file or
19 > directory
20 > libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk
21 > vdev=hda spec.backend=unknown
22 > libxl: debug: libxl_device.c:298:libxl__device_disk_set_backend: Disk
23 > vdev=hda, using backend phy
24 > libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk
25 > vdev=hdc spec.backend=unknown
26 > libxl: debug: libxl_device.c:215:disk_try_backend: Disk vdev=hdc, backend
27 > phy unsuitable as phys path not a block device
28 > libxl: debug: libxl_device.c:298:libxl__device_disk_set_backend: Disk
29 > vdev=hdc, using backend qdisk
30 > libxl: debug: libxl_create.c:907:initiate_domain_create: running bootloader
31 > libxl: debug: libxl_bootloader.c:323:libxl__bootloader_run: not a PV
32 > domain, skipping bootloader
33 > libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch
34 > w=0x1a97d70: deregister unregistered
35 > libxl: debug: libxl_numa.c:483:libxl__get_numa_candidate: New best NUMA
36 > placement candidate found: nr_nodes=1, nr_cpus=12, nr_vcpus=26,
37 > free_memkb=9875
38 > libxl: debug: libxl_numa.c:483:libxl__get_numa_candidate: New best NUMA
39 > placement candidate found: nr_nodes=1, nr_cpus=12, nr_vcpus=26,
40 > free_memkb=10311
41 > libxl: detail: libxl_dom.c:196:numa_place_domain: NUMA placement candidate
42 > with 1 nodes, 12 cpus and 10311 KB free selected
43 > libxl: detail: libxl_dom.c:254:hvm_set_viridian_features: base group
44 > enabled
45 > libxl: detail: libxl_dom.c:254:hvm_set_viridian_features: freq group
46 > enabled
47 > libxl: detail: libxl_dom.c:254:hvm_set_viridian_features: time_ref_count
48 > group enabled
49 > xc: error: Could not open kernel image (2 = No such file or directory):
50 > Internal error
51 > libxl: error: libxl_dom.c:818:libxl__build_hvm: hvm building failed
52 > libxl: error: libxl_create.c:1121:domcreate_rebuild_done: cannot
53 > (re-)build domain: -3
54 > libxl: error: libxl_dm.c:1595:kill_device_model: unable to find device
55 > model pid in /local/domain/12/image/device-model-pid
56 > libxl: error: libxl.c:1608:libxl__destroy_domid:
57 > libxl__destroy_device_model failed for 12
58 > libxl: info: libxl.c:1691:devices_destroy_cb: forked pid 5036 for destroy
59 > of domain 12
60 > libxl: debug: libxl_create.c:1520:do_domain_create: ao 0x1a97440:
61 > inprogress: poller=0x1a974a0, flags=i
62 > libxl: debug: libxl_event.c:1765:libxl__ao_complete: ao 0x1a97440:
63 > complete, rc=-3
64 > libxl: debug: libxl_event.c:1737:libxl__ao__destroy: ao 0x1a97440: destroy
65 > xc: debug: hypercall buffer: total allocations:197 total releases:197
66 > xc: debug: hypercall buffer: current allocations:0 maximum allocations:4
67 > xc: debug: hypercall buffer: cache current size:4
68 > xc: debug: hypercall buffer: cache hits:182 misses:4 toobig:11
69 >
70 >
71 > The configuration for the VM is as follows:
72 >
73 >
74 > # This configures an HVM rather than PV guest
75 > builder = "hvm"
76 >
77 > # Guest name
78 > name = "ws-01.hvm"
79 >
80 > # 128-bit UUID for the domain as a hexadecimal number.
81 > # Use "uuidgen" to generate one if required.
82 > # The default behavior is to generate a new UUID each time the guest is
83 > started.
84 > #uuid = "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
85 >
86 > # Enable Microsoft Hyper-V compatibile paravirtualisation /
87 > # enlightenment interfaces. Turning this on can improve Windows guest
88 > # performance and is therefore recommended
89 > viridian = 1
90 >
91 > # Initial memory allocation (MB)
92 > memory = 4096
93 >
94 > # Maximum memory (MB)
95 > # If this is greater than `memory' then the slack will start ballooned
96 > # (this assumes guest kernel support for ballooning)
97 > #maxmem = 512
98 >
99 > # Number of VCPUS
100 > vcpus = 2
101 >
102 > # Network devices
103 > # A list of 'vifspec' entries as described in
104 > # docs/misc/xl-network-configuration.markdown
105 > vif = [ 'bridge=brloc' ]
106 >
107 > # Disk Devices
108 > # A list of `diskspec' entries as described in
109 > # docs/misc/xl-disk-configuration.txt
110 > disk = [ 'phy:/dev/sde1,ioemu:hda,w',
111 > 'file:/root/installers/de_windows_7_professional_with_sp1_x64_dvd_u_676919.iso,ioemu:hdc:cdrom,r'
112 > ]
113 >
114 > boot="dc"
115 >
116 > # Guest VGA console configuration, either SDL or VNC
117 > sdl = 0
118 > vnc = 1
119 >
120 >
121 > Any idea why I cannot create VMs? Is this a Gentoo problem or a problem
122 > with xen? Do I need to install some more packages?
123 >
124 >
125 Please post the output of
126 emerge --info xen
127 emerge --info xen-tools
128
129 Were you able to start any virtual machine in your Xen environment yet or
130 this is the first try?

Replies

Subject Author
Re: [gentoo-user] xen doesn't work hw <hw@×××××××××××××××××××××.de>