Yes it does support 64bit
xen-users-request@lists.xensource.com wrote:
>Send Xen-users mailing list submissions to
> xen-users@lists.xensource.com
>
>To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.xensource.com/mailman/listinfo/xen-users
>or, via email, send a message with subject or body ''help''
to
> xen-users-request@lists.xensource.com
>
>You can reach the person managing the list at
> xen-users-owner@lists.xensource.com
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Xen-users digest..."
>Today''s Topics:
>
> 1. Re: Do systems have to be IDENTICAL for live migration?
> (James Pifer)
> 2. Re: I need Vanilla Xen images of major Linux distributions
> (Donny Brooks)
> 3. Re: Re: Xen 4.0 - Support for Citrix WHQL-certified Windows
> PV drivers (benco)
> 4. Xen Cloud Platform 0.5 released! (Dave Scott)
> 5. Re: Do systems have to be IDENTICAL for live migration?
> (Nick Couchman)
> 6. 2.6.32.15 pvops amd 64 support (Amina Khalid)
> 7. Re: Problem pinging the xen guest after live migration (Srija G)
> 8. Re: Do systems have to be IDENTICAL for live migration?
> (James Pifer)
> 9. Re: Problem pinging the xen guest after live migration
> (Bart Coninckx)
> 10. xend start (not building br0 or vif interfaces)
> (Horton, Steve - IS)
> 11. RE: BusyBox (Gave up waiting on root device) (Horton, Steve - IS)
> 12. RE: BusyBox (Gave up waiting on root device) (Horton, Steve - IS)
> 13. XCP 0.5 release upgrade, oddity (Vern Burke)
> 14. XCP 0.5 release upgrade, bug 2 (Vern Burke)
> 15. [XCP] Strange bug this avaible memory for guests (George Shuklin)
>On Wed, 2010-07-07 at 09:30 -0300, Cristian Colombo wrote:
>> Maybe in .cfg file you have the domUs confired to use more than 8
>> cores....
>>
>
>No, I don''t have any that use over 4.
>
>James
>
>
>
>I can concur. I was having major issues getting ubuntu 10.04 to install
>a pv domu on my centos dom0 with xen3.4.2 and xen4.0. I got a
>subscription to stacklet and within the hour I had a working image. They
>have all kinds of distros.
>
>Donny B.
>
>On 7/7/2010 2:09 AM, Jonathan Tripathy wrote:
>> Stacklet.com is your friend
>>
>> On 07/07/10 06:47, Jimmy Pierre wrote:
>>> Greetings,
>>>
>>> I am attempting to create a cloud demo and having problems building
the
>>> images. As time is of essence, if you have vanilla Xen images of
>>> openSUSE,
>>> Debian, Ubuntu, Feudora, RedHat et al, to share, I would take them
,-)
>>>
>>> Cheers,
>>> Jimmy
>>>
>>>
>>> _______________________________________________
>>> Xen-users mailing list
>>> Xen-users@lists.xensource.com
>>> http://lists.xensource.com/xen-users
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
>
>
>
>Hello,
>
>I''m also trying to use Citrix PV drivers for Windows (from XCP
0.1.1 and
>0.5 RC3) instead of GPLPV drivers. I have both Xen 4.0.0/kernel 2.6.32.11
>and Xen 4.0.1 (latest RC) with kernel 2.6.32.15. VM''s are Win2003,
>Win2008R2_x64 and Win7x64.
>
>The only semi-working setup is Win2003Server on Xen 4.0.1 with Citrix PV
>driver from XCP 0.1.1. After driver installation I see working PV DISK and
>PV Ethernet devices, two other devices (XEN\console and XEN\vfb) are
>unrecognized.
>
>Other combinations:
>
>* Xen 4.0.[0-1]/PV driver 0.5/Win2008 - unable to boot, stop on progress bar
>* Xen 4.0.[0-1]/PV driver 0.1.1/Win2008 - boot only into safe mode
>* Xen 4.0.[0-1]/PV driver 0.5/Win2003 - unable to boot, stop on boot screen
>* Xen 4.0.[0-1]/PV driver 0.5/Win7 - unable to boot, stop on boot screen
>* Xen 4.0.[0-1]/PV driver 0.1.1/Win7 - \Windows\System32\DRIVERS\xevtchn.sys
> error at the beginning of boot process
>
>Win2008 + PV driver 0.5 install and boot log is attached.
>
>Regards,
>
>Roman
>
>On Thu, Jun 03, 2010 at 12:43:11AM +0200, Peter Braun wrote:
>> Hi,
>>
>> little progress in XCP windows drivers.
>>
>> XCP Win PV drivers installed in despite of unknown driver publisher
>> sucessfully to Windows 2008 SP1 x86 HVM domU.
>>
>> Disk and network i/o raised dramaticaly.
>>
>> Still remains 2 unrecognised PV devices:
>> - XEN\console
>> - XEN\vfg
>>
>>
>> Does it means that XCP Win PV drivers are x86 only not usable for x64
domU?
>>
>>
>> Peter
>>
>>
>>
>> 2010/5/27 Peter Braun <xenware@gmail.com>:
>> > Hi,
>> >
>> > recently Ive installed Windows 2008 x64 HVM domain on Xen 4.0.
>> >
>> >
>> > On xen wiki is info:
>> > Support for Citrix WHQL-certified Windows PV drivers, included in
XCP
>> > (Xen Cloud Platform). Xen Cloud Platform:
>> >
>> >
>> > So I installed them on Windows 2008 x64 domain and its not able to
boot anymore:
>> >
>> > File: \windows\system32\Drivers\xevtchn.sys
>> >
>> > Status: 0xc0000428
>> >
>> > Info: Windows cannot verify the digital signature for this file
>> >
>> >
>> >
>> > Can anybody explain me whats the status of Citrix drivers usage on
Xen 4.0?
>> >
>> >
>> > Thanks
>> >
>> >
>> > Peter
>> >
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
>
>--
>----------------------------------------------------------------------
> ,''''`. [benco] | mailto: benco@acid.sk | silc: /msg
benco
> : :'' :
-------------------------------------------------------------
> `. `'' GPG publickey: http://www.acid.sk/pubkey.asc
> `- KF = 0DF6 0592 74D2 F17A DACF A5C3 1720 CB7C F54C F429
>Hi,
>
>We''re pleased to announce the release of the Xen Cloud Platform
(XCP) 0.5, a complete open-source cloud infrastructure platform with a powerful
management toolstack based on open APIs, support for multi-tenancy, QoS and
detailed metrics for consumption based charging.
>
>The XCP 0.5 bits have been tested extensively (including 100,000s of
CPU-hours) and are considered suitable for production use.
>
>XCP 0.5 can be downloaded from:
>
>http://www.xen.org/products/cloud_source.html
>
>XCP 0.5 contains the following features:
>* xen 3.4.2
>* linux 2.6.27
>* openvswitch
>* fully signed windows PV drivers
>* improved SR-IOV support
>* heterogeneous machine resource pool support
>* templates for many different guest types (including latest Ubuntu, Debian)
>* full-featured enterprise-class management toolstack
>** multi-host resource pools
>** live VM snapshots, checkpoints, migration
>** disaster recovery support
>** flexible storage, networking, host power management
>** event tracking, progress notification
>** performance monitoring and alerting
>** XMLRPC-based API and powerful CLI
>
>XCP-unstable development has been happening in parallel with the
stabilization of XCP 0.5 and there are lots of cool new features in the
pipeline.
>
>What''s coming next in XCP-unstable:
>* automatic weekly builds on xen.org
>* xen 4.0
>* linux 2.6.32
>* libxenlight integration
>* new vhd-based storage management service
>* local disk storage optimizations
>* DRBD integration
>* network performance improvements
>* improved support for boot-from-SAN (including multipath)
>
>If you want to join us and help make XCP even more awesome, check out:
> xen-api@lists.xensource.com
> irc.freenode.net #xen-api
>
>Cheers,
>Dave
>
>
>>>> On 2010/07/07 at 06:21, James Pifer
<jep@obrien-pifer.com> wrote:
>> On Thu, 2010-07-01 at 21:01 -0400, James Pifer wrote:
>>> I have several systems running 64bit SLES11SP1. I''m trying
to Live
>>> Migrate between a couple of them and it''s not working,
although the
>same
>>> VM will run on each one starting it manually.
>>>
>>> The system are not identical. Would one expect migration to work
>>> between these two systems? See below.
>>>
>>> Thanks,
>>> James
>>
>> Just an update to this. I can migrate from the DL360 G5 (8 CPU) to
>the
>> DL360 G6 (16 CPU) but not the other way around.
>>
>> Is that expected? Is the CPU count the issue possibly?
>>
>> Thanks,
>> James
>
>Could you more clearly define "not working" - error messages, log
>entries, etc.? Sometimes CPU differences can prevent live migration
>from working properly, but there are other factors, too. It would be
>useful to know what Xen says about why live migration is failing. Also,
>could you specify exactly what CPUs are in those boxes? I don''t
use HP,
>but I know with Dell servers the model/generation of server you''re
using
>can have a wide range of processors in it, so just specifying the server
>model/brand does not really tell anything useful.
>
>-Nick
>
>
>--------
>This e-mail may contain confidential and privileged material for the sole
use of the intended recipient. If this email is not intended for you, or you
are not responsible for the delivery of this message to the intended recipient,
please note that this message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information. In such a case, you are strictly prohibited
from downloading, photocopying, distributing or otherwise using this message,
its contents or attachments in any way. If you have received this message in
error, please notify us immediately by replying to this e-mail and delete the
message from your mailbox. Information contained in this message that does not
relate to the business of SEAKR is neither endorsed by nor attributable to
SEAKR.
>Hi
>
>I am new to XEN and I need to know whether 2.6.32.15 pvops supports amd 64.
>
>Thanks
>Thank you so much to both of you John and Matej.
>
>Yes, both of your solution, worked when I am live migrating the guest
>from one dom0 to another dom0.
>
>What i am doing now,
>
> - In Host-B , I am executing the command ,
>
> ping Guest-15a
>
> - In the Host-A , I am executing the command
>
> xm migrate --live Guest-15a Host-B
>
> The result:
>
> * Live migration went very well, found there is just 1 sec
>stop in between but I think that is acceptable.*
>
>Our network team says that portfast is already configured at switch .
>
>But as the first option worked , so I hope I can move on - right? If
>not please advice....
>
>My second question is, mode=4 , ie 802.2ad ( link aggregation ) did not
>work still yet. I wanted to
>set the mode=4 as it is much faster. Found one document , here is the url
>
>http://wiki.oracle.com/page/Cisco+Systems+IOS-based+switches-+interface+bonding+and+trunking
>
>It is very good . In this document , the first line it is mentioned :
>
>***** It is important that the native VLANs *be identical* on both sides
>of the link
>
>What does it mean VLANs *be identical* on both sides of the link ? Sorry
>for the silly question though.
>
> Would you please explain , do I need to check /configure anything on the
>server side? My configuration is simple enough ,
>
>In my configuration I have used eth0 and eth1 bonded to bond0, and for
>each subnet, created the
>
>config files, as ifcfg-bond0.15, ifcfg-bond0.16, ifcfg-bond0.17. Then
>in the /etc/xen/scripts , I have created
>
>a custom file where I mentioned all the bridges for each vlan tag. And
>this custom file is being called
>
>from /etc/xen/xend-config.sxp...
>
>
>Please advice, do you need to proceed with aggregation link or with
>mode=1, which is now configured and
>you all helped me a work around...
>
>Thanks again.
>
>
>
>
>On Mon, Jul 5, 2010 at 6:25 AM, John Haxby <john.haxby@oracle.com>
wrote:
>
>>
>> On Sat, 2010-07-03 at 17:57 -0400, Srija G wrote:
>>> Hi ,
>>> [snip]
>>>
>>> Can anyone please advice , where to check? Do you think it is the
switch
>>> configuration issues?
>>>
>>>
>>>
>>
>> It''s almost certainly a switch issue: the switch
doesn''t know that the MAC
>> address for the recently migrated machine is on a different port.
>>
>> There are two possibilities: you can either ping something (eg the
default
>> router) _from_ the guest after it has migrated or you can set portfast
on
>> the switch. The former just informs the switch that the originating
MAC
>> address is now on a different port; the latter makes the switch less
willing
>> to hold on to the MAC address/port association for a long time and is
>> something that the network people can do. You might want to try doing
both.
>>
>> jch
>>
>>
>>
>
>> Could you more clearly define "not working" - error messages,
log
>> entries, etc.? Sometimes CPU differences can prevent live migration
>> from working properly, but there are other factors, too. It would be
>> useful to know what Xen says about why live migration is failing.
Also,
>> could you specify exactly what CPUs are in those boxes? I
don''t use HP,
>> but I know with Dell servers the model/generation of server
you''re using
>> can have a wide range of processors in it, so just specifying the
server
>> model/brand does not really tell anything useful.
>>
>> -Nick
>
>Hi Nick. I actually had all of this in the original post, but cut it in
>replies. See below.
>
>Thanks,
>James
>
>The first system is a ProLiant DL360 G6:
>Proc 1:2533 MHz
>Execution technology:4/4 cores; 8 maximum threads
>Memory technology:64-bit capable
>Processor 1 Internal L1 Cache:128 KB
>Processor 1 Internal L2 Cache:1024 KB
>Processor 1 Internal L3 Cache:8192 KB
>
>Proc 2:2533 MHz
>Execution technology:4/4 cores; 8 maximum threads
>Memory technology:64-bit capable
>Processor 2 Internal L1 Cache:128 KB
>Processor 2 Internal L2 Cache:1024 KB
>Processor 2 Internal L3 Cache:8192 KB
>
>
>The second system is a ProLiant DL360 G5:
>Proc 1:2500 MHz
>Execution technology:4/4 cores; 4 threads
>Memory technology:64-bit capable
>Processor 1 Internal L1 Cache:128 KB
>Processor 1 Internal L2 Cache:12288 KB
>
>Proc 2:2500 MHz
>Execution technology:4/4 cores; 4 threads
>Memory technology:64-bit capable
>Processor 2 Internal L1 Cache:128 KB
>Processor 2 Internal L2 Cache:12288 KB
>
>
>
>When I tried to Live Migrate a VM from system one to system two I got:
>[2010-07-01 12:06:49 5660] DEBUG (XendDomainInfo:237)
XendDomainInfo.restore([''domain'', [''domid'',
''3''], [''cpu_weight'',
''256''], [''cpu_cap'', ''0''],
[''pool_name'', ''Pool-0''],
[''bootloader''], [''vcpus'',
''2''], [''node'', ''8002''],
[''cpus'', [[], []]], [''on_poweroff'',
''destroy''], [''description''],
[''on_crash'', ''destroy''],
[''uuid'',
''92b1b8f4-94aa-d393-92a4-3d78262bf092''],
[''bootloader_args''], [''name'',
''chsimp2''], [''on_reboot'',
''restart''], [''maxmem'',
''2048''], [''memory'',
''2048''], [''shadow_memory'',
''18''], [''vcpu_avail'',
''3''], [''features''],
[''on_xend_start'', ''ignore''],
[''on_xend_stop'', ''ignore''],
[''start_time'', ''1277985922.2''],
[''cpu_time'', ''2433.09449026''],
[''online_vcpus'', ''2''],
[''image'', [''hvm'',
[''kernel''], [''superpages'',
''0''], [''videoram'', ''4''],
[''hpet'', ''0''], [''stdvga'',
''0''], [''loader'',
''/usr/lib/xen/boot/hvmloader''],
[''xen_platform_pci'', ''1''],
[''rtc_timeoffset'', ''0''],
[''pci'', []], [''hap'', ''1''],
[''localtime'', ''0''],
[''timer_mode'', ''1''],
[''pci_msitranslate'', ''1''],
[''oos'', ''1''], [''apic'',
''0''
],
[''sdl'', ''0''],
[''usbdevice'', ''tablet''],
[''vpt_align'', ''1''],
[''extid'', ''0''],
[''vncunused'', ''1''],
[''boot'', ''c''], [''pae'',
''1''], [''viridian'', ''0''],
[''acpi'', ''1''], [''vnc'',
''1''], [''nographic'', ''0''],
[''nomigrate'', ''0''],
[''usb'', ''1''], [''tsc_mode'',
''0''], [''guest_os_type'',
''default''], [''device_model'',
''/usr/lib64/xen/bin/qemu-dm''],
[''pci_power_mgmt'', ''0''],
[''xauthority'', ''/root/.Xauthority''],
[''isa'', ''0''], [''notes'',
[''SUSPEND_CANCEL'', ''1'']]]],
[''status'', ''2''], [''state'',
''-b----''], [''store_mfn'',
''1044476''], [''device'',
[''vif'', [''bridge'', ''br0''],
[''mac'', ''00:16:3e:1f:ea:77''],
[''script'', ''/etc/xen/scripts/vif-bridge''],
[''uuid'',
''53301d91-5283-d69d-4b7d-5beb3deee963''],
[''backend'', ''0'']]],
[''device'', [''console'',
[''protocol'', ''vt100''],
[''location'', ''4''],
[''uuid'',
''b02891b0-855e-fc59-9744-5685e1950c19'']]],
[''device'', [''vbd'',
[''protocol'', ''x86_32-abi''],
[''uuid'',
''31c2d623-a977-4e81-5ecc-2ab09907f76e''],
[''bootable'', ''1''], [''dev'',
''hda:disk''], [''uname'',
''phy:/dev/disk/by-id/scsi-200d0b29d2d002200''
],
[''mode'', ''w''], [''backend'',
''0''], [''VDI'']]],
[''device'', [''vfb'',
[''vncunused'', ''1''],
[''vnc'', ''1''], [''uuid'',
''e40219c2-a740-c910-2840-be3a2aaa9548''],
[''location'', ''127.0.0.1:5902'']]],
[''change_home_server'',
''False'']])>[2010-07-01 12:06:49 5660] DEBUG (XendDomainInfo:2543)
XendDomainInfo.constructDomain
>[2010-07-01 12:06:49 5660] DEBUG (balloon:239) Balloon: 31107320 KiB free;
need 16384; done.
>[2010-07-01 12:06:49 5660] DEBUG (XendDomain:465) Adding Domain: 1
>[2010-07-01 12:06:49 5660] DEBUG (XendDomainInfo:3470) Storing VM details:
{''on_xend_stop'': ''ignore'',
''pool_name'': ''Pool-0'',
''shadow_memory'': ''18'',
''uuid'':
''92b1b8f4-94aa-d393-92a4-3d78262bf092'',
''on_reboot'': ''restart'',
''start_time'': ''1277985922.2'',
''on_poweroff'': ''destroy'',
''bootloader_args'': '''',
''on_xend_start'': ''ignore'',
''on_crash'': ''destroy'',
''xend/restart_count'': ''0'',
''vcpus'': ''2'',
''vcpu_avail'': ''3'',
''bootloader'': '''', ''image'':
''(hvm (kernel ) (superpages 0) (videoram 4) (hpet 0) (stdvga 0) (loader
/usr/lib/xen/boot/hvmloader) (xen_platform_pci 1) (rtc_timeoffset 0) (pci ())
(hap 1) (localtime 0) (timer_mode 1) (pci_msitranslate 1) (oos 1) (apic 0) (sdl
0) (usbdevice tablet) (vpt_align 1) (extid 0) (vncunused 1) (boot c) (pae 1)
(viridian 0) (acpi 1) (vnc 1) (nographic 0) (nomigrate 0) (usb 1) (tsc_mode 0)
(guest_os_type default) (device_model /usr/lib64/xen/bin/qemu-dm)
(pci_power_mgmt 0) (xauthority /root/.Xauthority) (isa 0) (notes (SUSPEND_CANCEL
1)))'', ''name'': ''chsi
mp2''}>[2010-07-01 12:06:49 5660] INFO (XendDomainInfo:2402) createDevice: console
: {''protocol'': ''vt100'',
''location'': ''4'', ''uuid'':
''b02891b0-855e-fc59-9744-5685e1950c19''}
>[2010-07-01 12:06:49 5660] DEBUG (DevController:95) DevController: writing
{''state'': ''1'',
''backend-id'': ''0'',
''backend'':
''/local/domain/0/backend/console/1/0''} to
/local/domain/1/device/console/0.
>[2010-07-01 12:06:49 5660] DEBUG (DevController:97) DevController: writing
{''domain'': ''chsimp2'',
''frontend'':
''/local/domain/1/device/console/0'', ''uuid'':
''b02891b0-855e-fc59-9744-5685e1950c19'',
''frontend-id'': ''1'',
''state'': ''1'', ''location'':
''4'', ''online'': ''1'',
''protocol'': ''vt100''} to
/local/domain/0/backend/console/1/0.
>[2010-07-01 12:06:49 5660] INFO (XendDomainInfo:2402) createDevice: vfb :
{''vncunused'': ''1'',
''other_config'': {''vncunused'':
''1'', ''vnc'': ''1''},
''vnc'': ''1'', ''uuid'':
''e40219c2-a740-c910-2840-be3a2aaa9548'',
''location'': ''127.0.0.1:5902''}
>[2010-07-01 12:06:49 5660] 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.
>[2010-07-01 12:06:49 5660] DEBUG (DevController:97) DevController: writing
{''vncunused'': ''1'',
''domain'': ''chsimp2'',
''frontend'': ''/local/domain/1/device/vfb/0'',
''uuid'':
''e40219c2-a740-c910-2840-be3a2aaa9548'',
''frontend-id'': ''1'',
''state'': ''1'', ''location'':
''127.0.0.1:5902'', ''online'':
''1'', ''vnc'': ''1''} to
/local/domain/0/backend/vfb/1/0.
>[2010-07-01 12:06:49 5660] INFO (XendDomainInfo:2402) createDevice: vbd :
{''protocol'': ''x86_32-abi'',
''uuid'':
''31c2d623-a977-4e81-5ecc-2ab09907f76e'',
''bootable'': 1, ''driver'':
''paravirtualised'', ''dev'':
''hda:disk'', ''uname'':
''phy:/dev/disk/by-id/scsi-200d0b29d2d002200'',
''mode'': ''w'', ''backend'':
''0''}
>[2010-07-01 12:06:49 5660] DEBUG (DevController:95) DevController: writing
{''virtual-device'': ''768'',
''protocol'': ''x86_32-abi'',
''device-type'': ''disk'',
''backend-id'': ''0'',
''state'': ''1'', ''backend'':
''/local/domain/0/backend/vbd/1/768''} to
/local/domain/1/device/vbd/768.
>[2010-07-01 12:06:49 5660] DEBUG (DevController:97) DevController: writing
{''domain'': ''chsimp2'',
''frontend'':
''/local/domain/1/device/vbd/768'', ''uuid'':
''31c2d623-a977-4e81-5ecc-2ab09907f76e'',
''bootable'': ''1'', ''dev'':
''hda'', ''state'': ''1'',
''params'':
''/dev/disk/by-id/scsi-200d0b29d2d002200'',
''mode'': ''w'', ''online'':
''1'', ''frontend-id'': ''1'',
''type'': ''phy''} to
/local/domain/0/backend/vbd/1/768.
>[2010-07-01 12:06:49 5660] INFO (XendDomainInfo:2402) createDevice: vif :
{''bridge'': ''br0'', ''mac'':
''00:16:3e:1f:ea:77'', ''script'':
''/etc/xen/scripts/vif-bridge'', ''uuid'':
''53301d91-5283-d69d-4b7d-5beb3deee963'',
''backend'': ''0''}
>[2010-07-01 12:06:49 5660] DEBUG (DevController:95) DevController: writing
{''backend-id'': ''0'', ''mac'':
''00:16:3e:1f:ea:77'', ''handle'':
''0'', ''state'': ''1'',
''backend'':
''/local/domain/0/backend/vif/1/0''} to
/local/domain/1/device/vif/0.
>[2010-07-01 12:06:49 5660] DEBUG (DevController:97) DevController: writing
{''bridge'': ''br0'',
''domain'': ''chsimp2'',
''handle'': ''0'', ''uuid'':
''53301d91-5283-d69d-4b7d-5beb3deee963'',
''script'': ''/etc/xen/scripts/vif-bridge'',
''mac'': ''00:16:3e:1f:ea:77'',
''frontend-id'': ''1'',
''state'': ''1'', ''online'':
''1'', ''frontend'':
''/local/domain/1/device/vif/0''} to
/local/domain/0/backend/vif/1/0.
>[2010-07-01 12:06:49 5660] DEBUG (XendDomainInfo:1835) Storing domain
details: {''console/port'': ''4'',
''description'': '''',
''console/limit'': ''1048576'',
''image/suspend-cancel'': ''1'',
''domid'': ''1'', ''vm'':
''/vm/92b1b8f4-94aa-d393-92a4-3d78262bf092'',
''cpu/0/availability'': ''online'',
''memory/target'': ''2097152'',
''control/platform-feature-multiprocessor-suspend'':
''1'', ''console/type'':
''ioemu'', ''cpu/1/availability'':
''online'', ''store/port'':
''3'', ''name'': ''chsimp2''}
>[2010-07-01 12:06:49 5660] INFO (XendCheckpoint:343) restore hvm domain 1,
apic=0, pae=1
>[2010-07-01 12:06:49 5660] DEBUG (image:339) No VNC passwd configured for
vfb access
>[2010-07-01 12:06:49 5660] DEBUG (image:901) args: boot, val: c
>[2010-07-01 12:06:49 5660] DEBUG (image:901) args: fda, val: None
>[2010-07-01 12:06:49 5660] DEBUG (image:901) args: fdb, val: None
>[2010-07-01 12:06:49 5660] DEBUG (image:901) args: soundhw, val: None
>[2010-07-01 12:06:49 5660] DEBUG (image:901) args: localtime, val: 0
>[2010-07-01 12:06:49 5660] DEBUG (image:901) args: serial, val: None
>[2010-07-01 12:06:49 5660] DEBUG (image:901) args: std-vga, val: 0
>[2010-07-01 12:06:49 5660] DEBUG (image:901) args: isa, val: 0
>[2010-07-01 12:06:49 5660] DEBUG (image:901) args: acpi, val: 1
>[2010-07-01 12:06:49 5660] DEBUG (image:901) args: usb, val: 1
>[2010-07-01 12:06:49 5660] DEBUG (image:901) args: usbdevice, val: tablet
>[2010-07-01 12:06:49 5660] DEBUG (image:901) args: gfx_passthru, val: None
>[2010-07-01 12:06:49 5660] INFO (image:833) Need to create platform
device.[domid:1]
>[2010-07-01 12:06:49 5660] DEBUG (XendCheckpoint:361) restore:shadow=0x12,
_static_max=0x80000000, _static_min=0x0,
>[2010-07-01 12:06:49 5660] DEBUG (XendCheckpoint:380) [xc_restore]:
/usr/lib64/xen/bin/xc_restore 17 1 3 4 1 1 0 0
>[2010-07-01 12:06:49 5660] INFO (XendCheckpoint:482) xc_domain_restore
start: p2m_size = 100000
>[2010-07-01 12:06:49 5660] INFO (XendCheckpoint:482) Reloading memory pages:
0%
>[2010-07-01 12:08:12 5660] INFO (XendCheckpoint:482) Read 1448 bytes of QEMU
data
>[2010-07-01 12:08:12 5660] INFO (XendCheckpoint:482) Read 5544 bytes of QEMU
data
>[2010-07-01 12:08:12 5660] INFO (XendCheckpoint:482) Read 9 bytes of QEMU
data
>[2010-07-01 12:08:13 5660] INFO (XendCheckpoint:482) ERROR Internal error:
Error when reading batch size
>[2010-07-01 12:08:13 5660] INFO (XendCheckpoint:482) ERROR Internal error:
error when buffering batch, finishing
>[2010-07-01 12:08:13 5660] INFO (XendCheckpoint:482)
>[2010-07-01 12:08:13 5660] INFO (XendCheckpoint:482) Writing 7001 bytes of
QEMU data
>[2010-07-01 12:08:13 5660] INFO (XendCheckpoint:482) ERROR Internal error:
error setting the HVM context
>[2010-07-01 12:08:14 5660] INFO (XendCheckpoint:482) Restore exit with rc=1
>[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:3111)
XendDomainInfo.destroy: domid=1
>[2010-07-01 12:08:14 5660] ERROR (XendDomainInfo:3125)
XendDomainInfo.destroy: domain destruction failed.
>Traceback (most recent call last):
> File
"/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line
3118, in destroy
> xc.domain_pause(self.domid)
>Error: (3, ''No such process'')
>[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:2451) No device model
>[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:2453) Releasing devices
>[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:2459) Removing vif/0
>[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:1289)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
>[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:2459) Removing console/0
>[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:1289)
XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
>[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:2459) Removing vbd/768
>[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:1289)
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
>[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:2459) Removing vfb/0
>[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:1289)
XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
>[2010-07-01 12:08:14 5660] INFO (XendDomain:1108) Domain chsimp2
(92b1b8f4-94aa-d393-92a4-3d78262bf092) deleted.
>[2010-07-01 12:08:14 5660] ERROR (XendCheckpoint:416)
/usr/lib64/xen/bin/xc_restore 17 1 3 4 1 1 0 0 failed
>Traceback (most recent call last):
> File
"/usr/lib64/python2.6/site-packages/xen/xend/XendCheckpoint.py", line
384, in restore
> forkHelper(cmd, fd, handler.handler, True)
> File
"/usr/lib64/python2.6/site-packages/xen/xend/XendCheckpoint.py", line
470, in forkHelper
> raise XendError("%s failed" % string.join(cmd))
>XendError: /usr/lib64/xen/bin/xc_restore 17 1 3 4 1 1 0 0 failed
>[2010-07-01 12:08:14 5660] ERROR (XendDomain:1176) Restore failed
>Traceback (most recent call last):
> File
"/usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py", line
1160, in domain_restore_fd
> dominfo = XendCheckpoint.restore(self, fd, paused=paused,
relocating=relocating)
> File
"/usr/lib64/python2.6/site-packages/xen/xend/XendCheckpoint.py", line
417, in restore
> raise exn
>XendError: /usr/lib64/xen/bin/xc_restore 17 1 3 4 1 1 0 0 failed
>
>
>
>On Wednesday 07 July 2010 17:27:23 Srija G wrote:
>> Thank you so much to both of you John and Matej.
>>
>> Yes, both of your solution, worked when I am live migrating the
guest
>> from one dom0 to another dom0.
>>
>> What i am doing now,
>>
>> - In Host-B , I am executing the command ,
>>
>> ping Guest-15a
>>
>> - In the Host-A , I am executing the command
>>
>> xm migrate --live Guest-15a Host-B
>>
>> The result:
>>
>> * Live migration went very well, found there is just 1
sec
>> stop in between but I think that is acceptable.*
>>
>> Our network team says that portfast is already configured at switch .
>>
>> But as the first option worked , so I hope I can move on - right?
If
>> not please advice....
>>
>> My second question is, mode=4 , ie 802.2ad ( link aggregation ) did
not
>> work still yet. I wanted to
>> set the mode=4 as it is much faster. Found one document , here is the
url
>>
>>
http://wiki.oracle.com/page/Cisco+Systems+IOS-based+switches-+interface+bon
>> ding+and+trunking
>>
>> It is very good . In this document , the first line it is mentioned
:
>>
>> ***** It is important that the native VLANs *be identical* on both
sides
>> of the link
>>
>> What does it mean VLANs *be identical* on both sides of the link ?
Sorry
>> for the silly question though.
>>
>> Would you please explain , do I need to check /configure anything on
the
>> server side? My configuration is simple enough ,
>>
>> In my configuration I have used eth0 and eth1 bonded to bond0, and
for
>> each subnet, created the
>>
>> config files, as ifcfg-bond0.15, ifcfg-bond0.16, ifcfg-bond0.17.
Then
>> in the /etc/xen/scripts , I have created
>>
>> a custom file where I mentioned all the bridges for each vlan tag.
And
>> this custom file is being called
>>
>> from /etc/xen/xend-config.sxp...
>>
>>
>> Please advice, do you need to proceed with aggregation link or with
>> mode=1, which is now configured and
>> you all helped me a work around...
>>
>> Thanks again.
>>
>> On Mon, Jul 5, 2010 at 6:25 AM, John Haxby
<john.haxby@oracle.com> wrote:
>> > On Sat, 2010-07-03 at 17:57 -0400, Srija G wrote:
>> >> Hi ,
>> >> [snip]
>> >>
>> >> Can anyone please advice , where to check? Do you think it is
the
>> >> switch configuration issues?
>> >
>> > It''s almost certainly a switch issue: the switch
doesn''t know that the
>> > MAC address for the recently migrated machine is on a different
port.
>> >
>> > There are two possibilities: you can either ping something (eg the
>> > default router) _from_ the guest after it has migrated or you can
set
>> > portfast on the switch. The former just informs the switch that
the
>> > originating MAC address is now on a different port; the latter
makes the
>> > switch less willing to hold on to the MAC address/port association
for a
>> > long time and is something that the network people can do. You
might
>> > want to try doing both.
>> >
>> > jch
>>
>
>Why don''t you use multipathing in stead of bonding?
>
>B.
>
>
>I''ve just gotten xen-4.0.1-rc4-pre on top of Ubuntu 10.04 using the
2.6.32.15 kernel source installed and booting into Dom0 thanks to you guys!
>
>I was under the impression that xend would setup at least a basic bridge
interface and some vif interfaces automaticlly.. I don''t get any of
that. And when I try to start xend manually after reboot I get:
>ifdown: interface eth0 not configured
>RTNTELINK answers: Device or resource busy
>
>Not sure what''s going on.
>Thanks,
>-S
>
>________________________________
>This e-mail and any files transmitted with it may be proprietary and are
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this e-mail in error please notify the sender.
>Please note that any views or opinions presented in this e-mail are solely
those of the author and do not necessarily represent those of ITT Corporation.
The recipient should check this e-mail and any attachments for the presence of
viruses. ITT accepts no liability for any damage caused by any virus transmitted
by this e-mail.
>
>
>Thanks Dan,
>I tried that and it worked :-)
>Thanks to Cristian Columbo yourself for all your help!
>-Steve
>
>________________________________________
>From: Dante Cinco [dantecinco@gmail.com]
>Sent: Tuesday, July 06, 2010 4:31 PM
>To: Horton, Steve - IS; Xen-users
>Subject: [Xen-users] BusyBox (Gave up waiting on root device)
>
>Try adding "dummy=dummy" in your dom0 kernel cmdline:
>
>menuentry "Xen-test" {
>set root=''(hd0,1)''
>multiboot /boot/xen.gz dom0_mem=1000M
>module /boot/vmlinuz-2.6.32.15 dummy=dummy root=/dev/sda1 ro
>module /boot/initrd.img-2.6.32.15
>}
>
>Dante
>
>-----Original Message-----
>From: xen-users-bounces@lists.xensource.com
>[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Horton,
>Steve - IS
>Sent: Tuesday, July 06, 2010 12:30 PM
>To: xen-users@lists.xensource.com
>Subject: [Xen-users] BusyBox (Gave up waiting on root device)
>
>I used the guide at
>http://bderzhavets.wordpress.com<http://bderzhavets.wordpress.com/> to
>install xen-4.0.1-rc4-pre on top of Ubuntu 10.04 using the 2.6.32.15
>kernel source from jeremy''s repo. I got the kernel built and
managed
>to get xen all built and installed but when it''s booting it drops
to a
>busybox shell after it finds my NIC(s). It says: Gave up waiting on
>root device.
>
>It''s acts like it can''t mount /dev/sda1 but I
don''t know why.
>
>Not sure if this is correct.. but here is my 40_custom file:
>
>menuentry "Xen-test" {
>set root=''(hd0,1)''
>multiboot /boot/xen.gz dom0_mem=1000M
>module /boot/vmlinuz-2.6.32.15 root=/dev/sda1 ro
>module /boot/initrd.img-2.6.32.15
>}
>
>Thanks!
>-S
>
>This e-mail and any files transmitted with it may be proprietary and are
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this e-mail in error please notify the sender.
>Please note that any views or opinions presented in this e-mail are solely
those of the author and do not necessarily represent those of ITT Corporation.
The recipient should check this e-mail and any attachments for the presence of
viruses. ITT accepts no liability for any damage caused by any virus transmitted
by this e-mail.
>
>
>Sure,
>My 40_custom file contains the following:
>
>menuentry "Xen-test" {
>set root=''(hd0,1)''
>multiboot /boot/xen.gz dom0_mem=1000M
>module /boot/vmlinuz-2.6.32.15 dummy root=/dev/sda1 ro
>module /boot/initrd.img-2.6.32.15
>}
>Then I just did an update-grub and rebooted off the new kernel.
>Hope this helps!
>-Steve
>________________________________
>From: Amina Khalid [amina.khalid@gmail.com]
>Sent: Wednesday, July 07, 2010 12:19 PM
>To: Horton, Steve - IS
>Subject: Re: [Xen-users] BusyBox (Gave up waiting on root device)
>
>Can you post how it worked? I am getting the same problem.
>
>Thanks
>
>On 7 July 2010 17:10, Horton, Steve - IS
<Steve.Horton@itt.com<mailto:Steve.Horton@itt.com>> wrote:
>Thanks Dan,
>I tried that and it worked :-)
>Thanks to Cristian Columbo yourself for all your help!
>-Steve
>
>________________________________________
>From: Dante Cinco [dantecinco@gmail.com<mailto:dantecinco@gmail.com>]
>Sent: Tuesday, July 06, 2010 4:31 PM
>To: Horton, Steve - IS; Xen-users
>Subject: [Xen-users] BusyBox (Gave up waiting on root device)
>
>Try adding "dummy=dummy" in your dom0 kernel cmdline:
>
>menuentry "Xen-test" {
>set root=''(hd0,1)''
>multiboot /boot/xen.gz dom0_mem=1000M
>module /boot/vmlinuz-2.6.32.15 dummy=dummy root=/dev/sda1 ro
>module /boot/initrd.img-2.6.32.15
>}
>
>Dante
>
>-----Original Message-----
>From:
xen-users-bounces@lists.xensource.com<mailto:xen-users-bounces@lists.xensource.com>
>[mailto:xen-users-bounces@lists.xensource.com<mailto:xen-users-bounces@lists.xensource.com>]
On Behalf Of Horton,
>Steve - IS
>Sent: Tuesday, July 06, 2010 12:30 PM
>To:
xen-users@lists.xensource.com<mailto:xen-users@lists.xensource.com>
>Subject: [Xen-users] BusyBox (Gave up waiting on root device)
>
>I used the guide at
>http://bderzhavets.wordpress.com<http://bderzhavets.wordpress.com/> to
>install xen-4.0.1-rc4-pre on top of Ubuntu 10.04 using the 2.6.32.15
>kernel source from jeremy''s repo. I got the kernel built and
managed
>to get xen all built and installed but when it''s booting it drops
to a
>busybox shell after it finds my NIC(s). It says: Gave up waiting on
>root device.
>
>It''s acts like it can''t mount /dev/sda1 but I
don''t know why.
>
>Not sure if this is correct.. but here is my 40_custom file:
>
>menuentry "Xen-test" {
>set root=''(hd0,1)''
>multiboot /boot/xen.gz dom0_mem=1000M
>module /boot/vmlinuz-2.6.32.15 root=/dev/sda1 ro
>module /boot/initrd.img-2.6.32.15
>}
>
>Thanks!
>-S
>
>This e-mail and any files transmitted with it may be proprietary and are
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this e-mail in error please notify the sender.
>Please note that any views or opinions presented in this e-mail are solely
those of the author and do not necessarily represent those of ITT Corporation.
The recipient should check this e-mail and any attachments for the presence of
viruses. ITT accepts no liability for any damage caused by any virus transmitted
by this e-mail.
>
>_______________________________________________
>Xen-users mailing list
>Xen-users@lists.xensource.com<mailto:Xen-users@lists.xensource.com>
>http://lists.xensource.com/xen-users
>
>
>
>You knew it was going to happen, you just knew it :).
>
>I just started upgrading the production cloud from 0.1.1 to 0.5 this
>afternoon. Migrated all the VMs to the slaves, upgraded the pool master,
>then I thought I''d check to make sure the upgraded pool master
rejoined
>the pool ok, so I tried to view all VMs from the console and got "This
>feature is not available in pools with more than 100 virtual machines."
>
>I don''t know if this is just an artifact of doing this on a
partially
>upgraded pool or what, but since I have well south of 100 VMs, I''d
call
>it a bug :). Good news is that XCCS displays this info correctly, so
>this appears to be a non-critical bug :).
>
>
>--
>Vern Burke
>
>SwiftWater Telecom
>http://www.swiftwatertel.com
>ISP/CLEC Engineering Services
>Data Center Services
>Remote Backup Services
>
>
>Once again, another apparently non-critical bug but one you have to
>watch out for.
>
>VMs in the pool with the 0.1.1 pv drivers are shown to the 0.5 pool
>master as pv drivers up to date when the pv drivers are clearly out of
>date. This is verified by noting that the 0.5 pool master can''t get
the
>IP addresses in use from a VM with 0.1.1 pv drivers.
>
>Remember to update your VM''s pv drivers :).
>--
>Vern Burke
>
>SwiftWater Telecom
>http://www.swiftwatertel.com
>ISP/CLEC Engineering Services
>Data Center Services
>Remote Backup Services
>
>
>I got really strange situation with memory on host:
>
>
>xe host-list params=memory-free
>memory-free ( RO) : 10305536
>(10Mb)
>
>xe host-compute-free-memory
>3147059200
>(3Gb)
>
>A huge difference! And xentop show different numbers too!
>
>I will keep this host online "as is" and I am ready to provide
information for debbugging or perform needed actions.
>
>--
>wBR,George.
>
>
>_______________________________________________
>Xen-users mailing list
>Xen-users@lists.xensource.com
>http://lists.xensource.com/xen-users
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users