similar to: RE: How to configure VBD hard disk drives in Linux HVMdomain?

Dear, "Xenoppix-x86-64(Xen3.0.2+KNOPPIX-x86_64-5.0.1) CD size" is released. http://unit.aist.go.jp/itri/knoppix/xen/index-en.html Xenoppix-x86-64 exploits latest CPU (Intel Core2 Duo and AMD Athlon64). * Xenoppix-x86-64 boots both X86 and X86_64 linux kernel on HVM of Xen. * Xenoppix-x86-64 looks like KNOPPIX but all packages are replaced for X86_64. * Xenoppix-x86-64 also

Hi, since I upgraded from Lenny, DRBD VBD scripts not works at all. This config works : disk = [ 'phy:/dev/drbd/by-res/ads-disk,xvda,w' ] But his one doesn't work at all : disk = [ 'drbd:ads-disk,xvda,w' ] I obtain this error : # xm create ads.cfg Using config file "/etc/xen/ads.cfg". Error: Device 51712 (vbd) could not be connected. Hotplug scripts

hi, I am trying to start a new domainU but got the error: Error: Device 0 (vif) could not be connected. Hotplug scripts not working I have struggled with it for a long time. I found somebody else report this but can not find a solution. The xen version is xen-3.0 latest version. I do not have a initrd. Domain0 works fine but when I create a new domain, it always gives an error as above. Thanks,

Hi, I have set maxvcpus and vcpus options in my domU configuration file, and I can see that X number of vcpu are set for the domU. I tried to activate all the vpcus by using vpcu_avail option (using decimal to represent vpcu bitmask e.g. 24=11000) but it doesn''t seem to work, and only the first vpcu is activated (i.e. has -b- state) while all other vpcu''s set for the domU are

Hi, I have set maxvcpus and vcpus options in my domU configuration file, and I can see that X number of vcpu are set for the domU. I tried to activate all the vpcus by using vpcu_avail option (using decimal to represent vpcu bitmask e.g. 24=11000) but it doesn''t seem to work, and only the first vpcu is activated (i.e. has -b- state) while all other vpcu''s set for the domU are

>-----Original Message----- >From: xen-users-bounces@lists.xensource.com >[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Liang Yang >Sent: 2006年9月12日 8:57 >To: xen-users@lists.xensource.com >Subject: [Xen-users] Help: Xen HVM Domain can ONLY support four hard >drivesat most??? > >Hi, > >I have 5 SATA hard drives and I want to expose all these five

If I start a domain with a number of vbd devices, it''s a crap shoot if they''ll all show up in the domU''s /proc/partitions. I''ll eventually see all the devices if I keep rebooting the domU. The value of /local/domain/$DOMID/device/vbd/*/state are all 1 for the missing devices, and 4 for the ones that show up. When it works: domU:~# cat /proc/partitions

Last week, I mentioned an error I was getting, as described below. I''ve seen several mailing list posts describing a similar problem as far back as December, 2005. This seems to be a problem plaguing all Xen 3 releases (to date). > > 3. After booting and then destroying approximately 25 domains, the > system will require a reboot before I can add further domains. The

Hi, have a debian 5.0 with all patches and xen 4.3.1 (debian repo) installed. If I use a VM with paravirtualizing it works fine. But a full virtualized image doesn''t boot. Message: ---8<--- # xm create deb50.cfg: Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. ---8<--- That is my deb50.cfg ---8<--- # Debian 5.0 import os, re arch = os.uname()[4]

tail /var/log/xen/xen-hotplug.log xenstore-read: couldn't read path backend/vbd/6/768/node /etc/xen/scripts/xen-hotplug-cleanup: line 24: [: !=: unary operator expected /etc/xen/scripts/xen-hotplug-cleanup: line 24: [: !=: unary operator expected xenstore-read: couldn't read path backend/vbd/6/5632/node xenstore-read: couldn't read path backend/vbd/6/768/node

I''m trying to add vbd resize to GPLPV, but it doesn''t seem to work: xm block-attach w2k3test32 phy:/dev/vg-xen/virt-test-0 hdb w xenstore-read /local/domain/0/backend/vbd/377/832/sectors =44056576 lvextend --size=+1M /dev/vg-xen/virt-test-0 xenstore-read /local/domain/0/backend/vbd/377/832/sectors =44056576 The xenstore backend isn''t updated to reflect the new size

Hi, From cset 10921, ioemu: prefix is removed from disk config in /etc/xen/xmexample.hvm. Now HVM VBD driver is available, this thus raises a question: how would HVM domain know if one disk is a qemu-dm disk or a VBD disk? From current implementation, qemu-dm will recognize disk had, hdb, hdc, hdd, and VBD drive can recognize all disk (had~hdd, hde, hdf ...) . So the result is: qemu-dm will

After a few times of building xen by source, I can''t start domU anyway. I tried "yum erase xen kernel-xen" and "yum install xen kernel-xen" again, but the problem is still exist. There are xenstore-write errors in /var/log/xen/xen-hotplug.log: xenstore-write: could not write path backend/vbd/1/2050/hotplug-error xenstore-write: could not write path

Error: Device 2051 (vbd) could not be connected. Hotplug scripts not working. Hello xen users,                  i got the following error Device 2051 (vbd) could not be connected. Hotplug scripts not working. my xend log (last part)looks like this [2007-06-06 12:49:44 32539] DEBUG (__init__:1094) Storing domain details: {''console/ring-ref'': ''187566'',

Hi, I encountered a problem while porting Solaris as a guest OS on Xen. The problem I found is that when frontend vbd driver get unloaded, it will close the vbd interface by changing the state to XenbusStateClosed. This appears to cause the dom0 hotplug scripts to remove the vbd entry from xenstore for the domU guest, preventing the vbd from being re-attached. So, my questions are: + This

Hi, I have a running LVM-DRBD-Xen-HVM/Win2k3 cluster-stack under debian/ lenny managed by heartbeat/crm. At takeover/failover heartbeat first is stopping my HVM-domU with success apparently: -------------- corresponding heartbeat log line ----------------- greatmama-n2 lrmd: [3382]: info: RA output: (xendom_infra_win:stop:stdout) Domain infra-win2003sbs terminated All domains terminated

Hi. I''ve just upgrade my xen 3.0.1 to xen unstable. I noticed that there is no vmx driver here, only hvm. Actually I cannot start my VT domain: root@akira:/etc/xen# xm create bluszcz.hvm Using config file "bluszcz.hvm". Error: Device 768 (vbd) could not be connected. Backend device not found. root@akira:/etc/xen# my config: import os, re arch = os.uname()[4] if

Hi! Please help me. # xm create win7.hvm Using config file "./win7.hvm". Error: Device 768 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/9/768 state: 1 grep -v ^# /etc/xen/win7.hvm | grep -vx '''' kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' memory = 2048 name = "win7" vif = [

I am trying to get PV drivers running on both Centos 5.1 and Centos 5.3 HVMs, my DomU is Centos 5.2 with Xen 3.31. For 5.1 I install the kmod-xenpv RPM but for 5.3 the drivers seem to be built-in. For the network drivers to work I had to unload the Realtek NIC driver and renamed its .ko files to stop it loading. Adding the Xen-Vnif alias to modprobe.conf then got the PV NICs working nicely (Much

I sent before few days. However, anyone did not comments. So, I resend this patch series. I hope to response for this patch series. This patch series provides the function to display VBD information through xentop. VBD information will be possible to get through sysfs which is locale in /sys/devices/xen-backed/vbd-x-xxxx, by previous patch. In this patch series, libxenstat collects these