Praveen Kushwaha
2007-Mar-27 11:24 UTC
[Xen-users] calling the VMX instructions from HVM guest application
Hi
Since the xen provide the VMX instruction set (like VMPTRLD,
VMREAD, VMWRITE, VMCLEAR VMCALL etc.) to manage the VMCS.
I have some queries regarding these instructions:
1. Can an application in HVM guest call these VMX instructions?
2. Is VMCS structure is updated by the processor automatically in
case VMexit happens ? Suppose VMExit operation caused due to VMcall then
Will the VMCS structure will be updated automatically(i.e. Guest
state information is saved on VMCS) ? can the application in HVM guest
also
store some information on VMCS?
3. what are the other way to pass information from HVM guest to
hypervisor. Though there is VMWRITE instruction is there, but how
actually it works?
If anyone has information regarding it please reply.
Thanks,
Praveen Kushwaha
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Praveen Kushwaha
2007-Mar-28 06:56 UTC
[Xen-devel] calling the VMX instructions from HVM guest application
Hi
Since the xen(Intel) provide the VMX instruction set (like
VMPTRLD, VMREAD, VMWRITE, VMCLEAR VMCALL etc.) to manage the VMCS.
I have some queries regarding these instructions:
1. Can an application in HVM guest call these VMX instructions? If
yes how to call these VMX instructions, is it through the hyper calls or
through other mechanism?
2. Is VMCS structure is updated by the processor automatically in
case VMexit happens ? Suppose VMExit operation caused due to VMcall then
Will the VMCS structure will be updated automatically(i.e. Guest
state information is saved on VMCS) ? can the application in HVM guest
also
store some information on VMCS?
3. what are the other way to pass information from HVM guest to
hypervisor. Though there is VMWRITE instruction is there, but how
actually it works? I mean to say that , if VMWRITE instruction will be
called then VMExit will happen. Then how exactly to pass information to
hypervisor using VMCS?
Above of some questions might not be intelligent enough. If
anyone has information regarding it please reply.
Thanks,
Praveen Kushwaha
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Petersson, Mats
2007-Mar-28 08:59 UTC
RE: [Xen-devel] calling the VMX instructions from HVM guest application
> -----Original Message----- > From: xen-devel-bounces@lists.xensource.com > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of > Praveen Kushwaha > Sent: 28 March 2007 07:56 > To: xen-devel@lists.xensource.com; xen-users@lists.xensource.com > Subject: [Xen-devel] calling the VMX instructions from HVM > guest application > > > > Hi > > Since the xen(Intel) provide the VMX instruction set > (like VMPTRLD, VMREAD, VMWRITE, VMCLEAR VMCALL etc.) to > manage the VMCS. > > I have some queries regarding these instructions: > > > > 1. Can an application in HVM guest call these VMX > instructions? If yes how to call these VMX instructions, is > it through the hyper calls or through other mechanism?There is ONE of these instructions that can be used (without problems) by the guest: VMCALL, which forces a VMExit to the hypervisor. Ok, so if you do a VMCLEAR for example in the guest, then it will actually just cause a VMExit for that too - but with a different exit value (in this particular example EXIT_REASON_VMCLEAR), which will be used by the hypervisor to instruct the guest to do a "invalid opcode" [1] (using the vmx_inject_exception function). See line 2754 in .../xen/arch/x86/hvm/vmx/vmx.c). It seems like the svm.c code isn''t doing exactly the same thing (it''s crashing the guest instead. I''ll see if I can fix that up - I don''t think the current behaviour is correct). [1] Invalid opcode is also the result if this instruction was executed without enabling VMX/SVM in the first place. See AMD and Intel documentation for the respective instructions.> > 2. Is VMCS structure is updated by the processor > automatically in case VMexit happens ? Suppose VMExit > operation caused due to VMcall then > > Will the VMCS structure will be updated > automatically(i.e. Guest state information is saved on VMCS) > ?Yes, the processor writes to VMCS with the current state of the processor at the time of VMExit (regardless of the reason for te Vmexit).> can the application in HVM guest also > store some information on VMCS?Aside from register values stored by the processor (rAX, rSP), there is no information that the guest has free control over that is stored in the VMCS. As part of the VMEXIT handler, the rest of the registers from the guest are also stored, so those can be seen and modified by the hypervisor (this is for example the case on a mov %cr0,%rbx).> > 3. what are the other way to pass information from HVM > guest to hypervisor. Though there is VMWRITE instruction is > there, but how actually it works? I mean to say that , if > VMWRITE instruction will be called then VMExit will happen. > Then how exactly to pass information to hypervisor using VMCS?The VWWRITE instruction is only allowed within the hypervisor itself. The guest is not allowed (and should never be allowed) to touch the VMCS. The VMCS belongs to the hypervisor to control the guest, and there''s no reason why the guest should even know that such a think exists. -- Mats> > > > Above of some questions might not be intelligent > enough. If anyone has information regarding it please reply. > > > > Thanks, > > Praveen Kushwaha > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Nicolai Lang
2007-Apr-15 16:02 UTC
[Xen-users] Debian 4.0, domU''s can not get network access
Hi all,
I have installed a Debian 4.0 (newly released), compiled and installed Xen.
All went as I am used to from Ubuntu.
I created a new guest with Debian Etch debootstrap, and it boots without
problems. But it can not fetch an IP address from my DHCP server
(10.13.15.1). When I use TCPDump on xenbr0, it only shows the requets being
transmitted but nothing is recieved.
I hope I have included all relevant information below, and I hope someone
can help me where to look for the cause. I have searched widely in the Wiki,
google and mailinglist.
Once I suceed, I will post an new article on the Wiki with a step-by-step
guide to compiling and installing Xen from source on Debian 4.0.
Thank you very much in advance
Best regards
Nicolai
root@judas:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:0E:A6:F9:95:61
inet addr:10.13.15.50 Bcast:10.13.15.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:677 errors:0 dropped:0 overruns:0 frame:0
TX packets:522 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:85879 (83.8 KiB) TX bytes:96248 (93.9 KiB)
Interrupt:17 Base address:0x6000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
xenbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
root@judas:~# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
root@judas:~#
Console during startup:
Setting up networking....
Configuring network interfaces...Internet Systems Consortium DHCP Client
V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/eth0/00:16:3e:00:01:03
Sending on LPF/eth0/00:16:3e:00:01:03
Sending on Socket/fallback
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
After the startup - notice that vifl1.0 and xenbr0 recieves data, but
nothing is transmitted
root@judas:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:0E:A6:F9:95:61
inet addr:10.13.15.50 Bcast:10.13.15.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:960 errors:0 dropped:0 overruns:0 frame:0
TX packets:826 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:108668 (106.1 KiB) TX bytes:203020 (198.2 KiB)
Interrupt:17 Base address:0x6000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:15 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:3420 (3.3 KiB) TX bytes:0 (0.0 b)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:15 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3420 (3.3 KiB) TX bytes:0 (0.0 b)
root@judas:~# brctl show
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no vif1.0
deamon.log:
Apr 15 17:17:44 judas logger: /etc/xen/scripts/block: add
XENBUS_PATH=backend/vbd/1/770
Apr 15 17:17:44 judas logger: /etc/xen/scripts/block: add
XENBUS_PATH=backend/vbd/1/769
Apr 15 17:17:45 judas logger: /etc/xen/scripts/vif-bridge: online
XENBUS_PATH=backend/vif/1/0
Apr 15 17:17:45 judas logger: /etc/xen/scripts/block: Writing
backend/vbd/1/769/node /dev/loop0 to xenstore.
Apr 15 17:17:45 judas logger: /etc/xen/scripts/block: Writing
backend/vbd/1/769/physical-device 7:0 to xenstore.
Apr 15 17:17:45 judas logger: /etc/xen/scripts/block: Writing
backend/vbd/1/769/hotplug-status connected to xenstore.
Apr 15 17:17:45 judas logger: /etc/xen/scripts/vif-bridge: Successful
vif-bridge online for vif1.0, bridge xenbr0.
Apr 15 17:17:45 judas logger: /etc/xen/scripts/vif-bridge: Writing
backend/vif/1/0/hotplug-status connected to xenstore.
Apr 15 17:17:46 judas logger: /etc/xen/scripts/block: Writing
backend/vbd/1/770/node /dev/loop1 to xenstore.
Apr 15 17:17:46 judas logger: /etc/xen/scripts/block: Writing
backend/vbd/1/770/physical-device 7:1 to xenstore.
Apr 15 17:17:46 judas logger: /etc/xen/scripts/block: Writing
backend/vbd/1/770/hotplug-status connected to xenstore.
messages:
Apr 15 17:16:14 judas dhcdbd: message_handler: message handler not found
under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Apr 15 17:16:14 judas dhcdbd: message_handler: message handler not found
under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Apr 15 17:16:16 judas dhcdbd: message_handler: message handler not found
under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
Apr 15 17:16:16 judas dhcdbd: message_handler: message handler not found
under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.domain_name
Apr 15 17:16:16 judas dhcdbd: message_handler: message handler not found
under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Apr 15 17:16:16 judas dhcdbd: message_handler: message handler not found
under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Apr 15 17:16:17 judas kernel: Bridge firewalling registered
Apr 15 17:17:45 judas kernel: device vif1.0 entered promiscuous mode
Apr 15 17:17:45 judas kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Apr 15 17:17:49 judas kernel: xenbr0: port 1(vif1.0) entering learning state
Apr 15 17:17:49 judas kernel: xenbr0: topology change detected, propagating
Apr 15 17:17:49 judas kernel: xenbr0: port 1(vif1.0) entering forwarding
state
xend-debug.log:
Xend started at Sun Apr 15 17:16:16 2007.
ifdown: interface eth0 not configured
SIOCSIFNAME: Device or resource busy
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
ben henrion
2007-Apr-25 07:26 UTC
Re: [Xen-users] Debian 4.0, domU''s can not get network access
HI i'' ve tried xen 3.0.4 with etch 4.0 and ive exactly the same problem. 2007/4/15, Nicolai Lang <nicolai@hjorth.com>:> > Hi all, > > I have installed a Debian 4.0 (newly released), compiled and installed > Xen. > All went as I am used to from Ubuntu. > > I created a new guest with Debian Etch debootstrap, and it boots without > problems. But it can not fetch an IP address from my DHCP server > (10.13.15.1). When I use TCPDump on xenbr0, it only shows the requets > being > transmitted but nothing is recieved. > > I hope I have included all relevant information below, and I hope someone > can help me where to look for the cause. I have searched widely in the > Wiki, > google and mailinglist. > > Once I suceed, I will post an new article on the Wiki with a step-by-step > guide to compiling and installing Xen from source on Debian 4.0. > > Thank you very much in advance > > Best regards > Nicolai > > > root@judas:~# ifconfig > eth0 Link encap:Ethernet HWaddr 00:0E:A6:F9:95:61 > inet addr:10.13.15.50 Bcast:10.13.15.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:677 errors:0 dropped:0 overruns:0 frame:0 > TX packets:522 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:85879 (83.8 KiB) TX bytes:96248 (93.9 KiB) > Interrupt:17 Base address:0x6000 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > xenbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > ---->We can just notice that when xend start, it don''t put the PETH0 and > vif0.0 in the bridge Xenbr0, plus we can add that xend don''t creat PETH0 > and vif0.0.... > > maybe a bug with ETCH 4.0.....root@judas:~# iptables -L> Chain INPUT (policy ACCEPT) > target prot opt source destination > > Chain FORWARD (policy ACCEPT) > target prot opt source destination > > Chain OUTPUT (policy ACCEPT) > target prot opt source destination > root@judas:~# > > > Console during startup: > Setting up networking.... > Configuring network interfaces...Internet Systems Consortium DHCP Client > V3.0.4 > Copyright 2004-2006 Internet Systems Consortium. > All rights reserved. > For info, please visit http://www.isc.org/sw/dhcp/ > > Listening on LPF/eth0/00:16:3e:00:01:03 > Sending on LPF/eth0/00:16:3e:00:01:03 > Sending on Socket/fallback > DHCPREQUEST on eth0 to 255.255.255.255 port 67 > DHCPREQUEST on eth0 to 255.255.255.255 port 67 > DHCPREQUEST on eth0 to 255.255.255.255 port 67 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 > No DHCPOFFERS received. > > ----> No peth0 in the bridge ... so we can''t have a network....After the startup - notice that vifl1.0 and xenbr0 recieves data, but> nothing is transmittedroot@judas:~# ifconfig> eth0 Link encap:Ethernet HWaddr 00:0E:A6:F9:95:61 > inet addr:10.13.15.50 Bcast:10.13.15.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:960 errors:0 dropped:0 overruns:0 frame:0 > TX packets:826 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:108668 (106.1 KiB) TX bytes:203020 (198.2 KiB) > Interrupt:17 Base address:0x6000 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:15 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:32 > RX bytes:3420 (3.3 KiB) TX bytes:0 (0.0 b) > > xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:15 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:3420 (3.3 KiB) TX bytes:0 (0.0 b) > > root@judas:~# brctl show > bridge name bridge id STP enabled interfaces > xenbr0 8000.feffffffffff no vif1.0 > > deamon.log: > Apr 15 17:17:44 judas logger: /etc/xen/scripts/block: add > XENBUS_PATH=backend/vbd/1/770 > Apr 15 17:17:44 judas logger: /etc/xen/scripts/block: add > XENBUS_PATH=backend/vbd/1/769 > Apr 15 17:17:45 judas logger: /etc/xen/scripts/vif-bridge: online > XENBUS_PATH=backend/vif/1/0 > Apr 15 17:17:45 judas logger: /etc/xen/scripts/block: Writing > backend/vbd/1/769/node /dev/loop0 to xenstore. > Apr 15 17:17:45 judas logger: /etc/xen/scripts/block: Writing > backend/vbd/1/769/physical-device 7:0 to xenstore. > Apr 15 17:17:45 judas logger: /etc/xen/scripts/block: Writing > backend/vbd/1/769/hotplug-status connected to xenstore. > Apr 15 17:17:45 judas logger: /etc/xen/scripts/vif-bridge: Successful > vif-bridge online for vif1.0, bridge xenbr0. > Apr 15 17:17:45 judas logger: /etc/xen/scripts/vif-bridge: Writing > backend/vif/1/0/hotplug-status connected to xenstore. > Apr 15 17:17:46 judas logger: /etc/xen/scripts/block: Writing > backend/vbd/1/770/node /dev/loop1 to xenstore. > Apr 15 17:17:46 judas logger: /etc/xen/scripts/block: Writing > backend/vbd/1/770/physical-device 7:1 to xenstore. > Apr 15 17:17:46 judas logger: /etc/xen/scripts/block: Writing > backend/vbd/1/770/hotplug-status connected to xenstore. > > messages: > Apr 15 17:16:14 judas dhcdbd: message_handler: message handler not found > under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason > Apr 15 17:16:14 judas dhcdbd: message_handler: message handler not found > under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason > Apr 15 17:16:16 judas dhcdbd: message_handler: message handler not found > under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name > Apr 15 17:16:16 judas dhcdbd: message_handler: message handler not found > under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.domain_name > Apr 15 17:16:16 judas dhcdbd: message_handler: message handler not found > under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain > Apr 15 17:16:16 judas dhcdbd: message_handler: message handler not found > under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers > Apr 15 17:16:17 judas kernel: Bridge firewalling registered > Apr 15 17:17:45 judas kernel: device vif1.0 entered promiscuous mode > Apr 15 17:17:45 judas kernel: ip_tables: (C) 2000-2006 Netfilter Core Team > Apr 15 17:17:49 judas kernel: xenbr0: port 1(vif1.0) entering learning > state > Apr 15 17:17:49 judas kernel: xenbr0: topology change detected, > propagating > Apr 15 17:17:49 judas kernel: xenbr0: port 1(vif1.0) entering forwarding > state > > xend-debug.log: > Xend started at Sun Apr 15 17:16:16 2007. > ifdown: interface eth0 not configured > SIOCSIFNAME: Device or resource busy > > > Somebady have found something???? > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- Benjamin HENRION Elève de 4eme année de l'' EXIA (Nancy) Ecole supérieure d''informatique Spé Réseaux _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Rene Purcell
2007-Apr-25 14:20 UTC
Re: [Xen-users] Debian 4.0, domU''s can not get network access
On 4/25/07, ben henrion <benjhenrion.xen@gmail.com> wrote:> > HI i'' ve tried xen 3.0.4 with etch 4.0 and ive exactly the same problem. > > > 2007/4/15, Nicolai Lang < nicolai@hjorth.com>: > > > > Hi all, > > > > I have installed a Debian 4.0 (newly released), compiled and installed > > Xen. > > All went as I am used to from Ubuntu. > > > > I created a new guest with Debian Etch debootstrap, and it boots without > > problems. But it can not fetch an IP address from my DHCP server > > (10.13.15.1). When I use TCPDump on xenbr0, it only shows the requets > > being > > transmitted but nothing is recieved. > > > > I hope I have included all relevant information below, and I hope > > someone > > can help me where to look for the cause. I have searched widely in the > > Wiki, > > google and mailinglist. > > > > Once I suceed, I will post an new article on the Wiki with a > > step-by-step > > guide to compiling and installing Xen from source on Debian 4.0. > > > > Thank you very much in advance > > > > Best regards > > Nicolai > > > > > > root@judas:~# ifconfig > > eth0 Link encap:Ethernet HWaddr 00:0E:A6:F9:95:61 > > inet addr: 10.13.15.50 Bcast:10.13.15.255 Mask:255.255.255.0 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:677 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:522 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:85879 (83.8 KiB) TX bytes:96248 (93.9 KiB) > > Interrupt:17 Base address:0x6000 > > > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask: 255.0.0.0 > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > > > xenbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > > > ---->We can just notice that when xend start, it don''t put the PETH0 and > > vif0.0 in the bridge Xenbr0, plus we can add that xend don''t creat > > PETH0 and vif0.0.... > > > > maybe a bug with ETCH 4.0..... > > > > > > root@judas:~# iptables -L > > Chain INPUT (policy ACCEPT) > > target prot opt source destination > > > > Chain FORWARD (policy ACCEPT) > > target prot opt source destination > > > > Chain OUTPUT (policy ACCEPT) > > target prot opt source destination > > root@judas:~# > > > > > > Console during startup: > > Setting up networking.... > > Configuring network interfaces...Internet Systems Consortium DHCP Client > > V3.0.4 > > Copyright 2004-2006 Internet Systems Consortium. > > All rights reserved. > > For info, please visit http://www.isc.org/sw/dhcp/ > > > > Listening on LPF/eth0/00:16:3e:00:01:03 > > Sending on LPF/eth0/00:16:3e:00:01:03 > > Sending on Socket/fallback > > DHCPREQUEST on eth0 to 255.255.255.255 port 67 > > DHCPREQUEST on eth0 to 255.255.255.255 port 67 > > DHCPREQUEST on eth0 to 255.255.255.255 port 67 > > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 > > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 > > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 > > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 > > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 > > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 > > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 > > No DHCPOFFERS received. > > > > ----> No peth0 in the bridge ... so we can''t have a network.... > > > > > After the startup - notice that vifl1.0 and xenbr0 recieves data, but > > nothing is transmitted > > > > > root@judas:~# ifconfig > > eth0 Link encap:Ethernet HWaddr 00:0E:A6:F9:95:61 > > inet addr:10.13.15.50 Bcast:10.13.15.255 Mask:255.255.255.0 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:960 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:826 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:108668 (106.1 KiB) TX bytes:203020 (198.2 KiB) > > Interrupt:17 Base address:0x6000 > > > > lo Link encap:Local Loopback > > inet addr: 127.0.0.1 Mask:255.0.0.0 > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > > > vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > > RX packets:15 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:32 > > RX bytes:3420 (3.3 KiB) TX bytes:0 (0.0 b) > > > > xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > > RX packets:15 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:3420 (3.3 KiB) TX bytes:0 (0.0 b) > > > > root@judas:~# brctl show > > bridge name bridge id STP enabled interfaces > > xenbr0 8000.feffffffffff no vif1.0 > > > > deamon.log: > > Apr 15 17:17:44 judas logger: /etc/xen/scripts/block: add > > XENBUS_PATH=backend/vbd/1/770 > > Apr 15 17:17:44 judas logger: /etc/xen/scripts/block: add > > XENBUS_PATH=backend/vbd/1/769 > > Apr 15 17:17:45 judas logger: /etc/xen/scripts/vif-bridge: online > > XENBUS_PATH=backend/vif/1/0 > > Apr 15 17:17:45 judas logger: /etc/xen/scripts/block: Writing > > backend/vbd/1/769/node /dev/loop0 to xenstore. > > Apr 15 17:17:45 judas logger: /etc/xen/scripts/block: Writing > > backend/vbd/1/769/physical-device 7:0 to xenstore. > > Apr 15 17:17:45 judas logger: /etc/xen/scripts/block: Writing > > backend/vbd/1/769/hotplug-status connected to xenstore. > > Apr 15 17:17:45 judas logger: /etc/xen/scripts/vif-bridge: Successful > > vif-bridge online for vif1.0, bridge xenbr0. > > Apr 15 17:17:45 judas logger: /etc/xen/scripts/vif-bridge: Writing > > backend/vif/1/0/hotplug-status connected to xenstore. > > Apr 15 17:17:46 judas logger: /etc/xen/scripts/block: Writing > > backend/vbd/1/770/node /dev/loop1 to xenstore. > > Apr 15 17:17:46 judas logger: /etc/xen/scripts/block: Writing > > backend/vbd/1/770/physical-device 7:1 to xenstore. > > Apr 15 17:17:46 judas logger: /etc/xen/scripts/block: Writing > > backend/vbd/1/770/hotplug-status connected to xenstore. > > > > messages: > > Apr 15 17:16:14 judas dhcdbd: message_handler: message handler not found > > under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason > > Apr 15 17:16:14 judas dhcdbd: message_handler: message handler not found > > > > under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason > > Apr 15 17:16:16 judas dhcdbd: message_handler: message handler not found > > under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name > > Apr 15 17:16:16 judas dhcdbd: message_handler: message handler not found > > > > under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.domain_name > > Apr 15 17:16:16 judas dhcdbd: message_handler: message handler not found > > under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain > > Apr 15 17:16:16 judas dhcdbd: message_handler: message handler not found > > > > under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers > > Apr 15 17:16:17 judas kernel: Bridge firewalling registered > > Apr 15 17:17:45 judas kernel: device vif1.0 entered promiscuous mode > > Apr 15 17:17:45 judas kernel: ip_tables: (C) 2000-2006 Netfilter Core > > Team > > Apr 15 17:17:49 judas kernel: xenbr0: port 1(vif1.0) entering learning > > state > > Apr 15 17:17:49 judas kernel: xenbr0: topology change detected, > > propagating > > Apr 15 17:17:49 judas kernel: xenbr0: port 1(vif1.0) entering forwarding > > > > state > > > > xend-debug.log: > > Xend started at Sun Apr 15 17:16:16 2007. > > ifdown: interface eth0 not configured > > SIOCSIFNAME: Device or resource busy > > > > > > Somebady have found something???? > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > > > > -- > Benjamin HENRION > Elève de 4eme année de l'' EXIA (Nancy) > Ecole supérieure d''informatique > Spé Réseaux > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >check your xend-config.sxp in /etc/xen and take a look at your network configuration.. try to replace (network-script network-dummy) with (network-script network-bridge) Hope it can help! -- René Jr Purcell Chargé de projet, sécurité et sytèmes Techno Centre Logiciels Libres, http://www.tc2l.ca/ Téléphone : (418) 681-2929 #124 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users