Xen users - Nov 2011 - Help get Xen 4.1 running

Hi,
I''m trying to get Xen 4.1 running on Ubuntu Server 11.10 Dom0.
I installed the following: apt-get install xen-hypervisor-4.1-amd64
xen-utils-4.1 xenwatch xen-tools xen-utils-common xenstore-utils

Xen grub kernel starts, and xend is running.

In xend-config.sxp (vif-script vif-bridge) is uncommented while
(network-script ''network-bridge'') is not.  I used
http://wiki.xensource.com/xenwiki/HostConfiguration/Networking to configure
xenbr0.  Here''s sample brctl output taken after a domU started:
bridge name     bridge id               STP enabled     interfaces
virbr0          8000.000000000000       yes
xenbr0          8000.00219ba1a024       no              eth0
                                                        tap4.0
                                                        vif4.0

Then I created LVM volume called "ubuntu" (didn''t call mkfs
on it) and
created .cfg file:
kernel = "/usr/lib/xen-default/boot/hvmloader"
builder=''hvm''
memory = 512
shadow_memory = 8
vcpus = 1
name = "ubuntu"
vif = [ ''type=ioemu, bridge=xenbr0'' ]
disk = [ ''phy:/dev/storage/ubuntu,ioemu:hda,w'',
''file:/mnt/iso/ubuntu-11.10-server-amd64.iso,ioemu:hdc:cdrom,r''
]
device_model = ''/usr/lib/xen-default/bin/qemu-dm''
boot="dc"
sdl=0
vnc=1
vnclisten="0.0.0.0"
vncconsole=1
vncpasswd=''''
stdvga=0

The ubuntu installation ISO boots and I can VNC into the installation.
 First the installation throws an error "error while running modprobe -v
xenbus_probe_frontend" during the search for cdrom step.  Then installation
detects no networks - even though you can see the bridge is there along
with some interfaces like vif4.0.  Finally there are no hard disks
detected!

Thanks for any help.

Below are the log files.  There are a few errors in the logs, but I
couldn''t google how to fix them.

qemu-dm-ubuntu.log
domid: 5
-videoram option does not work with cirrus vga device model. Videoram set
to 4M.
Using file /dev/storage/ubuntu in read-write mode
Strip off blktap sub-type prefix to /mnt/iso/ubuntu-11.10-server-amd64.iso
(drv ''aio'')
Using file /mnt/iso/ubuntu-11.10-server-amd64.iso in read-only mode
Watching /local/domain/0/device-model/5/logdirty/cmd
Watching /local/domain/0/device-model/5/command
Watching /local/domain/5/cpu
char device redirected to /dev/pts/2
qemu_map_cache_init nr_buckets = 4000 size 327680
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = 265c73e0-93ee-4c26-834e-c4c8fa99e1c9
xen be core: xen be core: can''t open gnttab device
can''t open gnttab device
xen be core: xen be core: can''t open gnttab device
can''t open gnttab device
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/5/xen_extended_power_mgmt): read error
medium change watch on `hdc'' (index: 1):
aio:/mnt/iso/ubuntu-11.10-server-amd64.iso
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Log-dirty: no command yet.
vcpu-set: watch node error.
xs_read(/local/domain/5/log-throttling): read error
qemu: ignoring not-understood drive `/local/domain/5/log-throttling''
medium change watch on `/local/domain/5/log-throttling'' - unknown
device,
ignored
cirrus vga map change while on lfb mode
mapping vram to f0000000 - f0400000
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw
state.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro
state.
Unknown PV product 3 loaded in guest
PV driver build 1
region type 1 at [c100,c200).
region type 0 at [f3001000,f3001100).
squash iomem [f3001000, f3001100).

xend.log
[2011-11-09 19:31:12 3351] INFO (SrvDaemon:332) Xend Daemon started
[2011-11-09 19:31:12 3351] INFO (SrvDaemon:336) Xend changeset: unavailable.
[2011-11-09 19:31:12 3351] INFO (XendNetwork:114) Not recreating missing
unmanaged network eth0
[2011-11-09 19:31:13 3351] DEBUG (XendNode:332) pscsi record count: 14
[2011-11-09 19:31:13 3351] DEBUG (XendCPUPool:747) recreate_active_pools
[2011-11-09 19:31:13 3351] DEBUG (XendDomainInfo:151)
XendDomainInfo.recreate({''max_vcpu_id'': 15,
''cpu_time'': 2335142351715L,
''ssidref'': 0, ''hvm'': 0,
''shutdown_reason'': 255, ''dying'': 0,
''online_vcpus'':
8, ''domid'': 0, ''paused'': 0,
''crashed'': 0, ''running'': 1,
''maxmem_kb'':
4294967292L, ''shutdown'': 0, ''mem_kb'':
6495820L, ''blocked'': 0, ''handle'': [0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], ''cpupool'': 0,
''name'':
''Domain-0''})
[2011-11-09 19:31:13 3351] INFO (XendDomainInfo:169) Recreating domain 0,
UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0
[2011-11-09 19:31:13 3351] DEBUG (XendDomain:476) Adding Domain: 0
[2011-11-09 19:31:13 3351] DEBUG (XendDomain:410) number of vcpus to use is
0
[2011-11-09 19:31:13 3351] DEBUG (XendDomainInfo:1881)
XendDomainInfo.handleShutdownWatch
[2011-11-09 19:31:13 3351] WARNING (XendAPI:708) API call: VBD.set_device
not found
[2011-11-09 19:31:13 3351] WARNING (XendAPI:708) API call: VBD.set_type not
found
[2011-11-09 19:31:13 3351] WARNING (XendAPI:708) API call:
session.get_all_records not found
[2011-11-09 19:31:13 3351] WARNING (XendAPI:708) API call: event.get_record
not found
[2011-11-09 19:31:13 3351] WARNING (XendAPI:708) API call: event.get_all
not found
[2011-11-09 19:31:13 3351] WARNING (XendAPI:708) API call: VIF.set_device
not found
[2011-11-09 19:31:13 3351] WARNING (XendAPI:708) API call: VIF.set_MAC not
found
[2011-11-09 19:31:13 3351] WARNING (XendAPI:708) API call: VIF.set_MTU not
found
[2011-11-09 19:31:13 3351] WARNING (XendAPI:708) API call: debug.get_all
not found
[2011-11-09 19:31:13 3351] INFO (XMLRPCServer:161) Opening Unix domain
socket XML-RPC server on /var/run/xend/xmlrpc.sock.
[2011-11-09 19:31:13 3351] INFO (XMLRPCServer:161) Opening Unix domain
socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has
been disabled for this server.
[2011-11-09 19:32:21 3351] DEBUG (XendDomainInfo:151)
XendDomainInfo.recreate({''max_vcpu_id'': 0,
''cpu_time'': 0L, ''ssidref'': 0,
''hvm'': 1, ''shutdown_reason'': 255,
''dying'': 0, ''online_vcpus'': 1,
''domid'':
5, ''paused'': 1, ''crashed'': 0,
''running'': 0, ''maxmem_kb'': 525312L,
''shutdown'': 0, ''mem_kb'': 515988L,
''handle'': [38, 92, 115, 224, 147, 238,
76, 38, 131, 78, 196, 200, 250, 153, 225, 201], ''blocked'': 0,
''cpupool'': 0})
[2011-11-09 19:32:21 3351] INFO (XendDomainInfo:169) Recreating domain 5,
UUID 265c73e0-93ee-4c26-834e-c4c8fa99e1c9. at /local/domain/5
[2011-11-09 19:32:21 3351] DEBUG (XendDomain:476) Adding Domain: 5
[2011-11-09 19:32:21 3351] DEBUG (XendDomainInfo:1881)
XendDomainInfo.handleShutdownWatch

xen-hotplug.log
RTNETLINK answers: Operation not supported


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Thu, Nov 10, 2011 at 7:45 AM, Bud Bundy <budric@gmail.com>
wrote:
> Then I created LVM volume called "ubuntu" (didn''t call
mkfs on it) and
> created .cfg file:
> kernel = "/usr/lib/xen-default/boot/hvmloader"
> builder=''hvm''
Why HVM? PV should provide better performance, and last time I tested it works.
> vif = [ ''type=ioemu, bridge=xenbr0'' ]
drop "type=ioemu" from there (doesn''t really do anything
anyway)
> The ubuntu installation ISO boots and I can VNC into the installation.
>  First the installation throws an error "error while running modprobe
-v
> xenbus_probe_frontend" during the search for cdrom step.
Try adding xen_platform_pci=0 to domU config file, and try running
"ethtool -K tx off" for vif*.* and tap* on dom0.

If using xen_platform_pci works, it means you''re using qemu-emulated
devices. You can change it later after domU is successfully installed
so that it''d use PV drivers.

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Thanks for your suggestions.
Adding xen_platform_pci=0 made the network card AND the hard drive
available.

You said
>> If using xen_platform_pci works, it means you''re using
qemu-emulated devices
Can you or someone explain further what this option does?  I want HVM and
emulated devices.  I plan to install Windows later and this was supposed to
be a quick test for running HVM machines.  By why isn''t
builder=''hvm'' and
kernel=... and device_model=''/usr/lib/xen-default/bin/qemu-dm''
enough to
specify that?  What is it doing when I don''t specify
xen_platform_pci=0?

Thanks.


On Wed, Nov 9, 2011 at 10:53 PM, Fajar A. Nugraha <list@fajar.net> wrote:
> On Thu, Nov 10, 2011 at 7:45 AM, Bud Bundy <budric@gmail.com> wrote:
> > Then I created LVM volume called "ubuntu" (didn''t
call mkfs on it) and
> > created .cfg file:
> > kernel = "/usr/lib/xen-default/boot/hvmloader"
> > builder=''hvm''
>
> Why HVM? PV should provide better performance, and last time I tested it
> works.
>
> > vif = [ ''type=ioemu, bridge=xenbr0'' ]
>
> drop "type=ioemu" from there (doesn''t really do anything
anyway)
>
> > The ubuntu installation ISO boots and I can VNC into the installation.
> >  First the installation throws an error "error while running
modprobe -v
> > xenbus_probe_frontend" during the search for cdrom step.
>
> Try adding xen_platform_pci=0 to domU config file, and try running
> "ethtool -K tx off" for vif*.* and tap* on dom0.
>
> If using xen_platform_pci works, it means you''re using
qemu-emulated
> devices. You can change it later after domU is successfully installed
> so that it''d use PV drivers.
>
> --
> Fajar
>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Thu, Nov 10, 2011 at 10:20 PM, Bud Bundy <budric@gmail.com>
wrote:
> Thanks for your suggestions.
> Adding xen_platform_pci=0 made the network card AND the hard drive
> available.
> You said
>>> If using xen_platform_pci works, it means you''re using
>>> qemu-emulated devices
> Can you or someone explain further what this option does?  I want HVM and
> emulated devices.  I plan to install Windows later and this was supposed to
> be a quick test for running HVM machines.  By why isn''t
builder=''hvm'' and
> kernel=...
and device_model=''/usr/lib/xen-default/bin/qemu-dm'' enough to
> specify that?  What is it doing when I don''t
specify xen_platform_pci=0?
It''s something related to the fact that if BOTH pv and emulated
devices available (which is the case in old-version linux pv drivers),
users can accidently mount both thus corrupting the data. Or it could
simply make it harder to use the pv device (e.g. when using LVM, it''d
get confused seeing two identical PVs). So in newer versions of Linux,
if pv drivers are available then emulated devices get unplugged.

The problem with that is in some distro xen_platform_pci is compiled
as module, and not included by default in initrd. That means the
kernel remembers that it had xen pv drivers support, thus unplugging
the emulated devices. However because the module is not included in
initrd, the frontend drivers (xen-blkfront, etc) won''t load, thus no
devices are available.

xen_platform_pci (in domU config file) controls the visibility of a
device needed (in domU side) for pv drivers to work. If set to 0, pv
drivers won''t work, and the emulated devices won''t get
unplugged.

You should remove the setting (or set it to 1) if:
- you use windows + pv drivers (e.g. GPLPV)
- you use linux, and you compiled xen_platform_pci as builtin, or have
xen_platform_pci module loaded

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users