User Tools

Site Tools


virtualization:xenserver:xenserver_troubleshoot

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
virtualization:xenserver:xenserver_troubleshoot [2016/11/22 14:14]
gcooper
virtualization:xenserver:xenserver_troubleshoot [2019/04/30 06:34] (current)
gcooper
Line 21: Line 21:
 :!: You probably won't see the kernel panic (hang on boot) until **after installing SP1** (XenServer 6.2). :!: You probably won't see the kernel panic (hang on boot) until **after installing SP1** (XenServer 6.2).
  
-===== File System on Control Domain Full ===== +==== Check Disk Space ====
- +
-http://xenserver.org/component/easyblog/entry/xenserver-root-disk-maintenance.html?Itemid=179 +
- +
-Check disk space:+
  
 <file> <file>
Line 47: Line 43:
 rm -rf /root/* rm -rf /root/*
 </file> </file>
 +
 +===== File System on Control Domain Full =====
 +
 +https://support.citrix.com/article/CTX202821
 +
 +http://xenserver.org/component/easyblog/entry/xenserver-root-disk-maintenance.html?Itemid=179
 +
 +===== Detach a VHD from the Control Domain =====
 +
 +<note important>It is suggested to rename the REAL virtual disk so you DO NOT delete the wrong one!  Rename the real one because you can't rename the one connected to the control domain.  You can rename the REAL one back to the original name when you are done.</note>
 +
 +List out the VBD (connector object between VM and VDI) based on the VDI UUID:
 +
 +<file>
 +xe vdi-list | grep -B1 -A5 -i "part-of-vm-name"
 +
 +xe vdi-list name-label="<VDI-name-label>"
 +
 +xe vbd-list vdi-uuid=<UUID of VDI>
 +
 +</file>
 +<note important>Verify the VBD is the one connected to control domain!
 +</note>
 +
 +Once done, you want to first try to make VBD inactive (it may already be inactive),
 +
 +<file>
 +xe vbd-unplug uuid=<UUID of VBD>
 +</file>
 +
 +Once done, you can then break the connection:
 +
 +<file>
 +xe vbd-destroy uuid=<UUID of VBD>
 +</file>
 +
 +Check in XenCenter to verify and delete the virtual disk.
 +
 +===== Log Partition Full =====
  
 Delete rotated log files: Delete rotated log files:
Line 52: Line 87:
 <file> <file>
 find /var/log/ -type f -name *.gz -exec rm -f {} \; find /var/log/ -type f -name *.gz -exec rm -f {} \;
 +</file>
 +
 +Delete ''tapdisk'' log files:
 +
 +<file>
 +rm -f /var/log/blktap/*
 </file> </file>
  
Line 97: Line 138:
 This is a procedure to fix XenTools networking issues: This is a procedure to fix XenTools networking issues:
  
-  - Remove network adapter via XenCenter+  - Remove network interface via XenCenter
   - Uninstall all Citrix XenTools packages from Add/Remove Programs   - Uninstall all Citrix XenTools packages from Add/Remove Programs
   - Remove Citrix from filesystem and registry   - Remove Citrix from filesystem and registry
Line 110: Line 151:
   - Check things out and remove any 'ghosted' or hidden network adapters   - Check things out and remove any 'ghosted' or hidden network adapters
   - Reboot again   - Reboot again
-  - Add network adapter+  - Add network adapter in XenCenter
   - Reconfigure the networking until it works properly again   - Reconfigure the networking until it works properly again
   - Reboot   - Reboot
-  - Reinstall XenTools+  - Reinstall XenTools patiently
  
virtualization/xenserver/xenserver_troubleshoot.1479849246.txt.gz · Last modified: 2016/11/22 14:14 by gcooper