[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xen-devel
Subject:    Re: [Xen-devel] Re: Problems with 'xl create winxp' (hvm) on xen
From:       Ian Campbell <Ian.Campbell () citrix ! com>
Date:       2011-10-31 10:56:51
Message-ID: 1320058611.23193.63.camel () zakaz ! uk ! xensource ! com
[Download RAW message or body]

On Sat, 2011-10-29 at 07:17 +0100, jim burns wrote:
> On Sat October 29 2011, 1:57:12 AM, jim burns wrote:
> > For the remaining problems, note that 'xl create winxp' creates a qemu-dm 
> > process with the following parameters:
> > 
> > qemu-dm -d 8 -domain-name winxp -vnc 0.0.0.0:3 -k en-us -serial pty
> > -videoram  4 -boot cda -usb -usbdevice tablet -soundhw es1370 -acpi -vcpus
> > 2 -vcpu_avail 0x3 -net nic,vlan=0,macaddr=00:16:3e:23:1d:36,model=rtl8139
> > -net tap,vlan=0,ifname=tap8.0,bridge=xenbr0,script=no -M xenfv
> 
> Note, starting the domain with 'xm create' with the same config results in:
> 
> /usr/lib/xen/bin/qemu-dm -d 11 -domain-name winxp -videoram 4 -k en-us -vnc 
> 0.0.0.0:3 -monitor vc -vcpus 2 -vcpu_avail 0x3 -boot cda -soundhw es1370 -
> localtime -serial pty -acpi -usbdevice tablet -net 
> nic,vlan=1,macaddr=00:16:3e:23:1d:36,model=rtl8139 -net 
> tap,vlan=1,ifname=tap11.0,bridge=xenbr0 -M xenfv
> 
> Note, 'xl create' does not pass the '-localtime' option,

that's the source of one of the missing features. Fixing it should be a
case of adding the option to libxl_domain_build_info in the IDL,
reacting to it in libxl__build_device_model_args_old and
libxl__build_device_model_args_new and parsing the config file option
into it in parse_config_data().

>  and its '-net tap' specifies 'script=no', unlike 'xm create'.

This is expected, with xl the script for tap devices is run via the
hotplug mechanism (i.e. the same as vif) whereas xend apparently runs it
via qemu. Either _should_ work.

> Also, for some reason, the vlan numbers are different between xl and xm.

That's ok, they are effectively arbitrary and just serve to bind the
"-net nic,..." and "-net tap,..." options to one another (IOW the vlan
ID needs to be consistent across those two options but is otherwise
unimportant).

Ian.



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
[prev in list] [next in list] [prev in thread] [next in thread]