A mistake in sys admining on my part has caused a major malfunction. I created a domain called max01 and some where along the line I noticed that I deleted the host configuration file in /etc/xen/ YES a backup of /etc would be nice right now but, I do not have one. [root@xen02 ~]# ls -l /etc/xen/ total 92 drwxr-xr-x 2 root root 4096 2008-02-28 10:06 auto -rwxr-xr-x 1 root root 828 2008-02-28 10:04 qemu-ifup drwxr-xr-x 2 root root 4096 2008-05-31 21:27 scripts -rw-r--r-- 1 root root 8780 2008-02-28 10:04 xend-config.sxp -rw-r--r-- 1 root root 7001 2007-11-15 08:35 xend-config-xenapi.sxp -rw-r--r-- 1 root root 1256 2007-11-15 08:35 xend-pci-permissive.sxp -rw-r--r-- 1 root root 4129 2007-11-15 08:35 xend-pci-quirks.sxp -rw-r--r-- 1 root root 1545 2007-11-15 08:35 xm-config-xenapi.xml -rw-r--r-- 1 root root 1559 2007-11-15 08:35 xm-config.xml -rw-r--r-- 1 root root 6434 2007-11-15 08:35 xmexample1 -rw-r--r-- 1 root root 7725 2007-11-15 08:35 xmexample2 -rw-r--r-- 1 root root 7725 2007-11-15 08:35 xmexample.hvm -rw-r--r-- 1 root root 5473 2007-11-15 08:35 xmexample.vti I thought it should be trivial enough just look at a example on another machine. root@xen:~# less /etc/xen/lund01 name = "lund01" uuid = "9da5a5a1-58db-4b41-af55-76ab74f8f40c" total 92 drwxr-xr-x 2 root root 4096 2008-02-28 10:06 auto -rwxr-xr-x 1 root root 828 2008-02-28 10:04 qemu-ifup drwxr-xr-x 2 root root 4096 2008-05-31 21:27 scripts -rw-r--r-- 1 root root 8780 2008-02-28 10:04 xend-config.sxp -rw-r--r-- 1 root root 7001 2007-11-15 08:35 xend-config-xenapi.sxp -rw-r--r-- 1 root root 1256 2007-11-15 08:35 xend-pci-permissive.sxp -rw-r--r-- 1 root root 4129 2007-11-15 08:35 xend-pci-quirks.sxp -rw-r--r-- 1 root root 1545 2007-11-15 08:35 xm-config-xenapi.xml total 92 drwxr-xr-x 2 root root 4096 2008-02-28 10:06 auto -rwxr-xr-x 1 root root 828 2008-02-28 10:04 qemu-ifup drwxr-xr-x 2 root root 4096 2008-05-31 21:27 scripts -rw-r--r-- 1 root root 8780 2008-02-28 10:04 xend-config.sxp -rw-r--r-- 1 root root 7001 2007-11-15 08:35 xend-config-xenapi.sxp -rw-r--r-- 1 root root 1256 2007-11-15 08:35 xend-pci-permissive.sxp -rw-r--r-- 1 root root 4129 2007-11-15 08:35 xend-pci-quirks.sxp -rw-r--r-- 1 root root 1545 2007-11-15 08:35 xm-config-xenapi.xml maxmem = 256 memory = 256 vcpus = 1 builder = "hvm" kernel = "/usr/lib/xen/boot/hvmloader" boot = "c" pae = 1 acpi = 1 apic = 1 on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" device_model = "/usr/lib64/xen/bin/qemu-dm" sdl = 0 vnc = 1 vncunused = 1 disk = [ "file:/home/lundman/lund01,hda,w" ] vif = [ "mac=00:16:3e:5d:04:1c,bridge=xenbr0,type=ioemu" ] serial = "pty" It does not seem so difficult but where would I get the UUID info and VIF info? Other details: [root@xen02 ~]# uname -a Linux xen02.hugedesigns.net 2.6.21.7-3.fc8xen #1 SMP Thu Mar 20 14:58:12 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux AMD Phenom 9500 4GB DDR2 and 1Terabyte of disc space. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Erin Hughes <eredicatorx@hugedesigns.net> writes:> A mistake in sys admining on my part has caused a major malfunction. > > I created a domain called max01 and some where along the line I > noticed that I deleted the host configuration file in /etc/xen/ > YES a backup of /etc would be nice right now but, I do not have one.> vif = [ "mac=00:16:3e:5d:04:1c,bridge=xenbr0,type=ioemu" ]> It does not seem so difficult but where would I get the UUID info and > VIF info?First, if the box is still up, you can xm list -l domainname that will give you the old values. You can leave out the UUID completely. You can also leave out the mac=''...'' value from the vif and it will generate a mac address for you (every time you reboot, so you might want to pick a non-conflicting mac address) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Luke S Crawford wrote:> > First, if the box is still up, you can > > xm list -l domainname > > that will give you the old values. > >Yes it is! Sweet that is exactly what I needed ... I knew there had to be a command for it ...> You can leave out the UUID completely. > > You can also leave out the mac=''...'' value from the vif and it will generate > a mac address for you (every time you reboot, so you might want to pick a > non-conflicting mac address) >Cool I JUST rsynced my data back to this vm. I when I was wondering why it was so slow. I realized that it was only using 1 core and went to add the others to it and noticed ... it was gone. All fixed up now. Thanks. E./ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Wednesday 04 of June 2008 03:14:32 Luke S Crawford napisał(a):> Erin Hughes <eredicatorx@hugedesigns.net> writes: > > A mistake in sys admining on my part has caused a major malfunction. > > > > I created a domain called max01 and some where along the line I > > noticed that I deleted the host configuration file in /etc/xen/ > > YES a backup of /etc would be nice right now but, I do not have one. > > > > vif = [ "mac=00:16:3e:5d:04:1c,bridge=xenbr0,type=ioemu" ] > > > > > > It does not seem so difficult but where would I get the UUID info and > > VIF info? > > First, if the box is still up, you can > > xm list -l domainname > > that will give you the old values. > > > You can leave out the UUID completely. > > You can also leave out the mac=''...'' value from the vif and it will > generate a mac address for you (every time you reboot, so you might want to > pick a non-conflicting mac address) > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-usersHi, I have ubuntu in one of my domUs. It''s crucial to specify MAC when defining vifs. If the MAC is autoregenerated, ubuntu udev scripts recognize the vif as a different NIC and the NIC is named eth1. After subsequent reboots it is renamed to eth2, eth3, ... This way your vif does not use IP settings, you''ve defined for eth0, and your domU get inaccessible from the network. Similar things happen if your domU looks for vif''s IP settings in DHCP. So, if you have ubuntu, look into /etc/udev/rules.d/70-persistent-net.rules on it. If its down, you can safely mount its root partition (remember to unmount). Kind regards, -- Bartosz Lis @ Institute of Comp. Science, Technical University of Lodz, Poland bartoszl @ ics.p.lodz.pl _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users