search for: 3tera

Hello, The xm config option boot="c" is intended to boot from the "first" harddrive; however, the enumeration of harddrives is independent of device enumeration (hda|hdb|hdc|hdd), leading to unreliable boot device selection. Example A: I am building a Windows HVM appliance which performs file-system level operations over mounted NTFS volumes - for example a file-system

After reading the digital shortcut and the documentation on the web site I''m confused. Which one should I use? pen, balance or nginx ? I don''t want to use a behemoth like appache and ssl is not needed so it reduces my choice to those three only.... What are the pros and cons of each? I don''t have much money, so the less ressources I use the better it is for me.... As

Hello, I''ve recently installed a hvm domU opensuse 11 guest and I cannot set the screen resolution higher then 640x480. This seems very strange to me, because I don''t have any problem to set higher resolution on a windows 7 domU, using the following parameters in the configuration file: stdvga=1 videoram=16 What could the problem be? Is some video driver missing? -- Flavio

Hello, I''ve recently installed a hvm domU opensuse 11 guest and I cannot set the screen resolution higher then 640x480. This seems very strange to me, because I don''t have any problem to set higher resolution on a windows 7 domU, using the following parameters in the configuration file: stdvga=1 videoram=16 What could the problem be? Is some video driver missing? -- Flavio

Hello, I have a Windows appliance which I would like to always boot using the active partition on disk 0 (hda). In operation this appliance is booted with one or more disks (hdb, hdc) which may or may not also contain an active (bootable) partition. In practice, if disk 1 (hdb) also contains an active partition, the appliance boots from disk 1 rather than disk 0. Is there a way to control

Hi - I have built a number of Windows based appliances under Xen 3.2.1. Each was created on an AMD based machine and includes a clean install of a Windows OS and cygwin. Each worked fine. I then rsync'd the images to three different Xeon based machines, each running an identical version of Xen. On these machines, under the 64-bit OS's, the cygwin bash builtin test ("[")

I am running OpenSolaris 2008.05 as a PV guest under Xen. If you import the bootable root pool of a VM into another Solaris VM, the root pool is no longer bootable. It is related to the device associated to the pool, which is originally c4d0s0, but on import (-f) becomes c0d2s0 in this case. Afterwards, booting the original image results in a kernel panic because, I think, zfs_mountroot()