search for: hvmimagehandl

Hi Ewan, I''m almost ready to integrate some PPC-specific stuff into xend, and I was wondering if you had a plan for how that should work. First example: the device tree data structure we talked about a few weeks ago. We will need to pass the config data to PPC code, probably in XendDomainInfo.initDomain(), and then pass the resulting data structure into libxc''s xc_linux_load()

...; #----------------------------------------------------------------------------- diff -r 2abb1c801ab7 tools/python/xen/xend/image.py --- a/tools/python/xen/xend/image.py Wed Jul 19 16:09:59 2006 +0800 +++ b/tools/python/xen/xend/image.py Thu Jul 20 21:19:07 2006 +0800 @@ -249,7 +249,7 @@ class HVMImageHandler(ImageHandler): # Return a list of cmd line args to the device models based on the # xm config file def parseDeviceModelArgs(self, imageConfig, deviceConfig): - dmargs = [ ''cdrom'', ''boot'', ''fda'', ''fdb'', &...

...python/xen/xend/image.py Wed Nov 28 13:36:56 2007 +0000 +++ b/tools/python/xen/xend/image.py Wed Nov 28 09:48:59 2007 -0700 @@ -22,6 +22,7 @@ import math import math import time import signal +import struct import xen.lowlevel.xc from xen.xend.XendConstants import * @@ -426,6 +427,7 @@ class HVMImageHandler(ImageHandler): self.apic = int(vmConfig[''platform''].get(''apic'', 0)) self.acpi = int(vmConfig[''platform''].get(''acpi'', 0)) + self.guest_os_type = vmConfig[''platform''].get(''g...

...DomainInfo.destroyDomain(11) [2006-05-18 14:48:06 xend] ERROR (image:404) Unwatching hvm shutdown watch failed. Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/image.py", line 401, in unregister_shutdown_watch if self.shutdownWatch: AttributeError: HVMImageHandler instance has no attribute ''shutdownWatch'' [2006-05-18 14:48:06 xend] DEBUG (image:406) hvm shutdown watch unregistered [2006-05-18 14:48:06 xend] ERROR (xmlrpclib2:124) (22, ''Invalid argument'') Traceback (most recent call last): File "/usr/lib/python2.4/...

> Thanks all point about security, I''ll do as follows. > I thought that the point was the following two. > > > 1. Storage place of encrypted password > Should I store it in /etc/xen/passwd ? > Or, should I wait for DB of Xen that will be released in > the future? The xend life cycle management patches were posted by Alistair a couple of months back.

...s patch corrects above. Regards, Masami ------------------------------------ diff -r a661566745ae tools/python/xen/xend/image.py --- a/tools/python/xen/xend/image.py Tue Oct 24 16:46:02 2006 +0100 +++ b/tools/python/xen/xend/image.py Wed Oct 25 16:55:52 2006 +0900 @@ -395,9 +395,6 @@ class HVMImageHandler(ImageHandler): if vncpasswd != '''': self.vm.storeVm("vncpasswd", vncpasswd) - # remove password - config.remove([''vncpasswd'', vncpasswd_vmconfig]) - return ret def createDeviceModel(self): ---...

Hi everyone, I generated my own DomU guest using opensuse''s yast dirinstall and stored it on a seperate iscsi target. I created it as a DomU on my Domain0 (2.6.25.16-0.1-xen kernel) successfully, using the following configuration: name = "vm01-opensuse11-base-LAMP" memory = 256 kernel = "/boot/vmlinuz-xen" ramdisk = "/boot/initrd-xen" root =

The following series of 10 patches is a merge of the xenfb and xenconsoled functionality into the qemu-dm code. The general approach taken is to have qemu-dm provide two machine types - one for xen paravirt, the other for fullyvirt. For compatability the later is the default. The goals overall are to kill LibVNCServer, remove alot of code duplication and/or parallel impls of the same concepts, and