similar to: hvm with no network config and how to boot up

hi there guys recently, i am studying the qemu , so i have a idea , using the qemu to emulate a winxp in hvm domian(the system is debian). But when i install the winxp , the installtion interface appearing, some seconds later , the hvm domian restart anybody experienced the same problem? Regards _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org

Package: xen-utils-common Version: 4.1.3-8 Severity: important When antispoof is set to 'on', the vif-common script does not create an ALLOW firewall rule for the emulated vif devices. This means that HVM nodes, unless a Xen PV driver is installed and running, cannot access the external network. The vif-common script creates an ACCEPT entry for the normal vif device (e.g. vif4.0) but not

Hi, I seem to have an interesting issue with vif-route. This is after an update to Xen 4.2.1, switching from xm to xl. I have 10 PV domUs on the host and two FreeBSD ones. All the PV domUs are now working nicely. Since FreeBSD has always been just slightly broken as PV I chose a HVM domU for those, but with PV drivers. Those PV drivers all blew up now after the upgrade. I''m now trying

Greetings, I would like to know how one can identify if a DomU is PV or HVM? Any docs which may indicate a way to find out? I have a CentOS 5.5 64bit DomU which might be HVM - how can this DomU can be made PV? Just stop the DomU, and then delete it using Virtual Machine Manager and the create another config file for a PV DomU and use xm new and then xm start? Let''s say I have a config

Dear,Beg for your help. I am really puzzled with this problem.HVM domain can not boot up with Qcow incremental image(using command: qcow-create size incremental_file original_Qcow_img_file), but it can boot up with the original Qcow disk image file. When using Qcow incremental image, the guest qemu window would disappear before loading grub, and `xm list` can not find this guest domain.The VM

tag 554805 + patch thanks The problem to solve is that qemu-ifup assumes the world is always bridged, and vif-routed does not know of the concept of TAP devices, and even if it did, it has at this point no way to get at qemu's TAP device anyway. The following set of patches help run in the ioemu-HVM situation: * xend-image.py.diff : modifies the HVM loader so that when running in

Dear, I''ve attempted to upgrade a Xen box from 3.1.2 to 3.2.1. Unfortunately it has been a partial success only. At this point I''m really stuck with a network problem that affects my HVM machines (Linux PV run fine). The really odd thing is that everything seems to work properly, except that the "vif" network interfaces in dom0 seem to have only dropped TX packets for

Hello, This is my first post in this list. I''m running Debian Squeeze as Dom0 on a bi-xeon 64 bits : root@sd-29499:/etc/xen# uname -a Linux sd-29499 2.6.32-5-xen-amd64 #1 SMP Tue Mar 8 00:01:30 UTC 2011 x86_64 GNU/Linux I''m trying to install a Squeeze DomU but there is no network card, even during install wich doesn''t show any network card with lspci (but when I

Greetings all, I''m having an issue getting a winxp hvm running. It will install just fine from iso, but then when I change the .cfg file to boot from ''c'', it will give me: invalid boot.ini file booting from c:\windows ntdetect failed Please see the below config file: import os, re arch = os.uname()[4] if re.search(''64'', arch): arch_libdir =

Hello, When using xen without a bridge but NAT or routing, HVM domains can''t boot, and qemu-dm-n.log contains: config qemu network with xen bridge for tap0 xenbr0 bridge xenbr0 does not exist! That''s because the qemu-ifup script always tries to add the vif to a default-named xenbr0 bridge. On the contrary, PV domains just work fine with the same configuration file except HVM

Greetings xen gurus... I''m working with xen-3.0-testing downloaded on July 3, 2006. I have configured an hvm domain and want to use vif-route and network-route to configure the communication. The domU starts up fine. I was able to complete the installation of the OS (RHES3) and can restart the domain repeatedly. However, I cannot ping the network interface from dom0 using the

Is anyone running lots of Xen HVM guests on a 3.10 Dom0 kernel? We've had a few weird issues where PV guests are fine, but HVM guests are getting < 1Kb/s network throughput. The configuration on the host machine, VIF and inside the VM is fine. CPU and IO is fine too. It only seems to affect servers with Broadcom network chipsets. Rolling back to a 3.4 Dom0 kernel fixes the problem, so its

Hi, I use Centos 5.4 x86_64 kernel used is 2.6.18-164.11.1.el5xen I have a physical machine running Debian Etch (32 bit) and Debian Lenny and I virtualized the first one as follows: *Created a HVM DomU with Virt-Manager with a virtual disk file of 40000 M *Boot from LiveCD, and created a swap and a ext3 partitions (Yes, very simple layout). *Rsync''d files from root partition of

Hi, I''m running Nevada 75a configured as dom0. I added a domU HVM running Nevada 75a, on a Sun X4600 with 8 ADM Dual cores. I can get the domU installed and configured, however, I can not get any network connectivity. I followed the steps accoding to documents on Open Solaris. I also followed some of the threads of the list to verify the configuration, but I can not fix the

Hi, I cannot boot Windows XP domU on SXCE104 dom0. It was running for weeks.. Is it a known bug? # virsh start wxpp01 & # virsh dumpxml wxpp01 <domain type=''xen'' id=''-1''> <name>wxpp01</name> <uuid>fb96e8c9-940d-7e0a-12ef-f167a7f1102c</uuid> <os> <type>hvm</type>

Hi I have a Xen 4.4 installation with Windows in a HVM domain and I need to use a routed setup. However the vif-route script does not work for HVM domains. So far I used an outdated Xen 4.1 installation with manually patched scripts that could do routed setups with HVM. But now I wanted to update and switch from xm to xl. Is there any way to make Xen work with HVM in a routed setup? Or do I

Hi -- I wanted to boot s10 HVM in 64-bit mode but it always boots in 32-bit mode. Is there a special grub entry to boot s10 HVM domU in 64-bit mode? Or is it HVM loader? The grub entry is like this title Solaris 10 5/08 s10x_u5wos_01 X86 kernel /platform/i86pc/multiboot module /platform/i86pc/boot_archive s10.py file is as follows :- import os, re arch = os.uname()[4] if

Hello, I am running two dom0s, one on CentOS 5 with Xen 4.1.2 (from Gitco) and the other one on CentOS 6 with Xen 4.2.4 (from Xen4CentOS). I host one LVM based domU on both from the same template (CentOS 6 PV) with the same Xen config (see below). However, the domU on Xen 4.1 reports itself as Xen PV while the domU on Xen4CentOS reports itself as Xen HVM. == First domU == virt-what and cPanel

Hi, I've been testing the Debian packages ahead of the Debian 7 release (which is very imminent) I believe this is a serious bug[1] in the package, as it appears that HVM networking is broken, or at the very least, requires some undocumented configuration step Specifically: - I can start the HVM domU without any vif - if I attach a vif, the domU will not start Looking at

I found that the example HVM config doesn't work at all on amd64 I used the following, based on various postings I found through Google. Could you include a working example in the package? I think that specifying the full kernel and device_model paths makes a difference on amd64 # Enable hardware virtualisation using HVM kernel = '/usr/lib64/xen-3.2-1/boot/hvmloader' device_model =